)]}'
{"doc/source/container.rst":[{"author":{"_account_id":7233,"name":"Matthew Oliver","email":"matt@oliver.net.au","username":"mattoliverau"},"change_message_id":"457833b501867c7d3ac0898db7589c68a12dc111","unresolved":false,"context_lines":[{"line_number":44,"context_line":"    :undoc-members:"},{"line_number":45,"context_line":"    :show-inheritance:"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":".. _container-reconciler:"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"Container Reconciler"},{"line_number":50,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":51,"context_line":""},{"line_number":52,"context_line":".. automodule:: swift.container.reconciler"},{"line_number":53,"context_line":"    :members:"},{"line_number":54,"context_line":"    :undoc-members:"},{"line_number":55,"context_line":"    :show-inheritance:"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":".. _container-sharder:"},{"line_number":58,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5f7c97a3_18cf3380","line":55,"range":{"start_line":47,"start_character":0,"end_line":55,"end_character":22},"updated":"2018-05-04 08:01:34.000000000","message":"If these are supposed to be in alphabetical order, this is in the wrong spot.\n\nI\u0027ll look at moving it as I update the images.","commit_id":"057396496e62c37e32672124ed0f919b2bb69e3c"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"c680e0d83be654008754c2307227af9711497e2f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":14,"id":"5f7c97a3_9979ff30","updated":"2018-05-17 23:48:48.000000000","message":"This may have been better in the parent patch.","commit_id":"60ae7db88708546f64dec356b631a44243af33d6"}],"doc/source/overview_architecture.rst":[{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"c680e0d83be654008754c2307227af9711497e2f","unresolved":false,"context_lines":[{"line_number":131,"context_line":"container. The listings are stored as sqlite database files, and replicated"},{"line_number":132,"context_line":"across the cluster similar to how objects are. Statistics are also tracked"},{"line_number":133,"context_line":"that include the total number of objects, and total storage usage for that"},{"line_number":134,"context_line":"container."},{"line_number":135,"context_line":""},{"line_number":136,"context_line":"--------------"},{"line_number":137,"context_line":"Account Server"}],"source_content_type":"text/x-rst","patch_set":14,"id":"5f7c97a3_b982bbff","line":134,"updated":"2018-05-17 23:48:48.000000000","message":"I wonder if this deserves some expansion now...","commit_id":"60ae7db88708546f64dec356b631a44243af33d6"}],"doc/source/overview_container_sharding.rst":[{"author":{"_account_id":7233,"name":"Matthew Oliver","email":"matt@oliver.net.au","username":"mattoliverau"},"change_message_id":"457833b501867c7d3ac0898db7589c68a12dc111","unresolved":false,"context_lines":[{"line_number":249,"context_line":""},{"line_number":250,"context_line":"    account_autocreate \u003d True"},{"line_number":251,"context_line":""},{"line_number":252,"context_line":"in the ``[proxy-server]`` section."},{"line_number":253,"context_line":""},{"line_number":254,"context_line":"A container database may require several visits by the ``container-sharder``"},{"line_number":255,"context_line":"daemon before it is fully sharded. On each visit the ``container-sharder``"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5f7c97a3_18a2d39b","line":252,"updated":"2018-05-04 08:01:34.000000000","message":"because of the above line, would people get confused and thing the cleave_batch_size should live in the [proxy-server] section?","commit_id":"057396496e62c37e32672124ed0f919b2bb69e3c"},{"author":{"_account_id":7233,"name":"Matthew Oliver","email":"matt@oliver.net.au","username":"mattoliverau"},"change_message_id":"457833b501867c7d3ac0898db7589c68a12dc111","unresolved":false,"context_lines":[{"line_number":254,"context_line":"A container database may require several visits by the ``container-sharder``"},{"line_number":255,"context_line":"daemon before it is fully sharded. On each visit the ``container-sharder``"},{"line_number":256,"context_line":"daemon will move a subset of object records to new shard containers by cleaving"},{"line_number":257,"context_line":"new shard container databases from the original. By default, two shard are"},{"line_number":258,"context_line":"processed per visit; this number may be configured by the ``cleave_batch_size``"},{"line_number":259,"context_line":"option."},{"line_number":260,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5f7c97a3_58984b69","line":257,"range":{"start_line":257,"start_character":65,"end_line":257,"end_character":70},"updated":"2018-05-04 08:01:34.000000000","message":"shards - I\u0027ll correct this when I push, but noting so I remember :)","commit_id":"057396496e62c37e32672124ed0f919b2bb69e3c"},{"author":{"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},"change_message_id":"4c35ade535e7c561f3b3bbd32671dea6bf74ecb3","unresolved":false,"context_lines":[{"line_number":86,"context_line":"containers are included in the ``sharding_candidate`` data."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":""},{"line_number":89,"context_line":".. _swift_manage_shard_ranges:"},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"``swift-manage-shard-ranges`` CLI tool"},{"line_number":92,"context_line":"--------------------------------------"}],"source_content_type":"text/x-rst","patch_set":13,"id":"5f7c97a3_d7a67754","line":89,"updated":"2018-05-17 10:19:39.000000000","message":"I thought it might be nice to have the CLI tool docs in the module then include to here via automodule. That is because I took a time to look for the docs when reviewing swift-manage-shard-ranges, then reached to here.\n\nBut it\u0027s okay to leave for now, then do it in follow up.","commit_id":"8b11b8231e1ced698b5878623774cb08a94dfccb"},{"author":{"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},"change_message_id":"4c35ade535e7c561f3b3bbd32671dea6bf74ecb3","unresolved":false,"context_lines":[{"line_number":99,"context_line":""},{"line_number":100,"context_line":"    ``swift-manage-shard-ranges`` must only be used on one replica of a"},{"line_number":101,"context_line":"    container database to avoid inconsistent results. The modifications made by"},{"line_number":102,"context_line":"    ``swift_manage_shard_ranges`` will be automatically copied to other"},{"line_number":103,"context_line":"    replicas of the container database via normal replication processes."},{"line_number":104,"context_line":""},{"line_number":105,"context_line":"There are three steps in the process of initiating sharding, each of which may"}],"source_content_type":"text/x-rst","patch_set":13,"id":"5f7c97a3_12495d31","line":102,"range":{"start_line":102,"start_character":6,"end_line":102,"end_character":31},"updated":"2018-05-17 10:19:39.000000000","message":"nits) the mixture of usage of both underscore and dash (i.e. swift-manage-shard-ranges and swift_manage-shard_ranges) confuses readers. it looks like both are same meaning so we should change the underscore here to dash. And same thing at Line 60.","commit_id":"8b11b8231e1ced698b5878623774cb08a94dfccb"},{"author":{"_account_id":7847,"name":"Alistair Coles","email":"alistairncoles@gmail.com","username":"acoles"},"change_message_id":"38001249dd3a927dbd0f9170846d1b683666865a","unresolved":false,"context_lines":[{"line_number":99,"context_line":""},{"line_number":100,"context_line":"    ``swift-manage-shard-ranges`` must only be used on one replica of a"},{"line_number":101,"context_line":"    container database to avoid inconsistent results. The modifications made by"},{"line_number":102,"context_line":"    ``swift_manage_shard_ranges`` will be automatically copied to other"},{"line_number":103,"context_line":"    replicas of the container database via normal replication processes."},{"line_number":104,"context_line":""},{"line_number":105,"context_line":"There are three steps in the process of initiating sharding, each of which may"}],"source_content_type":"text/x-rst","patch_set":13,"id":"5f7c97a3_c77301b1","line":102,"range":{"start_line":102,"start_character":6,"end_line":102,"end_character":31},"in_reply_to":"5f7c97a3_12495d31","updated":"2018-05-18 17:55:12.000000000","message":"it\u0027s a bug, thanks.","commit_id":"8b11b8231e1ced698b5878623774cb08a94dfccb"},{"author":{"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},"change_message_id":"4c35ade535e7c561f3b3bbd32671dea6bf74ecb3","unresolved":false,"context_lines":[{"line_number":101,"context_line":"    container database to avoid inconsistent results. The modifications made by"},{"line_number":102,"context_line":"    ``swift_manage_shard_ranges`` will be automatically copied to other"},{"line_number":103,"context_line":"    replicas of the container database via normal replication processes."},{"line_number":104,"context_line":""},{"line_number":105,"context_line":"There are three steps in the process of initiating sharding, each of which may"},{"line_number":106,"context_line":"be performed in isolation or, as shown below, using a single command."},{"line_number":107,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"5f7c97a3_03ad8de9","line":104,"updated":"2018-05-17 10:19:39.000000000","message":"I\u0027m not sure I understand correctly so please fix my thought if it\u0027s wrong.\n\nI think a normal container db -\u003e a sharding db is one-way. Therefore no way to get back to disable container sharding, correct? I think it\u0027s ok as a constraint of this staff but I prefer to write down the note (here or somewhere suitable) to prevent unfortunate accident to enable the sharding. And I\u0027d see docs about the shard ranges modification chance too. It looks like BEFORE enabling the sharding, we can re-do on replace, delete the shard range (e.g. row_size) until it become as users want. However, how about, after enabling the sharding? At L206, it suggests find, replace, and enable at once. Is it a painful command if the shard ranges is not being desirable one for the user?","commit_id":"8b11b8231e1ced698b5878623774cb08a94dfccb"},{"author":{"_account_id":7847,"name":"Alistair Coles","email":"alistairncoles@gmail.com","username":"acoles"},"change_message_id":"38001249dd3a927dbd0f9170846d1b683666865a","unresolved":false,"context_lines":[{"line_number":101,"context_line":"    container database to avoid inconsistent results. The modifications made by"},{"line_number":102,"context_line":"    ``swift_manage_shard_ranges`` will be automatically copied to other"},{"line_number":103,"context_line":"    replicas of the container database via normal replication processes."},{"line_number":104,"context_line":""},{"line_number":105,"context_line":"There are three steps in the process of initiating sharding, each of which may"},{"line_number":106,"context_line":"be performed in isolation or, as shown below, using a single command."},{"line_number":107,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"5f7c97a3_472a9190","line":104,"in_reply_to":"5f7c97a3_03ad8de9","updated":"2018-05-18 17:55:12.000000000","message":"Done","commit_id":"8b11b8231e1ced698b5878623774cb08a94dfccb"},{"author":{"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},"change_message_id":"4c35ade535e7c561f3b3bbd32671dea6bf74ecb3","unresolved":false,"context_lines":[{"line_number":211,"context_line":"    Injected 7 shard ranges."},{"line_number":212,"context_line":"    Run container-replicator to replicate them to other nodes."},{"line_number":213,"context_line":"    Container moved to state \u0027sharding\u0027 with epoch 1525345669.46153."},{"line_number":214,"context_line":"    Run container-sharder on all nodes to shard the container."},{"line_number":215,"context_line":""},{"line_number":216,"context_line":".. _sharder_daemon:"},{"line_number":217,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"5f7c97a3_68ed3e8a","line":214,"updated":"2018-05-17 10:19:39.000000000","message":"If I didn\u0027t miss, no docs found about existing `delete` subcommand.","commit_id":"8b11b8231e1ced698b5878623774cb08a94dfccb"},{"author":{"_account_id":7847,"name":"Alistair Coles","email":"alistairncoles@gmail.com","username":"acoles"},"change_message_id":"38001249dd3a927dbd0f9170846d1b683666865a","unresolved":false,"context_lines":[{"line_number":211,"context_line":"    Injected 7 shard ranges."},{"line_number":212,"context_line":"    Run container-replicator to replicate them to other nodes."},{"line_number":213,"context_line":"    Container moved to state \u0027sharding\u0027 with epoch 1525345669.46153."},{"line_number":214,"context_line":"    Run container-sharder on all nodes to shard the container."},{"line_number":215,"context_line":""},{"line_number":216,"context_line":".. _sharder_daemon:"},{"line_number":217,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"5f7c97a3_4755b11c","line":214,"in_reply_to":"5f7c97a3_68ed3e8a","updated":"2018-05-18 17:55:12.000000000","message":"Done","commit_id":"8b11b8231e1ced698b5878623774cb08a94dfccb"},{"author":{"_account_id":597,"name":"Pete Zaitcev","email":"zaitcev@kotori.zaitcev.us","username":"zaitcev"},"change_message_id":"83e4ad74a6d84ef8f06600720a02de1e978f7146","unresolved":false,"context_lines":[{"line_number":359,"context_line":"Shard range        A range of the object namespace defined by a lower"},{"line_number":360,"context_line":"                   bound and and upper bound."},{"line_number":361,"context_line":"Shard container    A container that holds object records for a shard"},{"line_number":362,"context_line":"                   range. Shard containers exist a hidden account"},{"line_number":363,"context_line":"                   mirroring the user\u0027s account."},{"line_number":364,"context_line":"Misplaced objects  Items that don\u0027t belong in a container\u0027s shard"},{"line_number":365,"context_line":"                   range. These will be moved to their correct"}],"source_content_type":"text/x-rst","patch_set":15,"id":"5f7c97a3_61d77425","line":362,"updated":"2018-05-19 01:56:33.000000000","message":"\"exist _in_ a hidden account\"","commit_id":"5c5b08d0472f695a0d81655ab80725f1be08d308"},{"author":{"_account_id":597,"name":"Pete Zaitcev","email":"zaitcev@kotori.zaitcev.us","username":"zaitcev"},"change_message_id":"83e4ad74a6d84ef8f06600720a02de1e978f7146","unresolved":false,"context_lines":[{"line_number":436,"context_line":"``.shards_``, and ``c`` is a container name that is derived from the original"},{"line_number":437,"context_line":"container and includes the index of the shard range. The final container name"},{"line_number":438,"context_line":"for the shard range uses the pattern of ``{original contianer name}-{hash of"},{"line_number":439,"context_line":"parent container}-{timestamp}-{shard index}``."},{"line_number":440,"context_line":""},{"line_number":441,"context_line":"The ``enable`` sub-command then creates some final state required to initiate"},{"line_number":442,"context_line":"sharding the container, including a special shard range record referred to as"}],"source_content_type":"text/x-rst","patch_set":15,"id":"5f7c97a3_f0b4aff4","line":439,"updated":"2018-05-19 01:56:33.000000000","message":"What is \"parent container\"?\nIf hash of \"parent container\" is included, and is stable, why is the name of the original container included? Is there a risk of sharding to become impossible if the name of the original container is so long that the rest of the generated name cannot fit into permissible size?","commit_id":"5c5b08d0472f695a0d81655ab80725f1be08d308"},{"author":{"_account_id":7847,"name":"Alistair Coles","email":"alistairncoles@gmail.com","username":"acoles"},"change_message_id":"cac218996fe1e781ac1101809646633c3ff287ee","unresolved":false,"context_lines":[{"line_number":436,"context_line":"``.shards_``, and ``c`` is a container name that is derived from the original"},{"line_number":437,"context_line":"container and includes the index of the shard range. The final container name"},{"line_number":438,"context_line":"for the shard range uses the pattern of ``{original contianer name}-{hash of"},{"line_number":439,"context_line":"parent container}-{timestamp}-{shard index}``."},{"line_number":440,"context_line":""},{"line_number":441,"context_line":"The ``enable`` sub-command then creates some final state required to initiate"},{"line_number":442,"context_line":"sharding the container, including a special shard range record referred to as"}],"source_content_type":"text/x-rst","patch_set":15,"id":"5f7c97a3_4924ccc6","line":439,"in_reply_to":"5f7c97a3_f0b4aff4","updated":"2018-05-21 10:38:06.000000000","message":"The parent is the container from which a shard has been cleaved. For the first sharding operation this is the same as the root container. When a shard container is sharded, the parent is the sharding shard, and is then different from the root.\n\nThe name of the original container is included to assist with identifying shard container relationships when listing the .shards_ account.\n\nHidden container names can be twice the length of a user container name (since https://review.openstack.org/#/c/465776/) which allows sufficient length for the sharc ontainers suffix.","commit_id":"5c5b08d0472f695a0d81655ab80725f1be08d308"},{"author":{"_account_id":597,"name":"Pete Zaitcev","email":"zaitcev@kotori.zaitcev.us","username":"zaitcev"},"change_message_id":"83e4ad74a6d84ef8f06600720a02de1e978f7146","unresolved":false,"context_lines":[{"line_number":475,"context_line":"  container have been cleaved."},{"line_number":476,"context_line":"* SHRINKING: the shard range has been enabled for shrinking; or"},{"line_number":477,"context_line":"* SHARDING: the shard range has been enabled for sharding."},{"line_number":478,"context_line":"* SHARDED: the shard range has completed sharding or shrinking."},{"line_number":479,"context_line":""},{"line_number":480,"context_line":"..note::"},{"line_number":481,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"5f7c97a3_b020774b","line":478,"updated":"2018-05-19 01:56:33.000000000","message":"I do not understand the difference between ACTIVE and SHARDED.","commit_id":"5c5b08d0472f695a0d81655ab80725f1be08d308"},{"author":{"_account_id":7847,"name":"Alistair Coles","email":"alistairncoles@gmail.com","username":"acoles"},"change_message_id":"cac218996fe1e781ac1101809646633c3ff287ee","unresolved":false,"context_lines":[{"line_number":475,"context_line":"  container have been cleaved."},{"line_number":476,"context_line":"* SHRINKING: the shard range has been enabled for shrinking; or"},{"line_number":477,"context_line":"* SHARDING: the shard range has been enabled for sharding."},{"line_number":478,"context_line":"* SHARDED: the shard range has completed sharding or shrinking."},{"line_number":479,"context_line":""},{"line_number":480,"context_line":"..note::"},{"line_number":481,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"5f7c97a3_bc9a80c2","line":478,"in_reply_to":"5f7c97a3_b020774b","updated":"2018-05-21 10:38:06.000000000","message":"A sharded container\u0027s shard range will be in state SHARDED. It\u0027s constituent shard ranges will be in state ACTIVE. If on eof the latter requires sharding, it will progress from ACTIVE to SHARDED.\n\nI\u0027ll try to clarify in a patch.","commit_id":"5c5b08d0472f695a0d81655ab80725f1be08d308"}],"tox.ini":[{"author":{"_account_id":7233,"name":"Matthew Oliver","email":"matt@oliver.net.au","username":"mattoliverau"},"change_message_id":"808be15ad05916e0a9129e45c9cba1a950196fee","unresolved":false,"context_lines":[{"line_number":97,"context_line":"[testenv:docs]"},{"line_number":98,"context_line":"basepython \u003d python2.7"},{"line_number":99,"context_line":"deps \u003d -r{toxinidir}/doc/requirements.txt"},{"line_number":100,"context_line":"commands \u003d sphinx-build -W -b html doc/source doc/build/html"},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"[testenv:api-ref]"},{"line_number":103,"context_line":"# This environment is called from CI scripts to test and publish"}],"source_content_type":"text/x-properties","patch_set":2,"id":"5f7c97a3_89574403","line":100,"range":{"start_line":100,"start_character":24,"end_line":100,"end_character":26},"updated":"2018-05-08 03:23:14.000000000","message":"opps I accidentally removed the -W because of the building issues. This should probably be put back.","commit_id":"057396496e62c37e32672124ed0f919b2bb69e3c"}]}
