We are running Kafka 2.0.1 and lately the brokers have been crashing with
several different SIGSEGV errors as listed below. I was wondering if anybody
has encountered similar errors or might have advice on what the problem could
be?
Thanks,
David
1.
#
# A fatal error has been detected by the
But G1GC is the default garbage collection algo used in kafka, it'll still
be using G1GC.
Did you add remove/add other parameters as well?
Also, which kafka version are you using?
On Fri, Jan 11, 2019 at 2:34 AM wenxing zheng
wrote:
> Previously we added G1GC option to the JVM options when start
Previously we added G1GC option to the JVM options when starting the Kafka, and
now we remove this option and it works fine up to now.
On 2019/01/08 07:58:01, Car Devops wrote:
> Hi folks :)
>
> Can you please Wenxing comfirm that removing G1GC really solved the problem.
> Unfortunately I fac
Hi Peter,
Regarding retention, I was not referring to log retention, but to the
window store retention.
Since a new window is created every second (for example), there are in
principle an unbounded
number of windows (the longer the application runs, the more windows there
are, with no end).
Howeve
Thatns Robin. Can you send reference to it? Also can it be used for log
file stored locally (not in DB)?
Thanks,
Parth Gandhi
DevOps
On Thu, Jan 10, 2019 at 9:17 AM Robin Moffatt wrote:
> You can use kafkacat to examine the timestamp (and other metadata). Here's
> an example of calling it, and
Okay, but
what if one also needs to preserve the order of messages coming from a
particular device?
With Kafka, this is perhaps possible if all messages from a particular device
go into the same partition.
Would it be a good and efficient solution for this approach to set the key of
each Kaf
You can use kafkacat to examine the timestamp (and other metadata). Here's
an example of calling it, and two sample output records:
$ kafkacat -b localhost:9092 -t mysql_users -C -c2 -f '\nKey (%K bytes):
%k\t\nValue (%S bytes): %s\nTimestamp: %T\tPartition: %p\tOffset: %o\n--\n'
Key (1 bytes): 1
Hi,
Does kafka record the timestamp of the incoming message in its data log? I
checked one of the partition log and I can see the message without any
timestamp. Also there are few special characters in the message log. IS
that normal?
Here is a sample log: pastebin.com/hStyCW13
Thanks,
Parth Gan
Hi,
I think it's the zk client's problem.
1. Where the log producted:
if (to <= 0) {
String warnInfo;
warnInfo = "Client session timed out, have not heard from server in "
+ clientCnxnSocket.getIdleRecv()
+ "ms"
+ " for sessionid 0x"
+ Long.toHexStrin
Hi everyone,
we are planning to add some user activity tracking to an application and I
wanted to ask around for your general experiences and best practices.
Do you use one topic per application or more granular?
Do you write directly from the application to Kafka for tracking purposes?
How to be
10 matches
Mail list logo
