Skip to content

Zookeeper primary pod won't start #546

Description

@snocke

Affected version

3.8.0

Current and expected behavior

I wanted to set up a zookeeper cluster with primary and secondary setup. Just like the integration test

However, just the primary-0 won't start. Please see the log and setup below

Possible solution

No response

Additional context

grafik

grafik

Environment

Mac M1
MacOs Montery 12.5
docker image explicitly build for ARM machines
Client Version: v1.24.3
Kustomize Version: v4.5.4
Server Version: v1.24.0

zookeeper.log.txt
zookeeper.yaml.txt

Would you like to work on fixing this bug?

maybe

Activity

  1. nightkr commented on Sep 19, 2022

    @nightkr
    Contributor

    Looks like ZooKeeper node ID confusion.

    If you use multiple rolegroups then you need to configure myidOffset per rolegroup so that the sequences of myidOffset .. myidOffset + replicas don't overlap.

    For example, you could change your ZookeeperCluster to:

    apiVersion: zookeeper.stackable.tech/v1alpha1
    kind: ZookeeperCluster
    metadata:
      name: zookeeper
    spec:
      config:
        quorumTlsSecretClass: tls
      servers:
        roleGroups:
          primary:
            replicas: 2
          secondary:
            replicas: 1
            config:
              myidOffset: 10
      version: 3.8.0-stackable0.99.0
      stopped: false
  2. nightkr commented on Oct 11, 2022

    @nightkr
    Contributor

    @snocke Did this fix your issue?

  3. lfrancke commented on Dec 13, 2022

    @lfrancke
    Member

    We'll solve this using documentation for now but in the end the operator could also warn about this, right?

  4. snocke commented on Dec 14, 2022

    @snocke
    Author

    Sorry, I somehow did not get notified about your comment
    Thank you @teozkr for your fix.

    @lfrancke Warning about it would definitly be helpful.

  5. fhennig commented on Dec 14, 2022

    @fhennig
    Contributor

    A warning sounds like a good idea, if @lfrancke you agree I'd suggest to move this into a new ticket.

    This is fixed, I'm closing it.

  6. lfrancke commented on Dec 15, 2022

    @lfrancke
    Member

    Yes, please, can you open an issue?

  7. fhennig commented on Dec 19, 2022

    @fhennig
    Contributor

    Sure! Here it is: #610

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions