You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Nick Vatamaniuc <va...@apache.org> on 2019/07/19 18:23:28 UTC
[DISCUSS] [PROPOSAL] Support only remote replication endpoints
In 2.x local replication endpoints only seem to work like in 1.x but they
do something quite confusing: instead of replicating a clustered database
they replicate a node local database on the node where the replication job
happens to run. The node were replication runs is essentially random as far
as users are concerned. So "local" replications in 2.x almost never do what
users expect.
Over the years this confusion led to numerous question and issues raised in
the IRC channel. So the proposal is to remove support for "local"
replications from versions 3.x and up, and only support "remote"
replication endpoints. That will reduce the support and issue load as well
as replicator code size.
What does everyone think?
Re: [DISCUSS] [PROPOSAL] Support only remote replication endpoints
Posted by Jan Lehnardt <ja...@apache.org>.
Even better, thanks for clarifying!
Cheers
Jan
—
> On 19. Jul 2019, at 21:51, Joan Touzet <wo...@apache.org> wrote:
>
> couchup uses URLs of the form http://127.0.0.1:5984/ and :5986 (or whatever ports are passed in on the CLI), so this won't be an issue.
>
> https://github.com/apache/couchdb/blob/master/rel/overlay/bin/couchup#L223-L230
>
> +100
>
> -Joan
>
>> On 2019-07-19 3:02 p.m., Jan Lehnardt wrote:
>> I think we left in the loophole for the couchup utility that helps folks to go from 1.x to 2.x, no need for that in 3.x.
>> Cheers
>> Jan
>> —
>>> On 19. Jul 2019, at 20:23, Nick Vatamaniuc <va...@apache.org> wrote:
>>>
>>> In 2.x local replication endpoints only seem to work like in 1.x but they
>>> do something quite confusing: instead of replicating a clustered database
>>> they replicate a node local database on the node where the replication job
>>> happens to run. The node were replication runs is essentially random as far
>>> as users are concerned. So "local" replications in 2.x almost never do what
>>> users expect.
>>>
>>> Over the years this confusion led to numerous question and issues raised in
>>> the IRC channel. So the proposal is to remove support for "local"
>>> replications from versions 3.x and up, and only support "remote"
>>> replication endpoints. That will reduce the support and issue load as well
>>> as replicator code size.
>>>
>>> What does everyone think?
Re: [DISCUSS] [PROPOSAL] Support only remote replication endpoints
Posted by Joan Touzet <wo...@apache.org>.
couchup uses URLs of the form http://127.0.0.1:5984/ and :5986 (or
whatever ports are passed in on the CLI), so this won't be an issue.
https://github.com/apache/couchdb/blob/master/rel/overlay/bin/couchup#L223-L230
+100
-Joan
On 2019-07-19 3:02 p.m., Jan Lehnardt wrote:
> I think we left in the loophole for the couchup utility that helps folks to go from 1.x to 2.x, no need for that in 3.x.
>
> Cheers
> Jan
> —
>
>> On 19. Jul 2019, at 20:23, Nick Vatamaniuc <va...@apache.org> wrote:
>>
>> In 2.x local replication endpoints only seem to work like in 1.x but they
>> do something quite confusing: instead of replicating a clustered database
>> they replicate a node local database on the node where the replication job
>> happens to run. The node were replication runs is essentially random as far
>> as users are concerned. So "local" replications in 2.x almost never do what
>> users expect.
>>
>> Over the years this confusion led to numerous question and issues raised in
>> the IRC channel. So the proposal is to remove support for "local"
>> replications from versions 3.x and up, and only support "remote"
>> replication endpoints. That will reduce the support and issue load as well
>> as replicator code size.
>>
>> What does everyone think?
>
Re: [DISCUSS] [PROPOSAL] Support only remote replication endpoints
Posted by Jan Lehnardt <ma...@jan.io>.
I think we left in the loophole for the couchup utility that helps folks to go from 1.x to 2.x, no need for that in 3.x.
Cheers
Jan
—
> On 19. Jul 2019, at 20:23, Nick Vatamaniuc <va...@apache.org> wrote:
>
> In 2.x local replication endpoints only seem to work like in 1.x but they
> do something quite confusing: instead of replicating a clustered database
> they replicate a node local database on the node where the replication job
> happens to run. The node were replication runs is essentially random as far
> as users are concerned. So "local" replications in 2.x almost never do what
> users expect.
>
> Over the years this confusion led to numerous question and issues raised in
> the IRC channel. So the proposal is to remove support for "local"
> replications from versions 3.x and up, and only support "remote"
> replication endpoints. That will reduce the support and issue load as well
> as replicator code size.
>
> What does everyone think?
Re: [DISCUSS] [PROPOSAL] Support only remote replication endpoints
Posted by Jan Lehnardt <ja...@apache.org>.
Oh god, please, yes.
Cheers
Jan
—
> On 19. Jul 2019, at 20:23, Nick Vatamaniuc <va...@apache.org> wrote:
>
> In 2.x local replication endpoints only seem to work like in 1.x but they
> do something quite confusing: instead of replicating a clustered database
> they replicate a node local database on the node where the replication job
> happens to run. The node were replication runs is essentially random as far
> as users are concerned. So "local" replications in 2.x almost never do what
> users expect.
>
> Over the years this confusion led to numerous question and issues raised in
> the IRC channel. So the proposal is to remove support for "local"
> replications from versions 3.x and up, and only support "remote"
> replication endpoints. That will reduce the support and issue load as well
> as replicator code size.
>
> What does everyone think?