[JIRA] (JENKINS-54001) Jenkins master does not reflect kafka agent disconnection

[phamvutua...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pham Vu Tuan started work on  JENKINS-54001  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Pham Vu Tuan  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-54001) Jenkins master does not reflect kafka agent disconnection

[federi...@al.com.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Naum created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54001  
 
 
  Jenkins master does not reflect kafka agent disconnection   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Pham Vu Tuan  
 
 
Components: 
 remoting-kafka-plugin  
 
 
Created: 
 2018-10-11 00:55  
 
 
Environment: 
 Jenkins 2.141 - kafka-plugin-1.1.0  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Federico Naum  
 

  
 
 
 
 

 
 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.        
 

  
 
 
 
 

 
 
 

 
 
 Add Comment