[ 
https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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=#FFFFCE}
{code:}
select * from table;
{code}


{code:xml}
    <test>
        <another tag="attribute"/>
    </test>
{code}
{panel}


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


{code:xml}
    <test>
        <another tag="attribute"/>
    </test>
{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)

Reply via email to