niketh opened a new issue #7376: Failing Broker Queries - Faulty Channel
URL: https://github.com/apache/incubator-druid/issues/7376
 
 
   Broker queries fail with Faulty Channel Exception
   
   ### Description
   
   This error occurs when the broker queries fail on MM due to improper 
shutdown of Peon Task. I have patched this locally by explicitly un-announcing 
the peon task before destroy is called
   
   This change was applied here 
https://github.com/apache/incubator-druid/blob/master/indexing-service/src/main/java/org/apache/druid/indexing/overlord/ForkingTaskRunner.java#L605
   
   ```
         curatorDruidNodeAnnouncer.unannounce(new DiscoveryDruidNode(
             new DruidNode(
                 node.getServiceName(),
                 node.getHost(),
                 taskInfo.processHolder.port,
                 taskInfo.processHolder.port,
                 taskInfo.processHolder.tlsPort,
                 node.isEnablePlaintextPort(),
                 node.isEnableTlsPort()
             ),
             DruidNodeDiscoveryProvider.NODE_TYPE_PEON,
             ImmutableMap.of()
         ));
   
         try {
           log.info("Destroying task: %s . Sleeping for 10000 millis", taskid);
           Thread.sleep(10000);
         } catch (InterruptedException e) {
           log.error("Sleep interuppedted for task: %s", taskid);
         }
   
         taskInfo.processHolder.process.destroy();
   ```
   
   This is similar to https://github.com/apache/incubator-druid/issues/6043 but 
the exceptions reported there are slightly different.
   

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to