You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Bill Foshay <bi...@noteandgo.com> on 2015/02/09 16:51:17 UTC

Continous Replications Stopping Unexpectedly

Hi,

We're experiencing issues with continuous replications just mysteriously 
stopping. We're using IrisCouch which runs CouchDb v1.3. After we kick off 
continuous push/pull replications they will run for roughly 1-4 days before 
stopping. The CouchDb Status page no longer shows them and the replication 
documents are no longer even in the replicator database. So we have to 
restart them. Any idea what could be going wrong or if there's something we 
could point the IrisCouch support team to that would help them troubleshoot 
this issue?

Thanks,
Bill


Re: Continous Replications Stopping Unexpectedly

Posted by Bill Foshay <bi...@noteandgo.com>.
> But perhaps you should present some more facts about your installation and
> environment and some of the gurus can help :)

Thanks Sinan. We actually didn't install anything which is what makes 
troubleshooting difficult. Our CouchDb is hosted by IrisCouch 
(http://www.iriscouch.com/) and I believe they host them on Ubuntu. I'm not 
entirely familiar with all of the CouchDb settings but if there's a setting 
I should ask their support team about I'd be more than happy to see what 
they have to say. I appreciate any assistance.

Thanks!
Bill




Re: Continous Replications Stopping Unexpectedly

Posted by Kiril Stankov <ki...@open-net.biz>.
Hi,

I had similar case.
One of our servers got out of disk space and not only replication 
stopped, but the entries were removed from the _replicator DB.
The source of the problem was that someone started cleanup,  when there 
was not enough space, e.g. at least twice the size of the new, "clean" Db.
I had to manually re-create the replication definitions, once this was 
done, things were Ok.
May be there is some sort of "expiration" setting and once this is hit, 
the replication entry is removed?
------------------------------------------------------------------------
*With best regards,*
Kiril Stankov,
CEO


            This Email disclaimer
            <http://open-net.biz/emailsignature.html> is integral part
            of this message.

On 2/9/2015 10:30 PM, Sinan Gabel wrote:
> I have not tried it but I understand that coucdb will crash somehow if
> there is not enough disk space during compaction.
> But perhaps you should present some more facts about your installation and
> environment and some of the gurus can help :)
>
>
> On Monday, February 9, 2015, Bill Foshay <bi...@noteandgo.com> wrote:
>
>>> Another thing you may want to check is that you have enough disk space
>> for
>>> compaction. As I recall it needs at least 2x the size of the compacted db
>>> size.
>> Does compaction affect continuous replications? Will it cause them to stop
>> or to be removed from the replicator database?
>>
>>
>>
>>


Re: Continous Replications Stopping Unexpectedly

Posted by Sinan Gabel <si...@gmail.com>.
I have not tried it but I understand that coucdb will crash somehow if
there is not enough disk space during compaction.
But perhaps you should present some more facts about your installation and
environment and some of the gurus can help :)


On Monday, February 9, 2015, Bill Foshay <bi...@noteandgo.com> wrote:

> > Another thing you may want to check is that you have enough disk space
> for
> > compaction. As I recall it needs at least 2x the size of the compacted db
> > size.
>
> Does compaction affect continuous replications? Will it cause them to stop
> or to be removed from the replicator database?
>
>
>
>

Re: Continous Replications Stopping Unexpectedly

Posted by Bill Foshay <bi...@noteandgo.com>.
> Another thing you may want to check is that you have enough disk space for
> compaction. As I recall it needs at least 2x the size of the compacted db
> size.

Does compaction affect continuous replications? Will it cause them to stop 
or to be removed from the replicator database?




Re: Continous Replications Stopping Unexpectedly

Posted by Sinan Gabel <si...@gmail.com>.
Hi,
Another thing you may want to check is that you have enough disk space for
compaction. As I recall it needs at least 2x the size of the compacted db
size.
 On 9 Feb 2015 19:59, "Bill Foshay" <bi...@noteandgo.com> wrote:

> > You may want to take a look at e.g. "Resource Limits" at
> > http://wiki.apache.org/couchdb/Performance .
> >
> > Also the previous discussion thread "Tweaking CouchDB For DB-Per-User" is
> > about the same.
> >
>
> Thanks Sinan. I looked at the links you provided and we can certainly try
> increasing the resource limits but I'm not sure we're at a point yet where
> we're hitting limitations. We're simply trying to continuously replicate
> between two databases, one of them being on IrisCouch. The database size is
> only 25GB and our number of client connections is below 50. I can see how a
> DB-Per-User scenario could be problematic but again, we're just running one
> central DB and using replication as a way to copy the database to a
> different server.
>
> Even if an error occurs, shouldn't the replications still be stored in the
> replicator database? Do they get removed when errors are encountered?
>
> Thanks for the help!
>
> Bill
>
>
>
>
>

Re: Continous Replications Stopping Unexpectedly

Posted by Bill Foshay <bi...@noteandgo.com>.
> You may want to take a look at e.g. "Resource Limits" at
> http://wiki.apache.org/couchdb/Performance .
> 
> Also the previous discussion thread "Tweaking CouchDB For DB-Per-User" is
> about the same.
> 

Thanks Sinan. I looked at the links you provided and we can certainly try 
increasing the resource limits but I'm not sure we're at a point yet where 
we're hitting limitations. We're simply trying to continuously replicate 
between two databases, one of them being on IrisCouch. The database size is 
only 25GB and our number of client connections is below 50. I can see how a 
DB-Per-User scenario could be problematic but again, we're just running one 
central DB and using replication as a way to copy the database to a 
different server.

Even if an error occurs, shouldn't the replications still be stored in the 
replicator database? Do they get removed when errors are encountered?

Thanks for the help!

Bill





Re: Continous Replications Stopping Unexpectedly

Posted by Sinan Gabel <si...@gmail.com>.
Hi!

You may want to take a look at e.g. "Resource Limits" at
http://wiki.apache.org/couchdb/Performance .

Also the previous discussion thread "Tweaking CouchDB For DB-Per-User" is
about the same.


Best,
Sinan

On 9 February 2015 at 16:51, Bill Foshay <bi...@noteandgo.com> wrote:

> Hi,
>
> We're experiencing issues with continuous replications just mysteriously
> stopping. We're using IrisCouch which runs CouchDb v1.3. After we kick off
> continuous push/pull replications they will run for roughly 1-4 days before
> stopping. The CouchDb Status page no longer shows them and the replication
> documents are no longer even in the replicator database. So we have to
> restart them. Any idea what could be going wrong or if there's something we
> could point the IrisCouch support team to that would help them troubleshoot
> this issue?
>
> Thanks,
> Bill
>
>