[jira] [Resolved] (YUNIKORN-1523) add Chinese translation for release announcement 1.2
[ https://issues.apache.org/jira/browse/YUNIKORN-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1523. -- Resolution: Done > add Chinese translation for release announcement 1.2 > > > Key: YUNIKORN-1523 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1523 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: documentation, release >Reporter: Wilfred Spiegelenburg >Assignee: Chen Yu Teng >Priority: Major > Labels: pull-request-available > > Release announcement for the release 1.2 should be translated to zh-cn as > part of the release -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Closed] (YUNIKORN-1552) Emit metrics for resource usage at non-leaf queues
[ https://issues.apache.org/jira/browse/YUNIKORN-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu closed YUNIKORN-1552. Resolution: Cannot Reproduce > Emit metrics for resource usage at non-leaf queues > -- > > Key: YUNIKORN-1552 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1552 > Project: Apache YuniKorn > Issue Type: New Feature > Components: metrics >Reporter: Chaoran Yu >Assignee: Qi Zhu >Priority: Major > > YuniKorn currently has resource usage metrics for leaf queues. But sometimes > it will be useful to look at the resource usage at a non-leaf queue. For > example, for a parent queue, we want to know the total aggregate usage of all > its child queues and remaining quota for this parent queue. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1553) Queue max metrics are not available
[ https://issues.apache.org/jira/browse/YUNIKORN-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1553. -- Resolution: Cannot Reproduce > Queue max metrics are not available > --- > > Key: YUNIKORN-1553 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1553 > Project: Apache YuniKorn > Issue Type: New Feature > Components: metrics >Reporter: Chaoran Yu >Assignee: Qi Zhu >Priority: Major > > We have metrics for real-time allocations of each leaf queue, but the max > capacity metrics are not available. Max capacity of a queue can be modified > via REST APIs, scheduler ConfigMap etc and the metric tracking the max value > should automatically reflect the change. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-1553) Queue max metrics are not available
Chaoran Yu created YUNIKORN-1553: Summary: Queue max metrics are not available Key: YUNIKORN-1553 URL: https://issues.apache.org/jira/browse/YUNIKORN-1553 Project: Apache YuniKorn Issue Type: New Feature Components: metrics Reporter: Chaoran Yu We have metrics for real-time allocations of each leaf queue, but the max capacity metrics are not available. Max capacity of a queue can be modified via REST APIs, scheduler ConfigMap etc and the metric tracking the max value should automatically reflect the change. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-1552) Emit metrics for resource usage at non-leaf queues
Chaoran Yu created YUNIKORN-1552: Summary: Emit metrics for resource usage at non-leaf queues Key: YUNIKORN-1552 URL: https://issues.apache.org/jira/browse/YUNIKORN-1552 Project: Apache YuniKorn Issue Type: New Feature Components: metrics Reporter: Chaoran Yu YuniKorn currently has resource usage metrics for leaf queues. But sometimes it will be useful to look at the resource usage at a non-leaf queue. For example, for a parent queue, we want to know the total aggregate usage of all its child queues and remaining quota for this parent queue. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1495) Update the copyright years in NOTICE files to 2023
[ https://issues.apache.org/jira/browse/YUNIKORN-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1495. -- Resolution: Done > Update the copyright years in NOTICE files to 2023 > -- > > Key: YUNIKORN-1495 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1495 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Wilfred Spiegelenburg >Assignee: Ting Yao,Huang >Priority: Major > Labels: newbie, pull-request-available > > A new year is starting and we need to update the year in the NOTICE file from > 2022 to 2023: > * all 6 repos have a NOTICE file in the root > * release repo only: release-top-level-artifacts/NOTICE > See YUNIKORN-1013 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1503) Chinese translation of troubleshooting
[ https://issues.apache.org/jira/browse/YUNIKORN-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1503. -- Target Version: 1.2.0 Resolution: Done > Chinese translation of troubleshooting > -- > > Key: YUNIKORN-1503 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1503 > Project: Apache YuniKorn > Issue Type: Task >Reporter: Chen Yu Teng >Assignee: Wu hsuang zong >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1313) update release procedure gpg key for helm signing
[ https://issues.apache.org/jira/browse/YUNIKORN-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1313. -- Resolution: Fixed > update release procedure gpg key for helm signing > - > > Key: YUNIKORN-1313 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1313 > Project: Apache YuniKorn > Issue Type: Task > Components: release >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Labels: pull-request-available > > The gpg secring requirement for the helm chart signing is not clear we should > pull in more of the doc from helm to explain what is needed and what to check. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1521) fix release announcement jira links
[ https://issues.apache.org/jira/browse/YUNIKORN-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1521. -- Fix Version/s: 1.2.0 Resolution: Fixed > fix release announcement jira links > --- > > Key: YUNIKORN-1521 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1521 > Project: Apache YuniKorn > Issue Type: Task > Components: documentation >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Minor > Labels: pull-request-available > Fix For: 1.2.0 > > > The releases 0.12.2 and 1.1.0 contain broken links for the jiras that are > fixed in the release. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1504) Chinese translation of Run MPI jobs in workload
[ https://issues.apache.org/jira/browse/YUNIKORN-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1504. -- Resolution: Done > Chinese translation of Run MPI jobs in workload > --- > > Key: YUNIKORN-1504 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1504 > Project: Apache YuniKorn > Issue Type: Task >Reporter: Chen Yu Teng >Assignee: Wu hsuang zong >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1479) Yunikorn Dashboard fa-question link got broken
[ https://issues.apache.org/jira/browse/YUNIKORN-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1479. -- Fix Version/s: 1.2.0 Resolution: Fixed > Yunikorn Dashboard fa-question link got broken > -- > > Key: YUNIKORN-1479 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1479 > Project: Apache YuniKorn > Issue Type: Bug > Components: webapp >Reporter: Jagadeesan A S >Assignee: Jagadeesan A S >Priority: Minor > Labels: pull-request-available > Fix For: 1.2.0 > > > Yunikorn Dashboard UI, Help icon link got broken > It needs to redirect to https://yunikorn.apache.org/community/events > but currently https://yunikorn.apache.org/community/events/sessions -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1444) contribution guideline update: jira signup procedure
[ https://issues.apache.org/jira/browse/YUNIKORN-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1444. -- Resolution: Done > contribution guideline update: jira signup procedure > - > > Key: YUNIKORN-1444 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1444 > Project: Apache YuniKorn > Issue Type: Task > Components: website >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Labels: pull-request-available > > The public signup for Jira was disabled, this disables new people from > creating a Jira account, in order to prevent spamming around Jira. > The Infra page with the details: > [https://infra.apache.org/jira-guidelines.html] > Based on the email thread we'll use an email to private@ and the slack > channel to request a Jira account -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1355) Generic example of GPU scheduling with Yunikorn
[ https://issues.apache.org/jira/browse/YUNIKORN-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1355. -- Resolution: Done > Generic example of GPU scheduling with Yunikorn > --- > > Key: YUNIKORN-1355 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1355 > Project: Apache YuniKorn > Issue Type: Improvement > Components: deployment >Reporter: Chen, Kai-Chun >Assignee: Chen, Kai-Chun >Priority: Minor > Labels: pull-request-available > > [https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/gpu-sharing.html#testing-gpu-time-slicing-with-the-nvidia-gpu-operator] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1429) Support k8s ingress on helm chart for yunikorn ui
[ https://issues.apache.org/jira/browse/YUNIKORN-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1429. -- Target Version: 1.2.0 Resolution: Done > Support k8s ingress on helm chart for yunikorn ui > - > > Key: YUNIKORN-1429 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1429 > Project: Apache YuniKorn > Issue Type: Improvement > Components: release >Reporter: Wansoo Kim >Assignee: Wansoo Kim >Priority: Minor > Labels: pull-request-available > > Port-forwarding is required to access web ui from helm chart. We need to > support `ingress` to make it accessible from outside the cluster. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1034) Add Chinese translation for performance documents
[ https://issues.apache.org/jira/browse/YUNIKORN-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1034. -- Resolution: Done > Add Chinese translation for performance documents > - > > Key: YUNIKORN-1034 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1034 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: documentation >Reporter: cdmikechen >Assignee: Chen Yu Teng >Priority: Major > Labels: pull-request-available > > Add Chinese translation for user guide documents, this is a sub task on > https://issues.apache.org/jira/browse/YUNIKORN-1029 > This issue include YuniKorn site performance documents. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-1282) Resource metrics are not tracked correctly for all queue types
Chaoran Yu created YUNIKORN-1282: Summary: Resource metrics are not tracked correctly for all queue types Key: YUNIKORN-1282 URL: https://issues.apache.org/jira/browse/YUNIKORN-1282 Project: Apache YuniKorn Issue Type: Bug Components: core - common Affects Versions: 1.0.0 Reporter: Chaoran Yu Assignee: Chaoran Yu Fix For: 1.1.0 Based on the conversation on Slack: [https://yunikornworkspace.slack.com/archives/CL9CRJ1KM/p1660758189285209], currently metrics for resource usage have two issues: * Metrics are only tracked for leaf queues. No metrics are exported for non-leaf queues. * Metrics are not updated in all places when they should be updated: when config is updated and when nodes are updated in the cluster -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-868) Add doc to address that placeholder now supports affinity
[ https://issues.apache.org/jira/browse/YUNIKORN-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-868. - Resolution: Done > Add doc to address that placeholder now supports affinity > - > > Key: YUNIKORN-868 > URL: https://issues.apache.org/jira/browse/YUNIKORN-868 > Project: Apache YuniKorn > Issue Type: Task > Components: documentation >Reporter: Weiwei Yang >Assignee: Ted Lin >Priority: Major > Labels: pull-request-available > > YUNIKORN-861 adds affinity support for GS placeholders, we need to update the > doc accordingly. > http://yunikorn.apache.org/docs/next/user_guide/gang_scheduling#how-to-define-task-groups. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-1261) Helm upgrade does not detect changes in ConfigMap
Chaoran Yu created YUNIKORN-1261: Summary: Helm upgrade does not detect changes in ConfigMap Key: YUNIKORN-1261 URL: https://issues.apache.org/jira/browse/YUNIKORN-1261 Project: Apache YuniKorn Issue Type: Bug Components: release Affects Versions: 1.0.0 Reporter: Chaoran Yu For an existing Helm release of YuniKorn, when there's a change in the ConfigMap (e.g. new queue configurations) and the release is upgraded using the "helm upgrade" command, the ConfigMap doesn't get updated -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1236) add artifacthub-repo.yml file for helm
[
https://issues.apache.org/jira/browse/YUNIKORN-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chaoran Yu resolved YUNIKORN-1236.
--
Resolution: Fixed
> add artifacthub-repo.yml file for helm
> --
>
> Key: YUNIKORN-1236
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1236
> Project: Apache YuniKorn
> Issue Type: Task
> Components: release
>Reporter: Wilfred Spiegelenburg
>Assignee: Wilfred Spiegelenburg
>Priority: Major
> Labels: pull-request-available
>
> To claim ownership of the helm charts again we need to have a
> \{{artifacthub-repo.yml}} file. The file should contain the owner emails to
> allow us to take back ownership of the repo.
> See [ownership
> claim|https://github.com/artifacthub/hub/blob/master/docs/repositories.md#ownership-claim]
> on the artifact hub.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1223) Add Chinese translation for 1.0.0 Release
[ https://issues.apache.org/jira/browse/YUNIKORN-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1223. -- Resolution: Done > Add Chinese translation for 1.0.0 Release > - > > Key: YUNIKORN-1223 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1223 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: documentation >Reporter: cdmikechen >Assignee: cdmikechen >Priority: Major > Labels: pull-request-available > > Documents changed: > # download.md > # roadmap.md > # 1.0.0.md -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-1224) Failed to publish website due to incompatible node version
Chaoran Yu created YUNIKORN-1224: Summary: Failed to publish website due to incompatible node version Key: YUNIKORN-1224 URL: https://issues.apache.org/jira/browse/YUNIKORN-1224 Project: Apache YuniKorn Issue Type: Bug Components: website Reporter: Chaoran Yu Assignee: Chaoran Yu Fix For: 1.1.0 Website publish no longer works. Example: [https://github.com/apache/yunikorn-site/runs/6638395350?check_suite_focus=true#step:3:73.] The error is: yarn install v1.22.15 [64|https://github.com/apache/yunikorn-site/runs/6638395350?check_suite_focus=true#step:3:65]info No lockfile found. [65|https://github.com/apache/yunikorn-site/runs/6638395350?check_suite_focus=true#step:3:66][1/4] Resolving packages... [66|https://github.com/apache/yunikorn-site/runs/6638395350?check_suite_focus=true#step:3:67][2/4] Fetching packages... [67|https://github.com/apache/yunikorn-site/runs/6638395350?check_suite_focus=true#step:3:68]error @docusaurus/core@2.0.0-beta.21: The engine "node" is incompatible with this module. Expected version ">=16.14". Got "16.13.0" [68|https://github.com/apache/yunikorn-site/runs/6638395350?check_suite_focus=true#step:3:69]info Visit [https://yarnpkg.com/en/docs/cli/install] for documentation about this command. [69|https://github.com/apache/yunikorn-site/runs/6638395350?check_suite_focus=true#step:3:70]error Found incompatible module. [70|https://github.com/apache/yunikorn-site/runs/6638395350?check_suite_focus=true#step:3:71]The command '/bin/sh -c yarn install' returned a non-zero code: 1 [71|https://github.com/apache/yunikorn-site/runs/6638395350?check_suite_focus=true#step:3:72] Need to change the base image to use node 16.14 or higher -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1174) Document changes from YUNIKORN-998
[ https://issues.apache.org/jira/browse/YUNIKORN-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1174. -- Resolution: Done > Document changes from YUNIKORN-998 > -- > > Key: YUNIKORN-1174 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1174 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: documentation, website >Reporter: Craig Condit >Assignee: Craig Condit >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1173) Basic scheduling fails on an existing cluster
[ https://issues.apache.org/jira/browse/YUNIKORN-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1173. -- Resolution: Cannot Reproduce > Basic scheduling fails on an existing cluster > - > > Key: YUNIKORN-1173 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1173 > Project: Apache YuniKorn > Issue Type: Bug > Components: shim - kubernetes >Reporter: Chaoran Yu >Priority: Blocker > Attachments: logs.txt, statedump.txt > > > Environment: EKS K8s 1.20. > K8shim built based on commit: > [https://github.com/apache/yunikorn-k8shim/commit/be3bb70d9757b27d0c40d446306b928c79c80a9f] > Core version used: v0.0.0-20220325135453-73d55282f052 > After YuniKorn is deployed, I deleted one of the pods managed by K8s > deployment, but YK didn't schedule the new pod that's created: > *spo-og60-03-spark-operator-86cc7ff747-9vzxl* > is the name of the new pod. It's stuck in pending and its event said > "spark-operator/spo-og60-03-spark-operator-86cc7ff747-9vzxl is queued and > waiting for allocation" > State dump and scheduler logs are attached -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-1173) Basic scheduling fails on an existing cluster
Chaoran Yu created YUNIKORN-1173: Summary: Basic scheduling fails on an existing cluster Key: YUNIKORN-1173 URL: https://issues.apache.org/jira/browse/YUNIKORN-1173 Project: Apache YuniKorn Issue Type: Bug Components: shim - kubernetes Reporter: Chaoran Yu Attachments: logs.txt, statedump.txt Environment: EKS K8s 1.20. K8shim built based on commit: [https://github.com/apache/yunikorn-k8shim/commit/be3bb70d9757b27d0c40d446306b928c79c80a9f] Core version used: v0.0.0-20220325135453-73d55282f052 After YuniKorn is deployed, I deleted one of the pods managed by K8s deployment, but YK didn't schedule the new pod that's created: *spo-og60-03-spark-operator-86cc7ff747-9vzxl* is the name of the new pod. It's stuck in pending and its event said "spark-operator/spo-og60-03-spark-operator-86cc7ff747-9vzxl is queued and waiting for allocation" State dump and scheduler logs are attached -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-1143) Create a troubleshooting guide
Chaoran Yu created YUNIKORN-1143: Summary: Create a troubleshooting guide Key: YUNIKORN-1143 URL: https://issues.apache.org/jira/browse/YUNIKORN-1143 Project: Apache YuniKorn Issue Type: Task Components: website Reporter: Chaoran Yu We need to create a user-facing troubleshooting guide that includes info on: * Common scheduling failure scenarios * What to look for when there's an issue with the scheduler (logs, YuniKorn UI, etc) * Information to persist: scheduler logs, UI screenshots, scheduler state dump, REST endpoint results etc) * Next steps: common troubleshooting steps and what to do if those don't work (e.g. file a Jira and include the info recorded in the preceding step) -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1138) rename the variables that end with infos and informations
[
https://issues.apache.org/jira/browse/YUNIKORN-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chaoran Yu resolved YUNIKORN-1138.
--
Resolution: Fixed
> rename the variables that end with infos and informations
> -
>
> Key: YUNIKORN-1138
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1138
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
>Reporter: ted
>Assignee: ted
>Priority: Minor
> Labels: newbie, pull-request-available
>
> {{informations}} and {{infos}} are not valid words.
> rename the variables that end with {{informations}} and {{infos}} by removing
> the {{s.}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1123) UpdateNode may cause the scheduler to crash
[
https://issues.apache.org/jira/browse/YUNIKORN-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chaoran Yu resolved YUNIKORN-1123.
--
Resolution: Fixed
> UpdateNode may cause the scheduler to crash
> ---
>
> Key: YUNIKORN-1123
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1123
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
>Reporter: Chaoran Yu
>Assignee: Manikandan R
>Priority: Critical
> Labels: pull-request-available
>
> [https://github.com/apache/incubator-yunikorn-core/blob/master/pkg/rmproxy/rmproxy.go#L369]
> may cause the scheduler to crash because the node.Attributes map could be
> uninitialized.
> Example:
>
> {code:java}
> 2022-03-16T05:22:46.077Z INFO cache/nodes.go:216 report updated nodes to
> scheduler {"request":
> "nodes: action:DECOMISSION > rmID:\"mycluster\" "}
> panic: assignment to entry in nil map
> goroutine 395199 [running]:
> github.com/apache/incubator-yunikorn-core/pkg/rmproxy.(*RMProxy).UpdateNode.func1(0xc02d9fa320,
> 0xc00030)
>
> /go/pkg/mod/github.com/apache/incubator-yunikorn-core@v0.0.0-20220221055154-ff851af3b358/pkg/rmproxy/rmproxy.go:368
> +0x11d
> created by
> github.com/apache/incubator-yunikorn-core/pkg/rmproxy.(*RMProxy).UpdateNode
>
> /go/pkg/mod/github.com/apache/incubator-yunikorn-core@v0.0.0-20220221055154-ff851af3b358/pkg/rmproxy/rmproxy.go:364
> +0x7a
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-1123) UpdateNode may cause the scheduler to crash
Chaoran Yu created YUNIKORN-1123:
Summary: UpdateNode may cause the scheduler to crash
Key: YUNIKORN-1123
URL: https://issues.apache.org/jira/browse/YUNIKORN-1123
Project: Apache YuniKorn
Issue Type: Bug
Components: core - scheduler
Reporter: Chaoran Yu
[https://github.com/apache/incubator-yunikorn-core/blob/master/pkg/rmproxy/rmproxy.go#L369]
may cause the scheduler to crash because the node.Attributes map could be
uninitialized.
Example:
{code:java}
2022-03-16T05:22:46.077Z INFO cache/nodes.go:216 report updated nodes to
scheduler {"request":
"nodes: rmID:\"mycluster\" "}
panic: assignment to entry in nil map
goroutine 395199 [running]:
github.com/apache/incubator-yunikorn-core/pkg/rmproxy.(*RMProxy).UpdateNode.func1(0xc02d9fa320,
0xc00030)
/go/pkg/mod/github.com/apache/incubator-yunikorn-core@v0.0.0-20220221055154-ff851af3b358/pkg/rmproxy/rmproxy.go:368
+0x11d
created by
github.com/apache/incubator-yunikorn-core/pkg/rmproxy.(*RMProxy).UpdateNode
/go/pkg/mod/github.com/apache/incubator-yunikorn-core@v0.0.0-20220221055154-ff851af3b358/pkg/rmproxy/rmproxy.go:364
+0x7a
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1096) Add Release Announcement v0.12.2 translation zh-cn
[ https://issues.apache.org/jira/browse/YUNIKORN-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1096. -- Resolution: Done > Add Release Announcement v0.12.2 translation zh-cn > -- > > Key: YUNIKORN-1096 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1096 > Project: Apache YuniKorn > Issue Type: Improvement > Components: website >Reporter: cdmikechen >Priority: Major > Labels: pull-request-available > > Add Release Announcement v0.12.2 translation zh-cn -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-1085) DaemonSet pods may fail to be scheduled on new nodes added during autoscaling
Chaoran Yu created YUNIKORN-1085: Summary: DaemonSet pods may fail to be scheduled on new nodes added during autoscaling Key: YUNIKORN-1085 URL: https://issues.apache.org/jira/browse/YUNIKORN-1085 Project: Apache YuniKorn Issue Type: Bug Components: shim - kubernetes Affects Versions: 0.12.2 Environment: Amazon EKS, K8s 1.20, Cluster Autoscaler Reporter: Chaoran Yu After YUNIKORN-704 was done, YuniKorn should have the same mechanism as the default scheduler when it comes to scheduling DaemonSet pods. That's the case most times in our deployments. But recently we have found that DaemonSet scheduling became problematic again: When K8s Cluster Autoscaler adds new nodes in response to pending pods in the cluster, EKS will automatically create a CNI DaemonSet (Amazon's container networking module), one pod on each newly created node. But YuniKorn could not schedule these pods successfully. There's no informative error messages. The default queue that these pods belong to have available resources too. Because they couldn't be scheduled, EKS refuses to mark the new nodes as ready, they then get stuck in NotReady state. This issue is not always reproducible, but it has happened a few times. The root cause needs to be further researched -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1082) Helm should honor imagePullSecrets for admission controller
[ https://issues.apache.org/jira/browse/YUNIKORN-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1082. -- Resolution: Fixed > Helm should honor imagePullSecrets for admission controller > --- > > Key: YUNIKORN-1082 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1082 > Project: Apache YuniKorn > Issue Type: Bug > Components: release >Reporter: Craig Condit >Assignee: Craig Condit >Priority: Major > Labels: pull-request-available > > Currently, imagePullSecrets are only used for the scheduler deployment, not > the admission controller. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1081) Don't expose admission controller externally by default
[ https://issues.apache.org/jira/browse/YUNIKORN-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1081. -- Resolution: Fixed > Don't expose admission controller externally by default > --- > > Key: YUNIKORN-1081 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1081 > Project: Apache YuniKorn > Issue Type: Task > Components: release >Reporter: Craig Condit >Assignee: Craig Condit >Priority: Major > Labels: pull-request-available > > In our helm charts, we currently define the admission controller service as a > LoadBalancer. This should be ClusterIP instead. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1046) Fix website footer
[ https://issues.apache.org/jira/browse/YUNIKORN-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1046. -- Resolution: Fixed > Fix website footer > -- > > Key: YUNIKORN-1046 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1046 > Project: Apache YuniKorn > Issue Type: Task > Components: website >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Labels: newbie, pull-request-available > > The footer of the website contains a couple of issues: > * links to only 4 of the 6 repositories (release and web site) > * points to old blogs (release of 0.8) > * points to roster while we have a people page > * blog should be replaced with a link to the events under community -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1079) fix internal links in the release procedure
[ https://issues.apache.org/jira/browse/YUNIKORN-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1079. -- Resolution: Fixed > fix internal links in the release procedure > --- > > Key: YUNIKORN-1079 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1079 > Project: Apache YuniKorn > Issue Type: Task > Components: website >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Labels: pull-request-available > > Internal links in the release procedure document do not work after moving the > doc from the github repo to the website. > The internal links in the markdown document use mixed lower and upper case > they should all be lower case. > There is a difference between how the github rendering and the website > rendering works. The mixed case works in the github rendering not in the > website. > example: > * > [https://yunikorn.apache.org/community/release_procedure/#Create-a-Release] > fail > * > [https://yunikorn.apache.org/community/release_procedure/#create-a-release] > works > * > [https://github.com/apache/incubator-yunikorn-release/blob/branch-0.11/docs/release-procedure.md#Create-a-Release] > works > * > [https://github.com/apache/incubator-yunikorn-release/blob/branch-0.11/docs/release-procedure.md#create-a-release] > works -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1071) Update website for YuniKorn Meetup in Feb 2022
[ https://issues.apache.org/jira/browse/YUNIKORN-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1071. -- Resolution: Done > Update website for YuniKorn Meetup in Feb 2022 > -- > > Key: YUNIKORN-1071 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1071 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Chenya Zhang >Assignee: Chenya Zhang >Priority: Major > Labels: pull-request-available > > Update the "Events" section of the website. > https://yunikorn.apache.org/community/events -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1047) Move release procedure documentation from git repo to the website
[ https://issues.apache.org/jira/browse/YUNIKORN-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1047. -- Resolution: Done > Move release procedure documentation from git repo to the website > - > > Key: YUNIKORN-1047 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1047 > Project: Apache YuniKorn > Issue Type: Task > Components: website >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Labels: pull-request-available > > We have a clearly document release procedure. This procedure should be part > of the website and is documentation under the community not hidden in the > release repo. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1059) Add Chinese translation for get started documents
[ https://issues.apache.org/jira/browse/YUNIKORN-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1059. -- Resolution: Done > Add Chinese translation for get started documents > - > > Key: YUNIKORN-1059 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1059 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: cdmikechen >Assignee: cdmikechen >Priority: Major > Labels: pull-request-available > > Add Chinese translation for get started documents, this is a sub task on > https://issues.apache.org/jira/browse/YUNIKORN-1029 > This issue include YuniKorn site get started documents. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-1042) "Why YuniKorn" is not rendered properly on mobile
Chaoran Yu created YUNIKORN-1042: Summary: "Why YuniKorn" is not rendered properly on mobile Key: YUNIKORN-1042 URL: https://issues.apache.org/jira/browse/YUNIKORN-1042 Project: Apache YuniKorn Issue Type: Bug Components: website Reporter: Chaoran Yu Attachments: IMG_499E342B4680-1.jpeg Likely due to YUNIKORN-1036, now the Why YuniKorn section is not rendered properly when viewed on mobile. See the attached screenshot -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1036) Fix why yunikorn doc format on the home page
[ https://issues.apache.org/jira/browse/YUNIKORN-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1036. -- Resolution: Fixed > Fix why yunikorn doc format on the home page > > > Key: YUNIKORN-1036 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1036 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Weiwei Yang >Assignee: Weiwei Yang >Priority: Major > Labels: pull-request-available > > Currently, this is an image file, not flexible to provide different language > versions. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-1038) Admission controller does not ignore the YuniKorn scheduler pod
Chaoran Yu created YUNIKORN-1038: Summary: Admission controller does not ignore the YuniKorn scheduler pod Key: YUNIKORN-1038 URL: https://issues.apache.org/jira/browse/YUNIKORN-1038 Project: Apache YuniKorn Issue Type: Bug Components: shim - kubernetes Affects Versions: 0.12.2 Reporter: Chaoran Yu Fix For: 1.0.0 The admission controller currently intercepts the YuniKorn scheduler pod just like other pods. This shouldn't happen because YuniKorn won't there to schedule itself when it's restarting. This is caused by not returning the value at this line [https://github.com/apache/incubator-yunikorn-k8shim/blob/v0.12.2-1/pkg/plugin/admissioncontrollers/webhook/admission_controller.go#L127] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-1006) Address QU 30, 40, 50
[ https://issues.apache.org/jira/browse/YUNIKORN-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1006. -- Resolution: Done > Address QU 30, 40, 50 > - > > Key: YUNIKORN-1006 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1006 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Weiwei Yang >Assignee: Weiwei Yang >Priority: Major > Labels: pull-request-available > > QU30 > The project provides a well-documented, secure and private channel to report > security issues, along with a documented way of responding to them. > QU40 > The project puts a high priority on backwards compatibility and aims to > document any incompatible changes and provide tools and documentation to help > users transition to new features. > CO50 > The project documents how contributors can earn more rights such as commit > access or decision power, and applies these principles consistently. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-988) The YuniKorn logo doesn't render correctly on mobile
[ https://issues.apache.org/jira/browse/YUNIKORN-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-988. - Resolution: Fixed > The YuniKorn logo doesn't render correctly on mobile > > > Key: YUNIKORN-988 > URL: https://issues.apache.org/jira/browse/YUNIKORN-988 > Project: Apache YuniKorn > Issue Type: Bug > Components: website >Reporter: Chaoran Yu >Assignee: Wilfred Spiegelenburg >Priority: Major > Labels: newbie, pull-request-available > Attachments: IMG_2178.jpg, IMG_390AF0ABB151-1.jpeg, > site_screenshot_darkmode.jpeg > > > The YuniKorn logo appears to be distorted when viewing the website from > mobile. Tried with multiple mobile browsers and it's the same. Please see the > attached screenshot. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-996) update roadmap with v1.0 plan
[ https://issues.apache.org/jira/browse/YUNIKORN-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-996. - Resolution: Done > update roadmap with v1.0 plan > - > > Key: YUNIKORN-996 > URL: https://issues.apache.org/jira/browse/YUNIKORN-996 > Project: Apache YuniKorn > Issue Type: Task > Components: website >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Major > Labels: pull-request-available > > update the roadmap with the outcome of this discussion: > https://lists.apache.org/thread/b1rr6jj1sjkow53fcb0pxpq0nkqgbngh -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-828) Add YuniKorn core's queue-level capacity (guaranteed, max) metrics
[ https://issues.apache.org/jira/browse/YUNIKORN-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-828. - Resolution: Done > Add YuniKorn core's queue-level capacity (guaranteed, max) metrics > -- > > Key: YUNIKORN-828 > URL: https://issues.apache.org/jira/browse/YUNIKORN-828 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: core - common >Reporter: Chenya Zhang >Assignee: Chenya Zhang >Priority: Major > Labels: pull-request-available > > Queue-level capacity metrics (guaranteed resource, max resource) are not > implemented in code. > Users need to adjust the capacity threshold manually from any monitoring > dashboard if their queue capacity changes. > It is hard for users to evaluate and demonstrate historical usage trend. Not > a small amount of manual work is needed by users or dev ops. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-989) Update the copyright years in NOTICE file to 2022
Chaoran Yu created YUNIKORN-989: --- Summary: Update the copyright years in NOTICE file to 2022 Key: YUNIKORN-989 URL: https://issues.apache.org/jira/browse/YUNIKORN-989 Project: Apache YuniKorn Issue Type: Task Reporter: Chaoran Yu Fix For: 1.0.0 Similar to https://issues.apache.org/jira/browse/YUNIKORN-617, we need to do it again but for 2022 this time -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-988) The YuniKorn logo doesn't render correctly on mobile
Chaoran Yu created YUNIKORN-988: --- Summary: The YuniKorn logo doesn't render correctly on mobile Key: YUNIKORN-988 URL: https://issues.apache.org/jira/browse/YUNIKORN-988 Project: Apache YuniKorn Issue Type: Bug Components: website Reporter: Chaoran Yu Attachments: IMG_2178.jpg The YuniKorn logo appears to be distorted when viewing the website from mobile. Tried with multiple mobile browsers and it's the same. Please see the attached screenshot. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-987) remove references to Cloudera jiras
[ https://issues.apache.org/jira/browse/YUNIKORN-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-987. - Resolution: Fixed > remove references to Cloudera jiras > --- > > Key: YUNIKORN-987 > URL: https://issues.apache.org/jira/browse/YUNIKORN-987 > Project: Apache YuniKorn > Issue Type: Task > Components: test - e2e >Reporter: Wilfred Spiegelenburg >Assignee: Ryan Lo >Priority: Major > Labels: newbie, pull-request-available > > Two references for internal Cloudera jiras have slipped into the Apache code > base. > Both references should be removed. > COMPX-4042 in predicates_suite_test.go (twice): > Link to jira should be removed, comment text explains it all. > COMPX-4041 in drip_feed_schedule_test.go: > The test is not disabled and the comments referencing YUNIKORN-317 and > COMPX-4041 should be removed as they are not relevant. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-891) [Umbrella] YuniKorn 0.12 release-related efforts
[ https://issues.apache.org/jira/browse/YUNIKORN-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-891. - Resolution: Done > [Umbrella] YuniKorn 0.12 release-related efforts > > > Key: YUNIKORN-891 > URL: https://issues.apache.org/jira/browse/YUNIKORN-891 > Project: Apache YuniKorn > Issue Type: Task >Reporter: Chaoran Yu >Assignee: Chaoran Yu >Priority: Major > > This umbrella is to track the work items needed for the 0.12.0 release. > Release manager: Chaoran Yu. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-903) Clean up the release area on the download site
[ https://issues.apache.org/jira/browse/YUNIKORN-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-903. - Resolution: Done > Clean up the release area on the download site > -- > > Key: YUNIKORN-903 > URL: https://issues.apache.org/jira/browse/YUNIKORN-903 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Chaoran Yu >Assignee: Chaoran Yu >Priority: Major > > 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.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-901) Update the website for v0.12
[ https://issues.apache.org/jira/browse/YUNIKORN-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-901. - Resolution: Done > Update the website for v0.12 > > > Key: YUNIKORN-901 > URL: https://issues.apache.org/jira/browse/YUNIKORN-901 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: website >Reporter: Chaoran Yu >Assignee: Chaoran Yu >Priority: Major > Labels: pull-request-available > > 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.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-721) Improve YuniKorn core's queue-level and scheduler metrics
[ https://issues.apache.org/jira/browse/YUNIKORN-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-721. - Resolution: Done > Improve YuniKorn core's queue-level and scheduler metrics > - > > Key: YUNIKORN-721 > URL: https://issues.apache.org/jira/browse/YUNIKORN-721 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: core - common >Reporter: Chenya Zhang >Assignee: Chenya Zhang >Priority: Major > Labels: pull-request-available > > To improve YuniKorn core's queue-level and scheduler metrics: > - Differentiate queue level metrics with scheduler metrics, e.g. using > "IncQueueApplicationsAccepted" > - Refactor related queue and scheduler metrics definitions > - Refactor related queue and scheduler metrics operation functions > - Update metrics naming and help messages > - Update in-line comments and documentations -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-717) Refactor YuniKorn core's scheduler metrics for node number and sorting latency
[ https://issues.apache.org/jira/browse/YUNIKORN-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-717. - Resolution: Done > Refactor YuniKorn core's scheduler metrics for node number and sorting latency > -- > > Key: YUNIKORN-717 > URL: https://issues.apache.org/jira/browse/YUNIKORN-717 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: core - common >Reporter: Chenya Zhang >Assignee: Chenya Zhang >Priority: Major > Labels: pull-request-available > > Defining "totalNodeActive" and "totalNodeFailed" to initialize scheduler > metrics is redundant in code. > * It can be combined into "node" > * It can use a "prometheus.CounterVec" with different Prometheus labels > Defining "nodeSortingLatency", "appSortingLatency", and "queueSortingLatency" > to initialize scheduler metrics is redundant in code. > * It can be combined into "sortingLatency" > * It can use a "prometheus.CounterVec" with different Prometheus labels -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-796) Pod scheduling could disproportionately concentrate on one node
[ https://issues.apache.org/jira/browse/YUNIKORN-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-796. - Assignee: Chaoran Yu Resolution: Cannot Reproduce Resolving as Cannot Reproduce for now because I haven't seen this symptom for some time now. I'll either re-open it or create another one with more details if it happens again > Pod scheduling could disproportionately concentrate on one node > --- > > Key: YUNIKORN-796 > URL: https://issues.apache.org/jira/browse/YUNIKORN-796 > Project: Apache YuniKorn > Issue Type: Bug > Components: core - scheduler >Reporter: Chaoran Yu >Assignee: Chaoran Yu >Priority: Major > > We've observed a few cases when YK keeps scheduling incoming pods to just one > node, even though the cluster has many other nodes that have abundant > resources. Not sure what could be causing this behavior because we don't see > it in every K8s cluster we have. Maybe somewhere in the node sorting > algorithm, a node could be favored over all other nodes under some conditions? -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-755) Update the shim repo dependencies
[ https://issues.apache.org/jira/browse/YUNIKORN-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-755. - Resolution: Invalid Closing as Invalid because the repo has been updated by other PRs > Update the shim repo dependencies > - > > Key: YUNIKORN-755 > URL: https://issues.apache.org/jira/browse/YUNIKORN-755 > Project: Apache YuniKorn > Issue Type: Task > Components: shim - kubernetes >Reporter: Weiwei Yang >Assignee: Weiwei Yang >Priority: Trivial > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-900) Update helm index for v0.12
[ https://issues.apache.org/jira/browse/YUNIKORN-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-900. - Resolution: Done > Update helm index for v0.12 > --- > > Key: YUNIKORN-900 > URL: https://issues.apache.org/jira/browse/YUNIKORN-900 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: release >Reporter: Chaoran Yu >Assignee: Chaoran Yu >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-898) Add 0.12 to the artifact hub
[ https://issues.apache.org/jira/browse/YUNIKORN-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-898. - Resolution: Duplicate > Add 0.12 to the artifact hub > > > Key: YUNIKORN-898 > URL: https://issues.apache.org/jira/browse/YUNIKORN-898 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Chaoran Yu >Assignee: Chaoran Yu >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.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-892) Create 0.12 helm chart release
[ https://issues.apache.org/jira/browse/YUNIKORN-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-892. - Resolution: Done > Create 0.12 helm chart release > -- > > Key: YUNIKORN-892 > URL: https://issues.apache.org/jira/browse/YUNIKORN-892 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: release >Reporter: Chaoran Yu >Assignee: Chaoran Yu >Priority: Major > Labels: pull-request-available > > Release the helm charts in yunikorn-release repository with following steps: > * create a new branch: branch-0.12 > * update version to 0.12 in helm-charts/yunikorn/Chart.yaml > * tag v0.12.0 (after the release notes have been written) -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-893) Create 0.12 release notes
[ https://issues.apache.org/jira/browse/YUNIKORN-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-893. - Resolution: Done > Create 0.12 release notes > - > > Key: YUNIKORN-893 > URL: https://issues.apache.org/jira/browse/YUNIKORN-893 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: release >Reporter: Chaoran Yu >Assignee: Chaoran Yu >Priority: Major > > Release notes should be updated in CHANGELOG file which will be added into > the release artifacts. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-980) Improve the release procedure
Chaoran Yu created YUNIKORN-980: --- Summary: Improve the release procedure Key: YUNIKORN-980 URL: https://issues.apache.org/jira/browse/YUNIKORN-980 Project: Apache YuniKorn Issue Type: Improvement Components: documentation, release Reporter: Chaoran Yu Given the discussions at [https://mail-archives.apache.org/mod_mbox/yunikorn-dev/202112.mbox/%3CE828F0F4-F625-4D76-81C9-DA0ED337B744%40craigcondit.com%3E], finalize a new release procedure and update [https://github.com/apache/incubator-yunikorn-release/blob/master/docs/release-procedure.md] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-896) Tag release 0.12 and update go mod files
[ https://issues.apache.org/jira/browse/YUNIKORN-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-896. - Resolution: Done > Tag release 0.12 and update go mod files > > > Key: YUNIKORN-896 > URL: https://issues.apache.org/jira/browse/YUNIKORN-896 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: core - common, shim - kubernetes >Reporter: Chaoran Yu >Assignee: Chaoran Yu >Priority: Blocker > Labels: pull-request-available > > After tagging for the 0.12 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.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-902) Update the CHANGELOG and generate the 0.12 release
[
https://issues.apache.org/jira/browse/YUNIKORN-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chaoran Yu resolved YUNIKORN-902.
-
Resolution: Done
> Update the CHANGELOG and generate the 0.12 release
> --
>
> Key: YUNIKORN-902
> URL: https://issues.apache.org/jira/browse/YUNIKORN-902
> Project: Apache YuniKorn
> Issue Type: Sub-task
>Reporter: Chaoran Yu
>Assignee: Chaoran Yu
>Priority: Major
> Labels: pull-request-available
>
> * 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.12
> * 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.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-895) Update shim and core dependencies on master branch
[ https://issues.apache.org/jira/browse/YUNIKORN-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-895. - Resolution: Done > Update shim and core dependencies on master branch > -- > > Key: YUNIKORN-895 > URL: https://issues.apache.org/jira/browse/YUNIKORN-895 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: shim - kubernetes >Reporter: Chaoran Yu >Assignee: Chaoran Yu >Priority: Blocker > Labels: pull-request-available > > 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.12 release we need to update the dependency in > branch-0.12 to start pointing to a core version in branch-0.12 > * 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.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-899) [Helm chart] Update supported K8s versions
[ https://issues.apache.org/jira/browse/YUNIKORN-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-899. - Resolution: Done > [Helm chart] Update supported K8s versions > -- > > Key: YUNIKORN-899 > URL: https://issues.apache.org/jira/browse/YUNIKORN-899 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Chaoran Yu >Assignee: Chaoran Yu >Priority: Major > Labels: newbie, pull-request-available > > Right now the README in the Helm chart has the following info related the > supported K8s versions: > supported K8s versions > |K8s Version|Support?| > |-|:-:| > |1.16.x (or earlier)|X| > |1.17.x|√| > |1.18.x|√| > |1.19.x|√| > This is not true anymore, since the shim already uses 1.20 version, and the > tests are running with 1.18 1.19 and 1.20. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-966) Retrieve the username from the SparkApp CRD
Chaoran Yu created YUNIKORN-966: --- Summary: Retrieve the username from the SparkApp CRD Key: YUNIKORN-966 URL: https://issues.apache.org/jira/browse/YUNIKORN-966 Project: Apache YuniKorn Issue Type: Sub-task Components: shim - kubernetes Reporter: Chaoran Yu Currently the shim only looks at the pods to get the value of the label yunikorn.apache.org/username. When the Spark operator plugin is enabled, we should look at the SparkApp CRD for the label. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-964) Fix vulnerabilities reported by artifacthub
[ https://issues.apache.org/jira/browse/YUNIKORN-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-964. - Resolution: Fixed > 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 >Assignee: Wilfred Spiegelenburg >Priority: Blocker > Labels: pull-request-available > 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: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-925) Add document to explain existing yunikorn metrics
[ https://issues.apache.org/jira/browse/YUNIKORN-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-925. - Resolution: Done > Add document to explain existing yunikorn metrics > - > > Key: YUNIKORN-925 > URL: https://issues.apache.org/jira/browse/YUNIKORN-925 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: core - scheduler, documentation >Reporter: Weiwei Yang >Assignee: Ting Yao,Huang >Priority: Major > Labels: pull-request-available > > We need to add a section in > http://yunikorn.apache.org/docs/next/performance/metrics, to explain existing > metrics supported by yunikorn. We should list it as a table, and have all the > supported metrics in it, including some explanation about each of these > metrics. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-944) website deployment broken due to search
[
https://issues.apache.org/jira/browse/YUNIKORN-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chaoran Yu resolved YUNIKORN-944.
-
Resolution: Fixed
> website deployment broken due to search
> ---
>
> Key: YUNIKORN-944
> URL: https://issues.apache.org/jira/browse/YUNIKORN-944
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: website
>Reporter: Wilfred Spiegelenburg
>Assignee: Wilfred Spiegelenburg
>Priority: Major
> Labels: pull-request-available
>
> The changes for the website search were only added to the deployment build
> and not to the local build script \{{./local-build.sh}}.
> Builds that pass locally do not pass when run through the git hub deploy
> action.
> Major version changes are required to update the build process and get it to
> pass with the search:
> {code:java}
> error @docusaurus/theme-search-algolia@2.0.0-beta.9: The engine "node" is
> incompatible with this module. Expected version ">=14". Got "12.18.0"
> 104info Visit https://yarnpkg.com/en/docs/cli/install for documentation about
> this command.
> 105error Found incompatible module. {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-625) Use v1 for CertificateSigningRequest instead of v1beta1
[ https://issues.apache.org/jira/browse/YUNIKORN-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-625. - Resolution: Done > Use v1 for CertificateSigningRequest instead of v1beta1 > --- > > Key: YUNIKORN-625 > URL: https://issues.apache.org/jira/browse/YUNIKORN-625 > Project: Apache YuniKorn > Issue Type: Improvement >Reporter: Kinga Marton >Assignee: Kinga Marton >Priority: Major > Labels: pull-request-available > Fix For: 1.0.0 > > > Starting from Kubernetes v. 1.19 the CertificateSigningRequest API is > promoted to certificates.k8s.io/v1 with the following changes: > * spec.signerName is now required, and requests for > kubernetes.io/legacy-unknown are not allowed to be created via the > certificates.k8s.io/v1 API > * spec.usages is now required, may not contain duplicate values, and must > only contain known usages > * status.conditions may not contain duplicate types > * status.conditions[*].status is now required > * status.certificate must be PEM-encoded, and contain only CERTIFICATE > blocks (#91685, @liggitt) [SIG API Machinery, Architecture, Auth, CLI and > Testing] > See more details at: > https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.19.md -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-908) [Umbrella] Kubernetes 1.21 support
Chaoran Yu created YUNIKORN-908: --- Summary: [Umbrella] Kubernetes 1.21 support Key: YUNIKORN-908 URL: https://issues.apache.org/jira/browse/YUNIKORN-908 Project: Apache YuniKorn Issue Type: New Feature Components: shim - kubernetes Reporter: Chaoran Yu Assignee: Chaoran Yu Fix For: 1.0.0 Need the official support for Kubernetes 1.20. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-911) CLONE - Verify helm chart install on 1.20
Chaoran Yu created YUNIKORN-911: --- Summary: CLONE - Verify helm chart install on 1.20 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: Yi Zhen Xie Fix For: 1.0.0 Similar to YUNIKORN-671 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-910) CLONE - Verify predicates functions for K8s 1.20
Chaoran Yu created YUNIKORN-910: --- Summary: CLONE - Verify predicates functions for K8s 1.20 Key: YUNIKORN-910 URL: https://issues.apache.org/jira/browse/YUNIKORN-910 Project: Apache YuniKorn Issue Type: Sub-task Components: shim - kubernetes Reporter: Chaoran Yu Assignee: Zi Ling Li Fix For: 1.0.0 _emphasized text_Similar to YUNIKORN-672 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-909) CLONE - Add 1.20 to the e2e test support matrix
Chaoran Yu created YUNIKORN-909: --- Summary: CLONE - Add 1.20 to the e2e test support matrix Key: YUNIKORN-909 URL: https://issues.apache.org/jira/browse/YUNIKORN-909 Project: Apache YuniKorn Issue Type: Sub-task Components: shim - kubernetes Reporter: Chaoran Yu Assignee: Chaoran Yu Fix For: 1.0.0 Start to cover 1.18, 1.19, 1.20 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (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:all-tabpanel
]
Chaoran Yu resolved YUNIKORN-813.
-
Resolution: Fixed
> 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
> Labels: pull-request-available
> Fix For: 1.0.0
>
>
> {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: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-897) CLONE - CLONE - Update the copyright years in NOTICE file
[ https://issues.apache.org/jira/browse/YUNIKORN-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-897. - Assignee: Chaoran Yu (was: Tao Yang) Resolution: Not A Problem This Jira was generated after cloning the parent Jira of the 0.11 release. It is no longer applicable for the 1.0 release as we are still in the year of 2021 > CLONE - CLONE - Update the copyright years in NOTICE file > - > > Key: YUNIKORN-897 > URL: https://issues.apache.org/jira/browse/YUNIKORN-897 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Chaoran Yu >Assignee: Chaoran Yu >Priority: Major > Labels: newbie, pull-request-available > Fix For: 0.11 > > > Currently, the NOTICE file in the release tarball has the following context: > "Copyright 2019-2020 The Apache Software Foundation". According to > https://www.apache.org/legal/src-headers.html#notice, we need to update the > YEAR-YEAR to 2019-2021. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-903) CLONE - Cleanup release area
Chaoran Yu created YUNIKORN-903: --- Summary: CLONE - Cleanup release area Key: YUNIKORN-903 URL: https://issues.apache.org/jira/browse/YUNIKORN-903 Project: Apache YuniKorn Issue Type: Sub-task Reporter: Chaoran Yu Assignee: Kinga Marton 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: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-904) CLONE - Update website announce bar
Chaoran Yu created YUNIKORN-904: --- Summary: CLONE - Update website announce bar Key: YUNIKORN-904 URL: https://issues.apache.org/jira/browse/YUNIKORN-904 Project: Apache YuniKorn Issue Type: Sub-task Reporter: Chaoran Yu Assignee: Kinga Marton Fix For: 0.11 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-898) CLONE - Add 0.11.0 to the artifact hub
Chaoran Yu created YUNIKORN-898: --- Summary: CLONE - Add 0.11.0 to the artifact hub Key: YUNIKORN-898 URL: https://issues.apache.org/jira/browse/YUNIKORN-898 Project: Apache YuniKorn Issue Type: Sub-task Reporter: Chaoran Yu Assignee: Kinga Marton 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: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-901) CLONE - Update the website for v0.11
Chaoran Yu created YUNIKORN-901: --- Summary: CLONE - Update the website for v0.11 Key: YUNIKORN-901 URL: https://issues.apache.org/jira/browse/YUNIKORN-901 Project: Apache YuniKorn Issue Type: Sub-task Components: website Reporter: Chaoran Yu Assignee: Kinga Marton 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: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-894) CLONE - Create the docs release for v0.11
Chaoran Yu created YUNIKORN-894: --- Summary: CLONE - Create the docs release for v0.11 Key: YUNIKORN-894 URL: https://issues.apache.org/jira/browse/YUNIKORN-894 Project: Apache YuniKorn Issue Type: Sub-task Components: documentation Reporter: Chaoran Yu Assignee: Chen Yu Teng Fix For: 0.11 Update the doc version and add the release announcement on the web site following the [release procedure|https://github.com/apache/incubator-yunikorn-release/blob/master/docs/release-procedure.md#update-the-website] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-900) CLONE - Update helm index for v0.11
Chaoran Yu created YUNIKORN-900: --- Summary: CLONE - Update helm index for v0.11 Key: YUNIKORN-900 URL: https://issues.apache.org/jira/browse/YUNIKORN-900 Project: Apache YuniKorn Issue Type: Sub-task Components: release Reporter: Chaoran Yu Assignee: Kinga Marton Fix For: 0.11 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-902) CLONE - Update the CHANGELOG and generate the release
Chaoran Yu created YUNIKORN-902:
---
Summary: CLONE - Update the CHANGELOG and generate the release
Key: YUNIKORN-902
URL: https://issues.apache.org/jira/browse/YUNIKORN-902
Project: Apache YuniKorn
Issue Type: Sub-task
Reporter: Chaoran Yu
Assignee: Kinga Marton
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: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-893) CLONE - Create 0.11.0 release notes
Chaoran Yu created YUNIKORN-893: --- Summary: CLONE - Create 0.11.0 release notes Key: YUNIKORN-893 URL: https://issues.apache.org/jira/browse/YUNIKORN-893 Project: Apache YuniKorn Issue Type: Sub-task Components: release Reporter: Chaoran Yu Assignee: Kinga Marton 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: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-895) CLONE - Update shim and core dependencies on master branch
Chaoran Yu created YUNIKORN-895: --- Summary: CLONE - Update shim and core dependencies on master branch Key: YUNIKORN-895 URL: https://issues.apache.org/jira/browse/YUNIKORN-895 Project: Apache YuniKorn Issue Type: Sub-task Components: shim - kubernetes Reporter: Chaoran Yu Assignee: Kinga Marton 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: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-899) CLONE - [Helm chart] Update supported K8s versions
Chaoran Yu created YUNIKORN-899: --- Summary: CLONE - [Helm chart] Update supported K8s versions Key: YUNIKORN-899 URL: https://issues.apache.org/jira/browse/YUNIKORN-899 Project: Apache YuniKorn Issue Type: Sub-task Reporter: Chaoran Yu Assignee: Wen-Chien,Juan 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: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-891) [Umbrella] YuniKorn 1.0 release-related efforts
Chaoran Yu created YUNIKORN-891: --- Summary: [Umbrella] YuniKorn 1.0 release-related efforts Key: YUNIKORN-891 URL: https://issues.apache.org/jira/browse/YUNIKORN-891 Project: Apache YuniKorn Issue Type: Task Reporter: Chaoran Yu Assignee: Kinga Marton 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: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-897) CLONE - CLONE - Update the copyright years in NOTICE file
Chaoran Yu created YUNIKORN-897: --- Summary: CLONE - CLONE - Update the copyright years in NOTICE file Key: YUNIKORN-897 URL: https://issues.apache.org/jira/browse/YUNIKORN-897 Project: Apache YuniKorn Issue Type: Sub-task Reporter: Chaoran Yu Assignee: Tao Yang Fix For: 0.11 Currently, the NOTICE file in the release tarball has the following context: "Copyright 2019-2020 The Apache Software Foundation". According to https://www.apache.org/legal/src-headers.html#notice, we need to update the YEAR-YEAR to 2019-2021. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-892) CLONE - Create 0.11.0 helm chart release
Chaoran Yu created YUNIKORN-892: --- Summary: CLONE - Create 0.11.0 helm chart release Key: YUNIKORN-892 URL: https://issues.apache.org/jira/browse/YUNIKORN-892 Project: Apache YuniKorn Issue Type: Sub-task Components: release Reporter: Chaoran Yu Assignee: Kinga Marton 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: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-896) CLONE - Tag release 0.11.0 and update go mod files
Chaoran Yu created YUNIKORN-896: --- Summary: CLONE - Tag release 0.11.0 and update go mod files Key: YUNIKORN-896 URL: https://issues.apache.org/jira/browse/YUNIKORN-896 Project: Apache YuniKorn Issue Type: Sub-task Components: core - common, shim - kubernetes Reporter: Chaoran Yu Assignee: Kinga Marton 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: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Closed] (YUNIKORN-833) Utilization and used capacity of queues are not displayed
[
https://issues.apache.org/jira/browse/YUNIKORN-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chaoran Yu closed YUNIKORN-833.
---
Resolution: Cannot Reproduce
> Utilization and used capacity of queues are not displayed
> -
>
> Key: YUNIKORN-833
> URL: https://issues.apache.org/jira/browse/YUNIKORN-833
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: webapp
>Reporter: Chaoran Yu
>Assignee: Chia-Ping Tsai
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Screen Shot 2021-09-02 at 3.55.42 PM.png
>
>
> Two things that used to work are no longer working:
> * the color bar showing the utilization of each queue
> * The used capacity of all queues is now {{n/a}} as shown in the attached
> screenshot
> All the metrics are still showing up correctly through the metrics REST
> endpoint
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-833) Utilization and used capacity of queues are not displayed
Chaoran Yu created YUNIKORN-833:
---
Summary: Utilization and used capacity of queues are not displayed
Key: YUNIKORN-833
URL: https://issues.apache.org/jira/browse/YUNIKORN-833
Project: Apache YuniKorn
Issue Type: Bug
Components: webapp
Reporter: Chaoran Yu
Attachments: Screen Shot 2021-09-02 at 3.55.42 PM.png
Two things that used to work are no longer working: * the color bar showing the
utilization of each queue
* The used capacity of all queues is now {{n/a}} as shown in the attached
screenshot
All the metrics are still showing up correctly through the metrics REST endpoint
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-829) Produce metrics on queue-level resource utilization
Chaoran Yu created YUNIKORN-829: --- Summary: Produce metrics on queue-level resource utilization Key: YUNIKORN-829 URL: https://issues.apache.org/jira/browse/YUNIKORN-829 Project: Apache YuniKorn Issue Type: New Feature Components: core - scheduler, shim - kubernetes Reporter: Chaoran Yu YuniKorn already has metrics on the resources requested/allocated for each queue. But we have no visibility into how much of the allocated resources are actually being used. Take Spark as an example, an under-optimized job may request 1 TB of total executor memory but the actual processing logic only uses 100 GB. This has the consequence that other jobs might not be able to fit in the queue. Having a metric that shows the real utilization will help members of a queue better understand their job characteristics and optimize the jobs. K8s metrics server has metrics on real utilization. YK may be able to perform some aggregations to arrive at the stats at the queue level. This is a k8s-specific solution though. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-796) Pod scheduling could disproportionately concentrate on one node
Chaoran Yu created YUNIKORN-796: --- Summary: Pod scheduling could disproportionately concentrate on one node Key: YUNIKORN-796 URL: https://issues.apache.org/jira/browse/YUNIKORN-796 Project: Apache YuniKorn Issue Type: Bug Components: shim - kubernetes Reporter: Chaoran Yu Fix For: 1.0.0 We've observed a few cases when YK keeps scheduling incoming pods to just one node, even though the cluster has many other nodes that have abundant resources. Not sure what could be causing this behavior because we don't see it in every K8s cluster we have. Maybe somewhere in the node sorting algorithm, a node could be favored over all other nodes under some conditions? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-788) Make the scheduler max QPS match the default Kubernetes API server max requests inflight
Chaoran Yu created YUNIKORN-788: --- Summary: Make the scheduler max QPS match the default Kubernetes API server max requests inflight Key: YUNIKORN-788 URL: https://issues.apache.org/jira/browse/YUNIKORN-788 Project: Apache YuniKorn Issue Type: Improvement Components: shim - kubernetes Reporter: Chaoran Yu Assignee: Chaoran Yu The current max QPS is configured as 1000, which is much higher than the [400|https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/] max requests inflight that the API server supports. This mismatch could cause requests to be dropped/rejected by the API server when the load is high (e.g. when a surge occurs in the number of pods that need to be scheduled). We should make the YK default match the API server default. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-764) Document how to verify a release
Chaoran Yu created YUNIKORN-764: --- Summary: Document how to verify a release Key: YUNIKORN-764 URL: https://issues.apache.org/jira/browse/YUNIKORN-764 Project: Apache YuniKorn Issue Type: Improvement Components: documentation Reporter: Chaoran Yu Assignee: Chaoran Yu Fix For: 1.0.0 We should document how a community member can go about verifying a release. For example, Flink has such a [page|https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Release]. [https://yunikorn.apache.org/community/download/] already has some info about verifying the checksums and signature. But we also need info how to perform functionality checks -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-747) Document how to run Spark applications with Spark Operator
Chaoran Yu created YUNIKORN-747: --- Summary: Document how to run Spark applications with Spark Operator Key: YUNIKORN-747 URL: https://issues.apache.org/jira/browse/YUNIKORN-747 Project: Apache YuniKorn Issue Type: Sub-task Components: documentation Reporter: Chaoran Yu -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-711) Add license file to the release repo
Chaoran Yu created YUNIKORN-711: --- Summary: Add license file to the release repo Key: YUNIKORN-711 URL: https://issues.apache.org/jira/browse/YUNIKORN-711 Project: Apache YuniKorn Issue Type: Improvement Components: release Reporter: Chaoran Yu Add Apache 2.0 license file to the release repo. The file should reside at the project root directory. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-712) Add license file to the site repo
Chaoran Yu created YUNIKORN-712: --- Summary: Add license file to the site repo Key: YUNIKORN-712 URL: https://issues.apache.org/jira/browse/YUNIKORN-712 Project: Apache YuniKorn Issue Type: Improvement Components: website Reporter: Chaoran Yu Add Apache 2.0 license file to the site repo. The file should reside at the project root directory. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-710) Document how to upgrade a scheduler Helm release
Chaoran Yu created YUNIKORN-710: --- Summary: Document how to upgrade a scheduler Helm release Key: YUNIKORN-710 URL: https://issues.apache.org/jira/browse/YUNIKORN-710 Project: Apache YuniKorn Issue Type: Improvement Components: documentation Reporter: Chaoran Yu Assignee: Chaoran Yu Per the suggestions at [https://github.com/apache/incubator-yunikorn-k8shim/pull/276#pullrequestreview-687144851,] add documentation on the following two points once [YUNIKORN-696|https://issues.apache.org/jira/browse/YUNIKORN-696] is done: * How to perform a _helm upgrade_ * Clarify that _helm upgrade_ only upgrades the scheduler not the admission-controller -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-704) Scheduling of DaemonSet pods may fail
Chaoran Yu created YUNIKORN-704: --- Summary: Scheduling of DaemonSet pods may fail Key: YUNIKORN-704 URL: https://issues.apache.org/jira/browse/YUNIKORN-704 Project: Apache YuniKorn Issue Type: Bug Components: shim - kubernetes Reporter: Chaoran Yu Attachments: fluent-bit-describe.yaml, fluent-bit.yaml We sometimes see DaemonSet pods fail to be scheduled. Please see attached files for the YAML and _kubectl describe_ output of one such pod. We originally suspected [node reservation|https://github.com/apache/incubator-yunikorn-core/blob/v0.10.0/pkg/scheduler/context.go#L41] was to blame. But even after setting the DISABLE_RESERVATION environment variable to true, we still see such scheduling failures. The issue is especially severe when K8s nodes have disk pressure that causes lots of pods to be evicted. Newly created pods will stay in pending forever. We have to temporarily uninstall YuniKorn and let the default scheduler do the scheduling for these pods. This issue is critical because lots of important pods belong to a DaemonSet, such as Fluent Bit, a common logging solution. This is probably the last remaining roadblock for us to have the confidence to have YuniKorn entirely replace the default scheduler. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-703) During recovery no nodes are added to the scheduler cache
Chaoran Yu created YUNIKORN-703: --- Summary: During recovery no nodes are added to the scheduler cache Key: YUNIKORN-703 URL: https://issues.apache.org/jira/browse/YUNIKORN-703 Project: Apache YuniKorn Issue Type: Bug Components: shim - kubernetes Reporter: Chaoran Yu When the scheduler is installed or restarted, sometimes (about 1 in 3 times) no nodes are added to the cache during the initial recovery phase. The nodes REST endpoint (/ws/v1/nodes) shows an empty list. The issue will be fixed if restart is attempted multiple times. I'll add some logs later to this Jira once I get some -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
