tree 680ca1b36a0fe47459a20008c20af8ca1d7a4be6
parent 041075cd5d83e20952970c2be17e3e3911d9ccd8
author mynameborat <bharath.kumarasubramanian@gmail.com> 1631382024 -0700
committer GitHub <noreply@github.com> 1631382024 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJhPOoICRBK7hj4Ov3rIwAAD2wIAIV6SNgdW+Y2f7Ll+09Wt3dV
 mLNh5XDYpKFwq+9Ce3gMmc5kB9gjktx+ujb5dpHcyVkX9p/kYodWxuy+G8Xxv+JA
 ZE1CxR69m5ro7mv8El78eSPpUaSQww+rf9GMYltQwM8/KHEDW35gYZc9ZqHWNcJS
 poLFUnxNo6n9kJVxeaPlJM56XvprfXHxjBXQGFHyt+B9o9JwlfCgw4XOvuNkfrog
 8MveGiX5HXUeNqfVvkfRUBbZhXk4WBi4cZUqu/0UW/mW4J/XIp9sk44sgNTQKsg9
 Gt/SEcZOXEENpReu1BzvKw4EvVO3uvecEhyRJt+so+tTtGY1YKau1KhOURtFXO4=
 =hvas
 -----END PGP SIGNATURE-----
 

SAMZA-2663: Handle job model expiration and new job model flows for multiple incomplete rebalances (#1528)

Problem:
As part of SAMZA-2638, we introduced skipping container restart and stops on no changes to work assignment for processors across rebalances. However, we only update the active job model with the proposed job model on starting the container as part of onNewJobModel. This leads to a scenario where the processor is stopped but the future rebalances assume the container is still running. More information on scenario below.

Changes:

Track job model expiration
onNewJobModel triggers new job model as long as the active job model has been expired
Handle no change in work assignment optimization only during checkJobModelExpired flow.