Hi, During the community sync Mit raised a concern about the recurrence of a panic in the User and Group tracking code. The panic occurs under high loads if a user or group is deleted while other actions are performed on the trackers. This was fixed as YUNIKORN-3004 [1]
As part of YuniKorn 1.6.1 we marked YUNIKORN-3004 as delivered and fixed. It was part of the release announcement [2]. On closer inspection of the commits this was incorrect as the commit was never cherry-picked into the 1.6 branch. This oversight has been fixed since the community sync. The fix has been backported into the branch-1.6 [3] and the k8shim updated to pick up the correct core. We are also planning to fixi the release noted for 1.6.1 and put a note in the 1.6.2 release note. Over the next few days we will trigger a new release (1.6.3) and make it available for voting. Wilfred [1] https://issues.apache.org/jira/browse/YUNIKORN-3004 [2] https://yunikorn.apache.org/release-announce/1.6.1/#improper-locking-in-usergroup-tracking [3] https://github.com/apache/yunikorn-core/commit/e69b21c6d6c5f4b18591be33bf5c8dd0c40c4dda --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
