Re: Mirror maker fetcher thread unexpectedly stopped

2015-03-24 Thread Jiangjie Qin
Hi Xiao, I think the fix for IllegalStateExcepetion is correct. Can you also create a ticket and submit a patch? Thanks. Jiangjie (Becket) Qin On 3/24/15, 4:31 PM, tao xiao xiaotao...@gmail.com wrote: Hi community, I wanted to know if the solution I supplied can fix the

Re: Mirror maker fetcher thread unexpectedly stopped

2015-03-24 Thread tao xiao
Hi community, I wanted to know if the solution I supplied can fix the IllegalMonitorStateException issue. Our work is pending on this and we'd like to proceed ASAP. Sorry for bothering. On Mon, Mar 23, 2015 at 4:32 PM, tao xiao xiaotao...@gmail.com wrote: I think I worked out the answer to

Re: Mirror maker fetcher thread unexpectedly stopped

2015-03-24 Thread Jiangjie Qin
It should be another ticket. This is a AbstractFetcherThread issue rather than a mirror maker issue. I kind of think this case you saw was a special case as it¹s not actually a runtime error but a coding bug. Fetcher thread should not die by design. So I don¹t think we have a way to restart

Re: Mirror maker fetcher thread unexpectedly stopped

2015-03-24 Thread tao xiao
Thank you for the explanation. Patch submitted https://issues.apache.org/jira/browse/KAFKA-2048 On Wed, Mar 25, 2015 at 8:29 AM, Jiangjie Qin j...@linkedin.com.invalid wrote: It should be another ticket. This is a AbstractFetcherThread issue rather than a mirror maker issue. I kind of think

Re: Mirror maker fetcher thread unexpectedly stopped

2015-03-24 Thread tao xiao
Thanks JIanjie. Can I reuse KAFKA-1997 or should I create a new ticket? On Wed, Mar 25, 2015 at 7:58 AM, Jiangjie Qin j...@linkedin.com.invalid wrote: Hi Xiao, I think the fix for IllegalStateExcepetion is correct. Can you also create a ticket and submit a patch? Thanks. Jiangjie

Re: Mirror maker fetcher thread unexpectedly stopped

2015-03-24 Thread tao xiao
The other question I have is the fact that consumer client is unaware of the health status of underlying fetcher thread. If the fetcher thread dies like the case I encountered is there a way that consumer can restart the fetcher thread or release ownership of partitions so that other consumers can

Re: Mirror maker fetcher thread unexpectedly stopped

2015-03-23 Thread tao xiao
I think I worked out the answer to question 1. java.lang.IllegalMonitorStateException was thrown due to no ownership of ReentrantLock when trying to call await() on the lock condition. Here is the code snippet from the AbstractFetcherThread.scala in trunk partitionMapLock synchronized {

Mirror maker fetcher thread unexpectedly stopped

2015-03-22 Thread tao xiao
Hi, I was running a mirror maker and got java.lang.IllegalMonitorStateException that caused the underlying fetcher thread completely stopped. Here is the log from mirror maker. [2015-03-21 02:11:53,069] INFO Reconnect due to socket error: java.io.EOFException: Received -1 when reading from