[jira] [Assigned] (YUNIKORN-336) Sync application states from k8shim and core side
[ https://issues.apache.org/jira/browse/YUNIKORN-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton reassigned YUNIKORN-336: - Assignee: (was: Kinga Marton) > Sync application states from k8shim and core side > - > > Key: YUNIKORN-336 > URL: https://issues.apache.org/jira/browse/YUNIKORN-336 > Project: Apache YuniKorn > Issue Type: Improvement >Reporter: Kinga Marton >Priority: Major > > Right now the application states are not in sync between the core and shim > side. Also there are some states available in the shim what are not available > in the core side: > [https://github.com/apache/incubator-yunikorn-k8shim/blob/master/pkg/cache/application.go#L71-L101] > > [https://github.com/apache/incubator-yunikorn-core/blob/master/pkg/cache/application_state.go#L70-L100] > This should be in synch. Let's try to centralise the states and keep them in > synch. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-455) Make the core configurable
[ https://issues.apache.org/jira/browse/YUNIKORN-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton reassigned YUNIKORN-455: - Assignee: (was: Kinga Marton) > Make the core configurable > -- > > Key: YUNIKORN-455 > URL: https://issues.apache.org/jira/browse/YUNIKORN-455 > Project: Apache YuniKorn > Issue Type: Improvement >Reporter: Kinga Marton >Priority: Major > > There are some startup options in the core side, but they are not > configurable from outside. > Also make the reservation expiration configurable as well. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-560) Yunikorn recovery deletes existing placeholders
[ https://issues.apache.org/jira/browse/YUNIKORN-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton reassigned YUNIKORN-560: - Assignee: (was: Kinga Marton) > Yunikorn recovery deletes existing placeholders > --- > > Key: YUNIKORN-560 > URL: https://issues.apache.org/jira/browse/YUNIKORN-560 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: shim - kubernetes >Reporter: Kinga Marton >Priority: Major > Labels: recovery > > On recovery, Yunikorn may intermittently delete placeholder pods. To > reproduce, submit a gang job with minMembers > job parallelism (to guarantee > that there are some placeholders running) and then delete yunikorn scheduler > pod. > After recovery, there may not be any placeholder pods remaining. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-407) Create a design doc on the website
[ https://issues.apache.org/jira/browse/YUNIKORN-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton reassigned YUNIKORN-407: - Assignee: (was: Kinga Marton) > Create a design doc on the website > -- > > Key: YUNIKORN-407 > URL: https://issues.apache.org/jira/browse/YUNIKORN-407 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: documentation >Reporter: Weiwei Yang >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-457) Find a way to pass the RMID to the webservice
[ https://issues.apache.org/jira/browse/YUNIKORN-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton reassigned YUNIKORN-457: - Assignee: (was: Kinga Marton) > Find a way to pass the RMID to the webservice > - > > Key: YUNIKORN-457 > URL: https://issues.apache.org/jira/browse/YUNIKORN-457 > Project: Apache YuniKorn > Issue Type: Bug >Reporter: Kinga Marton >Priority: Major > > When updating the configuration through the REST API, we need an RMId to > reflect the changes in the configmap as well. With the actual approach this > might not work properly if we would have more than one RM registered, or if > we don't have any RM's. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-588) Placeholder pods are not cleaned up timely when the Spark driver fails
[ https://issues.apache.org/jira/browse/YUNIKORN-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton reassigned YUNIKORN-588: - Assignee: (was: Kinga Marton) > Placeholder pods are not cleaned up timely when the Spark driver fails > -- > > Key: YUNIKORN-588 > URL: https://issues.apache.org/jira/browse/YUNIKORN-588 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: shim - kubernetes >Affects Versions: 0.10 >Reporter: Chaoran Yu >Priority: Major > Labels: spark > Attachments: Screen Shot 2021-03-19 at 9.41.48 PM.png > > > When a Spark job is gang scheduled, if the driver pod fails immediately upon > running (e.g. due to an error in the Spark application code), the placeholder > pods will still try to reserve resources. They won't be terminated until > after the configured timeout has passed, even though they should have been > cleaned up the moment that the driver failed. Because we already knew at that > point, none of the executors would have a chance to start. > Something probably needs to be done at the Spark operator plugin level to > activate placeholder cleanup to release resources sooner. > Edit: Actually a fix needs to be developed without the Spark operator plugin > because the user might not be using it. The Spark job could well have been > submitted via spark-submit. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-941) split scheduler and admission controller deployment
[ https://issues.apache.org/jira/browse/YUNIKORN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton reassigned YUNIKORN-941: - Assignee: Peter Bacsko (was: Kinga Marton) > split scheduler and admission controller deployment > --- > > Key: YUNIKORN-941 > URL: https://issues.apache.org/jira/browse/YUNIKORN-941 > Project: Apache YuniKorn > Issue Type: Improvement > Components: shim - kubernetes >Reporter: Kinga Marton >Assignee: Peter Bacsko >Priority: Blocker > Labels: pull-request-available > > To support proper YuniKorn upgrades and restarts we should move the admission > controller out of the scheduler deployment and make it a separate deployment. > This could also allow the admission controller to be made high available and > allow simpler no down time upgrades possible. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-316) Automate helm chart generation
[ https://issues.apache.org/jira/browse/YUNIKORN-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-316. --- Resolution: Not A Bug > Automate helm chart generation > --- > > Key: YUNIKORN-316 > URL: https://issues.apache.org/jira/browse/YUNIKORN-316 > Project: Apache YuniKorn > Issue Type: Bug > Components: build >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > > Right now we have a helm chart package for the latest version as well. That > means that we have to regenerate it after each change in our helm chart. > Also the actual name of the chart including the latest app is 0.9.0. We > should choose a better naming, that will not cause conflicts and > misunderstandings. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-941) split scheduler and admission controller deployment
[ https://issues.apache.org/jira/browse/YUNIKORN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455091#comment-17455091 ] Kinga Marton commented on YUNIKORN-941: --- [~yuchaoran], [~wilfreds] I suggest to move out this issue from the 0.12 release. And remove the changes from the release repository from the 0.12 branch after it will be created. I am suggesting this because I found the root cause of the failing precommit: the secret is not created at the pint we want to mount it. The secret is created in the admission_util.sh script, what is running in a post start hook. And here we have a chicken and egg problem: * the secret needs the TLS certs, which are creeated fron the admission controller code, so in the actual setup we cannot create the secret in an init container. Instead of continuing to hack around the admission controller I suggest to remove the admission_util.sh script and use init containers for creating all the necessary certificates and secrets, but this is a bigger work. There is a good article about how we can create the admission controllers in a more elegant way than we are doing it now: [https://www.velotio.com/engineering-blog/managing-tls-certificate-for-kubernetes-admission-webhook] > split scheduler and admission controller deployment > --- > > Key: YUNIKORN-941 > URL: https://issues.apache.org/jira/browse/YUNIKORN-941 > Project: Apache YuniKorn > Issue Type: Improvement > Components: shim - kubernetes >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Blocker > Labels: pull-request-available > > To support proper YuniKorn upgrades and restarts we should move the admission > controller out of the scheduler deployment and make it a separate deployment. > This could also allow the admission controller to be made high available and > allow simpler no down time upgrades possible. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-964) Fix vulnerabilities reported by artifacthub
Kinga Marton created YUNIKORN-964: - Summary: Fix vulnerabilities reported by artifacthub Key: YUNIKORN-964 URL: https://issues.apache.org/jira/browse/YUNIKORN-964 Project: Apache YuniKorn Issue Type: Bug Reporter: Kinga Marton Fix For: 0.12 Artifacthub has a security report for each image. We need to check and fix the reported vulnerabilities: [https://artifacthub.io/packages/helm/yunikorn/yunikorn/0.11.0?modal=security-report] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-941) split scheduler and admission controller deployment
[ https://issues.apache.org/jira/browse/YUNIKORN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17452833#comment-17452833 ] Kinga Marton commented on YUNIKORN-941: --- Thank you [~yuchaoran2011] for the review in the release repository. Can you please check the shim side changes as well? This 2 are depending on each other. [https://github.com/apache/incubator-yunikorn-k8shim/pull/331] > split scheduler and admission controller deployment > --- > > Key: YUNIKORN-941 > URL: https://issues.apache.org/jira/browse/YUNIKORN-941 > Project: Apache YuniKorn > Issue Type: Improvement > Components: shim - kubernetes >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Blocker > Labels: pull-request-available > > To support proper YuniKorn upgrades and restarts we should move the admission > controller out of the scheduler deployment and make it a separate deployment. > This could also allow the admission controller to be made high available and > allow simpler no down time upgrades possible. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-941) split scheduler and admission controller deployment
[ https://issues.apache.org/jira/browse/YUNIKORN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17452463#comment-17452463 ] Kinga Marton commented on YUNIKORN-941: --- Some note on the newly created charts: * as [~yuchaoran2011] suggested, we will use a subchart for the admission controller. * since during a YK upgrade we want to make sure that no pods will be handled by the default scheduler during the YK downtime, it is essentially to have the admission controlller running when the scheduler will be upgraded. By using seubcharts this is possible with the following steps: ** update the admission controller (helm upgrade will do the upgrade only if there are some chnges, so for this steps we need to make sure that there are no changes in the scheduler) ** after the admission controller is updated, we can update the helm deployment again and include the scheduler changes as well. Since helm will detect the admission controller it is already up to date, it won't touch it. * We need to do the upgrade in this two steps, because during a normal upgrade helm aggregates all the manifests into one and then it will sort them according to their type and alphabetically, but will not wait for the dependeies being installed first. See more details in the following Helm documentation: [https://helm.sh/docs/topics/charts/#operational-aspects-of-using-dependencies] > split scheduler and admission controller deployment > --- > > Key: YUNIKORN-941 > URL: https://issues.apache.org/jira/browse/YUNIKORN-941 > Project: Apache YuniKorn > Issue Type: Improvement > Components: shim - kubernetes >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > Labels: pull-request-available > > To support proper YuniKorn upgrades and restarts we should move the admission > controller out of the scheduler deployment and make it a separate deployment. > This could also allow the admission controller to be made high available and > allow simpler no down time upgrades possible. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-952) nil pointer error in webservice.getApplicationJSON()
[
https://issues.apache.org/jira/browse/YUNIKORN-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton resolved YUNIKORN-952.
---
Fix Version/s: 0.12
Resolution: Fixed
> nil pointer error in webservice.getApplicationJSON()
>
>
> Key: YUNIKORN-952
> URL: https://issues.apache.org/jira/browse/YUNIKORN-952
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Labels: pull-request-available
> Fix For: 0.12
>
>
> The implementation of the new method {{getApplicationsDAO()}} is incorrect:
> {noformat}
> func getApplicationsDAO(lists map[string]*scheduler.PartitionContext)
> []*dao.ApplicationDAOInfo {
> result := make([]*dao.ApplicationDAOInfo, 0, 32)
> for _, partition := range lists {
> size := partition.GetTotalCompletedApplicationCount() +
> partition.GetTotalApplicationCount()
> appList := make([]*objects.Application, size)
> appList = append(appList, partition.GetApplications()...)
> appList = append(appList,
> partition.GetCompletedApplications()...)
>
> {noformat}
> The slice creation is incorrect - the initial length should be 0, and the
> capacity should be set to the "size":
> {noformat}
> appList := make([]*objects.Application, 0, size)
> {noformat}
> Right now appList will contail "nil" elements after creation:
> {noformat}
> goroutine 847 [running]:
> net/http.(*conn).serve.func1()
> /snap/go/8627/src/net/http/server.go:1801 +0xb9
> panic({0x14c04e0, 0x2476930})
> /snap/go/8627/src/runtime/panic.go:1047 +0x266
> github.com/apache/incubator-yunikorn-core/pkg/scheduler/objects.(*Application).GetAllAllocations(0x)
>
> /home/bacskop/repos/yunikorn-core/pkg/scheduler/objects/application.go:1134
> +0x51
> github.com/apache/incubator-yunikorn-core/pkg/webservice.getApplicationJSON(0x0)
> /home/bacskop/repos/yunikorn-core/pkg/webservice/handlers.go:250 +0x36
> github.com/apache/incubator-yunikorn-core/pkg/webservice.getApplicationsDAO(0xc006916270)
> /home/bacskop/repos/yunikorn-core/pkg/webservice/handlers.go:632 +0x313
> github.com/apache/incubator-yunikorn-core/pkg/webservice.doStateDump({0x188dee0,
> 0xc0002400e0})
> /home/bacskop/repos/yunikorn-core/pkg/webservice/state_dump.go:143
> +0x158
> github.com/apache/incubator-yunikorn-core/pkg/webservice.getFullStateDump({0x18b5138,
> 0xc0002400e0}, 0x489bf7)
> /home/bacskop/repos/yunikorn-core/pkg/webservice/state_dump.go:67 +0x45
> net/http.HandlerFunc.ServeHTTP(0x100, {0x18b5138, 0xc0002400e0},
> 0x90)
> /snap/go/8627/src/net/http/server.go:2046 +0x2f
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Comment Edited] (YUNIKORN-941) split scheduler and admission controller deployment
[ https://issues.apache.org/jira/browse/YUNIKORN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17448112#comment-17448112 ] Kinga Marton edited comment on YUNIKORN-941 at 11/23/21, 5:14 PM: -- I created the following 2 PR's: [https://github.com/apache/incubator-yunikorn-release/pull/50] [https://github.com/apache/incubator-yunikorn-k8shim/pull/331] In this PR's I just moved away the admission controller related things from the scheduler image. However now we have it in a different deployment, independently from the scheduler, I mould move forward and try to remove the admission_utils.sh script, and handle the admission controller from helm charts or from code, without running shell scripts. was (Author: kmarton): I created the following 2 PR's: [https://github.com/apache/incubator-yunikorn-release/pull/50] [https://github.com/apache/incubator-yunikorn-k8shim/pull/331] In this PR's I just moved away the admission controller related things from the scheduler image. However now we have it in a different deployment, independently from the scheduler, I mould moove forward and try to remove the admission_utils.sh script, and handle the admission controller from helm charts or from code, without running shell scripts. > split scheduler and admission controller deployment > --- > > Key: YUNIKORN-941 > URL: https://issues.apache.org/jira/browse/YUNIKORN-941 > Project: Apache YuniKorn > Issue Type: Improvement > Components: shim - kubernetes >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > Labels: pull-request-available > > To support proper YuniKorn upgrades and restarts we should move the admission > controller out of the scheduler deployment and make it a separate deployment. > This could also allow the admission controller to be made high available and > allow simpler no down time upgrades possible. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-941) split scheduler and admission controller deployment
[ https://issues.apache.org/jira/browse/YUNIKORN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17448112#comment-17448112 ] Kinga Marton commented on YUNIKORN-941: --- I created the following 2 PR's: [https://github.com/apache/incubator-yunikorn-release/pull/50] [https://github.com/apache/incubator-yunikorn-k8shim/pull/331] In this PR's I just moved away the admission controller related things from the scheduler image. However now we have it in a different deployment, independently from the scheduler, I mould moove forward and try to remove the admission_utils.sh script, and handle the admission controller from helm charts or from code, without running shell scripts. > split scheduler and admission controller deployment > --- > > Key: YUNIKORN-941 > URL: https://issues.apache.org/jira/browse/YUNIKORN-941 > Project: Apache YuniKorn > Issue Type: Improvement > Components: shim - kubernetes >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > > To support proper YuniKorn upgrades and restarts we should move the admission > controller out of the scheduler deployment and make it a separate deployment. > This could also allow the admission controller to be made high available and > allow simpler no down time upgrades possible. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-948) Data race in TestGetSchedulerHealthStatusContext
[
https://issues.apache.org/jira/browse/YUNIKORN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton resolved YUNIKORN-948.
---
Fix Version/s: 0.12
Resolution: Fixed
Thank you [~pbacsko] fox fixing it so quickly!
> Data race in TestGetSchedulerHealthStatusContext
> -
>
> Key: YUNIKORN-948
> URL: https://issues.apache.org/jira/browse/YUNIKORN-948
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: test - unit
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Labels: pull-request-available
> Fix For: 0.12
>
>
> When running the unit tests, the following data occurred:
> {noformat}
> ==
> WARNING: DATA RACE
> Write at 0x00c000398bd0 by goroutine 21:
> runtime.mapassign_faststr()
> /snap/go/8627/src/runtime/map_faststr.go:202 +0x0
>
> github.com/apache/incubator-yunikorn-core/pkg/scheduler.TestGetSchedulerHealthStatusContext()
>
> /home/bacskop/repos/incubator-yunikorn-core/pkg/scheduler/health_checker_test.go:100
> +0xc64
> testing.tRunner()
> /snap/go/8627/src/testing/testing.go:1259 +0x22f
> testing.(*T).Run·dwrap·21()
> /snap/go/8627/src/testing/testing.go:1306 +0x47
> Previous read at 0x00c000398bd0 by goroutine 23:
> runtime.mapiterinit()
> /snap/go/8627/src/runtime/map.go:802 +0x0
>
> github.com/apache/incubator-yunikorn-core/pkg/scheduler.(*PartitionContext).GetAppsByState()
>
> /home/bacskop/repos/incubator-yunikorn-core/pkg/scheduler/partition.go:1079
> +0x186
>
> github.com/apache/incubator-yunikorn-core/pkg/scheduler.(*PartitionContext).cleanupExpiredApps()
>
> /home/bacskop/repos/incubator-yunikorn-core/pkg/scheduler/partition.go:1364
> +0x4f
>
> github.com/apache/incubator-yunikorn-core/pkg/scheduler.partitionManager.cleanupExpiredApps()
>
> /home/bacskop/repos/incubator-yunikorn-core/pkg/scheduler/partition_manager.go:154
> +0x64
>
> github.com/apache/incubator-yunikorn-core/pkg/scheduler.partitionManager.Run·dwrap·45()
>
> /home/bacskop/repos/incubator-yunikorn-core/pkg/scheduler/partition_manager.go:57
> +0x64
> Goroutine 21 (running) created at:
> testing.(*T).Run()
> /snap/go/8627/src/testing/testing.go:1306 +0x726
> testing.runTests.func1()
> /snap/go/8627/src/testing/testing.go:1598 +0x99
> testing.tRunner()
> /snap/go/8627/src/testing/testing.go:1259 +0x22f
> testing.runTests()
> /snap/go/8627/src/testing/testing.go:1596 +0x7ca
> testing.(*M).Run()
> /snap/go/8627/src/testing/testing.go:1504 +0x9d1
> main.main()
> _testmain.go:197 +0x324
> Goroutine 23 (running) created at:
>
> github.com/apache/incubator-yunikorn-core/pkg/scheduler.partitionManager.Run()
>
> /home/bacskop/repos/incubator-yunikorn-core/pkg/scheduler/partition_manager.go:57
> +0x34b
>
> github.com/apache/incubator-yunikorn-core/pkg/scheduler.(*ClusterContext).updateSchedulerConfig·dwrap·6()
>
> /home/bacskop/repos/incubator-yunikorn-core/pkg/scheduler/context.go:329 +0x64
> ==
> --- FAIL: TestGetSchedulerHealthStatusContext (0.00s)
> testing.go:1152: race detected during execution of test
> {noformat}
> Let's use {{PartitionContext.AddApplication()}} which uses locking instead of
> directly manipulating the map.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-945) state dump testing improvements
[
https://issues.apache.org/jira/browse/YUNIKORN-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton resolved YUNIKORN-945.
---
Fix Version/s: 0.12
Resolution: Fixed
> state dump testing improvements
> ---
>
> Key: YUNIKORN-945
> URL: https://issues.apache.org/jira/browse/YUNIKORN-945
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: core - scheduler
>Reporter: Wilfred Spiegelenburg
>Assignee: Peter Bacsko
>Priority: Minor
> Labels: pull-request-available
> Fix For: 0.12
>
>
> Cleanup tasks for the tests:
> * The tests use GET requests while the definition is a PUT for
> {{periodicstatedump}}
> * {{assert.NilError()}} calls do not line up with the err returned by
> {{http.NewRequest}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-947) Add missing fields to the admission wehooks
Kinga Marton created YUNIKORN-947: - Summary: Add missing fields to the admission wehooks Key: YUNIKORN-947 URL: https://issues.apache.org/jira/browse/YUNIKORN-947 Project: Apache YuniKorn Issue Type: Bug Components: shim - kubernetes Reporter: Kinga Marton Assignee: Kinga Marton v1 api has 2 extra mandatory fields: admissionReviewVersions and sideEffects, what were not there in v1beta1 bersion. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-943) Document new state dump features introduced in YUNIKORN-940
[ https://issues.apache.org/jira/browse/YUNIKORN-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-943. --- Fix Version/s: 0.12 Resolution: Fixed > Document new state dump features introduced in YUNIKORN-940 > > > Key: YUNIKORN-943 > URL: https://issues.apache.org/jira/browse/YUNIKORN-943 > Project: Apache YuniKorn > Issue Type: Task > Components: documentation >Reporter: Peter Bacsko >Assignee: Peter Bacsko >Priority: Major > Labels: pull-request-available > Fix For: 0.12 > > > We added new features and REST endpoints in YUNIKORN-940. The documentation > should be updated accordingly. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-941) split scheduler and admission controller deployment
[ https://issues.apache.org/jira/browse/YUNIKORN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton reassigned YUNIKORN-941: - Assignee: Kinga Marton > split scheduler and admission controller deployment > --- > > Key: YUNIKORN-941 > URL: https://issues.apache.org/jira/browse/YUNIKORN-941 > Project: Apache YuniKorn > Issue Type: Improvement > Components: shim - kubernetes >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > > To support proper YuniKorn upgrades and restarts we should move the admission > controller out of the scheduler deployment and make it a separate deployment. > This could also allow the admission controller to be made high available and > allow simpler no down time upgrades possible. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-940) Periodic & on-demand state dump in Yunikorn
[ https://issues.apache.org/jira/browse/YUNIKORN-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-940. --- Fix Version/s: 0.12 Resolution: Fixed Thank you [~pbacsko] for working on this. I merged your PR to master > Periodic & on-demand state dump in Yunikorn > --- > > Key: YUNIKORN-940 > URL: https://issues.apache.org/jira/browse/YUNIKORN-940 > Project: Apache YuniKorn > Issue Type: Improvement > Components: core - scheduler, shim - kubernetes >Reporter: Peter Bacsko >Assignee: Peter Bacsko >Priority: Major > Labels: pull-request-available > Fix For: 0.12 > > > Currently, there are many REST endpoints in Yunikorn which provide a bunch of > useful information about applications, nodes, node utilization, etc. > However, it requires many round trips to retrieve all of these. Also, it is > often beneficial to periodically log detailed state information. > The scope of this ticket is: > * Introduce new REST endpoint which collects and returns all info which is > currently available separately > * Refactor code (extract DAO generating methods) > * Add new REST endpoints which enables/disables periodic state logging -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-782) Implement proper cleanup when a node is removed
[ https://issues.apache.org/jira/browse/YUNIKORN-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-782. --- Resolution: Duplicate > Implement proper cleanup when a node is removed > --- > > Key: YUNIKORN-782 > URL: https://issues.apache.org/jira/browse/YUNIKORN-782 > Project: Apache YuniKorn > Issue Type: Bug > Components: core - scheduler >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > > Right now when a node is removed, we just simply remove the allocations, > without doing a proper rollback for the in progress allocations. This might > cause some issues for example for GS (driver pods stuck in pending state) -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-782) Implement proper cleanup when a node is removed
[ https://issues.apache.org/jira/browse/YUNIKORN-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton updated YUNIKORN-782: -- Description: Right now when a node is removed, we just simply remove the allocations, without doing a proper rollback for the in progress allocations. This might cause some issues for example for GS (driver pods stuck in pending state) (was: Right now when a node is removed, we just simply remove the allocations, without doing a proper rollback for thee in progress allocations. This might cause some issues for example for GS (driver pods stuck in pending state)) > Implement proper cleanup when a node is removed > --- > > Key: YUNIKORN-782 > URL: https://issues.apache.org/jira/browse/YUNIKORN-782 > Project: Apache YuniKorn > Issue Type: Bug > Components: core - scheduler >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > > Right now when a node is removed, we just simply remove the allocations, > without doing a proper rollback for the in progress allocations. This might > cause some issues for example for GS (driver pods stuck in pending state) -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-932) Improve logging reliability
[ https://issues.apache.org/jira/browse/YUNIKORN-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-932. --- Fix Version/s: 0.12 Resolution: Fixed > Improve logging reliability > --- > > Key: YUNIKORN-932 > URL: https://issues.apache.org/jira/browse/YUNIKORN-932 > Project: Apache YuniKorn > Issue Type: Improvement >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > Labels: pull-request-available > Fix For: 0.12 > > > There are cases wheen our logs are not relyable. For example we have seen in > case of some escalations missing logs for hours and we don't know that it was > because the cluster was not heavily used, or it was some issues. > We need to add some log messages for the following cases: > * log a message periodically if there are no pending requests > * log a message in case of recovery if we haven't heared anything from the > API server for a while > Also it may worth to check the main log paths and extend the logs where it is > necessary. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-941) split scheduler and admission controller deployment
Kinga Marton created YUNIKORN-941: - Summary: split scheduler and admission controller deployment Key: YUNIKORN-941 URL: https://issues.apache.org/jira/browse/YUNIKORN-941 Project: Apache YuniKorn Issue Type: Improvement Components: shim - kubernetes Reporter: Kinga Marton To support proper YuniKorn upgrades and restarts we should move the admission controller out of the scheduler deployment and make it a separate deployment. This could also allow the admission controller to be made high available and allow simpler no down time upgrades possible. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-939) shim e2e tests fail on go 1.15
[
https://issues.apache.org/jira/browse/YUNIKORN-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton resolved YUNIKORN-939.
---
Fix Version/s: 0.12
Resolution: Fixed
> shim e2e tests fail on go 1.15
> --
>
> Key: YUNIKORN-939
> URL: https://issues.apache.org/jira/browse/YUNIKORN-939
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: build, test - e2e
>Reporter: Wilfred Spiegelenburg
>Assignee: Peter Bacsko
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 0.12
>
>
> Looks like we need to update to Go 1.16 to get the e2e tests to work again:
> {code:java}
> # github.com/onsi/gomega/matchers
> Error:
> /home/runner/go/pkg/mod/github.com/onsi/gomega@v1.17.0/matchers/have_http_body_matcher.go:84:30:
> undefined: io.ReadAll
> Error:
> /home/runner/go/pkg/mod/github.com/onsi/gomega@v1.17.0/matchers/have_http_status_matcher.go:81:16:
> undefined: io.ReadAll
> note: module requires Go 1.16 {code}
> This is caused by the deprecation of the ioutil package in go 1.16. ReadAll
> was moved into the io package.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-938) Admission controller: remove v1beta1 usage
[
https://issues.apache.org/jira/browse/YUNIKORN-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton reassigned YUNIKORN-938:
-
Assignee: Kinga Marton
> Admission controller: remove v1beta1 usage
> --
>
> Key: YUNIKORN-938
> URL: https://issues.apache.org/jira/browse/YUNIKORN-938
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
>Reporter: Wilfred Spiegelenburg
>Assignee: Kinga Marton
>Priority: Major
> Labels: newbie
>
> The admission controller uses {{v1beta1.AdmissionReview}} and
> {{v1beta1.AdmissionResponse}} in the calls. This API is removed in K8s 1.22
> and we should proactively move to the v1 versions of both.
> This also affects the registration of the webhooks in the yaml stored int the
> templates.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-932) Improve logging reliability
[ https://issues.apache.org/jira/browse/YUNIKORN-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton updated YUNIKORN-932: -- Description: There are cases wheen our logs are not relyable. For example we have seen in case of some escalations missing logs for hours and we don't know that it was because the cluster was not heavily used, or it was some issues. We need to add some log messages for the following cases: * log a message periodically if there are no pending requests * log a message in case of recovery if we haven't heared anything from the API server for a while Also it may worth to check the main log paths and extend the logs where it is necessary. was: There are cases wheen our logs are not relyable. For example we have seen in case of some escalations missing logs for hours and we don't know that it was because the cluster was not heavily used, or it was some issues. We need to add some log messages for the following cases: * log a message periodically ifthere are no pending request * log a message in case of recovery if we haven't heared anything from the API server for a while Also it may worth to check the main log paths and extend the logs where it is necessary. > Improve logging reliability > --- > > Key: YUNIKORN-932 > URL: https://issues.apache.org/jira/browse/YUNIKORN-932 > Project: Apache YuniKorn > Issue Type: Improvement >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > > There are cases wheen our logs are not relyable. For example we have seen in > case of some escalations missing logs for hours and we don't know that it was > because the cluster was not heavily used, or it was some issues. > We need to add some log messages for the following cases: > * log a message periodically if there are no pending requests > * log a message in case of recovery if we haven't heared anything from the > API server for a while > Also it may worth to check the main log paths and extend the logs where it is > necessary. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-932) Improve logging reliability
Kinga Marton created YUNIKORN-932: - Summary: Improve logging reliability Key: YUNIKORN-932 URL: https://issues.apache.org/jira/browse/YUNIKORN-932 Project: Apache YuniKorn Issue Type: Improvement Reporter: Kinga Marton Assignee: Kinga Marton There are cases wheen our logs are not relyable. For example we have seen in case of some escalations missing logs for hours and we don't know that it was because the cluster was not heavily used, or it was some issues. We need to add some log messages for the following cases: * log a message periodically ifthere are no pending request * log a message in case of recovery if we haven't heared anything from the API server for a while Also it may worth to check the main log paths and extend the logs where it is necessary. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-882) Setup health check call as liveness probe
[ https://issues.apache.org/jira/browse/YUNIKORN-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-882. --- Resolution: Duplicate > Setup health check call as liveness probe > - > > Key: YUNIKORN-882 > URL: https://issues.apache.org/jira/browse/YUNIKORN-882 > Project: Apache YuniKorn > Issue Type: Improvement >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > > We have a Health check API, what is checking the scheduler state. It would be > useful to set this as the liveness probe for the scheduler. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-887) Automate generation of k8shim FSM state transition diagrams
[ https://issues.apache.org/jira/browse/YUNIKORN-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-887. --- Fix Version/s: 1.0.0 Resolution: Fixed > Automate generation of k8shim FSM state transition diagrams > --- > > Key: YUNIKORN-887 > URL: https://issues.apache.org/jira/browse/YUNIKORN-887 > Project: Apache YuniKorn > Issue Type: Improvement > Components: shim - kubernetes >Reporter: Craig Condit >Assignee: Craig Condit >Priority: Major > Labels: pull-request-available > Fix For: 1.0.0 > > > Similar to YUNIKORN-543, we should automate generation of state diagrams for > the k8shim finite state machines as well. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-911) Verify helm chart install on 1.21
[ https://issues.apache.org/jira/browse/YUNIKORN-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17434377#comment-17434377 ] Kinga Marton commented on YUNIKORN-911: --- [~lowc1012], I added you to the contributor list, so now you can assign Jiras to yourself. > Verify helm chart install on 1.21 > - > > Key: YUNIKORN-911 > URL: https://issues.apache.org/jira/browse/YUNIKORN-911 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: release >Reporter: Chaoran Yu >Assignee: Ryan Lo >Priority: Major > Fix For: 1.0.0 > > > Similar to YUNIKORN-671 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-911) Verify helm chart install on 1.21
[ https://issues.apache.org/jira/browse/YUNIKORN-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton reassigned YUNIKORN-911: - Assignee: Ryan Lo > Verify helm chart install on 1.21 > - > > Key: YUNIKORN-911 > URL: https://issues.apache.org/jira/browse/YUNIKORN-911 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: release >Reporter: Chaoran Yu >Assignee: Ryan Lo >Priority: Major > Fix For: 1.0.0 > > > Similar to YUNIKORN-671 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-879) Extend health check with allocation check
[ https://issues.apache.org/jira/browse/YUNIKORN-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-879. --- Fix Version/s: 1.0.0 Resolution: Fixed > Extend health check with allocation check > - > > Key: YUNIKORN-879 > URL: https://issues.apache.org/jira/browse/YUNIKORN-879 > Project: Apache YuniKorn > Issue Type: Improvement >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > Labels: pull-request-available > Fix For: 1.0.0 > > > We need some extra checks in our health check to make it really useful, such > as: > * Check for unlinked allocations, both the node and the application should > be valid > * All the allocations from a node should be known allocations from an app > that is still running -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-885) Set healtch check as liveness probe
[ https://issues.apache.org/jira/browse/YUNIKORN-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-885. --- Fix Version/s: 1.0.0 Resolution: Fixed > Set healtch check as liveness probe > --- > > Key: YUNIKORN-885 > URL: https://issues.apache.org/jira/browse/YUNIKORN-885 > Project: Apache YuniKorn > Issue Type: Improvement > Components: release >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > Labels: pull-request-available > Fix For: 1.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-75) REST API for changing log level
[ https://issues.apache.org/jira/browse/YUNIKORN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-75. -- Fix Version/s: 1.0.0 Resolution: Fixed > REST API for changing log level > --- > > Key: YUNIKORN-75 > URL: https://issues.apache.org/jira/browse/YUNIKORN-75 > Project: Apache YuniKorn > Issue Type: Improvement > Components: core - scheduler >Reporter: Adam Antal >Assignee: Peter Bacsko >Priority: Major > Labels: pull-request-available > Fix For: 1.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > We need a rest API to change the logging level, so we can change the logging > level on-the-fly. It can be used to debug in production issues where for most > of the time, only INFO level log is needed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-886) Fix e2e tests after YUNIKORN-794
[
https://issues.apache.org/jira/browse/YUNIKORN-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton resolved YUNIKORN-886.
---
Fix Version/s: 1.0.0
Resolution: Fixed
> Fix e2e tests after YUNIKORN-794
>
>
> Key: YUNIKORN-886
> URL: https://issues.apache.org/jira/browse/YUNIKORN-886
> Project: Apache YuniKorn
> Issue Type: Test
> Components: shim - kubernetes
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.0.0
>
>
> YUNIKORN-794 changed the REST API, which broke the e2e tests:
> {noformat}
> /home/runner/work/incubator-yunikorn-k8shim/incubator-yunikorn-k8shim/test/e2e/queue_quota_mgmt/queue_quota_mgmt_test.go:34
> Verify_Queue_Quota_Allocation [It]
>
> /home/runner/work/incubator-yunikorn-k8shim/incubator-yunikorn-k8shim/test/e2e/queue_quota_mgmt/queue_quota_mgmt_test.go:69
> Test Panicked
> interface conversion: interface {} is nil, not string
> /opt/hostedtoolcache/go/1.15.15/x64/src/runtime/iface.go:261
> Full Stack Trace
>
> github.com/apache/incubator-yunikorn-k8shim/test/e2e/queue_quota_mgmt_test.glob..func3.2()
>
> /home/runner/work/incubator-yunikorn-k8shim/incubator-yunikorn-k8shim/test/e2e/queue_quota_mgmt/queue_quota_mgmt_test.go:105
> +0x29ff
> github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync(0xc38360,
> 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
>
> /home/runner/go/pkg/mod/github.com/onsi/ginkgo@v1.16.5/internal/leafnodes/runner.go:113
> +0xa3
> [...]
>
> github.com/apache/incubator-yunikorn-k8shim/test/e2e/queue_quota_mgmt_test.TestStateAwareAppScheduling(0xcee780)
>
> /home/runner/work/incubator-yunikorn-k8shim/incubator-yunikorn-k8shim/test/e2e/queue_quota_mgmt/queue_quota_mgmt_suite_test.go:83
> +0x156
> testing.tRunner(0xcee780, 0x1b75ca8)
> /opt/hostedtoolcache/go/1.15.15/x64/src/testing/testing.go:1123 +0xef
> created by testing.(*T).Run
> /opt/hostedtoolcache/go/1.15.15/x64/src/testing/testing.go:1168 +0x2b3
> --
> {noformat}
> Problem is that we expect strings like "maxcapacity", "usedcapacity", etc.
> but the JSON response was slightly modified.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-543) Document state diagram generation
[
https://issues.apache.org/jira/browse/YUNIKORN-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton resolved YUNIKORN-543.
---
Fix Version/s: 1.0.0
Resolution: Fixed
> Document state diagram generation
> -
>
> Key: YUNIKORN-543
> URL: https://issues.apache.org/jira/browse/YUNIKORN-543
> Project: Apache YuniKorn
> Issue Type: Improvement
>Reporter: Kinga Marton
>Assignee: Craig Condit
>Priority: Trivial
> Labels: newbie, pull-request-available
> Fix For: 1.0.0
>
>
> Extend the documentation about how to generate a state diagram.
> Right now we the information only in a PR:
> bq.The looplab/fsm code allows generating a graphviz file via
> {{fsm.Visualize(state-machine)}}. This file can be converted using the
> {{dot}} tool or other online tools into a svg or png file."
> Also it would be nice to be able to generate it through a make command
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-888) Add documentation for k8shim state diagrams
[ https://issues.apache.org/jira/browse/YUNIKORN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-888. --- Fix Version/s: 1.0.0 Resolution: Fixed > Add documentation for k8shim state diagrams > --- > > Key: YUNIKORN-888 > URL: https://issues.apache.org/jira/browse/YUNIKORN-888 > Project: Apache YuniKorn > Issue Type: Improvement > Components: documentation >Reporter: Craig Condit >Assignee: Craig Condit >Priority: Major > Labels: pull-request-available > Fix For: 1.0.0 > > > YUNIKORN-543 and YUNIKORN-887 are adding automation to the generation of > graphs for our finite state machines. We should add these to the website > design docs. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-885) Set healtch check as liveness probe
Kinga Marton created YUNIKORN-885: - Summary: Set healtch check as liveness probe Key: YUNIKORN-885 URL: https://issues.apache.org/jira/browse/YUNIKORN-885 Project: Apache YuniKorn Issue Type: Improvement Components: release Reporter: Kinga Marton Assignee: Kinga Marton -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-882) Setup health check call as liveness probe
Kinga Marton created YUNIKORN-882: - Summary: Setup health check call as liveness probe Key: YUNIKORN-882 URL: https://issues.apache.org/jira/browse/YUNIKORN-882 Project: Apache YuniKorn Issue Type: Improvement Reporter: Kinga Marton Assignee: Kinga Marton We have a Health check API, what is checking the scheduler state. It would be useful to set this as the liveness probe for the scheduler. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-879) Extend health check with allocation check
Kinga Marton created YUNIKORN-879: - Summary: Extend health check with allocation check Key: YUNIKORN-879 URL: https://issues.apache.org/jira/browse/YUNIKORN-879 Project: Apache YuniKorn Issue Type: Improvement Reporter: Kinga Marton Assignee: Kinga Marton We need some extra checks in our health check to make it really useful, such as: * Check for unlinked allocations, both the node and the application should be valid * All the allocations from a node should be known allocations from an app that is still running -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-875) Fix unit tests after upgrade to K8S 1.20
[ https://issues.apache.org/jira/browse/YUNIKORN-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-875. --- Resolution: Fixed > Fix unit tests after upgrade to K8S 1.20 > > > Key: YUNIKORN-875 > URL: https://issues.apache.org/jira/browse/YUNIKORN-875 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: shim - kubernetes >Reporter: Craig Condit >Assignee: Craig Condit >Priority: Major > Labels: pull-request-available > > Make sure that unit tests build successfully on 1.20. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-842) [Umbrella] YuniKorn performance tuning and benchmark
[ https://issues.apache.org/jira/browse/YUNIKORN-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17427122#comment-17427122 ] Kinga Marton commented on YUNIKORN-842: --- Is it possible to create some table with the resource consumption of YuniKorn in case of different cluster size and node numbers? It would be helpful to have a documentation about the suggested resources for YuniKorn according to the cluster size. We found out that for example the default resource settings are not enough for 400+ cluster. > [Umbrella] YuniKorn performance tuning and benchmark > > > Key: YUNIKORN-842 > URL: https://issues.apache.org/jira/browse/YUNIKORN-842 > Project: Apache YuniKorn > Issue Type: New Feature > Components: core - scheduler, shim - kubernetes >Reporter: Weiwei Yang >Assignee: Ting Yao,Huang >Priority: Major > Fix For: 1.0.0 > > > http://yunikorn.apache.org/docs/next/performance/evaluate_perf_function_with_kubemark > is a bit out-of-dated, we want to reveal the performance benchmark with the > latest codebase. With this effort, we want to ellivate possible bottleneck > and further improve the throughput and performance. In this process, we will > also further improve the metrics system. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-75) REST API for changing log level
[ https://issues.apache.org/jira/browse/YUNIKORN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton reassigned YUNIKORN-75: Assignee: Peter Bacsko (was: Adam Antal) > REST API for changing log level > --- > > Key: YUNIKORN-75 > URL: https://issues.apache.org/jira/browse/YUNIKORN-75 > Project: Apache YuniKorn > Issue Type: Improvement > Components: core - scheduler >Reporter: Adam Antal >Assignee: Peter Bacsko >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > We need a rest API to change the logging level, so we can change the logging > level on-the-fly. It can be used to debug in production issues where for most > of the time, only INFO level log is needed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-871) Admission controller should only validate yunikorn configmap changes
[
https://issues.apache.org/jira/browse/YUNIKORN-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton resolved YUNIKORN-871.
---
Fix Version/s: 1.0.0
Resolution: Fixed
> Admission controller should only validate yunikorn configmap changes
>
>
> Key: YUNIKORN-871
> URL: https://issues.apache.org/jira/browse/YUNIKORN-871
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.0.0
>
>
> Currently, the admission controller is watching all namespaces and tries to
> validate all configmap changes. But we only need to validate the
> yunikorn-related changes.
> Example:
> {noformat}
> $ kubectl logs yunikorn-admission-controller-695869b547-qtfpg
> ...
> 2021-10-04T11:52:19.379Z INFOwebhook/webhook.go:83 the admission
> controller started{"port": 9089, "listeningOn": ["/mutate",
> "/validate-conf"]}
> $ kubectl create namespace testnamespace
> namespace/testnamespace created
> $ kubectl create configmap my-config --from-literal=mykey=myval
> --namespace=testnamespace
> configmap/my-config created
> $ kubectl get cm
> NAME DATA AGE
> yunikorn-configs 1 11m
> $ kubectl get cm --namespace=testnamespace
> NAMEDATA AGE
> my-config 1 17s
> $ kubectl logs yunikorn-admission-controller-695869b547-qtfpg
> ...
> 2021-10-04T11:52:19.379Z INFOwebhook/webhook.go:83 the admission
> controller started{"port": 9089, "listeningOn": ["/mutate",
> "/validate-conf"]}
> 2021-10-04T12:03:57.806Z INFOwebhook/admission_controller.go:304
> AdmissionReviewResponse {"allowed": true}
> {noformat}
>
> We need something like the following in {{validations.yaml.template}}:
> {noformat}
> namespaceSelector:
> matchLabels:
>yunikorn
> {noformat}
> This problem was originally found by [~kmarton].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-791) Allow to register nodes with infinite resources
[ https://issues.apache.org/jira/browse/YUNIKORN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-791. --- Fix Version/s: 1.0.0 Resolution: Fixed > Allow to register nodes with infinite resources > --- > > Key: YUNIKORN-791 > URL: https://issues.apache.org/jira/browse/YUNIKORN-791 > Project: Apache YuniKorn > Issue Type: Improvement >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > Labels: pull-request-available > Fix For: 1.0.0 > > > When multiple schedulers are used, we might want to use YK just for quota > enforcement and allow the default scheduler(or some other scheduler) to do > the replacement. To bypass the “placement” phase, the simplest approach is to > register a node with infinite resources, so the pod resource always fits into > this node. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-873) Update core build dependencies to 1.20.11
[ https://issues.apache.org/jira/browse/YUNIKORN-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-873. --- Resolution: Fixed I merged the changes to the YUNIKOR-872 dev branch > Update core build dependencies to 1.20.11 > - > > Key: YUNIKORN-873 > URL: https://issues.apache.org/jira/browse/YUNIKORN-873 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: shim - kubernetes >Reporter: Craig Condit >Assignee: Craig Condit >Priority: Major > Labels: pull-request-available > > As part of the rebase on K8S 1.20, we need to first get the core build to > compile. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-872) [Umbrella] Build against kubernetes 1.20
[ https://issues.apache.org/jira/browse/YUNIKORN-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17425588#comment-17425588 ] Kinga Marton commented on YUNIKORN-872: --- Since this is a bigger feature, as we discussed offline, I created YUNIKORN-872 branch for working on the subtasks. > [Umbrella] Build against kubernetes 1.20 > > > Key: YUNIKORN-872 > URL: https://issues.apache.org/jira/browse/YUNIKORN-872 > Project: Apache YuniKorn > Issue Type: Improvement > Components: shim - kubernetes >Reporter: Craig Condit >Assignee: Craig Condit >Priority: Major > > Currently, the kubernetes shim is built against kubernetes 1.16. This version > has been end-of-life for quite some time now. We should update to build > against 1.20 prior to YuniKorn 1.0. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-871) Admission controller should only validate yunikorn configmap changes
[
https://issues.apache.org/jira/browse/YUNIKORN-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17424889#comment-17424889
]
Kinga Marton commented on YUNIKORN-871:
---
We can check for the configmap name, in the same way we are doing in the core
side. And handle only the YK configs, since this is not configurable.
> Admission controller should only validate yunikorn configmap changes
>
>
> Key: YUNIKORN-871
> URL: https://issues.apache.org/jira/browse/YUNIKORN-871
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
>
> Currently, the admission controller is watching all namespaces and tries to
> validate all configmap changes. But we only need to validate the
> yunikorn-related changes.
> Example:
> {noformat}
> $ kubectl logs yunikorn-admission-controller-695869b547-qtfpg
> ...
> 2021-10-04T11:52:19.379Z INFOwebhook/webhook.go:83 the admission
> controller started{"port": 9089, "listeningOn": ["/mutate",
> "/validate-conf"]}
> $ kubectl create namespace testnamespace
> namespace/testnamespace created
> $ kubectl create configmap my-config --from-literal=mykey=myval
> --namespace=testnamespace
> configmap/my-config created
> $ kubectl get cm
> NAME DATA AGE
> yunikorn-configs 1 11m
> $ kubectl get cm --namespace=testnamespace
> NAMEDATA AGE
> my-config 1 17s
> $ kubectl logs yunikorn-admission-controller-695869b547-qtfpg
> ...
> 2021-10-04T11:52:19.379Z INFOwebhook/webhook.go:83 the admission
> controller started{"port": 9089, "listeningOn": ["/mutate",
> "/validate-conf"]}
> 2021-10-04T12:03:57.806Z INFOwebhook/admission_controller.go:304
> AdmissionReviewResponse {"allowed": true}
> {noformat}
>
> We need something like the following in {{validations.yaml.template}}:
> {noformat}
> namespaceSelector:
> matchLabels:
>yunikorn
> {noformat}
> This problem was originally found by [~kmarton].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-814) The template of non-leaf queue should not be override by template of parent
[ https://issues.apache.org/jira/browse/YUNIKORN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-814. --- Fix Version/s: 1.0.0 Resolution: Fixed > The template of non-leaf queue should not be override by template of parent > --- > > Key: YUNIKORN-814 > URL: https://issues.apache.org/jira/browse/YUNIKORN-814 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Major > Labels: pull-request-available > Fix For: 1.0.0 > > > This is a bug introduced by YUNIKORN-193. The non-leaf queue get template > from conf but the template is override when it is added to parent queue. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-583) Codecov report is always failing
[ https://issues.apache.org/jira/browse/YUNIKORN-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420676#comment-17420676 ] Kinga Marton commented on YUNIKORN-583: --- I am setting this as a blocker for the next release, because it is very annoying during the review cylcles that the changeset has a lot of false warnings. > Codecov report is always failing > > > Key: YUNIKORN-583 > URL: https://issues.apache.org/jira/browse/YUNIKORN-583 > Project: Apache YuniKorn > Issue Type: Bug >Affects Versions: 0.11 >Reporter: Weiwei Yang >Priority: Blocker > Fix For: 1.0.0 > > Attachments: [YUNIKORN-631]_PR_comment.png > > > It looks like the codecov report is broken. The target is always bigger than > the result, seems like it is using a wrong base to compare. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-583) Codecov report is always failing
[ https://issues.apache.org/jira/browse/YUNIKORN-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton updated YUNIKORN-583: -- Priority: Blocker (was: Major) > Codecov report is always failing > > > Key: YUNIKORN-583 > URL: https://issues.apache.org/jira/browse/YUNIKORN-583 > Project: Apache YuniKorn > Issue Type: Bug >Affects Versions: 0.11 >Reporter: Weiwei Yang >Priority: Blocker > Attachments: [YUNIKORN-631]_PR_comment.png > > > It looks like the codecov report is broken. The target is always bigger than > the result, seems like it is using a wrong base to compare. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-583) Codecov report is always failing
[ https://issues.apache.org/jira/browse/YUNIKORN-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton updated YUNIKORN-583: -- Fix Version/s: 1.0.0 > Codecov report is always failing > > > Key: YUNIKORN-583 > URL: https://issues.apache.org/jira/browse/YUNIKORN-583 > Project: Apache YuniKorn > Issue Type: Bug >Affects Versions: 0.11 >Reporter: Weiwei Yang >Priority: Blocker > Fix For: 1.0.0 > > Attachments: [YUNIKORN-631]_PR_comment.png > > > It looks like the codecov report is broken. The target is always bigger than > the result, seems like it is using a wrong base to compare. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-385) Deleted partitions are not deleted from core
[ https://issues.apache.org/jira/browse/YUNIKORN-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-385. --- Fix Version/s: 1.0.0 Resolution: Fixed This was fixed by YUNIKORN-832 > Deleted partitions are not deleted from core > > > Key: YUNIKORN-385 > URL: https://issues.apache.org/jira/browse/YUNIKORN-385 > Project: Apache YuniKorn > Issue Type: Bug >Reporter: Kinga Marton >Assignee: Chen Yu Teng >Priority: Major > Fix For: 1.0.0 > > > If we delete a partition, that will be marked for removal, but is not > deleted, even if there is nothing assigned to that partition. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-832) Updating config can't remove partition
[
https://issues.apache.org/jira/browse/YUNIKORN-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton resolved YUNIKORN-832.
---
Fix Version/s: 1.0.0
Resolution: Fixed
> Updating config can't remove partition
> --
>
> Key: YUNIKORN-832
> URL: https://issues.apache.org/jira/browse/YUNIKORN-832
> Project: Apache YuniKorn
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.0.0
>
>
> All functions in `partition_manager` are using pass-by-value so setting the
> `stop` flag to true can't terminate other threads.
> {code:go}
> func (manager partitionManager) Stop() {
> manager.stop = true
> }
> {code}
> Also, the thread used to cleanup expired app can't be stopped quickly after
> removing partition because it needs to sleep for 24 hours.
> {code:go}
> func (manager partitionManager) cleanupExpiredApps() {
> for {
> if manager.stop {
> break
> }
> manager.pc.cleanupExpiredApps()
> time.Sleep(appRemovalInterval)
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-840) Downloads page broken for release announcements
[ https://issues.apache.org/jira/browse/YUNIKORN-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-840. --- Resolution: Fixed > Downloads page broken for release announcements > --- > > Key: YUNIKORN-840 > URL: https://issues.apache.org/jira/browse/YUNIKORN-840 > Project: Apache YuniKorn > Issue Type: Bug > Components: website >Affects Versions: 0.11, 0.10 >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Blocker > Labels: pull-request-available > Fix For: 0.11 > > > The release announcement links on the website are broken. > They point to: > [https://yunikorn.apache.org/community/release-announce/0.11.0] > While they should be pointing to: > [https://yunikorn.apache.org/release-announce/0.11.0/] > Beside those broken links we also have unaccessible links on the release > announcement pages for v0.10 and v0.11. The overview of fixes points to a > page for which you must be authenticated in Apache Jira. We should not have a > list like that behind authentication. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-835) Reminder readers that web-latest image in docker hub is not maintained anymore
[ https://issues.apache.org/jira/browse/YUNIKORN-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-835. --- Fix Version/s: 1.0.0 Resolution: Fixed > Reminder readers that web-latest image in docker hub is not maintained anymore > -- > > Key: YUNIKORN-835 > URL: https://issues.apache.org/jira/browse/YUNIKORN-835 > Project: Apache YuniKorn > Issue Type: Improvement > Components: documentation >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Minor > Labels: pull-request-available > Fix For: 1.0.0 > > > The docs is used to avoid users from exercising stale and incompatible docker > image. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-794) fix typo of /ws/v1/partitions response: usedcapacity -> usedCapacity
[ https://issues.apache.org/jira/browse/YUNIKORN-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton updated YUNIKORN-794: -- Labels: newbie (was: ) > fix typo of /ws/v1/partitions response: usedcapacity -> usedCapacity > > > Key: YUNIKORN-794 > URL: https://issues.apache.org/jira/browse/YUNIKORN-794 > Project: Apache YuniKorn > Issue Type: Bug >Reporter: Chia-Ping Tsai >Priority: Minor > Labels: newbie > Fix For: 1.0.0 > > > this change can break the compatibility so not sure whether we can change it > directly. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-729) [Umbrella] YuniKorn 0.11.0 release related efforts
[ https://issues.apache.org/jira/browse/YUNIKORN-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-729. --- Resolution: Fixed > [Umbrella] YuniKorn 0.11.0 release related efforts > -- > > Key: YUNIKORN-729 > URL: https://issues.apache.org/jira/browse/YUNIKORN-729 > Project: Apache YuniKorn > Issue Type: Task >Reporter: Weiwei Yang >Assignee: Kinga Marton >Priority: Major > Fix For: 0.11 > > > This umbrella is to track the work items needed for 0.11.0 release. > Release manager: Kinga Marton. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-822) Cleanup release area
[ https://issues.apache.org/jira/browse/YUNIKORN-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-822. --- Resolution: Fixed > Cleanup release area > > > Key: YUNIKORN-822 > URL: https://issues.apache.org/jira/browse/YUNIKORN-822 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > Labels: pull-request-available > Fix For: 0.11 > > > This step should be performed after the website updates have been made as the > download links change. > There should only be one release, the latest, in the release area. Any > release that has been in the release area will be automatically copied to the > archive. Older releases should be downloaded from the archive directly, not > from the release area. > The releases need to clean up in two locations: > * Remove the newly released version from the _dev_ area by removing the old > release candidate directory. For the location see [release candidate > location|https://github.com/apache/incubator-yunikorn-release/blob/master/docs/release-procedure.md#Upload-Release-Candidate-Artefacts] > * Remove the non-current release from the _release_ area by removing the old > release directory. For the location see [release > location|https://github.com/apache/incubator-yunikorn-release/blob/master/docs/release-procedure.md#Publish-the-Release] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-822) Cleanup release area
[ https://issues.apache.org/jira/browse/YUNIKORN-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17403710#comment-17403710 ] Kinga Marton commented on YUNIKORN-822: --- The release is removed from the dev area. I will remove the 0.10.0 release from release area once the PR with updating the download link for thee 0.10.0 release will be merged. > Cleanup release area > > > Key: YUNIKORN-822 > URL: https://issues.apache.org/jira/browse/YUNIKORN-822 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > Labels: pull-request-available > Fix For: 0.11 > > > This step should be performed after the website updates have been made as the > download links change. > There should only be one release, the latest, in the release area. Any > release that has been in the release area will be automatically copied to the > archive. Older releases should be downloaded from the archive directly, not > from the release area. > The releases need to clean up in two locations: > * Remove the newly released version from the _dev_ area by removing the old > release candidate directory. For the location see [release candidate > location|https://github.com/apache/incubator-yunikorn-release/blob/master/docs/release-procedure.md#Upload-Release-Candidate-Artefacts] > * Remove the non-current release from the _release_ area by removing the old > release directory. For the location see [release > location|https://github.com/apache/incubator-yunikorn-release/blob/master/docs/release-procedure.md#Publish-the-Release] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-823) Update website announce bar
[ https://issues.apache.org/jira/browse/YUNIKORN-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-823. --- Fix Version/s: 0.11 Resolution: Fixed > Update website announce bar > --- > > Key: YUNIKORN-823 > URL: https://issues.apache.org/jira/browse/YUNIKORN-823 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > Labels: pull-request-available > Fix For: 0.11 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-823) Update website announce bar
[ https://issues.apache.org/jira/browse/YUNIKORN-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton reassigned YUNIKORN-823: - Assignee: Kinga Marton > Update website announce bar > --- > > Key: YUNIKORN-823 > URL: https://issues.apache.org/jira/browse/YUNIKORN-823 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-823) Update website announce bar
[ https://issues.apache.org/jira/browse/YUNIKORN-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton reassigned YUNIKORN-823: - Assignee: (was: Kinga Marton) > Update website announce bar > --- > > Key: YUNIKORN-823 > URL: https://issues.apache.org/jira/browse/YUNIKORN-823 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-823) Update website announce bar
Kinga Marton created YUNIKORN-823: - Summary: Update website announce bar Key: YUNIKORN-823 URL: https://issues.apache.org/jira/browse/YUNIKORN-823 Project: Apache YuniKorn Issue Type: Sub-task Reporter: Kinga Marton -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-823) Update website announce bar
[ https://issues.apache.org/jira/browse/YUNIKORN-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton reassigned YUNIKORN-823: - Assignee: Kinga Marton > Update website announce bar > --- > > Key: YUNIKORN-823 > URL: https://issues.apache.org/jira/browse/YUNIKORN-823 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-736) Add 0.11.0 to the artifact hub
[ https://issues.apache.org/jira/browse/YUNIKORN-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17403656#comment-17403656 ] Kinga Marton commented on YUNIKORN-736: --- The charts are available: [https://artifacthub.io/packages/helm/yunikorn/yunikorn] > Add 0.11.0 to the artifact hub > -- > > Key: YUNIKORN-736 > URL: https://issues.apache.org/jira/browse/YUNIKORN-736 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > > We need to update our gh-pages in the release repository, so the artifacthub > will have the new release as well: > https://artifacthub.io/packages/helm/yunikorn/yunikorn -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-736) Add 0.11.0 to the artifact hub
[ https://issues.apache.org/jira/browse/YUNIKORN-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-736. --- Fix Version/s: 0.11 Resolution: Fixed > Add 0.11.0 to the artifact hub > -- > > Key: YUNIKORN-736 > URL: https://issues.apache.org/jira/browse/YUNIKORN-736 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > Fix For: 0.11 > > > We need to update our gh-pages in the release repository, so the artifacthub > will have the new release as well: > https://artifacthub.io/packages/helm/yunikorn/yunikorn -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-738) Update helm index for v0.11
[ https://issues.apache.org/jira/browse/YUNIKORN-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-738. --- Fix Version/s: 0.11 Resolution: Fixed > Update helm index for v0.11 > --- > > Key: YUNIKORN-738 > URL: https://issues.apache.org/jira/browse/YUNIKORN-738 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: release >Reporter: Tao Yang >Assignee: Kinga Marton >Priority: Major > Labels: pull-request-available > Fix For: 0.11 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-813) The capacity of undefined resource should NOT be considered zero
[
https://issues.apache.org/jira/browse/YUNIKORN-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17402981#comment-17402981
]
Kinga Marton commented on YUNIKORN-813:
---
If a resource is undefined I think it should be considered max value/unlimited.
We are already using this approach in a couple of places in the code such as i
queue quota check.
> The capacity of undefined resource should NOT be considered zero
>
>
> Key: YUNIKORN-813
> URL: https://issues.apache.org/jira/browse/YUNIKORN-813
> Project: Apache YuniKorn
> Issue Type: Improvement
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Major
>
> {code}
> resources:
> max:
> memory: 1
> {code}
> If above configuration is added to a leaf queue, the queue can't run any
> application since the "vcore" is assumed to be zero. That obstructs us from
> limiting only a part of resources.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-737) [Helm chart] Update supported K8s versions
[ https://issues.apache.org/jira/browse/YUNIKORN-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-737. --- Resolution: Fixed > [Helm chart] Update supported K8s versions > -- > > Key: YUNIKORN-737 > URL: https://issues.apache.org/jira/browse/YUNIKORN-737 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Wen-Chien,Juan >Priority: Major > Labels: newbie > Fix For: 0.11 > > > Right now the README in the Helm chart has the following info related the > supported K8s versions: > upported K8s versions > |K8s Version|Support?| > |-|:-:| > |1.12.x (or earlier)|X| > |1.13.x|√| > |1.14.x|√| > |1.15.x|√| > |1.16.x|To be verified| > |1.17.x|To be verified| > This is not true anymore, since the shim already uses 1.16 version, and the > tests are running with 1.17 1.18 and 1.19. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Comment Edited] (YUNIKORN-737) [Helm chart] Update supported K8s versions
[ https://issues.apache.org/jira/browse/YUNIKORN-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17401148#comment-17401148 ] Kinga Marton edited comment on YUNIKORN-737 at 8/18/21, 3:30 PM: - This needs to be updated in the Helm chart Readme file: [https://github.com/apache/incubator-yunikorn-release/tree/branch-0.11/helm-charts/yunikorn] But this one was also updated. Now the versions are updated, so I am closing this issue. was (Author: kmarton): This needs to be updated in the Helm chart Readme file: [https://github.com/apache/incubator-yunikorn-release/tree/branch-0.11/helm-charts/yunikorn] > [Helm chart] Update supported K8s versions > -- > > Key: YUNIKORN-737 > URL: https://issues.apache.org/jira/browse/YUNIKORN-737 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Wen-Chien,Juan >Priority: Major > Labels: newbie > Fix For: 0.11 > > > Right now the README in the Helm chart has the following info related the > supported K8s versions: > upported K8s versions > |K8s Version|Support?| > |-|:-:| > |1.12.x (or earlier)|X| > |1.13.x|√| > |1.14.x|√| > |1.15.x|√| > |1.16.x|To be verified| > |1.17.x|To be verified| > This is not true anymore, since the shim already uses 1.16 version, and the > tests are running with 1.17 1.18 and 1.19. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-737) [Helm chart] Update supported K8s versions
[ https://issues.apache.org/jira/browse/YUNIKORN-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17401148#comment-17401148 ] Kinga Marton commented on YUNIKORN-737: --- This needs to be updated in the Helm chart Readme file: [https://github.com/apache/incubator-yunikorn-release/tree/branch-0.11/helm-charts/yunikorn] > [Helm chart] Update supported K8s versions > -- > > Key: YUNIKORN-737 > URL: https://issues.apache.org/jira/browse/YUNIKORN-737 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Wen-Chien,Juan >Priority: Major > Labels: newbie > Fix For: 0.11 > > > Right now the README in the Helm chart has the following info related the > supported K8s versions: > upported K8s versions > |K8s Version|Support?| > |-|:-:| > |1.12.x (or earlier)|X| > |1.13.x|√| > |1.14.x|√| > |1.15.x|√| > |1.16.x|To be verified| > |1.17.x|To be verified| > This is not true anymore, since the shim already uses 1.16 version, and the > tests are running with 1.17 1.18 and 1.19. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-730) Create 0.11.0 helm chart release
[ https://issues.apache.org/jira/browse/YUNIKORN-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-730. --- Resolution: Fixed > Create 0.11.0 helm chart release > > > Key: YUNIKORN-730 > URL: https://issues.apache.org/jira/browse/YUNIKORN-730 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: release >Reporter: Tao Yang >Assignee: Kinga Marton >Priority: Major > Fix For: 0.11 > > > Release the helm charts in yunikorn-release repository with following steps: > * create a new branch: branch-0.11 > * update version to 0.110 in helm-charts/yunikorn/Chart.yaml > * tag v0.11.0 ( after 0.11.0 release notes have been ) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-731) Create 0.11.0 release notes
[ https://issues.apache.org/jira/browse/YUNIKORN-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-731. --- Resolution: Fixed > Create 0.11.0 release notes > --- > > Key: YUNIKORN-731 > URL: https://issues.apache.org/jira/browse/YUNIKORN-731 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: release >Reporter: Tao Yang >Assignee: Kinga Marton >Priority: Major > Fix For: 0.11 > > > Release notes should be updated in CHANGELOG file which will be added into > the release artifacts. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-791) Allow to register nodes with infinite resources
[ https://issues.apache.org/jira/browse/YUNIKORN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton reassigned YUNIKORN-791: - Assignee: Kinga Marton > Allow to register nodes with infinite resources > --- > > Key: YUNIKORN-791 > URL: https://issues.apache.org/jira/browse/YUNIKORN-791 > Project: Apache YuniKorn > Issue Type: Improvement >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > > When multiple schedulers are used, we might want to use YK just for quota > enforcement and allow the default scheduler(or some other scheduler) to do > the replacement. To bypass the “placement” phase, the simplest approach is to > register a node with infinite resources, so the pod resource always fits into > this node. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-791) Allow to register nodes with infinite resources
Kinga Marton created YUNIKORN-791: - Summary: Allow to register nodes with infinite resources Key: YUNIKORN-791 URL: https://issues.apache.org/jira/browse/YUNIKORN-791 Project: Apache YuniKorn Issue Type: Improvement Reporter: Kinga Marton When multiple schedulers are used, we might want to use YK just for quota enforcement and allow the default scheduler(or some other scheduler) to do the replacement. To bypass the “placement” phase, the simplest approach is to register a node with infinite resources, so the pod resource always fits into this node. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-791) Allow to register nodes with infinite resources
[ https://issues.apache.org/jira/browse/YUNIKORN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton updated YUNIKORN-791: -- Target Version: 1.0.0 > Allow to register nodes with infinite resources > --- > > Key: YUNIKORN-791 > URL: https://issues.apache.org/jira/browse/YUNIKORN-791 > Project: Apache YuniKorn > Issue Type: Improvement >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > > When multiple schedulers are used, we might want to use YK just for quota > enforcement and allow the default scheduler(or some other scheduler) to do > the replacement. To bypass the “placement” phase, the simplest approach is to > register a node with infinite resources, so the pod resource always fits into > this node. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-782) Implement proper cleanup when a node is removed
Kinga Marton created YUNIKORN-782: - Summary: Implement proper cleanup when a node is removed Key: YUNIKORN-782 URL: https://issues.apache.org/jira/browse/YUNIKORN-782 Project: Apache YuniKorn Issue Type: Bug Components: core - scheduler Reporter: Kinga Marton Assignee: Kinga Marton Right now when a node is removed, we just simply remove the allocations, without doing a proper rollback for thee in progress allocations. This might cause some issues for example for GS (driver pods stuck in pending state) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-768) License header missing on test file
[ https://issues.apache.org/jira/browse/YUNIKORN-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton updated YUNIKORN-768: -- Fix Version/s: (was: 1.0.0) 0.11 > License header missing on test file > --- > > Key: YUNIKORN-768 > URL: https://issues.apache.org/jira/browse/YUNIKORN-768 > Project: Apache YuniKorn > Issue Type: Bug > Components: shim - kubernetes >Affects Versions: 0.10 >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Labels: pull-request-available > Fix For: 0.11 > > > In YUNIKORN-427 we forgot to add the apache license header to the file: > test/e2e/predicates/predicates_test.go > We need to add the apache license header. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-767) Add license to mock_plugin_test.go
[ https://issues.apache.org/jira/browse/YUNIKORN-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton updated YUNIKORN-767: -- Fix Version/s: (was: 1.0.0) 0.11 > Add license to mock_plugin_test.go > -- > > Key: YUNIKORN-767 > URL: https://issues.apache.org/jira/browse/YUNIKORN-767 > Project: Apache YuniKorn > Issue Type: Bug > Components: core - scheduler >Affects Versions: 0.10 >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Labels: pull-request-available > Fix For: 0.11 > > > The mock plugin test added in YUNIKORN-505 does not have a license file as it > should have. We need to add it: > scheduler/mock_plugin_test.go -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-773) cleanup polyfills.ts comments
[ https://issues.apache.org/jira/browse/YUNIKORN-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-773. --- Fix Version/s: 0.11 Resolution: Fixed > cleanup polyfills.ts comments > - > > Key: YUNIKORN-773 > URL: https://issues.apache.org/jira/browse/YUNIKORN-773 > Project: Apache YuniKorn > Issue Type: Bug > Components: webapp >Affects Versions: 0.11 >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Labels: pull-request-available > Fix For: 0.11 > > > The polyfills.ts file was generated by angular but never cleaned up after it > was customised and included as part of our web app definition. This looks > strange. We should only have one setting in the file without all the > irrelevant comments. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-769) Licence-check is not working properly on precommit
Kinga Marton created YUNIKORN-769: - Summary: Licence-check is not working properly on precommit Key: YUNIKORN-769 URL: https://issues.apache.org/jira/browse/YUNIKORN-769 Project: Apache YuniKorn Issue Type: Bug Affects Versions: 0.10 Reporter: Kinga Marton Thee license-check is passing on pre-commit even if there are some missing headers. In this case it fails locally as expected. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-768) License header missing on test file
[ https://issues.apache.org/jira/browse/YUNIKORN-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-768. --- Fix Version/s: 1.0.0 Resolution: Fixed > License header missing on test file > --- > > Key: YUNIKORN-768 > URL: https://issues.apache.org/jira/browse/YUNIKORN-768 > Project: Apache YuniKorn > Issue Type: Bug > Components: shim - kubernetes >Affects Versions: 0.10 >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Labels: pull-request-available > Fix For: 1.0.0 > > > In YUNIKORN-427 we forgot to add the apache license header to the file: > test/e2e/predicates/predicates_test.go > We need to add the apache license header. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-767) Add license to mock_plugin_test.go
[ https://issues.apache.org/jira/browse/YUNIKORN-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-767. --- Fix Version/s: 1.0.0 Resolution: Fixed > Add license to mock_plugin_test.go > -- > > Key: YUNIKORN-767 > URL: https://issues.apache.org/jira/browse/YUNIKORN-767 > Project: Apache YuniKorn > Issue Type: Bug > Components: core - scheduler >Affects Versions: 0.10 >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Labels: pull-request-available > Fix For: 1.0.0 > > > The mock plugin test added in YUNIKORN-505 does not have a license file as it > should have. We need to add it: > scheduler/mock_plugin_test.go -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-713) Align YuniKorn core's scheduler metrics with queue metrics for total applications accepted
[ https://issues.apache.org/jira/browse/YUNIKORN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton updated YUNIKORN-713: -- Fix Version/s: (was: 1.0.0) 0.11 > Align YuniKorn core's scheduler metrics with queue metrics for total > applications accepted > -- > > Key: YUNIKORN-713 > URL: https://issues.apache.org/jira/browse/YUNIKORN-713 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: core - common >Reporter: Chenya Zhang >Assignee: Chenya Zhang >Priority: Minor > Labels: pull-request-available > Fix For: 0.11 > > > The metrics naming and operations are sometimes confusing in the code due to > not aligning with each other on similar concepts. > * Replace "totalApplicationsAdded" with "totalApplicationsAccepted" > * Update related metrics operation functions -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-714) Refactor YuniKorn core's scheduler metrics for application submission
[ https://issues.apache.org/jira/browse/YUNIKORN-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton updated YUNIKORN-714: -- Fix Version/s: (was: 1.0.0) 0.11 > Refactor YuniKorn core's scheduler metrics for application submission > - > > Key: YUNIKORN-714 > URL: https://issues.apache.org/jira/browse/YUNIKORN-714 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: core - common >Reporter: Chenya Zhang >Assignee: Chenya Zhang >Priority: Major > Labels: pull-request-available > Fix For: 0.11 > > > Defining "totalApplicationsAccepted" and "totalApplicationsRejected" to > initialize scheduler metrics is redundant in code. > * It can be combined into one "applicationSubmissions" metrics > * It can use a "prometheus.CounterVec" with different Prometheus labels -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-756) Set default scheduling policy to Hard for gang scheduling
[ https://issues.apache.org/jira/browse/YUNIKORN-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-756. --- Resolution: Fixed > Set default scheduling policy to Hard for gang scheduling > - > > Key: YUNIKORN-756 > URL: https://issues.apache.org/jira/browse/YUNIKORN-756 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > Labels: pull-request-available > Fix For: 0.11 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-756) Set default scheduling policy to Hard for gang scheduling
[ https://issues.apache.org/jira/browse/YUNIKORN-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton updated YUNIKORN-756: -- Summary: Set default scheduling policy to Hard for gang scheduling (was: Set Hard as default scheduling policy for gang scheduling) > Set default scheduling policy to Hard for gang scheduling > - > > Key: YUNIKORN-756 > URL: https://issues.apache.org/jira/browse/YUNIKORN-756 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > Fix For: 0.11 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-756) Set Hard as default scheduling policy for gang scheduling
[ https://issues.apache.org/jira/browse/YUNIKORN-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton updated YUNIKORN-756: -- Fix Version/s: 0.11 > Set Hard as default scheduling policy for gang scheduling > - > > Key: YUNIKORN-756 > URL: https://issues.apache.org/jira/browse/YUNIKORN-756 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > Fix For: 0.11 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-756) Set Hard as default scheduling policy for gang scheduling
Kinga Marton created YUNIKORN-756: - Summary: Set Hard as default scheduling policy for gang scheduling Key: YUNIKORN-756 URL: https://issues.apache.org/jira/browse/YUNIKORN-756 Project: Apache YuniKorn Issue Type: Sub-task Reporter: Kinga Marton Assignee: Kinga Marton -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-733) Update shim and core dependencies on master branch
[ https://issues.apache.org/jira/browse/YUNIKORN-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton updated YUNIKORN-733: -- Summary: Update shim and core dependencies on master branch (was: Update shim dependency on core for v0.11) > Update shim and core dependencies on master branch > -- > > Key: YUNIKORN-733 > URL: https://issues.apache.org/jira/browse/YUNIKORN-733 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: shim - kubernetes >Reporter: Wilfred Spiegelenburg >Assignee: Kinga Marton >Priority: Blocker > Fix For: 0.11 > > > The current scheduler is building with an older release of the core. > There are two changes that need to be made: > * In preparation for the v0.11 release we need to update the dependency in > branch-0.11 to start pointing to a core version in branch-0.11 > * The master of the shim needs an update to point to the latest version of > the core master -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-740) Update the CHANGELOG and generate the release
[
https://issues.apache.org/jira/browse/YUNIKORN-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton resolved YUNIKORN-740.
---
Fix Version/s: 0.11
Resolution: Fixed
> Update the CHANGELOG and generate the release
> -
>
> Key: YUNIKORN-740
> URL: https://issues.apache.org/jira/browse/YUNIKORN-740
> Project: Apache YuniKorn
> Issue Type: Sub-task
>Reporter: Kinga Marton
>Assignee: Kinga Marton
>Priority: Major
> Fix For: 0.11
>
>
> * Go to the [releases page in
> jira|https://issues.apache.org/jira/projects/YUNIKORN?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page=released-unreleased]
> * Click on the version that is about to be released, i.e. {{0.11}}
> * Click on the {{Release Notes}} link on the top of the page
> * Click the button {{Configure Release Notes}}
> * Select the style {{Text}} and click {{create}}
> * Scroll to the bottom of the page and copy the content of the text area and
> update the
> [CHANGELOG|https://github.com/apache/incubator-yunikorn-release/blob/master/release-top-level-artifacts/CHANGELOG]
> file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-740) Update the CHANGELOG and generate the release
[
https://issues.apache.org/jira/browse/YUNIKORN-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton updated YUNIKORN-740:
--
Summary: Update the CHANGELOG and generate the release (was: Update the
CHANGELOG)
> Update the CHANGELOG and generate the release
> -
>
> Key: YUNIKORN-740
> URL: https://issues.apache.org/jira/browse/YUNIKORN-740
> Project: Apache YuniKorn
> Issue Type: Sub-task
>Reporter: Kinga Marton
>Assignee: Kinga Marton
>Priority: Major
>
> * Go to the [releases page in
> jira|https://issues.apache.org/jira/projects/YUNIKORN?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page=released-unreleased]
> * Click on the version that is about to be released, i.e. {{0.11}}
> * Click on the {{Release Notes}} link on the top of the page
> * Click the button {{Configure Release Notes}}
> * Select the style {{Text}} and click {{create}}
> * Scroll to the bottom of the page and copy the content of the text area and
> update the
> [CHANGELOG|https://github.com/apache/incubator-yunikorn-release/blob/master/release-top-level-artifacts/CHANGELOG]
> file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-740) Update the CHANGELOG
[
https://issues.apache.org/jira/browse/YUNIKORN-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton updated YUNIKORN-740:
--
Description:
* Go to the [releases page in
jira|https://issues.apache.org/jira/projects/YUNIKORN?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page=released-unreleased]
* Click on the version that is about to be released, i.e. {{0.11}}
* Click on the {{Release Notes}} link on the top of the page
* Click the button {{Configure Release Notes}}
* Select the style {{Text}} and click {{create}}
* Scroll to the bottom of the page and copy the content of the text area and
update the
[CHANGELOG|https://github.com/apache/incubator-yunikorn-release/blob/master/release-top-level-artifacts/CHANGELOG]
file.
was:
* Go to the [releases page in
jira|https://issues.apache.org/jira/projects/YUNIKORN?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page=released-unreleased]
* Click on the version that is about to be released, i.e. {{0.8}}
* Click on the {{Release Notes}} link on the top of the page
* Click the button {{Configure Release Notes}}
* Select the style {{Text}} and click {{create}}
* Scroll to the bottom of the page and copy the content of the text area and
update the
[CHANGELOG|https://github.com/apache/incubator-yunikorn-release/blob/master/release-top-level-artifacts/CHANGELOG]
file.
> Update the CHANGELOG
>
>
> Key: YUNIKORN-740
> URL: https://issues.apache.org/jira/browse/YUNIKORN-740
> Project: Apache YuniKorn
> Issue Type: Sub-task
>Reporter: Kinga Marton
>Assignee: Kinga Marton
>Priority: Major
>
> * Go to the [releases page in
> jira|https://issues.apache.org/jira/projects/YUNIKORN?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page=released-unreleased]
> * Click on the version that is about to be released, i.e. {{0.11}}
> * Click on the {{Release Notes}} link on the top of the page
> * Click the button {{Configure Release Notes}}
> * Select the style {{Text}} and click {{create}}
> * Scroll to the bottom of the page and copy the content of the text area and
> update the
> [CHANGELOG|https://github.com/apache/incubator-yunikorn-release/blob/master/release-top-level-artifacts/CHANGELOG]
> file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-740) Update the CHANGELOG
Kinga Marton created YUNIKORN-740:
-
Summary: Update the CHANGELOG
Key: YUNIKORN-740
URL: https://issues.apache.org/jira/browse/YUNIKORN-740
Project: Apache YuniKorn
Issue Type: Sub-task
Reporter: Kinga Marton
Assignee: Kinga Marton
* Go to the [releases page in
jira|https://issues.apache.org/jira/projects/YUNIKORN?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page=released-unreleased]
* Click on the version that is about to be released, i.e. {{0.8}}
* Click on the {{Release Notes}} link on the top of the page
* Click the button {{Configure Release Notes}}
* Select the style {{Text}} and click {{create}}
* Scroll to the bottom of the page and copy the content of the text area and
update the
[CHANGELOG|https://github.com/apache/incubator-yunikorn-release/blob/master/release-top-level-artifacts/CHANGELOG]
file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-734) Tag release 0.11.0 and update go mod files
[ https://issues.apache.org/jira/browse/YUNIKORN-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-734. --- Resolution: Fixed go.mod files are updated and the tags are created > Tag release 0.11.0 and update go mod files > -- > > Key: YUNIKORN-734 > URL: https://issues.apache.org/jira/browse/YUNIKORN-734 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: core - common, shim - kubernetes >Reporter: Tao Yang >Assignee: Kinga Marton >Priority: Blocker > Fix For: 0.11 > > > After tagging for the 0.11.0 release the dependencies for the core and shim > need to be updated to point to the new tag. > Order: > * tag si and web > * tag core and go mod update (si ref) > * tag shim and go mod update (core and si ref) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-739) Update the website for v0.11
[ https://issues.apache.org/jira/browse/YUNIKORN-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton updated YUNIKORN-739: -- Summary: Update the website for v0.11 (was: CLONE - Update the website for v0.10) > Update the website for v0.11 > > > Key: YUNIKORN-739 > URL: https://issues.apache.org/jira/browse/YUNIKORN-739 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: website >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Major > Fix For: 0.11 > > > Updates include: > * Create a new documentation version. > * Create the release announcement. > * Update the download page of the website. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-739) Update the website for v0.11
[ https://issues.apache.org/jira/browse/YUNIKORN-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton reassigned YUNIKORN-739: - Assignee: Kinga Marton (was: Tao Yang) > Update the website for v0.11 > > > Key: YUNIKORN-739 > URL: https://issues.apache.org/jira/browse/YUNIKORN-739 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: website >Reporter: Tao Yang >Assignee: Kinga Marton >Priority: Major > Fix For: 0.11 > > > Updates include: > * Create a new documentation version. > * Create the release announcement. > * Update the download page of the website. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
