You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two eureka servers working in cluster mode and 3000+ eureka client instances. When one of the eureka servers restarts, I find that Eureka client gets only part of registered instances when the eureka server starts up in cluster mode.
According to information on the Internet, it will first retrieve the instance information from other cluster nodes and update the instance information to its own registry after the Eureka server starts. If the instance information fails to be retrieved, the Eureka server will retry after a period of time until the instance information is successfully retrieved.
I try to read source code of eureka and find this logic in PeerAwareInstanceRegistryImpl class.
/**
* Checks to see if the registry access is allowed or the server is in a
* situation where it does not all getting registry information. The server
* does not return registry information for a period specified in
* {@link EurekaServerConfig#getWaitTimeInMsWhenSyncEmpty()}, if it cannot
* get the registry information from the peer eureka nodes at start up.
*
* @return false - if the instances count from a replica transfer returned
* zero and if the wait time has not elapsed, otherwise returns true
*/
@Override
public boolean shouldAllowAccess(boolean remoteRegionRequired) {
if (this.peerInstancesTransferEmptyOnStartup) {
if (!(System.currentTimeMillis() > this.startupTime + serverConfig.getWaitTimeInMsWhenSyncEmpty())) {
return false;
}
}
if (remoteRegionRequired) {
for (RemoteRegionRegistry remoteRegionRegistry : this.regionNameVSRemoteRegistry.values()) {
if (!remoteRegionRegistry.isReadyForServingData()) {
return false;
}
}
}
return true;
}
startupTime's value is zero as default. And its values is changed by below method.
@Override
public void openForTraffic(ApplicationInfoManager applicationInfoManager, int count) {
// Renewals happen every 30 seconds and for a minute it should be a factor of 2.
this.expectedNumberOfClientsSendingRenews = count;
updateRenewsPerMinThreshold();
logger.info("Got {} instances from neighboring DS node", count);
logger.info("Renew threshold is: {}", numberOfRenewsPerMinThreshold);
this.startupTime = System.currentTimeMillis();
if (count > 0) {
this.peerInstancesTransferEmptyOnStartup = false;
}
DataCenterInfo.Name selfName = applicationInfoManager.getInfo().getDataCenterInfo().getName();
boolean isAws = Name.Amazon == selfName;
if (isAws && serverConfig.shouldPrimeAwsReplicaConnections()) {
logger.info("Priming AWS connections for all replicas..");
primeAwsReplicas(applicationInfoManager);
}
logger.info("Changing status to UP");
applicationInfoManager.setInstanceStatus(InstanceStatus.UP);
super.postInit();
}
But this method is not invoked before copying registry from neighboring eureka node is done. That means startupTime's value is zero when copying is processing. So System.currentTimeMillis() > this.startupTime + serverConfig.getWaitTimeInMsWhenSyncEmpty() will be true. This leads shouldAllowAccess method's logic does not take effect.
Below code works well in same case.
public boolean shouldAllowAccess(boolean remoteRegionRequired) {
if (this.peerInstancesTransferEmptyOnStartup) {
if (this.startupTime == 0 || !(System.currentTimeMillis() > this.startupTime + serverConfig.getWaitTimeInMsWhenSyncEmpty())) {
return false;
}
}
if (remoteRegionRequired) {
for (RemoteRegionRegistry remoteRegionRegistry : this.regionNameVSRemoteRegistry.values()) {
if (!remoteRegionRegistry.isReadyForServingData()) {
return false;
}
}
}
return true;
}
The text was updated successfully, but these errors were encountered:
I have two eureka servers working in cluster mode and 3000+ eureka client instances. When one of the eureka servers restarts, I find that Eureka client gets only part of registered instances when the eureka server starts up in cluster mode.
According to information on the Internet, it will first retrieve the instance information from other cluster nodes and update the instance information to its own registry after the Eureka server starts. If the instance information fails to be retrieved, the Eureka server will retry after a period of time until the instance information is successfully retrieved.
I try to read source code of eureka and find this logic in PeerAwareInstanceRegistryImpl class.
startupTime
's value is zero as default. And its values is changed by below method.But this method is not invoked before copying registry from neighboring eureka node is done. That means
startupTime
's value is zero when copying is processing. SoSystem.currentTimeMillis() > this.startupTime + serverConfig.getWaitTimeInMsWhenSyncEmpty()
will be true. This leadsshouldAllowAccess
method's logic does not take effect.Below code works well in same case.
The text was updated successfully, but these errors were encountered: