)]}'
{"swift/cli/ringbuilder.py":[{"author":{"_account_id":6968,"name":"Christian Schwede","email":"cschwede@nvidia.com","username":"cschwede"},"change_message_id":"bf021a5600d19561a4224a41824a485838847226","unresolved":false,"context_lines":[{"line_number":1039,"context_line":"    *****************************"},{"line_number":1040,"context_line":""},{"line_number":1041,"context_line":"    If you run this command and deploy rebalanced rings before a replication"},{"line_number":1042,"context_line":"    pass completes, you may introduce unavailability in your cluster. This"},{"line_number":1043,"context_line":"    has an end-user impact."},{"line_number":1044,"context_line":"        \"\"\""},{"line_number":1045,"context_line":"        builder.pretend_min_part_hours_passed()"}],"source_content_type":"text/x-python","patch_set":1,"id":"5a710552_8679fcfe","line":1042,"updated":"2015-12-15 09:49:27.000000000","message":"This sounds like data would get lost, but in fact it\u0027s \"only\" unavailable until the next replication run finished on all nodes (though this might take a long time). Maybe make this more clear?\n\nAnyways, it works for me, and anyone interested in this option should know what happens, at least after the big warning above.","commit_id":"40476ea0797690d3a90a9ed91906d26103dfa058"}]}