Jump to: navigation, search

Difference between revisions of "Meetings/Swift"

(529 intermediate revisions by 28 users not shown)
Line 1: Line 1:
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
| '''Meeting Time''' || Every Wednesday at 21:00 UTC in #openstack-meeting
+
! '''2100 UTC Meeting'''
 
|-
 
|-
| '''Meeting Logs''' || http://eavesdrop.openstack.org/meetings/swift/2016/
+
| '''Next meeting:''' January 20th, 2021
 
|-
 
|-
| '''Chair''' || notmyname
+
| '''Chair:''' timburke
 +
|-
 +
|
 +
<!-- List 2100UTC meeting items below here -->
 +
* Reconciler/EC/encryption interactions
 +
** https://bugs.launchpad.net/swift/+bug/1910804
 +
** https://review.opendev.org/c/openstack/swift/+/770522
 +
* SSYNC and non-durable frags
 +
** https://bugs.launchpad.net/swift/+bug/1778002
 +
** https://review.opendev.org/c/openstack/swift/+/770047
 +
* Cleaning up shards when root DB is deleted and reclaimed
 +
** https://bugs.launchpad.net/swift/+bug/1911232
 +
** https://review.opendev.org/c/openstack/swift/+/770529
 +
* Relinker issues
 +
** https://bugs.launchpad.net/swift/+bug/1910589 - Multiple part power increases leads to misplaced data
 +
*** https://review.opendev.org/c/openstack/swift/+/769855
 +
** https://bugs.launchpad.net/swift/+bug/1910470 - swift-object-relinker does not handle unmounted disks well
 +
*** https://review.opendev.org/c/openstack/swift/+/769632
 +
<!--
 +
** jerasure support in pyeclib/libec
 +
-->
 +
<!-- End 2100UTC meeting items -->
 
|}
 
|}
  
'''Agenda: January 20, 2016 2100 UTC'''
+
{| class="wikitable"
 
+
|-
* Patches
+
| '''Meeting Logs''' || http://eavesdrop.openstack.org/meetings/swift/2021/
** Change schedule priority of daemon/server in config - https://review.openstack.org/#/c/238799/ [peterlisak? onovy?]
+
|-
*** 2 big questions in the review comments
+
|'''Useful Commands'''|| #link #info #agreed #topic and #startmeeting
**** Does setting ionice actually improve anything? Swift's processes are rather interconnected, so it's very difficult to isolate a logical API operation by process. eg nice'ing the container server would impact object PUTs since the container is updated as part of the object write.
+
|}
**** Should we even be doing this in Swift itself instead of distro init scripts. On the one hand, the ionice priority "code" has to be rewritten for every distro. On the other, ops know ionice and how/when to use it and does that actually belong in Swift? If it does, why not other ops/management tools?
 
 
 
* I would like to discuss about below patches with following summary - http://paste.openstack.org/show/484089/ [ho]
 
** Fix posting accounts behavior when half of account servers downed - https://review.openstack.org/#/c/266190/
 
** Fix posting containers behavior when half of container servers downed - https://review.openstack.org/#/c/266193/
 
** Fix deleting containers behavior when half of container servers downed - https://review.openstack.org/#/c/266199/
 
** Fix 404 in container PUT when the majority of the accounts are missing
 
  
 +
----
  
 
When adding an item, please include your IRC nickname with it.
 
When adding an item, please include your IRC nickname with it.
 
  
 
----
 
----
  
 
[[Category:ObjectStorage]]
 
[[Category:ObjectStorage]]

Revision as of 20:35, 20 January 2021

2100 UTC Meeting
Next meeting: January 20th, 2021
Chair: timburke
Meeting Logs http://eavesdrop.openstack.org/meetings/swift/2021/
Useful Commands #link #info #agreed #topic and #startmeeting

When adding an item, please include your IRC nickname with it.