Skip to content

Improved stale JobSandbox recovery handling in multi-node environment [OFBIZ-13383]#1216

Open
Ankit-Joshi11 wants to merge 1 commit into
apache:trunkfrom
Ankit-Joshi11:OFBIZ-13383
Open

Improved stale JobSandbox recovery handling in multi-node environment [OFBIZ-13383]#1216
Ankit-Joshi11 wants to merge 1 commit into
apache:trunkfrom
Ankit-Joshi11:OFBIZ-13383

Conversation

@Ankit-Joshi11
Copy link
Copy Markdown
Contributor

Improved: Heartbeat based jobs tracking and recovering stale jobs that are still owned by the terminated or replaced nodes. Utilized atomic updates for the jobs heartbeat updates and recovering logic to avoid race conditions and state overriden between multiple nodes

…s OFBIZ-13383

Added heartbeat based jobs tracking and recovering stale jobs that are still owned by the terminated or replaced nodes.
Utilized atomic updates for the jobs heartbeat updates and recovering logic to avoid race conditions and state overriden between multiple nodes
EntityCondition.makeCondition(
EntityCondition.makeCondition("leaseUpdatedStamp", EntityOperator.LESS_THAN, expiryThreshold),
EntityOperator.OR,
EntityCondition.makeCondition("leaseUpdatedStamp", EntityOperator.EQUALS, null)));
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @Ankit-Joshi11
On environment with multiple pool, it would be useful to indicate to the JobManager to update only it dedicated pool ?

So add the condition
EntityCondition.makeCondition("poolId", EntityOperator.IN, getRunPools())

Or we just ignore the collision risk ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants