timeout on starting big local graphs is very annoying | Voters

timeout on starting big local graphs is very annoying

in progress

Vincent Vialard

Desktop does not recover from the timeout although the graph does get started. The only way to refresh the active graph pane is to reload Desktop.

Remark: The databases are not listed, I found out it might be because I played with the authentication settings...

May 17, 2021

Liza Shkirando

marked this post as

in progress

Jas Kuner

Thanks. We have been looking into this and we are aiming to gather more data in the next release around DBMS timeouts to help inform potential solutions.

Vincent Vialard

We solved this issue in our own OWL-RL inference engine which took sometimes quite a long time to initialize due to the reasoning step that way: we use a wrapper which starts the REST API first with only the "status" route activated, then starts the backend which reports its progress regularly (step/total steps + % of step when possible). The client checks the "status" route and informs the user of the progress. It got rid of unwanted timeouts and and improved the user experience.