commit | 8cf4896ff421898ea5d93de170ab8fbcbd317f4e | [log] [tgz] |
---|---|---|
author | brkolla <bkolla@cloudant.com> | Mon Feb 20 13:11:01 2017 -0500 |
committer | brkolla <bkolla@cloudant.com> | Mon Feb 20 14:01:58 2017 -0500 |
tree | 792939deb4ff71dc6e1c8c590a56ffb33f224147 | |
parent | f6e4c5629a7d996d284e4489f1897c057823f846 [diff] |
Rollback change in default value for max_write_delay config The default for `global_change:max_write_delay` config was changed from 500 to 25 and is causing performance regression. Reverting this change back to 500 is resulting in improved performance. COUCHDB-3304
This app supplies the functionality for the /_db_updates
endpoint.
When a database is created, deleted, or updated, a corresponding event will be persisted to disk (Note: This was designed without the guarantee that a DB event will be persisted or ever occur in the _db_updates
feed. It probably will, but it isn't guaranteed). Users can subscribe to a _changes
-like feed of these database events by querying the _db_updates
endpoint.
When an admin user queries the /_db_updates
endpoint, they will see the account name associated with the DB update as well as update
1: global_changes
, db_writes
: The number of doc updates caused by global_changes.
2: global_changes
, server_pending_updates
: The number of documents aggregated into the pending write batch.
3: global_changes
, listener_pending_updates
: The number of documents aggregated into the pending event batch.
4: global_changes
, event_doc_conflict
: The number of rev tree branches in event docs encountered by global_changes. Should never happen.
5: global_changes
, rpcs
: The number of non-fabric RPCs caused by global_changes.
1: global_changes
, max_event_delay
: (integer, milliseconds) The total timed added before an event is forwarded to the writer.
2: global_changes
, max_write_delay
: (integer, milliseconds) The time added before an event is sent to disk.
3: global_changes
, update_db
: (true/false) A flag setting whether to update the global_changes database. If false, changes will be lost and there will be no performance impact of global_changes on the cluster.