Details
-
Bug
-
Resolution: Fixed
-
Major
-
3.2.4
-
None
-
None
-
1
Description
Problem:
Calling WaitUntilReady on a cluster and bucket objects are never successful and always times out. I have tried increasing the time limit and it doesn't help. Also it's not a connection issue to the CB cluster as I can omit the wait until ready call and do ops as normal.
Example Code:
var cluster = await Cluster.ConnectAsync(options).ConfigureAwait(false); |
await cluster.WaitUntilReadyAsync(TimeSpan.FromSeconds(20)); |
//And or
|
var bucketLocal = await cluster.BucketAsync(bucketName).ConfigureAwait(false); |
await bucketLocal.WaitUntilReadyAsync(TimeSpan.FromSeconds(20)); |
Error Messages:
Example with cluster waituntilready.
fail: SdkdConsole.Daemon.Control[0]
|
Unexpected Exception on Run:One or more errors occurred. (Timed out after 00:00:10.)
|
System.AggregateException: One or more errors occurred. (Timed out after 00:00:10.)
|
---> Couchbase.Core.Exceptions.UnambiguousTimeoutException: Timed out after 00:00:10.
|
---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
|
at Couchbase.Cluster.WaitUntilReadyAsync(TimeSpan timeout, WaitUntilReadyOptions options) in /Users/willbroadbelt/Documents/repos/couchbase/couchbase-net-client/src/Couchbase/Cluster.cs:line 259
|
--- End of inner exception stack trace ---
|
at Couchbase.Cluster.WaitUntilReadyAsync(TimeSpan timeout, WaitUntilReadyOptions options) in /Users/willbroadbelt/Documents/repos/couchbase/couchbase-net-client/src/Couchbase/Cluster.cs:line 264
|
at SdkdConsole.Daemon.Handle.ClusterAsync(ClusterOptions options) in /Users/willbroadbelt/Documents/repos/couchbase/sdkd-net/src/SdkdConsole/Daemon/Handle.cs:line 409
|
-----------------------Context Info---------------------------
|
null
|
|
--- End of inner exception stack trace ---
|
at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
|
at System.Threading.Tasks.Task`1.get_Result()
|
at SdkdConsole.Daemon.Handle.Run() in /Users/willbroadbelt/Documents/repos/couchbase/sdkd-net/src/SdkdConsole/Daemon/Handle.cs:line 107
|
And here's the error message from using WaitUntilReady on a bucket object.
warn: Couchbase.Core.Configuration.Server.ConfigHandler[7000]
|
Issue getting Cluster Map on server 172.23.111.128:11210!
|
Couchbase.Core.Configuration.Server.ContextStoppedException: ConfigHandler is in stopped mode.
|
at Couchbase.Core.Configuration.Server.ConfigHandler.Publish(BucketConfig config) in /Users/willbroadbelt/Documents/repos/couchbase/couchbase-net-client/src/Couchbase/Core/Configuration/Server/ConfigHandler.cs:line 193
|
at Couchbase.Core.Configuration.Server.ConfigHandler.<Poll>b__13_0() in /Users/willbroadbelt/Documents/repos/couchbase/couchbase-net-client/src/Couchbase/Core/Configuration/Server/ConfigHandler.cs:line 113
|
fail: SdkdConsole.Daemon.Control[0]
|
Unexpected Exception on Run:One or more errors occurred. (Timed out after 00:00:20.)
|
System.AggregateException: One or more errors occurred. (Timed out after 00:00:20.)
|
---> Couchbase.Core.Exceptions.UnambiguousTimeoutException: Timed out after 00:00:20.
|
---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
|
at Couchbase.Core.BucketBase.WaitUntilReadyAsync(TimeSpan timeout, WaitUntilReadyOptions options) in /Users/willbroadbelt/Documents/repos/couchbase/couchbase-net-client/src/Couchbase/Core/BucketBase.cs:line 245
|
--- End of inner exception stack trace ---
|
at Couchbase.Core.BucketBase.WaitUntilReadyAsync(TimeSpan timeout, WaitUntilReadyOptions options) in /Users/willbroadbelt/Documents/repos/couchbase/couchbase-net-client/src/Couchbase/Core/BucketBase.cs:line 250
|
at SdkdConsole.Daemon.Handle.GetBucketAsync(ICluster cluster) in /Users/willbroadbelt/Documents/repos/couchbase/sdkd-net/src/SdkdConsole/Daemon/Handle.cs:line 417
|
-----------------------Context Info---------------------------
|
null
|
|
--- End of inner exception stack trace ---
|
at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
|
at System.Threading.Tasks.Task`1.get_Result()
|
at SdkdConsole.Daemon.Handle.Run() in /Users/willbroadbelt/Documents/repos/couchbase/sdkd-net/src/SdkdConsole/Daemon/Handle.cs:line 109
|
warn: Couchbase.Core.Configuration.Server.ConfigHandler[7000]
|
Issue getting Cluster Map on server 172.23.111.129:11210!
|
System.ObjectDisposedException: Cannot access a disposed object.
|
Object name: 'DataFlowConnectionPool'.
|
at Couchbase.Utils.ThrowHelper.ThrowObjectDisposedException(String objectName) in /Users/willbroadbelt/Documents/repos/couchbase/couchbase-net-client/src/Couchbase/Utils/ThrowHelper.cs:line 50
|
at Couchbase.Core.IO.Connections.DataFlow.DataFlowConnectionPool.EnsureNotDisposed() in /Users/willbroadbelt/Documents/repos/couchbase/couchbase-net-client/src/Couchbase/Core/IO/Connections/DataFlow/DataFlowConnectionPool.cs:line 221
|
at Couchbase.Core.IO.Connections.DataFlow.DataFlowConnectionPool.SendAsync(IOperation operation, CancellationToken cancellationToken) in /Users/willbroadbelt/Documents/repos/couchbase/couchbase-net-client/src/Couchbase/Core/IO/Connections/DataFlow/DataFlowConnectionPool.cs:line 97
|
at Couchbase.Core.ClusterNode.<>c.<ExecuteOp>b__131_0(IOperation op2, Object state, CancellationToken effectiveToken) in /Users/willbroadbelt/Documents/repos/couchbase/couchbase-net-client/src/Couchbase/Core/ClusterNode.cs:line 645
|
at Couchbase.Core.ClusterNode.ExecuteOp(Func`4 sender, IOperation op, Object state, CancellationTokenPair tokenPair) in /Users/willbroadbelt/Documents/repos/couchbase/couchbase-net-client/src/Couchbase/Core/ClusterNode.cs:line 508
|
at Couchbase.Core.ClusterNode.GetClusterMap() in /Users/willbroadbelt/Documents/repos/couchbase/couchbase-net-client/src/Couchbase/Core/ClusterNode.cs:line 332
|
at Couchbase.Core.Configuration.Server.ConfigHandler.<Poll>b__13_0() in /Users/willbroadbelt/Documents/repos/couchbase/couchbase-net-client/src/Couchbase/Core/Configuration/Server/ConfigHandler.cs:line 109
|
Full sys logs here: SdkdConsole_ClustWaitFail.log and for the bucket wait until ready failure here: SdkdConsole_BucketWaitFail.log
Environment:
Dotnet client commit : 381c0b7c57733565e714cccdd9c3167bba512ece
Have tested this against CB Server 7.0.2 and 6.6.3.