You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2020/01/04 22:17:05 UTC

[GitHub] [couchdb] nickva opened a new pull request #2396: Lock shard splitting targets during the initial copy phase

nickva opened a new pull request #2396: Lock shard splitting targets during the initial copy phase
URL: https://github.com/apache/couchdb/pull/2396
 
 
   ### Overview
   
   During the initial copy phase target shards are opened outside the
   couch_server. Previously, it was possible to manually (via remsh for instance)
   open the same targets via the couch_server by using the `couch_db:open/2` API
   for example. That could lead to corruption as there would be two writers for
   the same DB file.
   
   In order to prevent such a scenario, introduce a mechanism for the shard
   splitter to lock the target shards such that any regular open call would fail
   during the initial copy phase.
   
   The locking mechanism is generic and would allow local locking of shards for
   possibly other reasons in the future as well.
   
   
   ### Testing recommendations
   
      `make eunit`
   
   ### Checklist
   
   - [x] Code is written and works correctly
   - [x] Changes are covered by tests
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [couchdb] nickva merged pull request #2396: Lock shard splitting targets during the initial copy phase

Posted by GitBox <gi...@apache.org>.
nickva merged pull request #2396: Lock shard splitting targets during the initial copy phase
URL: https://github.com/apache/couchdb/pull/2396
 
 
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services