[GitHub] [incubator-yunikorn-core] yangwwei commented on issue #90: Completed (and sometimes deleted) pods are still marked as "Running" and consume resources

[GitBox <gi...@apache.org>]

yangwwei commented on issue #90: Completed (and sometimes deleted) pods are still marked as "Running" and consume resources
URL: https://github.com/apache/incubator-yunikorn-core/issues/90#issuecomment-589878004
 
 
   Hi @jameschen1519 
   
   This is a kind of known issue for me, we are also hitting this internally while running Spark.
   For job completion, we added a completion handler in https://github.com/apache/incubator-yunikorn-k8shim/blob/fc2b3a5452acbfdea536c120fa755788baaa15fc/pkg/cache/application.go#L348, that is supposed to transit Spark job to complete after the driver completes. Somehow that is not triggered. I will look into this.
   
   > It is also worth noting that the driver and executor jobs enter the same queue regardless of what the executor podTemplateFile specifies. We are unsure if this is a feature or a bug.
   this is by design, for each job, we enforce all tasks are belonging to one same queue
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org