View Issue Details

IDProjectCategoryView StatusLast Update
0005791SymmetricDSBugpublic2023-10-03 23:00
Reporterelong Assigned Toelong  
Prioritynormal 
Status closedResolutionfixed 
Product Version3.14.0 
Target Version3.14.7Fixed in Version3.14.7 
Summary0005791: Allow registration of other nodes after registration and initial load is complete
DescriptionRegistration of client nodes is allowed after the server node is registered and received an initial load. It currently only checks if registration has started and if initial load has started, not completed. Registration is started when the node gets its identity and the registration_time is set, and then it's completed when the registration_enabled flag is turned off. If a client node is registered before the server registration is completed, it can be left with a record showing registration_enabled is on. The initial_load_time shows when the load starts, and the initial_load_end_time shows when it is complete. If a client node is registered before the server initial load is complete, the server may capture and resend the initial load to the client.
TagsNo tags attached.

Activities

There are no notes attached to this issue.

Related Changesets

SymmetricDS: 3.14 c6485387

2023-04-17 12:36:56

admin

Details Diff
0005791: Allow registration of other nodes after registration and
initial load is complete
Affected Issues
0005791
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/RegistrationService.java Diff File

SymmetricDS: 3.15 ea014a8c

2023-04-17 12:36:56

admin

Details Diff
0005791: Allow registration of other nodes after registration and
initial load is complete
Affected Issues
0005791
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/RegistrationService.java Diff File

SymmetricDS: 3.14 16dfbf42

2023-04-17 12:37:18

admin

Details Diff
0005791: Better logging of registration Affected Issues
0005791
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/ManageIncomingBatchListener.java Diff File

Issue History

Date Modified Username Field Change
2023-04-17 12:35 elong New Issue
2023-04-17 12:35 elong Status new => assigned
2023-04-17 12:35 elong Assigned To => elong
2023-04-17 12:51 elong Status assigned => resolved
2023-04-17 12:51 elong Resolution open => fixed
2023-04-17 12:51 elong Fixed in Version => 3.14.7
2023-04-17 13:00 admin Changeset attached => SymmetricDS 3.14 16dfbf42
2023-04-17 13:00 admin Changeset attached => SymmetricDS 3.14 c6485387
2023-05-12 19:49 admin Status resolved => closed
2023-10-03 23:00 admin Changeset attached => SymmetricDS 3.15 ea014a8c