Node addition and database replication issue

[bmx...@gmail.com]

Hi

Need some help here!

Bigcouch 0.4.2

First let me explain my goal: I want to add a node to an existing cluster where currently all of the participating nodes possesses their own local copies of all databases (all shards exists on all of them). The quorum settings were set accordingly at day one to ensure such a distribution.

What is required here is for the all-shiny new node to become "in-sync" with others by also having database (physically-wise) shards for all databases and their documents.

After reading around, I understand that what I need to do here is a either a push or pull one-off replication of all databases to the new node.  Fair enough this is easily doable by some scripting magic.

So I tested it manually with one database using the following:   curl 'http://localhost:5984/_replicate' -H 'Content-Type: application/json' -d '{"source":"http://localhost:5984/mydb","target":"http://targethost:5984/mydb","create_target": true }'

Despite the outcome of this command being a success ("ok":true  with a session_id), the new node does not contains any shards for this database.  Also the dbs database on the older nodes does not list the new node in the document "by_node" parameter.

Is there something I am not doing right ?  or am I missing a point here ?

Thanks for the help.

Sincerly,

Mike

[bmx...@gmail.com]

Well well,  really quiet here, quite disappointing!

Anyways I thought I would add more information about what I have found.

Replication will not actually copy anything if the bigcouch databases documents doesn't contains shard pointers to other nodes in each of their respective documents under dbs.  When one adds nodes to the cluster, the databases schemas (not shards) gets created on the new node, but even if you replicate nothing is copied over (no work is actually required as no shards exists on the new node)

In short the answer is here :  https://github.com/cloudant/bigcouch/issues/79

" nope, sorry. There's not even an unofficial milestone for automatic rebalancing."

One needs to follow instructions on this link to manually copy the shards over and then hack the dbs documents:

http://stackoverflow.com/questions/6676972/moving-a-shard-from-one-bigcouch-server-to-another-for-balancing

Yikes!  This is essential functionality in my opinion, and so easily done with MongoDB.

[Michael Miller]

Sorry about that, this list is deprecated in favor of the apache couchdb user list. If you ask there, I can guarantee an answer. I'll work on taking this down with an appropriate forwarding message!

-M

--
You received this message because you are subscribed to the Google Groups "BigCouch Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigcouch-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.