How to resolve this Couchbase timeout issue? and to store JWT Token in Couchbase what are the further steps?

@Configuration
public class CouchbaseConfig extends AbstractCouchbaseConfiguration{

@Override
public String getBucketName() {
	return "sessionstore";
}

@Override
public String getConnectionString() {
	return "172.16.62.81";
}

@Override
public String getPassword() {
	return "password";
}

@Override
public String getUserName() {
	return "Administrator";
}

}

Error Trace:
DEBUG com.couchbase.endpoint - [com.couchbase.endpoint][EndpointConnectedEvent][442ms] Endpoint connected successfully (no timings) {“circuitBreaker”:“DISABLED”,“coreId”:“0xa44e333d00000001”,“local”:“172.16.175.231:51467”,“remote”:“172.16.62.81:8091”,“type”:“MANAGER”}
DEBUG com.couchbase.endpoint - [com.couchbase.endpoint][EndpointStateChangedEvent] Endpoint changed state from CONNECTING to CONNECTED {“circuitBreaker”:“DISABLED”,“coreId”:“0xa44e333d00000001”,“local”:“172.16.175.231:51467”,“remote”:“172.16.62.81:8091”,“type”:“MANAGER”}
DEBUG com.couchbase.service - [com.couchbase.service][ServiceStateChangedEvent] Service changed state from CONNECTING to CONNECTED {“coreId”:“0xa44e333d00000001”,“remote”:“172.16.62.81:8091”,“type”:“MANAGER”}
DEBUG com.couchbase.node - [com.couchbase.node][NodeStateChangedEvent] Node changed state from CONNECTING to DEGRADED {“coreId”:“0xa44e333d00000001”,“managerPort”:“8091”,“remote”:“172.16.62.81”}
DEBUG com.couchbase.io - [com.couchbase.io][SaslMechanismsSelectedEvent] SASL Mechanism SCRAM_SHA512 selected. Allowed: [SCRAM_SHA1, SCRAM_SHA256, SCRAM_SHA512] {“bucket”:“sessionstore”,“coreId”:“0xa44e333d00000001”,“local”:“/172.16.175.231:51468”,“remote”:“/172.16.62.81:11210”}
DEBUG com.couchbase.request - [com.couchbase.request][RequestRetryScheduledEvent][512ms] Request CarrierGlobalConfigRequest retry scheduled per RetryStrategy (Reason: ENDPOINT_NOT_AVAILABLE) {“completed”:false,“coreId”:“0xa44e333d00000001”,“idempotent”:true,“lastDispatchedTo”:“172.16.62.81”,“requestId”:2,“requestType”:“CarrierGlobalConfigRequest”,“retried”:11,“retryReasons”:[“ENDPOINT_NOT_AVAILABLE”,“NODE_NOT_AVAILABLE”],“service”:{“opaque”:“0x9”,“target”:“172.16.62.81”,“type”:“kv”,“vbucket”:0},“timeoutMs”:10000}


Caused by: com.couchbase.client.core.error.RequestCanceledException: CarrierGlobalConfigRequest, Reason: TARGET_NODE_REMOVED {“cancelled”:true,“completed”:true,“coreId”:“0x334151de00000001”,“idempotent”:true,“lastDispatchedTo”:“172.16.62.81”,“reason”:“TARGET_NODE_REMOVED”,“requestId”:2,“requestType”:“CarrierGlobalConfigRequest”,“retried”:11,“retryReasons”:[“ENDPOINT_NOT_AVAILABLE”,“NODE_NOT_AVAILABLE”],“service”:{“opaque”:“0x9”,“target”:“172.16.62.81”,“type”:“kv”,“vbucket”:0},“timeoutMs”:10000}
at com.couchbase.client.core.msg.BaseRequest.cancel(BaseRequest.java:186)
… 14 common frames omitted
DEBUG com.couchbase.config - [com.couchbase.config][GlobalConfigRetriedEvent][1000us] Failed to open global config {“coreId”:“0x334151de00000001”}
com.couchbase.client.core.error.ConfigException: Caught exception while loading global config.
at com.couchbase.client.core.config.loader.GlobalLoader.lambda$load$3(GlobalLoader.java:72)
at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onError(FluxOnErrorResume.java:94)
at reactor.core.publisher.FluxMap$MapSubscriber.onError(FluxMap.java:134)

Hi @SANTOSH
What’s the actual error you’re seeing, in terms of what code is seeing what final exception? You may see transient failures like this at DEBUG level because under the hood collisions between cluster configurations are getting resolved and retried. Retries should take care of things and these errors should just be cosmetic.
If you are connecting to Couchbase over the internet, you may want to increase the timeouts to give connection bootstrapping extra time to complete.