Details
Critical Description
Yet it returns very quickly. So underneath the covers there seems to be no default timeout or something? Here's how it looks:
{'config_rev': 1802, 'id': '0x7f9d05442340', 'sdk': 'libcouchbase/3.0.0_beta3_28_g5d4015c7cd PYCBC/3.0.0b3.dev28+g5d4015c7', 'services': {'fts': [{'id': '0x7f9cd613ee10', 'latency_us': 1491, 'local': '10.143.193.1:50801', 'remote': '10.143.193.101:8094', 'status': 'ok'}], 'kv': [{'id': '0x7f9cd5502030', 'latency_us': 1607, 'local': '10.143.193.1:50791', 'remote': '10.143.193.101:11210', 'scope': 'default', 'status': 'ok'}, {'id': '0x7f9cd6141080', 'latency_us': 13498, 'local': '10.143.193.1:50805', 'remote': '10.143.193.102:11210', 'scope': 'default', 'status': 'timeout'}, {'id': '0x7f9cd60012f0', 'latency_us': 13585, 'local': '10.143.193.1:50806', 'remote': '10.143.193.103:11210', 'scope': 'default', 'status': 'timeout'}], 'n1ql': [{'id': '0x7f9cd613d250', 'latency_us': 2217, 'local': '10.143.193.1:50799', 'remote': '10.143.193.101:8093', 'status': 'ok'}, {'id': '0x7f9cd613f4b0', 'latency_us': 12258, 'local': '10.143.193.1:50802', 'remote': '10.143.193.101:8095', 'status': 'ok'}], 'views': [{'id': '0x7f9cd613e3e0', 'latency_us': 2824, 'local': '10.143.193.1:50800', 'remote': '10.143.193.101:8092', 'status': 'ok'}, {'id': '0x7f9cd6140200', 'latency_us': 3115, 'local': '10.143.193.1:50803', 'remote': '10.143.193.102:8092', 'status': 'ok'}, {'id': '0x7f9cd6140bd0', 'latency_us': 3030, 'local': '10.143.193.1:50804', 'remote': '10.143.193.103:8092', 'status': 'ok'}]}, 'version': 1}
|
This is for a 3 server cluster (2 nodes only kv, 1 node everything). Note the timeouts in the kv section.
Attachments
| For Gerrit Dashboard: PYCBC-836 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 140712,3 | PYCBC-797 Ping should use timeout if one is passed in | master | couchbase-python-client | Status: MERGED | +2 | +1 |