kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Swapnil Ghike (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-513) Add state change log to Kafka brokers
Date Fri, 02 Nov 2012 02:04:12 GMT

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

Swapnil Ghike commented on KAFKA-513:
-------------------------------------

Hi Prashanth, 

How far along are you in this jira? If you are busy, I can take a look at it. Also if you
have some unfinished patch, I can take it from there too.

Swapnil
                
> Add state change log to Kafka brokers
> -------------------------------------
>
>                 Key: KAFKA-513
>                 URL: https://issues.apache.org/jira/browse/KAFKA-513
>             Project: Kafka
>          Issue Type: Sub-task
>    Affects Versions: 0.8
>            Reporter: Neha Narkhede
>            Priority: Blocker
>              Labels: replication, tools
>             Fix For: 0.8
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> Once KAFKA-499 is checked in, every controller to broker communication can be modelled
as a state change for one or more partitions. Every state change request will carry the controller
epoch. If there is a problem with the state of some partitions, it will be good to have a
tool that can create a timeline of requested and completed state changes. This will require
each broker to output a state change log that has entries like
> [2012-09-10 10:06:17,280] broker 1 received request LeaderAndIsr() for partition [foo,
0] from controller 2, epoch 1
> [2012-09-10 10:06:17,350] broker 1 completed request LeaderAndIsr() for partition [foo,
0] from controller 2, epoch 1
> On controller, this will look like -
> [2012-09-10 10:06:17,198] controller 2, epoch 1, initiated state change request LeaderAndIsr()
for partition [foo, 0]
> We need a tool that can collect the state change log from all brokers and create a per-partition
timeline of state changes -
> [foo, 0]
> [2012-09-10 10:06:17,198] controller 2, epoch 1 initiated state change request LeaderAndIsr()

> [2012-09-10 10:06:17,280] broker 1 received request LeaderAndIsr() from controller 2,
epoch 1
> [2012-09-10 10:06:17,350] broker 1 completed request LeaderAndIsr() from controller 2,
epoch 1
> This JIRA involves adding the state change log to each broker and adding the tool to
create the timeline 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message