You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When checked by enabling debug mode, langchain_community.document_loaders.pebblo is giving warning when it is timing out(timeout in code is 20 seconds). WARNING:langchain_community.document_loaders.pebblo:Unable to reach pebblo server.
The logs also say that DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): localhost:8000, this means that the connection is established with Pebblo Server and server has accepted the request. Note that, "Unable to reach pebblo server" is custom message which is misleading here.
The exception is raised when timeout of 20 seconds is reached and in parallel, Pebblo Server is finished processing request with it's speed few seconds later if the payload is larger and generating report.
Issue is not on the Pebblo Server side, its the way connection timeout is handled on Pebblo Safe Loader side.
Below is the scenario when /loader/doc api server is busy classifying or generating report and pebblo langchain client waits for its response.
Reduced timeout to 5 seconds: reduced processing time by half, the plugin will not really wait for the response. (Earlier loading time was ~30 secs now it takes 15 secs to finish the loading(On my machine.))
Assumed pebblo-server and pebblo client relationship as async for now, hence changed warning logs to debug logs, this will suppress the unable to connect to pebblo server output and will now appear in debug mode.
@srics , can we reduce it even further? please share your thoughts.
Description
When execute RAG app, we are getting error "unable to reach pebblo server." but it is generating report as expected on Pebblo Server.
Error message
$ python3 fin_corp_rag_app.py
Loading RAG documents ...
Unable to reach pebblo server.
Loaded 93 documents ...
Hydrating Vector DB ...
Finished hydrating Vector DB ...
Expected behavior
It should call Pebblo APIs and pdf report should get generated without any error.
Additional context
Pebblo server was healthy when this error occured.
System:
The text was updated successfully, but these errors were encountered: