Last Modified: May 01, 2019
See more info
Known Affected Versions:
13.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 13.1.1, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52
Opened: Apr 12, 2018
If a discover task fails because of a network issue, the system tries to run the task again at the next scheduled time. If the discover interval is set to 0, the system retries immediately, which may cause restjavad hang.
The discover task tries to use a lot CPU when restjavad continuously retries the task.
If a provider has configured discover interval 0 and the discover task failed because of network issues.
Change the discover interval to 1 hour or more.
Now, if the discover interval is 0 and the discover task fails because of a network issue, the system sends the task to the finished state and does not retry anymore.