Has anyone else experienced issues importing docum...
# community-helpw
William Gogan
06/01/2022, 4:41 PMHas anyone else experienced issues importing documents? We’ve had an import pipeline working for months with zero issues (using coerce_or_drop).. and now suddenly we’re getting blank lines back in the jsonl response format
Possibly coincidentally, it started <12h after switching from single instance to clustered.
j
Jason Bosco
06/01/2022, 5:16 PMWith multi node clusters, write latency does increase since more nodes to ack the write. So I wonder if a client side timeout is kicking in (which usually manifests as a blank “response”)
Jason Bosco
06/01/2022, 5:16 PMCould you try increasing the connectionTimeout value when instantiating the client?
w
William Gogan
06/02/2022, 11:42 AMI don’t think I have that - looking at https://github.com/typesense/typesense-php/tree/master/examples, the comment history shows connection_timeout_seconds was removed.
https://github.com/typesense/typesense-php/commit/e529b421498693743698acf666624274f11b9b1c shows that option was removed.. I’m thinking I would need to pass a custom client instance to the typesense adapter to extend the timeout.
William Gogan
06/02/2022, 11:43 AMIt definitely fails fast, 1-2 seconds from the api call to when the blank line is returned
William Gogan
06/02/2022, 11:44 AMCurrently we’re sending 1000 documents per import batch.. I suppose the other option is to scale that down to 50 or 100 to ensure it falls inside the timing needed for consensus to appear
j
Jason Bosco
06/02/2022, 2:55 PMI’m thinking I would need to pass a custom client instance to the typesense adapter to extend the timeout.That's correct. The option was removed since we now allow any HTTP adapter to be passed in. So you would have to change the connection timeout in the particular HTTP client you're using