ystem
metrics, like java.util.logging)
Is there some configuration that I need to do in my Kafka server to enable this
behavior?
I looked into the documentation, but did not find a way to do this.
Thanks,
Priya
that it's best to keep
consumer.timeout.ms=-1 for high level consumer. I was wondering in which
situation is it beneficial to handle ConsumerTimeoutException?
Thanks,
Priya
Secondly,
Hello,
What is purgatory? I believe the following two properties relate to
consumer and producer respectively.
Could someone please explain the significance of these?
fetch.purgatory.purge.interval.requests=100
producer.purgatory.purge.interval.requests=100
Thanks,
Priya
log retention, however the topic should still
exist and remember its original configuration for # of partitions and
replication. How does it work behind the scenes?
Thanks,
Priya
ducer and consumer? Are messages dropped in this case?
Thanks,
Priya
On Thu, Oct 31, 2013 at 2:47 PM, Guozhang Wang wrote:
> Hello Priya,
>
> You can find the definitions of these two configs here:
>
> http://kafka.apache.org/documentation.html#brokerconfigs
>
> Guozhang
>
13 00:45:44] [pool-30-thread-2] 1740449 DEBUG
(com.googlecode.jmxtrans.model.output.GangliaWriter:141) - Sending Ganglia
metric GC.PSScavenge.CollectionCount=334
And I know that kafka is publishing jmx metrics because I can see them
using jmxsh-R5 command line tool,
Appreciate any pointers you can provide with regards to kafka.
Thanks,
Priya
onfigured above i.e.
ReplicaManager.Count
ReplicaManager.OneMinuteRate
ReplicaManager.MeanRate
ReplicaManager.Value
Then, how can one tell if for e.g. Value pertains to LeaderCount or
PartitionCount?
Even though it is laborious, isn't it good idea to explicitly specify the
name?
Thanks,
Priya
Can this unintentional topic creation be avoided by setting
auto.create.topics.enable=false?
On Mon, Nov 4, 2013 at 9:40 PM, Jason Rosenberg wrote:
> Ok, so this can happen, even if the node has not been placed back into
> rotation, at the metadata vip?
>
>
> On Tue, Nov 5, 2013 at 12:11 AM, Ne
gt; ReplicaManager.ISRExpandsPerSec.MeanRate
> ReplicaManager.ISRExpandsPerSec.OneMinuteRate
> ReplicaManager.LeaderCount.Value
>
> ReplicaManager.PartitionCount.Value
>
>
>
> In other words, the bean name is include in the metric name when jmxtrans
> sends it out. In our
n't need to be modified by users. The reason we added that was
> as
> > > > > > follows:
> > > > > > - We found that for low-volume topics, replica fetch requests
> were
> > > > > > getting expired but sitting around in purgatory
> &g
If you have 5 partitions and 3 consumers in one consumer group, the
consumers will balance all 5 partitions such that 2 consumers will get data
from 2 partitions each and 1 consumer will get data from remaining 5th
partition.
If you have 3 partitions and 5 consumers in one consumer group, 3 consume
It doesn't look like second broker is available. What is the broker list
property for each of the producers?
Best,
Priya Matpadi
> On Nov 11, 2013, at 12:12 AM, ji yan wrote:
>
> Hi Kafka Users
>
> I have a test setup at home with one machine hosting a zookeeper server a
..N] --> nPartions (ephemeral node)
On Mon, Nov 11, 2013 at 10:39 PM, ji yan wrote:
> @Priya, I have two brokers, each running on each of two machines. The
> producer broker-list is pointing to the broker server on the same machine
> as the producer.
>
> @Jun, I created the top
Hi,
I have 3 brokers and created a topic with replication factor 3.
I described topic after killing the brokers one by one.
When i deleted my last live broker and described topic it still shows value
for leader and isr.
I've enabled auto.leader.rebalance
Any clarifications for this confusing beha
lease.
>
> Thank you,
> Grant
>
> On Mon, Aug 17, 2015 at 3:52 AM, Priya Darsini
> wrote:
>
> > Hi,
> > I have 3 brokers and created a topic with replication factor 3.
> > I described topic after killing the brokers one by one.
> > When i deleted my la
Hello,
Is there any progress on this issue? We also experience socket leak in case
of network outage.
Thanks,
Priya
On Fri, Jan 24, 2014 at 7:30 AM, Jun Rao wrote:
> Thanks for find this out. We probably should disconnect on any exception.
> Could you file a jira and perhaps attach a
Further more, the problem is not just restricted to ReplicaFetcherThread.
Kafka consumer server also leaks sockets due to SendThread using same code
. See below stack trace:
2014-01-23 06:48:09,699 INFO [org.apache.zookeeper.ClientCnxn]
(OurKafkaMessageFetcher-blah1-SendThread(pkafka3.our.com:218
Hello,
Do we have a date yet for 0.8.1 release?
Thanks,
Priya
On Fri, Jan 31, 2014 at 8:48 AM, Neha Narkhede wrote:
> The delete topic functionality is in progress (KAFKA-330). We were hoping
> to release 0.8.1 with that. So it's probably 1-2 weeks away. As for the
> rest of
18 matches
Mail list logo
