Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Provisiond may stop creating newSuspectScans when discovering large ranges

Description

When using discoveryd to discover large ranges, provisiond appears to stop processing newSuspect events.

It appears that all of the threads 'scanExecutor' pool can get stuck in a waiting state.

Acceptance / Success Criteria

None

depends on

Lucidchart Diagrams

Activity

Show:

Jesse White October 24, 2016 at 3:49 PM

I've tried with both the full set of default detectors, and trimmed down list.

David Hustace October 24, 2016 at 3:47 PM

Jesse, are you running the default set of detectors?

Jesse White October 24, 2016 at 2:18 PM

I spent some more time trying to reproduce this. I've successfully detected and provisioned large ranges of IPs (10k+) without experiencing any problems.

Jesse White April 11, 2016 at 12:33 PM

I have been unable to reproduce the problem locally, we'll need a copy of provisiond.log and a stack trace if this reoccurs.

Jesse White April 11, 2016 at 12:32 PM

I've opened a separate issue the JMX detector timeout in https://opennms.atlassian.net/browse/NMS-8327#icft=NMS-8327.

I also added an additional log message that should help diagnose this if/when it reoccurs: 44fc5e89ec02ba990a477ef0a30c3ade0349bb22

Cannot Reproduce

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

PagerDuty

Created September 3, 2015 at 10:22 AM
Updated October 24, 2016 at 3:49 PM
Resolved October 24, 2016 at 2:19 PM

Flag notifications