Wilfred Spiegelenburg created YUNIKORN-2630:
---
Summary: Release context lock in shim when processing config in
the core
Key: YUNIKORN-2630
URL: https://issues.apache.org/jira/browse/YUNIKORN-2630
[
https://issues.apache.org/jira/browse/YUNIKORN-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg resolved YUNIKORN-2628.
-
Fix Version/s: 1.6.0
Resolution: Fixed
links are fixed after
Thanks for confirming. I think we should go for 1.5.2 and leave 1.5.1 as is. As
Craig said, tags should remain immutable.
-Mit
From: Peter Bacsko
Date: Thursday, May 16, 2024 at 12:35 PM
To: dev@yunikorn.apache.org
Subject: Re: [VOTE] Release Apache YuniKorn 1.5.1 RC1
Yes, that is correct.
Yes, that is correct.
On Thu, May 16, 2024 at 8:54 PM Desai, Mit wrote:
> This issue could also be faced by non-autoscaled clusters who still gets a
> node added at some point. Right?
>
> -Mit
>
> From: Peter Bacsko
> Date: Thursday, May 16, 2024 at 11:23 AM
> To: dev@yunikorn.apache.org
>
This issue could also be faced by non-autoscaled clusters who still gets a node
added at some point. Right?
-Mit
From: Peter Bacsko
Date: Thursday, May 16, 2024 at 11:23 AM
To: dev@yunikorn.apache.org
Subject: Re: [VOTE] Release Apache YuniKorn 1.5.1 RC1
I'm fine with either approach. If it's
I'm fine with either approach. If it's too late, then let's go ahead with
1.5.1.
Maybe it's better this way because we can do a more thorough verification.
Peter
On Thu, May 16, 2024 at 8:15 PM Craig Condit wrote:
> IMO, it’s too late to update 1.5.1. We’ve already cut the tags, and those
>
IMO, it’s too late to update 1.5.1. We’ve already cut the tags, and those must
remain immutable. Our best bet would probably be to continue with 1.5.1 as-is;
the new issue is unlikely to affect non-autoscaled clusters and it’s better
than 1.5.0. We should, I think, get this latest issue fixed
Dear community,
I've been working together with Jacob Salway on an issue and we found out
that there's one more deadlock in the shim which can be triggered when a
new node is added. This means that an autoscaler setup is prone to a
deadlock.
I filed a JIRA which explains the problem:
Peter Bacsko created YUNIKORN-2629:
--
Summary: Adding a node can result in a deadlock
Key: YUNIKORN-2629
URL: https://issues.apache.org/jira/browse/YUNIKORN-2629
Project: Apache YuniKorn
[
https://issues.apache.org/jira/browse/YUNIKORN-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko resolved YUNIKORN-2612.
Fix Version/s: 1.5.1
Resolution: Fixed
> Tagging for 1.5.1
> -
>
[
https://issues.apache.org/jira/browse/YUNIKORN-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved YUNIKORN-2602.
--
Fix Version/s: 1.6.0
Resolution: Fixed
> Fix spelling/grammar in
+1 binding
- Built images from source (amd64) on Ubuntu 22.04
- Run make test && make image
- Run it on a local cluster
- Checked some REST API endpoints
- Ran sample jobs
Thank you all for the voting on the RC1 for 1.5.1.
Voting for the release has passed with:
5 binding +1
3 non binding +1
[
https://issues.apache.org/jira/browse/YUNIKORN-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg resolved YUNIKORN-2627.
-
Fix Version/s: 1.6.0
Resolution: Fixed
Upgrdaed kind to
13 matches
Mail list logo
