[
https://issues.apache.org/jira/browse/YUNIKORN-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17194005#comment-17194005
]
Akhil PB edited comment on YUNIKORN-406 at 9/11/20, 5:49 AM:
-------------------------------------------------------------
Hi [~wwei],
The UI (client browser) is calling the YuniKorn REST API endpoint directly by
using the following logic.
{noformat}
REST API: http://<hostname where UI is running, which is same as the scheduler
hostname>:9080/...
{noformat}
I see that changing YK scheduler port while setting port-forwarding is an
issue. The question is that how would the UI know which YK scheduler port to
be used for REST call in case YK scheduler port is changed as shown in the
above port-forwarding 9081:9080 case (assuming if we want to fix this issue)?
In the latest UI code(master), a user friendly error message will be shown
saying "Oops, Something went wrong. YuniKorn scheduler is not accessible".
was (Author: akhilpb):
Hi [~wwei],
The UI (client browser) is calling the YuniKorn REST API endpoint directly by
using the following logic.
{noformat}
REST API: http://<hostname where UI is running, which is same as the scheduler
hostname>:9080/...
{noformat}
I see that changing YK scheduler port while setting port-forwarding is an
issue. The question is that how would the UI know which YK scheduler port to
be used for REST call in case YK scheduler port is changed as shown in the
above port-forwarding 9081:9080 case (assuming if want to fix this issue)? In
the latest UI code(master), a user friendly error message will be shown saying
"Oops, Something went wrong. YuniKorn scheduler is not accessible".
> Queue/apps is not getting displayed on yunikorn UI
> --------------------------------------------------
>
> Key: YUNIKORN-406
> URL: https://issues.apache.org/jira/browse/YUNIKORN-406
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler, webapp
> Reporter: Vishwas
> Priority: Major
> Attachments: error_ui_console.PNG, node_info.PNG, queue_info.PNG
>
>
> Hi,
> I am a newbie in to yunikorn. I am using the recently release 0.9.0 helm
> chart.
> I have disabled embedAdmissionController and below is the queue configuration
> in values.yaml
>
> {code:java}
> # Use this configuration to automatically map K8s namespaces to yunikorn
> queues
> configuration: |
> partitions:
> - name: default
> placementrules:
> - name: tag
> value: namespace
> create: true
> queues:
> - name: root
> submitacl: '*'
> queues:
> - name: tpcds
> {code}
>
>
> i am trying to launch a simple sleep pod just to see if the pod gets
> allocated to proper queue.
>
> {code:java}
> apiVersion: v1
> kind: Pod
> metadata:
> labels:
> app: sleep
> applicationId: "appli-sleepp-0001"
> #queue: "root"
> namespace: tpcds
> name: app-sleep-0
> spec:
> schedulerName: yunikorn
> containers:
> - name: sleep-30s
> image: "alpine:latest"
> command: ["sleep", "inf"]
> resources:
> requests:
> cpu: "100m"
> memory: "500M"
> ---
> {code}
>
>
> I see that the job i getting allocated properly to root.tpcds queue.I am able
> to confirm this only using rest api but I am not able to see anything in
> yunikorn-ui.
>
> With rest-api:
> {code:java}
> curl http://10.75.38.79:31165/ws/v1/apps
> [
> {
> "applicationID": "appli-sleepp-0001",
> "usedResource": "[memory:500 vcore:100]",
> "partition": "[mycluster]default",
> "queueName": "root.tpcds",
> "submissionTime": 1599644324773451800,
> "allocations": [
> {
> "allocationKey": "f095ab0f-cc25-40d2-8889-2dba31f51441",
> "allocationTags": null,
> "uuid": "83d6acbe-3242-4321-9207-fd6c6d4f38b5",
> "resource": "[memory:500 vcore:100]",
> "priority": "<nil>",
> "queueName": "root.tpcds",
> "nodeId": "vm-10-75-38-73",
> "applicationId": "appli-sleepp-0001",
> "partition": "default"
> }
> ],
> "applicationState": "Running"
> }
> ]
> {code}
>
> I do not see the same info in yunikorn-ui. I have attached the node-info and
> queue-info from UI.
> I have tried on firefox and chrome and the same issue is seen.
>
> kubernetes version: 1.17
> {code:java}
> [root@vm-10-75-38-79 vbm]# kubectl version
> Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.4",
> GitCommit:"8d8aa39598534325ad77120c120a22b3a990b5ea", GitTreeState:"clean",
> BuildDate:"2020-03-12T21:03:42Z", GoVersion:"go1.13.8", Compiler:"gc",
> Platform:"linux/amd64"}
> Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.4",
> GitCommit:"8d8aa39598534325ad77120c120a22b3a990b5ea", GitTreeState:"clean",
> BuildDate:"2020-03-12T20:55:23Z", GoVersion:"go1.13.8", Compiler:"gc",
> Platform:"linux/amd64"}
> {code}
> {code:java}
> [root@vm-10-75-38-79 vbm]# kubectl get all -n yunikorn
> NAME READY STATUS RESTARTS AGE
> pod/yunikorn-scheduler-59c7657ccb-lktxp 2/2 Running 0
> 4h1mNAME TYPE CLUSTER-IP EXTERNAL-IP
> PORT(S) AGE
> service/yunikorn-service NodePort 10.254.242.166 <none>
> 9080:31165/TCP,9889:30840/TCP 4h1mNAME
> READY UP-TO-DATE AVAILABLE AGE
> deployment.apps/yunikorn-scheduler 1/1 1 1
> 4h1mNAME DESIRED CURRENT READY
> AGE
> replicaset.apps/yunikorn-scheduler-59c7657ccb 1 1 1
> 4h1m
> {code}
>
>
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
