[jira] [Commented] (KAFKA-734) Migration tool needs a revamp, it was poorly written and has many performance bugs

2013-02-15 Thread John Fung (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13579438#comment-13579438
 ] 

John Fung commented on KAFKA-734:
-

** Tried the latest patch v4 and got the following FATAL error:

[2013-02-15 17:36:01,324] INFO Property queue.enqueue.timeout.ms is overridden 
to -1 (kafka.utils.VerifiableProperties)
[2013-02-15 17:36:01,358] ERROR Kafka migration tool failed:  
(kafka.tools.KafkaMigrationTool)
java.lang.IllegalArgumentException: Topic cannot be null.
at kafka.producer.KeyedMessage.init(KeyedMessage.scala:25)
at 
kafka.tools.KafkaMigrationTool$ProducerThread.init(KafkaMigrationTool.java:349)
at kafka.tools.KafkaMigrationTool.main(KafkaMigrationTool.java:236)
[2013-02-15 17:36:01,359] FATAL Migration thread failure due to  
(kafka.tools.KafkaMigrationTool$MigrationThread)
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
kafka.tools.KafkaMigrationTool$MigrationThread.run(KafkaMigrationTool.java:310)
Caused by: java.lang.InterruptedException
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:1961)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1996)
at 
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
at kafka.consumer.ConsumerIterator.makeNext(ConsumerIterator.scala:60)
at kafka.consumer.ConsumerIterator.makeNext(ConsumerIterator.scala:32)
at 
kafka.utils.IteratorTemplate.maybeComputeNext(IteratorTemplate.scala:59)
at kafka.utils.IteratorTemplate.hasNext(IteratorTemplate.scala:51)
... 5 more


 Migration tool needs a revamp, it was poorly written and has many performance 
 bugs
 --

 Key: KAFKA-734
 URL: https://issues.apache.org/jira/browse/KAFKA-734
 Project: Kafka
  Issue Type: Bug
  Components: tools
Affects Versions: 0.8
Reporter: Neha Narkhede
Assignee: Neha Narkhede
Priority: Blocker
  Labels: p1
 Attachments: kafka-734-v1.patch, kafka-734-v2.patch, 
 kafka-734-v3.patch, kafka-734-v4.patch


 Migration tool has a number of problems ranging from poor logging to poor 
 design. This needs to be thought through again

--
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

[jira] [Created] (KAFKA-758) startHighWaterMarksCheckPointThread is never called

2013-02-15 Thread Sriram Subramanian (JIRA) 
Sriram Subramanian created KAFKA-758:


 Summary: startHighWaterMarksCheckPointThread is never called
 Key: KAFKA-758
 URL: https://issues.apache.org/jira/browse/KAFKA-758
 Project: Kafka
  Issue Type: Bug
Affects Versions: 0.8
Reporter: Sriram Subramanian
Assignee: Sriram Subramanian
Priority: Blocker
 Fix For: 0.8


startHighWaterMarksCheckPointThread is never called during startup and hence we 
only persist the highwater mark file on a clean shutdown. With an unclean 
shutdown, the highwater marks are not persisted. This causes long recovery time 
for replicas after unclean shutdowns.

--
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

[jira] [Updated] (KAFKA-758) startHighWaterMarksCheckPointThread is never called

2013-02-15 Thread Sriram Subramanian (JIRA) 

 [ 
https://issues.apache.org/jira/browse/KAFKA-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sriram Subramanian updated KAFKA-758:
-

Attachment: KAFKA-758.patch

Call startHighWaterMarkCheck on startup

 startHighWaterMarksCheckPointThread is never called
 ---

 Key: KAFKA-758
 URL: https://issues.apache.org/jira/browse/KAFKA-758
 Project: Kafka
  Issue Type: Bug
Affects Versions: 0.8
Reporter: Sriram Subramanian
Assignee: Sriram Subramanian
Priority: Blocker
  Labels: p1
 Fix For: 0.8

 Attachments: KAFKA-758.patch


 startHighWaterMarksCheckPointThread is never called during startup and hence 
 we only persist the highwater mark file on a clean shutdown. With an unclean 
 shutdown, the highwater marks are not persisted. This causes long recovery 
 time for replicas after unclean shutdowns.

--
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

Re: Plans for a 0.7.3 release?

2013-02-15 Thread Jun Rao 
If there is enough interest, we could do a 0.7.3 release.

However, there weren't that many fixes after 0.7.2 and 0.8 will probably be
out in Mar. I am wondering if it's worth doing another 0.7 release.

Thanks,

Jun

On Thu, Feb 14, 2013 at 11:31 AM, David Arthur mum...@gmail.com wrote:

 I think this was discussed before, but are there any solid plans for it?

 Is there even an official release yet (with binaries and such)?

 -David