| Summary |
0006735: When cluster.lock.enabled is set to false, the unrouted data count is incorrect before the route job runs for the first time |
|
| Revision |
2025-02-25 16:13 by emiller |
|
| Description |
Before the route job runs, if the cluster.lock.enabled parameter is set to false, the unrouted data count is equal to the max data_id + 1. In the Pro version, if the user has a monitor configured for unrouted data, the very high unrouted data count will most likely cause the monitor to go off. |
|
| Revision |
2025-02-25 16:22 by emiller |
|
| Description |
Before the route job runs for the first time after startup, if the cluster.lock.enabled parameter is set to false, the unrouted data count is equal to the max data_id + 1. In the Pro version, if the user has a monitor configured for unrouted data, the very high unrouted data count will most likely cause the monitor to go off. |