sdk-doctor-windows.exe diagnose http://192.168.1.120:8091/AtomicSearchCache
Summary:
[33m[WARN][0m Connection string is using the deprecated `http://` scheme. Use the `couchbase://` scheme instead!
[33m[WARN][0m Your connection string specifies only a single host. You should consider adding additional static nodes from your cluster to this list to improve your applications fault-tolerance
[33m[WARN][0m Bootstrap host `192.168.1.120` is not using the canonical node hostname of `test-cb01.avionero.net`. This is not neccessarily an error, but has been known to result in strange and challenging to diagnose errors when DNS entries are reconfigured.
[33m[WARN][0m Could not test Search service on `test-cb01.avionero.net` as it was not in the config
[33m[WARN][0m Could not test Analytics service on `test-cb01.avionero.net` as it was not in the config
[33m[WARN][0m Could not test Search service on `test-cb02.avionero.net` as it was not in the config
[33m[WARN][0m Could not test Analytics service on `test-cb02.avionero.net` as it was not in the config
[33m[WARN][0m Could not test Search service on `test-cb03.avionero.net` as it was not in the config
[33m[WARN][0m Could not test Analytics service on `test-cb03.avionero.net` as it was not in the config
[33m[WARN][0m Memcached service on `test-cb01.avionero.net:11210` on average took longer than 10ms (was: 55ms) to reply. This is usually due to network-related issues, and could significantly affect application performance.
[33m[WARN][0m Memcached service on `test-cb01.avionero.net:11210` maximally took longer than 20ms (was: 93ms) to reply. This is usually due to network-related issues, and could significantly affect application performance.
[33m[WARN][0m Memcached service on `test-cb02.avionero.net:11210` on average took longer than 10ms (was: 55ms) to reply. This is usually due to network-related issues, and could significantly affect application performance.
[33m[WARN][0m Memcached service on `test-cb02.avionero.net:11210` maximally took longer than 20ms (was: 91ms) to reply. This is usually due to network-related issues, and could significantly affect application performance.
[33m[WARN][0m Memcached service on `test-cb03.avionero.net:11210` on average took longer than 10ms (was: 53ms) to reply. This is usually due to network-related issues, and could significantly affect application performance.
[33m[WARN][0m Memcached service on `test-cb03.avionero.net:11210` maximally took longer than 20ms (was: 65ms) to reply. This is usually due to network-related issues, and could significantly affect application performance.
sdk-doctor-windows.exe diagnose couchbase://test-cb01.avionero.net,test-cb02.avionero.net,test-cb03.avionero.net/AtomicSearchCache With this connection string code works
Summary:
[33m[WARN][0m Could not test Search service on `test-cb01.avionero.net` as it was not in the config
[33m[WARN][0m Could not test Analytics service on `test-cb01.avionero.net` as it was not in the config
[33m[WARN][0m Could not test Search service on `test-cb02.avionero.net` as it was not in the config
[33m[WARN][0m Could not test Analytics service on `test-cb02.avionero.net` as it was not in the config
[33m[WARN][0m Could not test Search service on `test-cb03.avionero.net` as it was not in the config
[33m[WARN][0m Could not test Analytics service on `test-cb03.avionero.net` as it was not in the config
[33m[WARN][0m Memcached service on `test-cb01.avionero.net:11210` on average took longer than 10ms (was: 53ms) to reply. This is usually due to network-related issues, and could significantly affect application performance.
[33m[WARN][0m Memcached service on `test-cb01.avionero.net:11210` maximally took longer than 20ms (was: 60ms) to reply. This is usually due to network-related issues, and could significantly affect application performance.
[33m[WARN][0m Memcached service on `test-cb02.avionero.net:11210` on average took longer than 10ms (was: 51ms) to reply. This is usually due to network-related issues, and could significantly affect application performance.
[33m[WARN][0m Memcached service on `test-cb02.avionero.net:11210` maximally took longer than 20ms (was: 55ms) to reply. This is usually due to network-related issues, and could significantly affect application performance.
[33m[WARN][0m Memcached service on `test-cb03.avionero.net:11210` on average took longer than 10ms (was: 50ms) to reply. This is usually due to network-related issues, and could significantly affect application performance.
[33m[WARN][0m Memcached service on `test-cb03.avionero.net:11210` maximally took longer than 20ms (was: 51ms) to reply. This is usually due to network-related issues, and could significantly affect application performance.