kafka
Here are 6,155 public repositories matching this topic...
-
Updated
Jul 4, 2021 - Java
-
Updated
Jun 24, 2021 - Java
-
Updated
May 6, 2021 - Scala
-
Updated
Jul 14, 2021 - Java

-
Updated
Jun 24, 2021 - Python
-
Updated
Jul 12, 2021 - C
-
Updated
Jul 14, 2021 - Java
-
Updated
Jul 13, 2021 - C#
I was looking at some logs and for a cluster that has no lag and only a single host (which was alive at the time) I was seeing the following exception:
Unable to execute pull query. All nodes are dead or exceed max allowed lag.
The error message doesn't help me understand what happened, which partition failed or if there's some other issue. We should print more debugging information.
Current Behaviour
The flamegraph sorts the siblings in ascending order by frame's name.
The reference to code is here
Expected Behaviour
The siblings should appear in order of their start time.
This can be achieved according to library docs mentioned [here](https://github.com/spiermar/d3-fla
-
Updated
Apr 24, 2020 - Jsonnet
-
Updated
Jun 5, 2021 - Java
-
Updated
Jul 13, 2021 - Go
-
Updated
Jul 14, 2021 - Go
-
Updated
Jul 13, 2021 - Go
-
Updated
Jun 7, 2021 - C#
For an implementation of #126 (PostgreSQL driver with SKIP LOCKED), I create a SQL table for each consumer group containing the offsets ready to be consumed. The name for these tables is build by concatenating some prefix, the name of the topic and the name of the consumer group. In some of the test cases in the test suite, UUID are used for both, the topic and the consumer group. Each UUID has
-
Updated
Jul 14, 2021 - Rust
日常答疑问题记录
-
Updated
Jul 13, 2021 - Java
-
Updated
Jul 14, 2021 - Java
Improve this page
Add a description, image, and links to the kafka topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the kafka topic, visit your repo's landing page and select "manage topics."