Prior to 2.1, Sync Gateway used system views for a variety of internal operations, including authentication and replication. Starting in 2.1, Sync Gateway will use GSI and N1QL to perform those tasks. A key advantage of the switch to GSI is that it supports index replicas, allowing Sync Gateway to reduce the downtime during a server upgrade, rebalance or failover from several hours to a few seconds. This change also improves overall query performance. Note that this only impacts system views. Users can continue to define views through the Sync Gateway Admin REST API. This capability is enabled by default and there are 2 properties in the configuration file which can be adjusted:
Use of GSI requires Couchbase Server 5.5, with at least one node running the Index Service.
Users wanting to run Sync Gateway 2.1 with an older version of Couchbase Server will need to continue to use views, by setting the
By default, Sync Gateway requires the Index Service to be running on at least two Couchbase Server nodes (required for index replica).
Users can run with a single Index Service node by setting Sync Gateway’s
Sync Gateway adds the ability to use X.509 certificates to authenticate against Couchbase Server 5.5 or higher. This functionality can be used instead or in addition to the existing authentication method which is to specify a username and password in the configuration file.
Continuous logging is a new feature in Sync Gateway 2.1 that provides more flexibility in how logs are generated and retained, whilst maintaining the level of logging required by Couchbase Support for investigation of issues.
Sync Gateway logging is now written to separate files by log level, with each log level supporting individual retention policies.
Console logging can also be configured independently, providing additional flexibility for system administrators depending on their needs.
The previous logging configuration (
logging.default) is being deprecated, and Sync Gateway 2.1 will display warnings on startup of what is required to update your configuration.
Detailed information about continuous logging can be found in the Logging guide.
sgcollect_info has been updated to use the continuous logging feature introduced in 2.1, and collects the four leveled files (sg_error.log, sg_warn.log, sg_info.log and sg_debug.log).
These new log files are rotated and compressed by Sync Gateway, so
sgcollect_info decompresses these rotated logs, and concatenates them back into a single file upon collection.
For example, if you have sg_debug.log, and sg_debug-2018-04-23T16-57-13.218.log.gz and then run
sgcollect_info as normal, both of these files get put into a sg_debug.log file inside the zip output folder.
All log outputs can be redacted, this means that user-data, considered to be private, is removed.
This feature is optional and can be enabled in the configuration with the
sgcollect_info now supports log redaction post-processing.
In order to utilize this, Sync Gateway needs to be run with the
logging.redaction_level property set to "partial".
Two new command line options have been added to
--log-redaction-level=REDACT_LEVEL: redaction level for the logs collected,
partialsupported. Defaults to
--log-redaction-levelis set to partial, two zip files are produced, and tagged contents in the redacted one should be hashed in the same way as
$ ./sgcollect_info --log-redaction-level=partial sgout.zip ... Zipfile built: sgout-redacted.zip Zipfile built: sgout.zip
--log-redaction-salt=SALT_VALUE: salt used in the hashing of tagged data when enabling redaction. Defaults to a random uuid.
databases.$db.bucket_op_timeout_ms property to override the default timeout used by Sync Gateway to query Couchbase Server.
It’s generally not necessary to change this property unless there is a particularly heavy load on Couchbase Server which would increase the response time.
This release contains a number of bug fixes and enhancements for Sync Gateway. Find out more in the release notes.