microsoft / microsoft/pai

Job initialization port conflict retry

Open
#5,566 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
2.7k
Forks
554
Avg merge
20h 42m
Merged PRs (30d)
14

Description

Organization Name:
Advantech

Short summary about the issue/question:
Port conflict error happened during Job initialization phase with infinite retry.

Brief what process you are following:

  1. Create a task with many port definition. The resource is enough.
  2. The job will enter status change flow loop: waiting ->running->error->waiting->running->error->...
  3. Only init.log and barrier.log are observed when jobs stay at running or error status

How to reproduce it:
Not sure the trigger condition. It will happened randomly.

OpenPAI Environment:

  • OpenPAI version:
    v1.0.1
  • Cloud provider or hardware configuration:
    Physical Machines
  • OS (e.g. from /etc/os-release):
    ubuntu 16.04
  • Kernel (e.g. uname -a):
    4.4.0-186-generic
  • Hardware (e.g. core number, memory size, storage size, GPU type etc.):
    48Core/256GB MEM/1.8TB DISK/GeForce RTX 2080 Ti
  • Others:
    a. CPU-only job with k8s default scheduler(Not hived scheduler)

Anything else we need to know:
Log files:
port_conflict_1_init.log
port_conflict_2_init.log

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the attached port_conflict_1_init.log and port_conflict_2_init.log with the reported job status loop during initialization. Determine the trigger for the port conflict and define done as preventing the job from retrying indefinitely or clearly reporting a terminal failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
distributed-systems, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.