Task #4847
closed
Open CPU timeout is too small
100%
Description
We face a problem when we try to run some experiments within the bluebridge infrastructure with openCpu/WPS client because a timeout error is thrown.
This is caused by the fact that OpenCpu is set to timeout after 90 seconds while some experiments can get some more time.
We strongly suggest to increase the opencpu's timeout settings to around 400 seconds to avoid these kind of problems due to the fact these experiments require heavy and time consuming calculations (an example is org.gcube.dataanalysis.wps.statisticalmanager.synchserver.mappedclasses.transducerers.ICHTHYOP_MODEL_ONE_BY_ONE )
the opencpu timeout can be configured inside /etc/opencpu/server.conf
to make the change effective a service restart is required with the command service opencpu restart
Updated by Pasquale Pagano over 8 years ago
- Tracker changed from Support to Upgrade
- Assignee changed from Gianpaolo Coro to _InfraScience Systems Engineer
GP is on holiday. I am assigning the ticket to out system admins to see if they can help.
Updated by Andrea Dell'Amico over 8 years ago
- Tracker changed from Upgrade to Task
- Status changed from New to In Progress
I suppose you are referring to the timelimit.post options, because the timelimit.get option has a timeout of 600 seconds. I'm increasing both of them to 900 seconds, anyway.
Updated by Andrea Dell'Amico over 8 years ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
Done. Let me know if it works.
Updated by Enrico Anello over 8 years ago
Yes, working fine!
Thank you for the quick fix.
Updated by Andrea Dell'Amico over 8 years ago
- Status changed from Feedback to Closed
