HPE Ezmeral Software platform
1755042 Members
3420 Online
108828 Solutions
New Discussion юеВ

Zookeeper Timeout while Data Fabric Installation from Scratch

 
msaidbilgehan
Advisor

Zookeeper Timeout while Data Fabric Installation from Scratch

We are installing Data Fabric from scratch to 6 nodes (Installer node also in it). While installing, all nodes gives ZK timeout. No firewall is enabled in nodes or the cluster network. No application binding any ports. All nodes are Ubuntu 20.04 LTS default installation and nothing more. Here is the SS and logs;

 

Screenshot 2023-09-01 at 08.50.32.png

 

 

2 REPLIES 2
Dave Olker
HPE Pro

Re: Zookeeper Timeout while Data Fabric Installation from Scratch

Looking at the installer log, the nodes in your cluster are:

            "all": [
                "node0.cluster",
                "installer.cluster",
                "node4.cluster",
                "node1.cluster",
                "node3.cluster",
                "node2.cluster"
            ],
            "cldb": [
                "installer.cluster",
                "node0.cluster",
                "node1.cluster",
                "node3.cluster",
                "node4.cluster"
            ],
            "es": [],
            "zk": [
                "installer.cluster",
                "node0.cluster",
                "node1.cluster",
                "node3.cluster",
                "node4.cluster"
            ]
 
Are those really the fully-qualified domain names for these nodes, and your hostname resolution provider (DNS, NIS, LDAP, etc.) can resolve these hostnames->IP and IP->hostname successfully?  
 
I'd check for any logfiles specific to the zookeeper under /opt/mapr/zookeeper/zookeeper-3.5.6/logs that you can check for errors.
I work for HPE

[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
msaidbilgehan
Advisor

Re: Zookeeper Timeout while Data Fabric Installation from Scratch

@Dave Olker Those are only local ip-hostname resolutions that only written to hosts file to access IPs over hostname. We didn't add these configurations to DNS servers because still working to get stable installation configurations for cluster. So it is basically a test cluster in our servers that every machine has each others IP and hostname in their hosts and hostname files respectively.