Hi,
This is exception is happening on a Kafka client - a consumer.
The Kafka client is of version 2.8.1 (same as the broker). The jmx exporter is
running as java agent in version 0.14.0.
Thanks, Peter
> Am 06.04.2022 um 14:47 schrieb Liam Clarke-Hutchinson :
>
>
> Hi Peter,
>
> Are you runnin
Hi Peter,
Are you running the Prometheus exporter on a broker? Or on a Kafka client?
Also, what version?
Cheers,
Liam Clarke-Hutchinson
On Wed, 6 Apr 2022 at 19:14, Peter Schrott (Extern)
wrote:
> Hi users,
>
> I am getting this following exceptions occasionally:
> JMX scrape failed: javax.
Hi users,
I am getting this following exceptions occasionally:
JMX scrape failed: javax.management.RuntimeMBeanException: getMBeanInfo threw
RuntimeException
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBeanInfo(DefaultMBeanServerInterceptor.java:1384)
at com.sun.jmx.mbeanserver
Yes. We will merge to trunk and cherry-pick to 2.1 branch.
Guozhang
On Thu, Dec 6, 2018 at 5:43 AM Mark Anderson wrote:
> Thanks. I assume this will be fixed in 2.1.1?
>
> On Thu, 6 Dec 2018 at 01:11 Guozhang Wang wrote:
>
> > Hmm.. seems like a regression introduced in since
> > "getExpiredI
Thanks. I assume this will be fixed in 2.1.1?
On Thu, 6 Dec 2018 at 01:11 Guozhang Wang wrote:
> Hmm.. seems like a regression introduced in since
> "getExpiredInflightBatches".
>
> Actually, just found someone already file a JIRA with a PR:
> https://github.com/apache/kafka/pull/6005/files
>
>
Hmm.. seems like a regression introduced in since
"getExpiredInflightBatches".
Actually, just found someone already file a JIRA with a PR:
https://github.com/apache/kafka/pull/6005/files
Guozhang
On Wed, Dec 5, 2018 at 6:54 AM Mark Anderson wrote:
> Hi,
>
> I'm periodically seeing ConcurrentM
Hi,
I'm periodically seeing ConcurrentModificationExceptions in the producer
when records are expired e.g.
ERROR Dec 05 11:56:13.033 388753 [kafka-producer-network-thread |
analogDataProducer] com.x.AnalogMessageBundler Exception
org.apache.kafka.common.errors.TimeoutException:
Expiring 1 record
Since you're running Storm to read data from Kafka, I'd expect it is not
due to 6349.
Could you provide a more detailed stack trace? The current provided one is
really small and not informative at all.
Guozhang
On Tue, Dec 12, 2017 at 6:42 PM, Ted Yu wrote:
> From the stack trace, it seems you
>From the stack trace, it seems you hit KAFKA-6349 (where Damian provided a
PR).
FYI
On Mon, Dec 11, 2017 at 11:29 PM, Mr.Wang <1282183...@qq.com> wrote:
> Hi~
> We found this error when we read kafka data using storm:
> java.util.ConcurrentModificationException at
> java.util.LinkedHash
Hi~
We found this error when we read kafka data using storm:
java.util.ConcurrentModificationException at
java.util.LinkedHashMap$LinkedHashIterator.nextNode(LinkedHashMap.java:719)
at java.util.LinkedHashMap$LinkedKeyIterator.next(LinkedHashMap.java:742)
at java.util.Abs
The ticket is still open, thus, it's not fixed.
If a ticket is resolved, you can check the "Fix Version" field to see
for which Kafka version it got fixed.
-Matthias
On 12/10/17 10:46 PM, wrote:
> Hello !
> We?0?2found?0?2this?0?2error?0?2when?0?2we?0?2read?0?2Kafka?0?2data?0?2using?0?2
Hello !
We found this error when we read Kafka data using storm , As shown in the
appendix.
https://issues.apache.org/jira/browse/KAFKA-4950 This BUG will cause some loss
of data . Is this BUG fixed now? Which version is it in?
Thankyou verymuch!
Hi,
looks like the exception is occurring at kryo serialization. make sure
you are not concurrently modifying java.util.Vector data structure.
kumar
On Wed, Aug 19, 2015 at 3:32 AM, Shenghua(Daniel) Wan wrote:
> Hi,
> Did anyone see java.util.ConcurrentModificationException when using
> broa
Hi,
Did anyone see java.util.ConcurrentModificationException when using
broadcast variables?
I encountered this exception when wrapping a Kafka producer like this in
the spark streaming driver.
Here is what I did.
KafkaProducer producer = new KafkaProducer(properties);
final Broadcast bCastProduce
14 matches
Mail list logo
