View Issue Details

IDProjectCategoryView StatusLast Update
0001229SymmetricDSBugpublic2019-12-13 18:09
Reporterrotten Assigned To 
Prioritylow 
Status closedResolutionfixed 
Product Version3.4.0 
Target Version3.10.0Fixed in Version3.10.0 
Summary0001229: Opening registration causes nodes to complain until it registers
DescriptionI opened registration on a new node today. When I did, I noticed that other nodes in the cluster immediately began to complain (in their logs). They continued to complain every few minutes until the new node started and was registered.

At the same time, the registration server started throwing errors about the nodes trying to open redundant connections to it.

I would have expected everything to remain quiet and happy until I started up the new node and it registered itself and published its presence to the rest of the cluster.

The problem is it is hard to tell if something else is horribly aawry
Steps To ReproduceOpen registration for a new node in a busy cluster, but don't actually start it up and register it for a while.
Additional InformationOn random nodes in the cluster:

2013-05-16 15:34:01,556 WARN [SymmetricDS] [DefaultOfflineClientListener] [symmetricds-pull-4] Node 'newnode' was too busy to accept the connection

2013-05-16 15:34:16,573 INFO [SymmetricDS] [PullService] [symmetricds-pull-6] somenodegroup:newnode:newnode at http://registrationserver:registrationport/sync was busy

2013-05-16 15:34:16,574 WARN [SymmetricDS] [DefaultOfflineClientListener] [symmetricds-pull-6] Node 'newnode' was too busy to accept the connection

2013-05-16 15:34:31,610 INFO [SymmetricDS] [PullService] [symmetricds-pull-4] somenodegroup:newnode:newnode at http://registrationserver:registrationport/sync was busy


Meanwhile, on the registration server:

2013-05-16 15:26:12,883 WARN [SymmetricDS] [ConcurrentConnectionManager] [qtp1219100908-13662] Node 'someoldnode' requested a /sync/pull connection, but was rejected because it already has one

2013-05-16 15:26:15,504 WARN [SymmetricDS] [ConcurrentConnectionManager] [qtp1219100908-13647] Node 'someotheroldnode' requested a /sync/pull connection, but was rejected because it already has one

Tagsregistration

Relationships

related to 0002791 closedelong SymmetricDS Pro Every network error is logged and alerts user on Dashboard 
related to 0003865 closedelong SymmetricDS Improve logging readability and appropriate levels 

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2013-05-16 21:53 rotten New Issue
2019-04-22 13:04 elong Tag Attached: registration
2019-10-26 19:57 elong Relationship added related to 0002791
2019-10-26 19:57 elong Relationship added related to 0003865
2019-10-26 19:58 elong Status new => resolved
2019-10-26 19:58 elong Resolution open => fixed
2019-10-26 19:58 elong Fixed in Version => 3.10.0
2019-12-13 18:09 elong Status resolved => closed