Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-54001

Jenkins master does not reflect kafka agent disconnection

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: In Progress (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: remoting-kafka-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.141 - kafka-plugin-1.1.0
    • Similar Issues:

      Description

      When the agent remoting process on a kafka node dies (or is manually killed),  Jenkins master  does not show that on the nodes page 

      Only once a job is trying to run in that agent, it will get marked as offline. 

      To repro this, connect an agent using kafka, then kill the process in the node and check the nodes page (http://jenkins:8081/computer/), you'll see the node is still online.

       

      Seems like a heartbeat/keepalive mechanism will be needed, but not sure if this is possible.  with the current architecture.

       

       

       

        Attachments

          Activity

            People

            Assignee:
            pvtuan10 Pham Vu Tuan
            Reporter:
            fnaum Federico Naum
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: