-Re: New exception (for us) in high-level consumer code -- OK to ignore?
Quite possibly. We are doing lots of restarts recovering from various issues.
We can pay more attention next time.
If it is a shutdown scenario, I guess we don't need to be that concerned?
On Jul 10, 2013, at 10:22 PM, Jun Rao <[EMAIL PROTECTED]> wrote:
> That can happen when shutting down the consumer. Is that the case?
> On Wed, Jul 10, 2013 at 6:43 PM, Philip O'Toole <[EMAIL PROTECTED]> wrote:
>> Hello -- we're doing some heavy lifting now with our high-level based
>> consumer. We open a Consumer Connection per partition within the one JVM,
>> and are using Kafka 0.72. We saw a burst of the exceptions shown below. Is
>> this something we should be concerned about? Or is this the normal output
>> from rebalancing, as the consumer starts up?
>> 2013-07-10 23:39:37,012 [ERROR] [ZookeeperConsumerConnector.error]
>> writer_writer0-1373499526097-ec0d4672 error during syncedRebalance
>> at kafka.utils.ZkUtils$.getCluster(ZkUtils.scala:202)
>> at scala.collection.immutable.Range.foreach$mVc$sp(Range.scala:75)
>> 2013-07-10 23:39:37,013 [INFO] [ZookeeperConsumerConnector.info]
>> writer_writer0-1373499534602-35941a8c begin rebalancing consumer
>> writer_writer0-1373499534602-35941a8c try #1