Thanks for the work this! Personally, I'd love to see a blog post on this
as I may want to use something like this in the future.
On Thu, Jul 27, 2017, 07:09 Carlos Alonso wrote:
> Cool!!
>
> So modifying my list a little bit following your last comment...
>
> *The internal replication way*
> Se
Cool!!
So modifying my list a little bit following your last comment...
*The internal replication way*
Set maintenance mode in the new shard's owner
Modify the shards map to ensure the new shard is considered
Let the internal replication process catch up
Remove maintenace flag
And if you want to
eacces means the file ownership or permissions were wrong, which indicates the
wrong settings on your rsync command. that error will persist until you chown /
chmod correctly.
> On 27 Jul 2017, at 12:08, Carlos Alonso wrote:
>
> eacces
ctory
> >
> > open_result error {not_found,no_db_file} for
> > shards/0fff-1553/my_db.1500994155
> > ```
> >
> > 4. Tries to create the file
> >
> > `creating missing database: shards/0fff-1553/my_db.1500994155`
> >
> >
>
bert Samuel Newson
> wrote:
>
>> Not sure if you saw my write-up from the BigCouch era, still valid for
>> CouchDB 2.0;
>>
>>
>> https://stackoverflow.com/questions/6676972/moving-a-shard-from-one-bigcouch-server-to-another-for-balancing
>>
>> Shar
se rebalancing is definitely a bit tricky and we
> could use better tools for it.
>
>
> > On 26 Jul 2017, at 18:10, Carlos Alonso
> wrote:
> >
> > Hi!
> >
> > I have had a few log errors when moving a shard under particular
> > circumstances and I
.
> On 26 Jul 2017, at 18:10, Carlos Alonso wrote:
>
> Hi!
>
> I have had a few log errors when moving a shard under particular
> circumstances and I'd like to share it here and get your input on whether
> this should be reported or not.
>
> So let me describe t
Hi!
I have had a few log errors when moving a shard under particular
circumstances and I'd like to share it here and get your input on whether
this should be reported or not.
So let me describe the steps I took:
1. 3 nodes cluster (couch-0, couch-1 and couch-2), 1 database (my_db) wi
