You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2018/10/17 10:10:56 UTC

[GitHub] tudordumitriu opened a new issue #1659: Replication calls to _replicate are returning entire history even if replicator.max_history is set

tudordumitriu opened a new issue #1659: Replication calls to _replicate are returning entire history even if replicator.max_history is set
URL: https://github.com/apache/couchdb/issues/1659
 
 
   <!--- Provide a general summary of the issue in the Title above -->
   Hi 
   We have a (potential) performance issue
   We are doing custom _replicate calls on our server services in order to keep user databases in sync according to our business logic rules, which means a lot of call and responses to be parsed.
   Everything works great, with one mention, the _replicate response contains ENTIRE history of all replications done upon that document.
   
   I have tried setting up max_history in replicator group in settings, but no luck.
   Since we are not interested at all replication history entries.
   
   I don't know if replicator.max_history is the correct setting, but I found it by checking CouchDB code.
   
   Please tell us how can we limit the ever-growing history in _replicate response
   
   ## Your Environment
   <!--- Include as many relevant details about the environment you experienced the bug in -->
   * Version used:2.1.1
   * Browser Name and version:Chrome
   * Operating System and version (desktop or mobile): Windows 10
   * Link to your project:
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services