java.util.concurrent.TimeoutException: Did not observe any item or terminal signal within 60000ms in 'source(MonoDefer)'

Can you help us analyze where this 60sec error log comes from? It says 60sec but we have changed to 100sec the default connection timeout. This error just happens when we restart the machine and CB service loads up with our wars being deployed. Maybe missing config?

OUR CONFIGURATION:
ClusterEnvironment env = ClusterEnvironment.builder()
.timeoutConfig(TimeoutConfig.connectTimeout(Duration.ofSeconds(100)).queryTimeout(Duration.ofSeconds(20))).build();

FROM THEIR TIMEOUT CLASS (NO 60sec)
public class TimeoutConfig {

public static final Duration DEFAULT_KV_TIMEOUT = Duration.ofMillis(2500);
public static final Duration DEFAULT_KV_DURABLE_TIMEOUT = Duration.ofSeconds(10);
public static final Duration DEFAULT_MANAGEMENT_TIMEOUT = Duration.ofSeconds(75);
public static final Duration DEFAULT_QUERY_TIMEOUT = Duration.ofSeconds(75);
public static final Duration DEFAULT_VIEW_TIMEOUT = Duration.ofSeconds(75);
public static final Duration DEFAULT_SEARCH_TIMEOUT = Duration.ofSeconds(75);
public static final Duration DEFAULT_ANALYTICS_TIMEOUT = Duration.ofSeconds(75);
public static final Duration DEFAULT_CONNECT_TIMEOUT = Duration.ofSeconds(10);
public static final Duration DEFAULT_DISCONNECT_TIMEOUT = Duration.ofSeconds(10);

EXCEPTION:

2020-08-14 13:06:20 WARN [LoggingEventConsumer.java:523] [com.couchbase.endpoint][EndpointConnectionFailedEvent][60s] Connect attempt 1 failed because of TimeoutException: Did not observe any item or terminal signal within 60000ms in ‘source(MonoDefer)’ (and no fallback has been configured) {“bucket”:“accounting”,“circuitBreaker”:“DISABLED”,“coreId”:“0xc9df432700000001”,“remote”:“172.31.35.186:11210”,“type”:“KV”}
java.util.concurrent.TimeoutException: Did not observe any item or terminal signal within 60000ms in ‘source(MonoDefer)’ (and no fallback has been configured)
at reactor.core.publisher.FluxTimeout$TimeoutMainSubscriber.handleTimeout(FluxTimeout.java:289)
at reactor.core.publisher.FluxTimeout$TimeoutMainSubscriber.doTimeout(FluxTimeout.java:274)
at reactor.core.publisher.FluxTimeout$TimeoutTimeoutSubscriber.onNext(FluxTimeout.java:396)
at reactor.core.publisher.StrictSubscriber.onNext(StrictSubscriber.java:89)
at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:73)
at reactor.core.publisher.MonoDelay$MonoDelayRunnable.run(MonoDelay.java:117)
at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:68)
at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:28)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

Hi Nikhil,

Did you got the solution of your problem coz I am also facing same issue locally. Kindly reply.

Thanks,
Arunendu Ravi

@Nikhil_Singh @Arunendu any luck in resolving this issue?

No we were not able to solve this.

Hey @Nikhil_Singh by any chance you got a solution for this?