We're Moving!

The Vertica Forum is moving to a new OpenText Analytics Database (Vertica) Community.

Join us there to post discussion topics, learn about

product releases, share tips, access the blog, and much more.

Create My New Community Account Now


Kafka Locking — Vertica Forum

Kafka Locking

 

Hi,

 

When i restart the scheduler & waited for hours. Below log just showed the same message.

May I know how to resolve this & what the way to unlock table kafka_config.kafka_lock table?

 

2016-09-07 15:42:05.523 com.vertica.solutions.kafka.scheduler.StreamCoordinator::Main  [DEBUG] Given scheduler schema and current scheduler version match: v7.2.2
2016-09-07 15:42:05.526 com.vertica.solutions.kafka.scheduler.StreamCoordinator::Main [INFO] Stream Coordinator starting application for leadership.
2016-09-07 15:42:05.528 com.vertica.solutions.kafka.scheduler.LeaderSelector::Main [DEBUG] INITIAL. Current Time is : 1473234125527. Waiting until: 1473234125527
2016-09-07 15:42:05.528 com.vertica.solutions.kafka.scheduler.LeaderSelector::Main [DEBUG] Completed waiting period.
2016-09-07 15:42:05.528 com.vertica.solutions.kafka.scheduler.LeaderSelector::Main [DEBUG] Attempting to refresh persistent connection.
2016-09-07 15:42:05.556 com.vertica.solutions.kafka.scheduler.LeaderSelector::Main [DEBUG] Persistent connection ready, attempting leadership locking.

 

Thanks in advance.

Comments

  •  

    Workaround:  i manually kill all running vertica+kafka processes before start job scheduler.

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file