You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Zachary Zolton <za...@gmail.com> on 2009/11/03 21:23:31 UTC
Replication Status Messages
Howdy,
I've been watching a push replication in Futon that's been crunching
for a while with the following message:
"W Processed source update #176"
Does this mean that the remote server has process my local revisions
up to sequence number 176? Also, should I be able to see an active
task, or something on the replication page, for the remote server?
Any explanations of what to look for would be greatly appreciated!
Cheers,
Zach
Re: Replication Status Messages
Posted by Adam Kocoloski <ko...@apache.org>.
Yeah, that's too long, something seems to have gone south. If
possible I'd try restarting CouchDB and then the replication. Best,
Adam
On Nov 3, 2009, at 3:37 PM, Zachary Zolton wrote:
> Coolio, so how long should I wait for that status message to change
> locally before I start fretting? It's been the same for like a good 10
> minutes, though I'm pushing to a remote couchy host on the
> intarwebs....
>
> (FYI, my local database is 7.1MB compacted, has 756 docs and is at
> seq# 1318)
>
>
> On Tue, Nov 3, 2009 at 2:32 PM, Adam Kocoloski <ko...@apache.org>
> wrote:
>> On Nov 3, 2009, at 3:23 PM, Zachary Zolton wrote:
>>
>>> Howdy,
>>>
>>> I've been watching a push replication in Futon that's been crunching
>>> for a while with the following message:
>>> "W Processed source update #176"
>>>
>>> Does this mean that the remote server has process my local revisions
>>> up to sequence number 176? Also, should I be able to see an active
>>> task, or something on the replication page, for the remote server?
>>>
>>> Any explanations of what to look for would be greatly appreciated!
>>>
>>>
>>> Cheers,
>>>
>>> Zach
>>
>> Hi Zach, that's correct, everything up to source update #176 should
>> be
>> available on the target server at that point.
>>
>> There's no easy way to generate a status update on the target server,
>> because to the target the replication just looks like a series of
>> normal
>> HTTP requests. Cheers,
>>
>> Adam
>>
Re: Replication Status Messages
Posted by Zachary Zolton <za...@gmail.com>.
Coolio, so how long should I wait for that status message to change
locally before I start fretting? It's been the same for like a good 10
minutes, though I'm pushing to a remote couchy host on the
intarwebs....
(FYI, my local database is 7.1MB compacted, has 756 docs and is at seq# 1318)
On Tue, Nov 3, 2009 at 2:32 PM, Adam Kocoloski <ko...@apache.org> wrote:
> On Nov 3, 2009, at 3:23 PM, Zachary Zolton wrote:
>
>> Howdy,
>>
>> I've been watching a push replication in Futon that's been crunching
>> for a while with the following message:
>> "W Processed source update #176"
>>
>> Does this mean that the remote server has process my local revisions
>> up to sequence number 176? Also, should I be able to see an active
>> task, or something on the replication page, for the remote server?
>>
>> Any explanations of what to look for would be greatly appreciated!
>>
>>
>> Cheers,
>>
>> Zach
>
> Hi Zach, that's correct, everything up to source update #176 should be
> available on the target server at that point.
>
> There's no easy way to generate a status update on the target server,
> because to the target the replication just looks like a series of normal
> HTTP requests. Cheers,
>
> Adam
>
Re: Replication Status Messages
Posted by Adam Kocoloski <ko...@apache.org>.
On Nov 3, 2009, at 3:23 PM, Zachary Zolton wrote:
> Howdy,
>
> I've been watching a push replication in Futon that's been crunching
> for a while with the following message:
> "W Processed source update #176"
>
> Does this mean that the remote server has process my local revisions
> up to sequence number 176? Also, should I be able to see an active
> task, or something on the replication page, for the remote server?
>
> Any explanations of what to look for would be greatly appreciated!
>
>
> Cheers,
>
> Zach
Hi Zach, that's correct, everything up to source update #176 should be
available on the target server at that point.
There's no easy way to generate a status update on the target server,
because to the target the replication just looks like a series of
normal HTTP requests. Cheers,
Adam