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
RPC calls that take longer than an arbitrary number of ms(defined in config) should be killed and the mongo query killed too with a request took too long error message
The text was updated successfully, but these errors were encountered:
I can add a TIMEOUT=x to the .env and use 'dotenv' module to pull it into the libraries and likely can achieve this..
(I think the newest version of NodeJS actually incorporates a way to import .env variables without 'dotenv' module?)
The architecture needs some refactoring in order to achieve this.. But I think it's possible to do in a short time frame.
Let me know if you'd like me to have a whack at this.. I've read most of the HE code base and have some idea of how this would be achieved.. I'm already a top 20 HE witness so achieving this would be a way to give back to a community that has voted me into a position where the node pays for itself.
As for the mongoDB edits I think with some work it's doable.. by default MongoDB will timeout a call to itself in 60 seconds if the query doesn't return a callback or data.. It may be possible to programmatically tie into the existing timeout in MongoDB and leverage that.
RPC calls that take longer than an arbitrary number of ms(defined in config) should be killed and the mongo query killed too with a request took too long error message
The text was updated successfully, but these errors were encountered: