[TINKERPOP-1126] A single Host spawns many reconnect tasks

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Done
• Affects Version/s: 3.1.0-incubating
• Fix Version/s: 3.2.0-incubating, 3.1.2-incubating
• Component/s: driver
• Assignee: Stephen Mallette
• Reporter: Kieran Sherlock
• Created: 04/Feb/16 22:16
• Updated: 22/Feb/16 13:31
• Resolved: 22/Feb/16 13:31

Description

While attempting to recover a connection to a gremlin server that has gone offline, the Host object spawns many reconnect tasks

The following code in Host.makeUnavailable() will always create and schedule a new Runnable no matter the value of reconnectionAttempt

        reconnectionAttempt.compareAndSet(null,
                this.cluster.executor().scheduleAtFixedRate(() -> {
                            logger.debug("Trying to reconnect to dead host at {}", this);
                            if (reconnect.apply(this)) reconnected();
                        }, cluster.connectionPoolSettings().reconnectInitialDelay,
                        cluster.connectionPoolSettings().reconnectInterval, TimeUnit.MILLISECONDS));

It is just that the ScheduledFuture returned by scheduleAtFixedRate will be ignored if reconnectionAttempt != null.

Issue Links

• is related to: TINKERPOP-1125 RoundRobin load balancing always uses the second Host when size = 2