On Thu, Feb 5, 2015 at 12:37 PM, Sumit Rangwala
wrote:
>
>
> On Wed, Feb 4, 2015 at 9:23 PM, Jun Rao wrote:
>
>> Could you try the 0.8.2.0 release? It fixed one issue related to topic
>> creation.
>>
>
Jun,
If you need more info let me know. Seems like TopicM
93)
at
kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:66)
at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:60)
>
> Thanks,
>
> Jun
>
> On Wed, Feb 4, 2015 at 12:58 AM, Sumit Rangwala
> wrote:
>
> > I am observing th
> Sumit
>
>
>
>> Thanks,
>>
>> Joel
>>
>> On Wed, Feb 04, 2015 at 01:00:46PM -0800, Sumit Rangwala wrote:
>> > >
>> > >
>> > >> I have since stopped the container so I cannot say if
>> > > LAX1-GRIFFIN-r45-1
On Wed, Feb 4, 2015 at 10:16 PM, Harsha wrote:
>
>whats your zookeeper.session.timeout.ms value
>
3 (30sec)
Sumit
>
> On Wed, Feb 4, 2015, at 09:35 PM, Sumit Rangwala wrote:
> > On Wed, Feb 4, 2015 at 6:14 PM, Joel Koshy wrote:
> >
> > >
twork and long GC are a possibility.
I will redo the experiment and keep the kakfa brokers running. However, I
will move to 0.8.2 release since Jun asked me to try it for another issue
(topic creation). I hope that is fine.
Sumit
> Thanks,
>
> Joel
>
> On Wed, Feb 04, 2015 at 01:
call
>> > deleteTopic and kafka goes through delete topic process but your
>> > consumer is running probably made a TopicMetadataRequest for the same
>> > topic which can re-create the topic with the default num.partitions and
>> > replication.factor. Did you try stop
I am observing the following exception with kafka client:
2015-02-04 00:17:27,345
(LAX1-GRIFFIN-r8-1423037468055-pf13797-lax1-GriffinDownloader-1423037818264_c7b1e843ff51-1423037822122-eb7afca7-leader-finder-thread)
ClientUtils$ WARN: Fetching topic metadata with correlation id 112 for
topics [Set
ly made a TopicMetadataRequest for the same
> > topic which can re-create the topic with the default num.partitions and
> > replication.factor. Did you try stopping the consumer first and issue
> > the topic delete.
> > -Harsha
> >
> > On Tue, Feb 3, 2015, at 0
mer is running probably made a TopicMetadataRequest for the same
> > topic which can re-create the topic with the default num.partitions and
> > replication.factor. Did you try stopping the consumer first and issue
> > the topic delete.
> > -Harsha
> >
&
e topic delete.
>
> -Harsha
>
> On Tue, Feb 3, 2015, at 08:37 PM, Sumit Rangwala wrote:
> > On Tue, Feb 3, 2015 at 6:48 PM, Harsha wrote:
> >
> > > Sumit,
> > >lets say you are deleting a older topic "test1" do you have any
> > &
a chance to get to it today.
> >
> > Joel
> >
> > On Tue, Feb 03, 2015 at 04:11:57PM -0800, Sumit Rangwala wrote:
> > > On Tue, Feb 3, 2015 at 3:37 PM, Joel Koshy
> wrote:
> > >
> > > > Hey Sumit,
> > > >
> > > >
roller logs at the very least and if possible server logs and send
> those over?
>
Here are all the logs you requested (there are three brokers in my setup
k1, k2, k3): http://d.pr/f/1kprY/2quHBRRT (Gmail has issue with the file)
Sumit
>
> Joel
>
> On Tue, Feb 03, 2015 at 03
In my setup kafka brokers are set for auto topic creation. In the scenario
below a node informs other nodes (currently 5 in total) about a number of
new (non-existent) topics, and all the nodes almost simultaneously open a
consumer for each of those topics. Sometime later another node informs all
, Jan 29, 2015 at 1:29 AM, Joel Koshy wrote:
> > If you can tell me where the find the logs I can check. I haven't
> restarted
> > my brokers since the issue.
>
> This will be specified in the log4j properties that you are using.
>
> On Wed, Jan 28, 2015 at 12:01:
Sumit
> On Tue, Jan 27, 2015 at 03:11:48PM -0800, Sumit Rangwala wrote:
> > I am using 0.8.2-beta on brokers 0.8.1.1 for client (producer and
> > consumers). delete.topic.enable=true on all brokers. replication factor
> is
> > < number of brokers. I see this issue with j
fault number of
> replicas is greater than number of available brokers. Check the
> default.replication.factor parameter.
>
> Gwen
>
> On Tue, Jan 27, 2015 at 12:29 AM, Joel Koshy wrote:
> > Which version of the broker are you using?
> >
> > On Mon, Jan 26
While running kafka in production I found an issue where a topic wasn't
getting created even with auto topic enabled. I then went ahead and created
the topic manually (from the command line). I then delete the topic, again
manually. Now my broker won't allow me to either create *the* topic or
delet
I was planning to start a new thread by my experience is similar to the one
described here. I am currently using 0.8.2-beta and my setup has a producer
producing to topic "DC-DATA", kafka brokers with auto-topic-creation
enabled, and mirrormaker set to replicate any ".*-DATA" topics. After the
prod
ic actually fully removes the topic from the cluster, which
> > also includes cleaning the logs and removing it from zookeeper (once
> > it is fully deleted).
> >
> > Tim
> >
> > On Fri, Jan 23, 2015 at 12:13 PM, Sumit Rangwala
> > wrote:
> > > I am
I am trying to find if there is a supported API to delete topic (from
within my code) specifically in 0.8.2. One method that I can think of is
calling kafka.admin.TopicCommand.main with the same parameters as one gives
on the command line. Is this the recommended way or is there a better way
of doi
20 matches
Mail list logo