https://pinot.apache.org/ logo
Join Slack
Powered by
I am not able to access the Pinot Console
# troubleshooting
s
I am not able to access the Pinot Console
m
What’s the error you get? Is the controller up?
s
Controller is up and running
Error :"This site can’t be reached"
I am running this command - "kubectl get all -n pinot-quickstart"
And I can see this NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/pinot-broker ClusterIP 10.100.156.159 <none> 8099/TCP 39h service/pinot-broker-external LoadBalancer 10.100.120.88 a36f20195655e438f9d4875aad2885c9-1628136870.us-east-1.elb.amazonaws.com 8099:31775/TCP 39h service/pinot-broker-headless ClusterIP None <none> 8099/TCP 39h service/pinot-controller ClusterIP 10.100.39.156 <none> 9000/TCP 39h service/pinot-controller-external LoadBalancer 10.100.135.134 a4c8786ddfacb4ad085eae5ee0ce97a2-1965132924.us-east-1.elb.amazonaws.com 9000:31473/TCP 39h service/pinot-controller-headless ClusterIP None <none> 9000/TCP 39h service/pinot-minion ClusterIP 10.100.75.195 <none> 9514/TCP 39h service/pinot-minion-headless ClusterIP None <none> 9514/TCP 39h service/pinot-server ClusterIP 10.100.174.197 <none> 8098/TCP,80/TCP 39h service/pinot-server-headless ClusterIP None <none> 8098/TCP,80/TCP 39h service/pinot-zookeeper ClusterIP 10.100.21.12 <none> 2181/TCP 39h service/pinot-zookeeper-headless ClusterIP None <none> 2181/TCP,3888/TCP,2888/TCP 39h
Does this mean controller is up?
If yes , then I am not able to access the Controller using Console or CLI
n
What's the url you're using?
s
Using the url for load balancer of controller http//&lt;load balancer dns&gt;9000
just to confirm if I am installing it correctly, below is the command I used to launch pinot on aws EKS:
Copy code
helm install pinot pinot/pinot \
    -n pinot-quickstart \
    --set cluster.name=pinot-quickstart \
    --set server.replicaCount=2 \
    --set server.persistence.storageClass=gp2 \
    --set controller.persistence.storageClass=gp2 \
    --set minion.persistence.storageClass=gp2 \
    --set controller.external.enabled=true \
    --set broker.external.enabled=true \
    --set controller.replicaCount=2
m
If you installed on k8s then perhaps you need to port-forward?
👍 1
s
I am new to k8 and was hoping that pinot quick start guide would have all the right steps. While I am trying to setup port forwarding, wondering that if networking isn't setup correctly, wouldn't the instance fail health-checks ? And loadbalancer wouldn't even add the host as a target. Right now, it shows that host is "inService" which I assume means that it passed the health checks. Below is what the K8 services for controller and load balancer look like, please let me know if there's something you think isn't right. Thank you! 
srishb@88665a03c46f pinot % kubectl describe services pinot-ab-controller-external -n pinot-quickstart
Name:                     pinot-ab-controller-external
Namespace:                pinot-quickstart
Labels:                   app=pinot
<http://app.kubernetes.io/managed-by=Helm|app.kubernetes.io/managed-by=Helm>
<http://app.kubernetes.io/version=0.2.4|app.kubernetes.io/version=0.2.4>
chart=pinot-0.2.4
component=controller
<http://helm.sh/chart=pinot-0.2.4|helm.sh/chart=pinot-0.2.4>
heritage=Helm
release=pinot-ab
Annotations:              <http://meta.helm.sh/release-name|meta.helm.sh/release-name>: pinot-ab
<http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>: pinot-quickstart
type: service-external
Selector:                 app=pinot,chart=pinot-0.2.4,component=controller,release=pinot-ab
Type:                     LoadBalancer
IP Family Policy:         SingleStack
IP Families:              IPv4
IP:                       10.100.2.4
IPs:                      10.100.2.4
LoadBalancer Ingress:     <http://a90475805400a45d381ba96c6bcdeafd-810729280.us-east-1.elb.amazonaws.com|a90475805400a45d381ba96c6bcdeafd-810729280.us-east-1.elb.amazonaws.com>
Port:                     external-controller  9000/TCP
TargetPort:               9000/TCP
NodePort:                 external-controller  32353/TCP
Endpoints:                192.168.35.71:9000,192.168.54.217:9000
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   <none>
srishb@88665a03c46f pinot % kubectl describe services pinot-ab-controller -n pinot-quickstart
Name:              pinot-ab-controller
Namespace:         pinot-quickstart
Labels:            app=pinot
<http://app.kubernetes.io/managed-by=Helm|app.kubernetes.io/managed-by=Helm>
<http://app.kubernetes.io/version=0.2.4|app.kubernetes.io/version=0.2.4>
chart=pinot-0.2.4
component=controller
<http://helm.sh/chart=pinot-0.2.4|helm.sh/chart=pinot-0.2.4>
heritage=Helm
release=pinot-ab
Annotations:       <http://meta.helm.sh/release-name|meta.helm.sh/release-name>: pinot-ab
<http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>: pinot-quickstart
type: service
Selector:          app=pinot,chart=pinot-0.2.4,component=controller,release=pinot-ab
Type:              ClusterIP
IP Family Policy:  SingleStack
IP Families:       IPv4
IP:                10.100.237.164
IPs:               10.100.237.164
Port:              controller  9000/TCP
TargetPort:        9000/TCP
Endpoints:         192.168.35.71:9000,192.168.54.217:9000
Session Affinity:  None
Events:            <none>
@Rong R @Mayank @Kishore G
m
@srishti bhargava if you are running on k8s that is not opened for access you need to port forward?
I meant that from you browser to k8s cluster. I am guessing you are running the browser from you local machine?
So you will need to run something like
Copy code
kubectl -n <namespace> port-forward <controller> 9000:9000
Then you can use http://localhost:9000 from your local node where you did the port-forward @srishti bhargava
s
Thanks Mayank , that worked
👍 1
Open in Slack
PreviousNext
Powered by