)]}'
{"specs/mitaka/couchdb-replication.rst":[{"author":{"_account_id":17360,"name":"Ishita Mandhan","email":"imandha@us.ibm.com","username":"imandhan"},"change_message_id":"5db84c84b1d732e52ca2fdec564964f678231f65","unresolved":false,"context_lines":[{"line_number":86,"context_line":"users can create new databases. Once we have created a CouchDB replication set"},{"line_number":87,"context_line":"through Trove, new databases created this way(using Futon) cannot be included"},{"line_number":88,"context_line":"in the existing replication pattern. Users will have to manually trigger"},{"line_number":89,"context_line":"replication for these databases instead."},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"CouchDB does not have officially support any failover mechanism in cases of"},{"line_number":92,"context_line":"replication failure. Hence in this release we will not be implementing the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a7e1126_639a4870","line":89,"range":{"start_line":89,"start_character":39,"end_line":89,"end_character":40},"updated":"2015-12-21 20:00:26.000000000","message":"is there a workaround possible to this?","commit_id":"78147889c9069b880a32c9bdfb26de7e2ea24bcc"},{"author":{"_account_id":17360,"name":"Ishita Mandhan","email":"imandha@us.ibm.com","username":"imandhan"},"change_message_id":"5db84c84b1d732e52ca2fdec564964f678231f65","unresolved":false,"context_lines":[{"line_number":97,"context_line":""},{"line_number":98,"context_line":"To detach a replica from a replication set, we will first have to go to the"},{"line_number":99,"context_line":"source replica and cancel all existing replications with the replica that we"},{"line_number":100,"context_line":"want to detach."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"PROMOTE TO REPLICA SOURCE"},{"line_number":103,"context_line":"--------------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a7e1126_63ed68b6","line":100,"range":{"start_line":100,"start_character":14,"end_line":100,"end_character":15},"updated":"2015-12-21 20:00:26.000000000","message":"Will this process have to be repeated twice since two replication requests were initiated with switched source and targets?","commit_id":"78147889c9069b880a32c9bdfb26de7e2ea24bcc"},{"author":{"_account_id":17360,"name":"Ishita Mandhan","email":"imandha@us.ibm.com","username":"imandhan"},"change_message_id":"5db84c84b1d732e52ca2fdec564964f678231f65","unresolved":false,"context_lines":[{"line_number":177,"context_line":""},{"line_number":178,"context_line":"Since CouchDB doesn\u0027t support manual failover for replication, there is no"},{"line_number":179,"context_line":"obvious way to select a node to be a new master(to implement"},{"line_number":180,"context_line":"eject_replica_source). Each CouchDB database consist of one or more"},{"line_number":181,"context_line":"documents and each document has a revision id associated with it. One way"},{"line_number":182,"context_line":"to find out the next master node would be to compare the revision id of"},{"line_number":183,"context_line":"any random document between the different nodes and pick the one with"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a7e1126_a6391ed9","line":180,"range":{"start_line":180,"start_character":45,"end_line":180,"end_character":52},"updated":"2015-12-21 20:00:26.000000000","message":"consists","commit_id":"78147889c9069b880a32c9bdfb26de7e2ea24bcc"},{"author":{"_account_id":4240,"name":"Craig Vyvial","email":"cp16net@gmail.com","username":"cp16net"},"change_message_id":"2786a868b2b23a880f3c448d12211b44cb2d4458","unresolved":false,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"Launchpad Blueprint:"},{"line_number":41,"context_line":"https://blueprints.launchpad.net/trove/+spec/name-of-blueprint"},{"line_number":42,"context_line":""},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"Problem Description"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5a5ae5dd_2bc56b8d","line":41,"updated":"2016-02-10 19:29:52.000000000","message":"link the bp here","commit_id":"285587cecb84aa02805201424c8aa34241372c3d"},{"author":{"_account_id":4240,"name":"Craig Vyvial","email":"cp16net@gmail.com","username":"cp16net"},"change_message_id":"bedd9e9f1196b91c51c0c0289cd401f27eba112a","unresolved":false,"context_lines":[{"line_number":197,"context_line":"Milestones"},{"line_number":198,"context_line":"----------"},{"line_number":199,"context_line":""},{"line_number":200,"context_line":"Mitaka"},{"line_number":201,"context_line":""},{"line_number":202,"context_line":"Work Items"},{"line_number":203,"context_line":"----------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a57f1b5_944794bb","line":200,"updated":"2016-02-11 16:36:54.000000000","message":"Netwon","commit_id":"285587cecb84aa02805201424c8aa34241372c3d"},{"author":{"_account_id":6413,"name":"Victoria Martinez de la Cruz","email":"victoria@redhat.com","username":"vkmc"},"change_message_id":"5fdba1eb725974ee9f9f0a588c113bff50f388be","unresolved":false,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"Launchpad Blueprint:"},{"line_number":41,"context_line":"https://blueprints.launchpad.net/trove/+spec/name-of-blueprint"},{"line_number":42,"context_line":""},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"Problem Description"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dae33548_383b0b9e","line":41,"updated":"2016-02-16 22:22:28.000000000","message":"NIT. https://blueprints.launchpad.net/trove/+spec/couchdb-replication","commit_id":"43ec1d7afc93d7763831394c82b9263d902cbedc"},{"author":{"_account_id":6413,"name":"Victoria Martinez de la Cruz","email":"victoria@redhat.com","username":"vkmc"},"change_message_id":"5fdba1eb725974ee9f9f0a588c113bff50f388be","unresolved":false,"context_lines":[{"line_number":45,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Even though CouchDB is a supported datastore in Trove, CouchDB replication"},{"line_number":48,"context_line":"hasn\u0027t been implemented in Trove. This spec addresses how this feature can"},{"line_number":49,"context_line":"be implemented in Trove."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Proposed Change"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dae33548_5806cfce","line":48,"updated":"2016-02-16 22:22:28.000000000","message":"NIT. s/Trove/yet","commit_id":"43ec1d7afc93d7763831394c82b9263d902cbedc"},{"author":{"_account_id":6413,"name":"Victoria Martinez de la Cruz","email":"victoria@redhat.com","username":"vkmc"},"change_message_id":"5fdba1eb725974ee9f9f0a588c113bff50f388be","unresolved":false,"context_lines":[{"line_number":82,"context_line":"will have to trigger bi-directional continuous replication for each database on"},{"line_number":83,"context_line":"the source instance with every replica."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"NOTE: CouchDB provides an administration console called Futon through which"},{"line_number":86,"context_line":"users can create new databases. Once we have created a CouchDB replication set"},{"line_number":87,"context_line":"through Trove, new databases created this way(using Futon) cannot be included"},{"line_number":88,"context_line":"in the existing replication pattern. Users will have to manually trigger"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dae33548_b8d71bbe","line":85,"updated":"2016-02-16 22:22:28.000000000","message":"Consider how we handle replication for other datastores, wouldn\u0027t it be wise to trigger replication for the added datastores not included in the existing replica-sets after, say, some time? Like a chron op. I\u0027m a bit concerned that the way we see replication right now is not as granular as CouchDB sees it. Maybe we can change how we manage replication to add more flexibility for this cases.","commit_id":"43ec1d7afc93d7763831394c82b9263d902cbedc"},{"author":{"_account_id":6413,"name":"Victoria Martinez de la Cruz","email":"victoria@redhat.com","username":"vkmc"},"change_message_id":"5fdba1eb725974ee9f9f0a588c113bff50f388be","unresolved":false,"context_lines":[{"line_number":95,"context_line":"DETACH REPLICA"},{"line_number":96,"context_line":"----------------"},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"To detach a replica from a replication set, we will first have to go to the"},{"line_number":99,"context_line":"source replica and cancel all existing replications with the replica that we"},{"line_number":100,"context_line":"want to detach. We also need to cancel the replications from the replica that"},{"line_number":101,"context_line":"is being detached."}],"source_content_type":"text/x-rst","patch_set":4,"id":"dae33548_4cef3087","line":98,"updated":"2016-02-16 22:22:28.000000000","message":"This in case of master-master replication right? In case of pull/push replication you are ok with simply cancelling replication from one side?","commit_id":"43ec1d7afc93d7763831394c82b9263d902cbedc"},{"author":{"_account_id":6413,"name":"Victoria Martinez de la Cruz","email":"victoria@redhat.com","username":"vkmc"},"change_message_id":"5fdba1eb725974ee9f9f0a588c113bff50f388be","unresolved":false,"context_lines":[{"line_number":169,"context_line":"Alternatives"},{"line_number":170,"context_line":"------------"},{"line_number":171,"context_line":"As mentioned above, CouchDB replication works only on a per database level."},{"line_number":172,"context_line":"Based on the conversations I have had with the CouchDB folks, the new"},{"line_number":173,"context_line":"clustering API will provide copies of all databases among different"},{"line_number":174,"context_line":"instances. (In CouchDB 2.0, it will maintain 3 copies of all databases -"},{"line_number":175,"context_line":"we can configure the number of copies/instances up and down). The above"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dae33548_ec8f24ca","line":172,"updated":"2016-02-16 22:22:28.000000000","message":"NIT. I\u0027d remove this line and simply say \"The new clustering API,...\" and specify which version you are talking about in comparison with which other version.","commit_id":"43ec1d7afc93d7763831394c82b9263d902cbedc"},{"author":{"_account_id":6413,"name":"Victoria Martinez de la Cruz","email":"victoria@redhat.com","username":"vkmc"},"change_message_id":"5fdba1eb725974ee9f9f0a588c113bff50f388be","unresolved":false,"context_lines":[{"line_number":174,"context_line":"instances. (In CouchDB 2.0, it will maintain 3 copies of all databases -"},{"line_number":175,"context_line":"we can configure the number of copies/instances up and down). The above"},{"line_number":176,"context_line":"mentioned method works best if nodes are located close together. Otherwise"},{"line_number":177,"context_line":"a replication based system is recommended."},{"line_number":178,"context_line":""},{"line_number":179,"context_line":"Since CouchDB doesn\u0027t support manual failover for replication, there is no"},{"line_number":180,"context_line":"obvious way to select a node to be a new master(to implement"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dae33548_8fff6a66","line":177,"updated":"2016-02-16 22:22:28.000000000","message":"What do you mean with replication based system?","commit_id":"43ec1d7afc93d7763831394c82b9263d902cbedc"}]}
