[jira] [Comment Edited] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

2017-12-08 Thread HongLiang (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283207#comment-16283207
 ] 

HongLiang edited comment on KAFKA-6326 at 12/8/17 8:37 AM:
---

[~huxi_2b][{color:red}2017-10-30 14:15:18,009{color}] 
[ZkClient-EventThread-28-] INFO 
[Controller-188-to-broker-187-send-thread], {color:red}Shutting down{color} 
(kafka.controller.RequestSendThread)
[{color:red}2017-10-30 14:15:43,828{color}] 
[Controller-188-to-broker-187-send-thread] WARN 
[Controller-188-to-broker-187-send-thread], Controller 188's connection to 
broker 187:9092 (id: 187 rack: null) was unsuccessful 
(kafka.controller.RequestSendThread)
java.net.SocketTimeoutException: Failed to connect within 3 ms
  at 
kafka.controller.RequestSendThread.brokerReady(ControllerChannelManager.scala:237)
  at 
kafka.controller.RequestSendThread.liftedTree1$1(ControllerChannelManager.scala:189)
  at 
kafka.controller.RequestSendThread.doWork(ControllerChannelManager.scala:188)
  at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:63)
[2017-10-30 14:15:43,828] [Controller-188-to-broker-187-send-thread] INFO 
[Controller-188-to-broker-187-send-thread], Stopped  
(kafka.controller.RequestSendThread)
[2017-10-30 14:15:43,828] [ZkClient-EventThread-28-xxx] INFO 
[Controller-188-to-broker-187-send-thread], Shutdown completed 
(kafka.controller.RequestSendThread)


was (Author: hongliang):
[~huxi_2b][{color:red}2017-10-30 14:15:18,009{color}] 
[ZkClient-EventThread-28-] INFO 
[Controller-188-to-broker-187-send-thread], {color:red}Shutting down{color} 
(kafka.controller.RequestSendThread)

> when broker is unavailable(such as broker's machine is down), controller will 
> wait 30 sec timeout 
> --
>
> Key: KAFKA-6326
> URL: https://issues.apache.org/jira/browse/KAFKA-6326
> Project: Kafka
>  Issue Type: Bug
>  Components: controller
>Affects Versions: 1.0.0
>Reporter: HongLiang
> Attachments: _f7d1d2b4-39ae-4e02-8519-99bcba849668.png
>
>
> when broker is unavailable(such as broker's machine is down), controller will 
> wait 30 sec timeout by dedault. it seems to be that the timeout waiting is 
> not necessary. It will be increase the MTTR of dead broker .



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

2017-12-07 Thread HongLiang (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283158#comment-16283158
 ] 

HongLiang edited comment on KAFKA-6326 at 12/8/17 7:32 AM:
---

sorry, the version is 0.10.2.1 [~huxi_2b]


was (Author: hongliang):
sorry, the version is 0.10.2.1

> when broker is unavailable(such as broker's machine is down), controller will 
> wait 30 sec timeout 
> --
>
> Key: KAFKA-6326
> URL: https://issues.apache.org/jira/browse/KAFKA-6326
> Project: Kafka
>  Issue Type: Bug
>  Components: controller
>Affects Versions: 1.0.0
>Reporter: HongLiang
> Attachments: _f7d1d2b4-39ae-4e02-8519-99bcba849668.png, 
> fast-recver-shutdownbroker.diff
>
>
> when broker is unavailable(such as broker's machine is down), controller will 
> wait 30 sec timeout by dedault. it seems to be that the timeout waiting is 
> not necessary. It will be increase the MTTR of dead broker .



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

2017-12-07 Thread HongLiang (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283053#comment-16283053
 ] 

HongLiang edited comment on KAFKA-6326 at 12/8/17 4:51 AM:
---

[~huxi_2b]  zookeeper.session.timeout.ms is 120 sec. but the zk session timeout 
not problem in this case.
the problem is broker has down. the controller still send broker .wait 30 sec. 
I think controller not wait. because controller know the broker has down.


was (Author: hongliang):
[~huxi_2b]  zookeeper.session.timeout.ms is 120 sec. but the zk session timeout 
not problem in this case.
the problem is broker has down(zookeeper has know in session.timeout). the 
controller still send broker .wait 30 sec. I think controller not wait. because 
controller know the broker has down.

> when broker is unavailable(such as broker's machine is down), controller will 
> wait 30 sec timeout 
> --
>
> Key: KAFKA-6326
> URL: https://issues.apache.org/jira/browse/KAFKA-6326
> Project: Kafka
>  Issue Type: Bug
>  Components: controller
>Affects Versions: 1.0.0
>Reporter: HongLiang
> Attachments: _f7d1d2b4-39ae-4e02-8519-99bcba849668.png, 
> _f7d1d2b4-39ae-4e02-8519-99bcba849668.png, fast-recver-shutdownbroker.diff
>
>
> when broker is unavailable(such as broker's machine is down), controller will 
> wait 30 sec timeout by dedault. it seems to be that the timeout waiting is 
> not necessary. It will be increase the MTTR of dead broker .



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

2017-12-07 Thread HongLiang (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282953#comment-16282953
 ] 

HongLiang edited comment on KAFKA-6326 at 12/8/17 2:57 AM:
---

[~liuweiwell]gao xiao ne?


was (Author: hongliang):
[~liuweiwell]gao xiao ni?

> when broker is unavailable(such as broker's machine is down), controller will 
> wait 30 sec timeout 
> --
>
> Key: KAFKA-6326
> URL: https://issues.apache.org/jira/browse/KAFKA-6326
> Project: Kafka
>  Issue Type: Bug
>  Components: controller
>Affects Versions: 1.0.0
>Reporter: HongLiang
> Attachments: _f7d1d2b4-39ae-4e02-8519-99bcba849668.png, 
> fast-recver-shutdownbroker.diff
>
>
> when broker is unavailable(such as broker's machine is down), controller will 
> wait 30 sec timeout by dedault. it seems to be that the timeout waiting is 
> not necessary. It will be increase the MTTR of dead broker .



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

2017-12-07 Thread wei liu (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281987#comment-16281987
 ] 

wei liu edited comment on KAFKA-6326 at 12/7/17 3:19 PM:
-

Hi [~China body] 
{panel:title=My SQL 
code|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#CE}
{code:}
select * from table;
{code}


{code:xml}



{code}
{panel}


was (Author: liuweiwell):
{panel:title=My SQL 
code|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#CE}
{code:}
select * from table;
{code}


{code:xml}



{code}
{panel}

> when broker is unavailable(such as broker's machine is down), controller will 
> wait 30 sec timeout 
> --
>
> Key: KAFKA-6326
> URL: https://issues.apache.org/jira/browse/KAFKA-6326
> Project: Kafka
>  Issue Type: Bug
>  Components: controller
>Affects Versions: 1.0.0
>Reporter: HongLiang
> Attachments: _f7d1d2b4-39ae-4e02-8519-99bcba849668.png, 
> fast-recver-shutdownbroker.diff
>
>
> when broker is unavailable(such as broker's machine is down), controller will 
> wait 30 sec timeout by dedault. it seems to be that the timeout waiting is 
> not necessary. It will be increase the MTTR of dead broker .



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout

2017-12-07 Thread wei liu (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281987#comment-16281987
 ] 

wei liu edited comment on KAFKA-6326 at 12/7/17 3:18 PM:
-

{panel:title=My SQL 
code|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#CE}
{code:}
select * from table;
{code}


{code:xml}



{code}
{panel}


was (Author: liuweiwell):
{panel:title=My SQL 
code|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#CE}
{code:}
select * from table;
{code}
{panel}

> when broker is unavailable(such as broker's machine is down), controller will 
> wait 30 sec timeout 
> --
>
> Key: KAFKA-6326
> URL: https://issues.apache.org/jira/browse/KAFKA-6326
> Project: Kafka
>  Issue Type: Bug
>  Components: controller
>Affects Versions: 1.0.0
>Reporter: HongLiang
> Attachments: _f7d1d2b4-39ae-4e02-8519-99bcba849668.png, 
> fast-recver-shutdownbroker.diff
>
>
> when broker is unavailable(such as broker's machine is down), controller will 
> wait 30 sec timeout by dedault. it seems to be that the timeout waiting is 
> not necessary. It will be increase the MTTR of dead broker .



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)