Issue with using embedded kafka

627 views
Skip to first unread message

Himani Arora

unread,
Feb 7, 2017, 5:33:38 AM2/7/17
to Lagom Framework Users
Hi, this is the stack trace that I get whenever I try to produce a message :

[warn] a.c.s.ShardRegion - Trying to register to coordinator at [Some(ActorSelection[Anchor(
akka://user-impl-application/), Path(/system/sharding/UserEventProcessorCoordinator/singleton/coordinator)])], but no acknowledgement. Total [1] buffered messages.
[warn] a.c.s.ShardRegion - Retry request for shard [usercrud.user.impl.events.UserEvent] homes from coordinator at [Actor[akka://user-impl-application/system/sharding/UserEventProcessorCoordinator/singleton/coordinator#1816980382]]. [1] buffered messages.
[info] c.k.u.u.i.e.UserEventProcessor -  buildHandler method ...
[warn] a.c.s.ShardRegion - Trying to register to coordinator at [Some(ActorSelection[Anchor(akka://user-impl-application/), Path(/system/sharding/kafkaProducer-greetingsCoordinator/singleton/coordinator)])], but no acknowledgement. Total [1] buffered messages.
[warn] a.c.s.ShardRegion - Retry request for shard [singleton] homes from coordinator at [Actor[akka://user-impl-application/system/sharding/kafkaProducer-greetingsCoordinator/singleton/coordinator#-1520459998]]. [1] buffered messages.


And if I subscribe to the topic, I get the following warnings:

[warn] o.a.k.c.NetworkClient - Error while fetching metadata with correlation id 1 : {greetings=LEADER_NOT_AVAILABLE}
[warn] o.a.k.c.NetworkClient - Error while fetching metadata with correlation id 2 : {greetings=LEADER_NOT_AVAILABLE}
[warn] o.a.k.c.NetworkClient - Error while fetching metadata with correlation id 4 : {greetings=LEADER_NOT_AVAILABLE}

James Roper

unread,
Feb 7, 2017, 7:20:42 PM2/7/17
to Himani Arora, Lagom Framework Users
Hi Himani,

Do the messages eventually get through, or are you seeing no messages get through?  Sometimes it can take time for a Lagom system to fully form a cluster, and those warnings are what you may see when it's doing that, you can usually ignore them, as long as they eventually go away once the system is running and stable.

Regards,

James

--
You received this message because you are subscribed to the Google Groups "Lagom Framework Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lagom-framework+unsubscribe@googlegroups.com.
To post to this group, send email to lagom-framework@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lagom-framework/1935adc4-24bb-456e-a7ab-8d5122ae586a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
James Roper
Software Engineer

Lightbend – Build reactive apps!
Twitter: @jroper

Himani Arora

unread,
Feb 7, 2017, 11:32:33 PM2/7/17
to James Roper, Lagom Framework Users
Hi,

No the message do not get through. I am not able to figure out what I am missing.
--
Regards/Thanks,

Himani Arora,

Tim Moore

unread,
Feb 8, 2017, 12:07:53 AM2/8/17
to Himani Arora, James Roper, Lagom Framework Users
Hi Himani,

Could you post the complete output you're getting from the start? Is this when you're running sbt runAll or mvn lagom:runAll or are you running in a production environment?

Thanks,
Tim


For more options, visit https://groups.google.com/d/optout.



--
Tim Moore
Senior Engineer, Lagom, Lightbend, Inc.


Reply all
Reply to author
Forward
0 new messages