Hi <@UDQU92KBK> <@U0122PWUVJT> Our API Team is no...
# troubleshooting
s
Hi @Mayank @Daniel Lavoie Our API Team is not able to connect to Pinot Broker. Can you help me with this? I am attaching the broker log.
Copy code
SEVERE: An I/O error has occurred while writing a response message entity to the container output stream.
org.glassfish.jersey.server.internal.process.MappableException: java.io.IOException: Connection closed
CC: @Mohamed Sultan @Sadim Nadeem
@Daniel Lavoie @Mayank Can you please help me troubleshoot this issue?
m
we are receiving 404 Error when we try to use broker ip
not sure why?
m
Does query via query console work?
m
yes. it is working
m
And can your query broker using curl
If query console works, that means broker up and running. that also implies you can query broker using curl. I’d suggest looking at your client side code. if you are getting 404, that means it is not hitting the right url?
m
Copy code
time="2021-05-28T04:59:26Z" level=error msg="Caught exception to execute SQL query select count(*) from vae_alert, Error: caught http exception when querying Pinot: 404 Not Found\n"
d
Which endpoint are you calling on the broker end?
m
load balancer ip provided by GCP
d
Yes, but what URL path?
m
@Manju Priyadharshini Can you post the URL path that you append in webservice code?
CC: @Sadim Nadeem
@Sandeep ?
m
@Daniel Lavoie We are using Pinot client , to pass the host and port as broker
It will return as the connection with which we are executing the query directly
This is how we used for older instance of Pinot and it's working fine.
d
Controller and broker have different endpoint for query
m
We are using broker ip ,right Sultan?
d
Broker are queried using
/query/sql
.
m
yes @Manju Priyadharshini
s
Not directly querying the pinot broker using curl but using golang pinot connector ie https://docs.pinot.apache.org/users/clients/golang
m
seems like /query/sql this is not used
s
doing it programmatically means querying programmatically by importing pinot-client library
one old pinot cluster.. its working but the latest one its not working
m
Exactly!
s
here.. I dont think we need to append /query/sql because here we just need to specify the host and port
d
Have you tested the query with curl first?
😕 1
s
it is working with other broker ip of other old cluster but not working with broker ip of new cluster
d
Test with curl first please, let’s eliminate the go client from the equation
m
Yes, this ^^
m
Curl, needs to be used with /query and broker ip?what is the endpoint
m
Check the link ^^
m
Okay
s
we tried with both the pinot cluster broker endpoints and the curl worked with both ! @Daniel Lavoie @Mayank
seems issue with only golang connector for one of the pinot clusters
Capture111.PNG
seems issue is realed to istio .. sorry for bothering @Mayank @Daniel Lavoie