Hi, HTTP 408 could be generated by a proxy server like squid if its in the row?
In general, 3 seconds seems to be pretty long for an AQL query. Did you revalidate using EXLPAIN that its properly using indices etc.? Can you elaborate a bit more on your setup? Single/Cluster? Do you have a (maybe transparent) proxy on your way out into the internet that could be proying arangodb? Cheers, Willi On Tuesday, November 21, 2017 at 1:04:25 PM UTC+1, [email protected] wrote: > > Hi all, > > I have a pretty weird bug that is troubling me, if anyone has any clues, > there will be more than welcome! > > We have a local arangoDB and a live arangoDB setup with the same > configuration. I am continuously receiving a 408 timeout error from my > application but only in the live server and not the local (development) > one. I isolated the HTTP request that was returning the error, the request > seems to run an aql query in the arango database. When I execute the > specific query from the arango interface it returns results every time > without an error both in my local and live database. On the contrary, when > I send the HTTP request from POSTMAN service I sometimes get the following > error : "Client Exception 408 Got a timeout while waiting for the server's > response", while other times it returns the results. This happens ONLY in > the live setup while in the local one it returns the results every time I > send the request. > > After sending several requests I noticed that every time that I got an > error, the response time was more than 3 sec, while when I saw results the > response time was always less than 3 sec, so I assume that is to blame. I > checked the apache configuration that has the default timeout time at 30 > seconds and then moved on to arango. After some digging, the only thing > that I could find related to 3 sec was the following: CLIENT options: > --server.connect-timeout <double> connect timeout in seconds (default: 3) > from https://docs.arangodb.com/3.1/Manual/GettingStarted/Arangosh.html. > Let me point out again that this happens only to the live server while > sending the request in the local server may take up to 14 seconds but > always returns the data. > > The troubling thing is that I have the same setup and same configuration > of arango in both machines, yet the timeout seems to be a problem only in > the live one, does anyone have any idea? > Moreover, I could not find any documentation as to how to change that time > and since I should have to do tests on a live server I want to be sure of > what I am changing. > > Thank you all for your time. > > All the best, > Afiontzi Eleni > -- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
