Please note: This schedule is for OpenStack Active Technical Contributors participating in the Icehouse Design Summit sessions in Hong Kong. These are working sessions to determine the roadmap of the Icehouse release and make decisions across the project. To see the full OpenStack Summit schedule, including presentations, panels and workshops, go to http://openstacksummitnovember2013.sched.org.
So you can change it! 4 replica clusters are the bee's knees - or are they?
In preparation for this session I will simulate failures on multi-node Swift deployments running 2, 3 and 4 replica rings and see where things break. I'd like to crunch some numbers and get laughed at for my naive arithmetic while attempting to explain how Swift's quorum calculation affect durability and availability when using different replica counts.
The goal of this session would be a public documentation of the current expected behavior which we can point to in defense when triaging bugs like "I have a two disk, two replica swift and if I unplug it I can't upload my lolcats".
I'm also open to the possibility of learning where it might make sense to propose changes (or a more tunable configuration - if there is no single obviously correct behavior) for valid use-cases that the Swift community *wants* to support. So I'll need you to come prepared to tell me what we think is reasonable.
