Clay Gerrard b19dc1ddec Always fix devices with multiple part-replica assignments ... I've found that given a sufficiently bad replica2part2dev table we can accidently not entirely fix palcement when more than two replicas of a part are assigned to the duplicate devices. It shows up most on > 3 replica rings when you have two *different* devices both holding two replicas. But you can see it on a three replica ring when all three replicas are assigned to the same device. Change-Id: Ieb213c1a259815a2ed657291242919cda568c7b5		2016-02-01 16:19:08 -08:00
..
__init__.py	Initial commit of Swift code	2010-07-12 17:03:45 -05:00
test_builder.py	Always fix devices with multiple part-replica assignments	2016-02-01 16:19:08 -08:00
test_ring.py	Merge "add test for zero weight region get_more_nodes"	2016-01-28 12:50:58 +00:00
test_utils.py	Put part-replicas where they go	2015-12-07 16:06:42 -08:00