what means 'starting' in the status for a continuous replication?

["Andrew U. Frank" <fr...@geoinfo.tuwien.ac.at>]

i have asked this question but did not get an answer:
the problem persists - any hlep?

i start continuous replication (using curl) and see then in futon the 
stauts as 'starting'. it seems to work (in the sense that new documents 
are replicated). is there a way to see if two couchdb replications are 
on the same state? (short of starting a non-continous replication)?

thank you

andrew

Re: what means 'starting' in the status for a continuous replication?

[Mark Hahn <ma...@boutiquing.com>]

Anything that implies other than normal operation is confusing.
Seeing "starting" for more than a minute is definitely misleading.  I
don't care what it says as long as it doesn't mislead.

How about "started"?

On Sat, Jun 25, 2011 at 10:20 PM, Paul Davis
<pa...@gmail.com> wrote:
> On Sat, Jun 25, 2011 at 9:58 PM, Mark Hahn <ma...@boutiquing.com> wrote:
>> May I suggest not calling it "starting" once it has started?  I found
>> that very confusing, and it is wrong.
>
> Yeah. Technically,
> "things-are-happening-but-will-happen-again-unless-we-get-to-the-first-checkpoint-so-that-we-don't-have-to-redo-this-part"
> would be more correct. If someone has a better word that summarizes
> that bit then I'd be happy to make the change, but I sure can't think
> of something better than "starting" or "initializing" or some other
> generic description that would cause less confusion.
>



-- 
Mark Hahn
Website Manager
mark@boutiquing.com
949-342-4246

Re: what means 'starting' in the status for a continuous replication?

[Benoit Chesneau <bc...@gmail.com>]

On Sun, Jun 26, 2011 at 7:20 AM, Paul Davis <pa...@gmail.com> wrote:
> On Sat, Jun 25, 2011 at 9:58 PM, Mark Hahn <ma...@boutiquing.com> wrote:
>> May I suggest not calling it "starting" once it has started?  I found
>> that very confusing, and it is wrong.
>
> Yeah. Technically,
> "things-are-happening-but-will-happen-again-unless-we-get-to-the-first-checkpoint-so-that-we-don't-have-to-redo-this-part"
> would be more correct. If someone has a better word that summarizes
> that bit then I'd be happy to make the change, but I sure can't think
> of something better than "starting" or "initializing" or some other
> generic description that would cause less confusion.
>

starting? :D

Re: what means 'starting' in the status for a continuous replication?

[Paul Davis <pa...@gmail.com>]

On Sat, Jun 25, 2011 at 9:58 PM, Mark Hahn <ma...@boutiquing.com> wrote:
> May I suggest not calling it "starting" once it has started?  I found
> that very confusing, and it is wrong.

Yeah. Technically,
"things-are-happening-but-will-happen-again-unless-we-get-to-the-first-checkpoint-so-that-we-don't-have-to-redo-this-part"
would be more correct. If someone has a better word that summarizes
that bit then I'd be happy to make the change, but I sure can't think
of something better than "starting" or "initializing" or some other
generic description that would cause less confusion.

Re: what means 'starting' in the status for a continuous replication?

[Mark Hahn <ma...@boutiquing.com>]

May I suggest not calling it "starting" once it has started?  I found
that very confusing, and it is wrong.


On Sat, Jun 25, 2011 at 2:43 PM, Filipe David Manana
<fd...@apache.org> wrote:
> On Sat, Jun 25, 2011 at 5:28 PM, Andrew U. Frank
> <fr...@geoinfo.tuwien.ac.at> wrote:
>> i have asked this question but did not get an answer:
>> the problem persists - any hlep?
>>
>> i start continuous replication (using curl) and see then in futon the stauts
>> as 'starting'. it seems to work (in the sense that new documents are
>> replicated). is there a way to see if two couchdb replications are on the
>> same state? (short of starting a non-continous replication)?
>
> Is is trunk you're using?
>
> If so, the status was kept as "Starting" until the first checkpoint
> happens. So, if you start a continuous replication and the target is
> up to date with the source, that "Starting" status will remain until
> the source gets updated and the updates are propagated to the target.
> Recently the status update was changed to say "Starting (from source
> sequence 1234)" when resuming a replication. I'm also about to change
> it again to provide a rough idea of the replication state by
> mentioning the source's current sequence number in addition to the
> currently processed source sequence number. E.g. "Processed 1234 /
> 5789".
>
>>
>> thank you
>>
>> andrew
>>
>>
>
>
>
> --
> Filipe David Manana,
> fdmanana@gmail.com, fdmanana@apache.org
>
> "Reasonable men adapt themselves to the world.
>  Unreasonable men adapt the world to themselves.
>  That's why all progress depends on unreasonable men."
>



-- 
Mark Hahn
Website Manager
mark@boutiquing.com
949-342-4246

Re: what means 'starting' in the status for a continuous replication?

[Filipe David Manana <fd...@apache.org>]

On Sat, Jun 25, 2011 at 5:28 PM, Andrew U. Frank
<fr...@geoinfo.tuwien.ac.at> wrote:
> i have asked this question but did not get an answer:
> the problem persists - any hlep?
>
> i start continuous replication (using curl) and see then in futon the stauts
> as 'starting'. it seems to work (in the sense that new documents are
> replicated). is there a way to see if two couchdb replications are on the
> same state? (short of starting a non-continous replication)?

Is is trunk you're using?

If so, the status was kept as "Starting" until the first checkpoint
happens. So, if you start a continuous replication and the target is
up to date with the source, that "Starting" status will remain until
the source gets updated and the updates are propagated to the target.
Recently the status update was changed to say "Starting (from source
sequence 1234)" when resuming a replication. I'm also about to change
it again to provide a rough idea of the replication state by
mentioning the source's current sequence number in addition to the
currently processed source sequence number. E.g. "Processed 1234 /
5789".

>
> thank you
>
> andrew
>
>



-- 
Filipe David Manana,
fdmanana@gmail.com, fdmanana@apache.org

"Reasonable men adapt themselves to the world.
 Unreasonable men adapt the world to themselves.
 That's why all progress depends on unreasonable men."