| Summary |
0004550: Initial load time empty at client |
|
| Revision |
2020-09-16 14:53 by elong |
|
| Description |
The initial load service can start the initial load and record the initial load time before registration is complete, which leads to the initial load time being left as null at the client. For multi-primary or multi-tier configurations, this can prevent the client node from allowing registrations to it. There are three states to registration: 1) registration flag on, registration time null, 2) registration flag on, registration time set, 3) registration flag off, registration time set. For state 2, the registration is still pending, so initial load service should wait until state 3 is reached. |
|
| Revision |
2020-09-16 14:53 by elong |
|
| Description |
The initial load service can start the initial load and record the initial load time before registration is complete, which leads to the initial load time being left as null at the client. For multi-primary or multi-tier configurations, this can prevent the client node from allowing registrations to it. There are three states to registration: 1) registration flag on, registration time null, 2) registration flag on, registration time set, 3) registration flag off, registration time set. For state 0000002, the registration is still pending, so initial load service should wait until state 3 is reached. |