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

Jun Rao commented on KAFKA-301:
-------------------------------

Can't seem to apply patch v1 to 0.8 branch.

patching file core/src/test/scala/unit/kafka/producer/AsyncProducerTest.scala
patching file core/src/test/scala/unit/kafka/server/LeaderElectionTest.scala
patching file core/src/test/scala/unit/kafka/server/StateChangeTest.scala
patching file core/src/main/scala/kafka/producer/Producer.scala
patching file core/src/main/scala/kafka/producer/async/QueueFullException.scala
patching file core/src/main/scala/kafka/admin/AdminUtils.scala
patching file 
core/src/main/scala/kafka/common/NoEpochForPartitionException.scala
can't find file to patch at input line 374
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: core/src/main/scala/kafka/common/QueueFullException.scala
|===================================================================
|--- core/src/main/scala/kafka/common/QueueFullException.scala  (revision 
1304473)
|+++ core/src/main/scala/kafka/common/QueueFullException.scala  (working copy)
--------------------------
File to patch: 

                
> Implement the broker startup procedure
> --------------------------------------
>
>                 Key: KAFKA-301
>                 URL: https://issues.apache.org/jira/browse/KAFKA-301
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Neha Narkhede
>            Assignee: Neha Narkhede
>         Attachments: kafka-301-draft.patch, kafka-301-v1.patch
>
>
> This JIRA will involve implementing the list of actions to be taken on broker 
> startup, as listed by the brokerStartup() and startReplica() algorithm in the 
> Kafka replication design doc. Since the stateChangeListener is part of 
> KAFKA-44, this JIRA can leave it as a stub.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to