couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dustin Sallings <dus...@spy.net>
Subject Re: [jira] [Commented] (COUCHDB-1259) Replication ID is not stable if local server has a dynamic port number
Date Mon, 05 Nov 2012 06:48:37 GMT
Benoit Chesneau <bchesneau@gmail.com>
writes:

>>   1. My home couchdb server (by hostname, only available from inside my
>>      house)
>>   2. My work couchdb server (by hostname, available inside and outside,
>>      but the IP addresses are different in each location).
>>   3. Iriscouch (by hostname, available everywhere on the same address)
>>
>>   In all three cases, it can stop replication, but will resume again if
>> I restart.
>>
> Most of these cases already work if you are using the new _replicator api.

  If you're referring to the replicator DB, then yes, that's the way
I set up all my replications, and why it starts back up when I restart.

>>   Under what circumstances do you consider "stop replicating after
>> sleep, but start again if the user restarts CouchDB" good behavior?
>
> - local replications should always restart.
> - replication with remote should restart only if the remote didn't
> change and my network didn't change.
>
> In other cases I need to rely on a mecanism to validate that I can
> continue the replication. In that case I agree it can be automated and
> we have different solution to do it. But that should never be a
> default mecanism imo.

  Let's assume what you're saying is OK and that the real bug here is
that it *does* restart when I kill and restart CouchDB...

  The one that I notice the most is an application that collects data in
my house that replicates to my laptop.  The *only* time this can
possibly work is when my laptop is on my home LAN.  That means, for it
to start properly, it has to be connected to my home LAN before I ever
see anything.

  Then I go somewhere else.  Let's assume the somewhere else has a
host named "menudo" (which is the unfortunate hostname of the machine in
my house running CouchDB).  Because I'm on a different network, the
replicator decides it's probably not the menudo I'm looking for, so it
ceases replication.

  When I go back home, shouldn't it start back up?

  Doesn't this whole thing get a lot more simple and inline with what
any reasonable user might expect if you just say, "configured
replications run as configured"?

-- 
dustin


Mime
View raw message