Hi Joe,
We're doing a similar thing that you're looking for with some of our app
nodes. We use the kafka.admin.AdminTools and its
topicExists()/createTopic() methods. Some additional code (e.g. Kafka
context check/creation) might be needed for dev/test environments if you're
using a specific Kafka
much of the data already existed on the broker.
-Timo
On 30 March 2015 at 21:28, Timo Ahokas wrote:
> A few more details before the looming crash. The broker replicating data
> and in sync (before GC cycle starts) - GC cycles taking nearly 1min real:
>
> 2015-03-30T21:08:39.502+0300:
.0*.jar
kafka.Kafka /opt/kafka/config/server.properties
Any suggestions more than welcome...
Best regards,
Timo
On 30 March 2015 at 20:34, Timo Ahokas wrote:
> Hi,
>
> A related issue which results in a similar increasing GC cycles (but
> doesn't recover)... We'
(1518976K), 3.3707200 secs] [Times: user=6.59 sys=0.01,
real=3.37 secs]
This goes up to when the realtime of the cycle is 1 min or so and then the
server becomes unresponsive.
Any suggestions on what cloud be causing this?
Best regards,
Timo
On 26 March 2015 at 19:27, Timo Ahokas wrote:
Hi,
We are seeing really weird GC behaviour on our Kafka cluster. After a clean
stop/start of the whole cluster, the servers go into a loop of increasingly
slow GC cycles for an hour and then seem to recover to a normal state
without any external changes to the servers or traffic. The load to the
