Reorder try/catch for start/finish redis key #3370
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The track availability job takes longer than 30 seconds, and the lock is getting released before the end time stamp gets fulfilled. This is as shown as the key value is null for all discovery prod nodes.
This PR is to reorder when the redis timestamp gets filled
Tests
No new tests since there is no change in functionality, just reordering operations.
Monitoring - How will this change be monitored? Are there sufficient logs / alerts?
See log for
Could not get latest track unavailability job end timestamp
in discovery node.