nickva commented on issue #4639:
URL: https://github.com/apache/couchdb/issues/4639#issuecomment-1587671324
As `{error,req_timedout}` indicates a timeout. Try to increase the
replication connection timeout.
https://docs.couchdb.org/en/stable/config/replicator.html#replicator/connection_timeout
The `instance_start_time` change, to return a db creation timestamp instead
of `0` is a 3.3 change . We did mention it in the [release
notes](https://docs.couchdb.org/en/stable/whatsnew/3.3.html#bugfixes) but did
not update the documentation. https://github.com/apache/couchdb/issues/3901
In all of the 3.x versions, `_ensure_full_commit` doesn't actually do
anything, it's a compatibility no-op. All the documents updates are now
committed during doc update operation. The only thing the API endpoint returns
is the database instance start time value. So, it is a bit strange that
`_ensure_full_commit` is timing out, unless the endpoint is not a 3.x Apache
CouchDB version but an older version or another couch implementation.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
