Hello Team, We have set up the Pinot EKS cluster,...
# troubleshooting
p
Hello Team, We have set up the Pinot EKS cluster, and the Pinot segments are in good condition. However, while querying Pinot, it is unable to resolve the hostname. I am sharing the error message and configuration details below. Could you please help us identify the possible cause of the issue? Alternatively, if you could share any sample configurations for Pinot that have worked for you, that would be greatly appreciated. Error Code: 425 java.net.UnknownHostException: pinot-server-0 at java.base/java.net.InetAddress$CachedAddresses.get(InetAddress.java:797) at java.base/java.net.InetAddress.getAllByName0(InetAddress.java:1533) at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1386) at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1307) Error Code: 427 3 servers [pinot-server-0_R, pinot-server-1_R, pinot-server-2_R] not responded ==== >*kubectl describe pod pinot-server-0 -n pinot* Name: pinot-server-0 Namespace: pinot Priority: 0 Service Account: default Node: ip-instance_ip.ap-south-1.compute.internal/instance_ip Start Time: Thu, 03 Apr 2025 160821 +0530 Labels: app=pinot apps.kubernetes.io/pod-index=0 component=server controller-revision-hash=pinot-server-74cc668884 statefulset.kubernetes.io/pod-name=pinot-server-0 Annotations: kubectl.kubernetes.io/restartedAt: 2025-04-03T160726+05:30 Status: Running IP: instance_ip IPs: IP: instance_ip Controlled By: StatefulSet/pinot-server Containers: pinot-server: Container ID: containerd://2555a9e50377d390c7fb74ce62d9ef79d6a89627c03ee9d3d83892b4eb251642 Image: apachepinot/pinot:1.1.0 Image ID: docker.io/apachepinot/pinot@sha256:84c50e845fade3d00809decca4daeb658d9347628e4e564b707cadf32dd3b74f Port: 8098/TCP Host Port: 0/TCP Command: /opt/pinot/bin/pinot-admin.sh StartServer -zkAddress zookeeper-0.zookeeper-headless.pinot.svc.cluster.local2181,zookeeper 1.zookeeper headless.pinot.svc.cluster.local2181,zookeeper-2.zookeeper-headless.pinot.svc.cluster.local:2181 -serverHost $(POD_NAME) State: Running Started: Thu, 03 Apr 2025 160830 +0530 Ready: True Restart Count: 0 Environment: JAVA_OPTS: -Dplugins.dir=/opt/pinot/plugins -Xms4G -Xmx10G -XX:+UseG1GC -XX:MaxGCPauseMillis=200 POD_NAME: pinot-server-0 (v1:metadata.name) PINOT_SET_INSTANCE_ID_TO_HOSTNAME: true Mounts: /opt/pinot/config from pinot-config (rw) /opt/pinot/logs from server-logs (rw) /tmp/data from server-data (rw) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-rqnkp (ro) Conditions: Type Status PodReadyToStartContainers True Initialized True Ready True ContainersReady True PodScheduled True Volumes: server-data: Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace) ClaimName: server-data-pinot-server-0 ReadOnly: false server-logs: Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace) ClaimName: server-logs-pinot-server-0 ReadOnly: false pinot-config: Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace) ClaimName: pinot-config-pinot-server-0 ReadOnly: false kube-api-access-rqnkp: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt ConfigMapOptional: nil DownwardAPI: true QoS Class: BestEffort Node-Selectors: none Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 41m default-scheduler Successfully assigned pinot/pinot-server-0 to ip-instance_ip.ap-south-1.compute.internal Normal Pulled 41m kubelet Container image "apachepinot/pinot:1.1.0" already present on machine Normal Created 41m kubelet Created container pinot-server Normal Started 41m kubelet Started container pinot-server
x
How do you query Pinot?
Can you check if statefulset service name and network services are configured
As well you dns could resolve the Pinot server hostname