Azocan Kara created FLINK-24594:
-----------------------------------

             Summary: /jobs endpoint returns same job id twice (suspended and 
running) until stopped
                 Key: FLINK-24594
                 URL: https://issues.apache.org/jira/browse/FLINK-24594
             Project: Flink
          Issue Type: Bug
          Components: Runtime / Coordination, Runtime / REST
    Affects Versions: 1.13.2
            Reporter: Azocan Kara


We observe this behavior since our migration to flink 1.13.2. 

/jobs GET endpoint returns the same job id twice :

 
{code:java}
{"jobs":[{"id":"58bde1f30e0ec30d511a996b74ab2e12","status":"RUNNING"},{"id":"58bde1f30e0ec30d511a996b74ab2e12","status":"SUSPENDED"}]}
{code}
/jobs/overview GET returns :
{code:java}
{"jobs":[{"jid":"58bde1f30e0ec30d511a996b74ab2e12","name":"Enrichissement 
Incidents 
HTA","state":"RUNNING","start-time":1634479775893,"end-time":-1,"duration":173551611,"last-modification":1634584098667,"tasks":{"total":1,"created":0,"scheduled":0,"deploying":0,"running":1,"finished":0,"canceling":0,"canceled":0,"failed":0,"reconciling":0,"initializing":0}},{"jid":"58bde1f30e0ec30d511a996b74ab2e12","name":"Enrichissement
 Incidents 
HTA","state":"SUSPENDED","start-time":1634300482098,"end-time":-1,"duration":179293293,"last-modification":0,"tasks":{"total":0,"created":0,"scheduled":0,"deploying":0,"running":0,"finished":0,"canceling":0,"canceled":0,"failed":0,"reconciling":0,"initializing":0}}]}
{code}
Of course, this also shows up on the overview page of the job-manager web UI.
 
/jobs/8bde1f30e0ec30d511a996b74ab2e12 returns details of the RUNNING job. 
 
flink stop command stops the running job and both jobs disappear from /jobs and 
/jobs/overview
 
We observed this several times on clusters we have migrated to flink 1.13.2, 
not sure yet how it happens.
 
I noticed this issue : https://issues.apache.org/jira/browse/FLINK-20195 , it 
may be related but this is not exactly the same issue, I get this response 
until job is canceled / stopped.
 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to