In testing the replacement of capsd with provisioned, I enabled provisiond to handle newSuspect events and disabled capsd in service-configuration.xml.
When I rescanned a node (that was originally autodiscovered) all services and interfaces were deleted from the node and the scan ended.
2010-06-01 15:54:19,549 DEBUG [scanExecutor-7] EventUtils: createServiceDeletedEvent for nodeid/ipaddr/service: 27/172.20.1.6 2010-06-01 15:54:19,549 DEBUG [scanExecutor-7] EventUtils: createServiceDeletedEvent for nodeid/ipaddr/service: 27/172.20.1.6 2010-06-01 15:54:19,550 DEBUG [scanExecutor-7] EventUtils: createServiceDeletedEvent for nodeid/ipaddr/service: 27/172.20.1.6 2010-06-01 15:54:19,552 DEBUG [scanExecutor-7] EventUtils: createServiceDeletedEvent for nodeid/ipaddr/service: 27/172.20.1.6 2010-06-01 15:54:19,553 DEBUG [scanExecutor-7] EventUtils: createInterfaceDeletedEvent for nodeid/ipaddr: 27/172.20.1.6 2010-06-01 15:54:19,634 DEBUG [scanExecutor-7] RunnableConsumerThreadPool$SizingFifoQueue: adjust: started fiber EventHandlerPool-fiber0 ratio = 2.0, alive = 1 2010-06-01 15:54:19,635 DEBUG [scanExecutor-7] RunnableConsumerThreadPool$SizingFifoQueue: adjust: started fiber EventHandlerPool-fiber1 ratio = 1.5, alive = 2 2010-06-01 15:54:19,635 DEBUG [scanExecutor-7] RunnableConsumerThreadPool$SizingFifoQueue: adjust: started fiber EventHandlerPool-fiber3 ratio = 1.3333334, alive = 3 2010-06-01 15:54:19,636 DEBUG [scanExecutor-7] NodeScan$NoAgentScan: Finished phase batch task 2010-06-01 15:54:19,638 DEBUG [pool-1-thread-9] NodeScan: Finished scanning node (default/null)
This, I assume, is less than optimal. (grin)
Environment
Operating System: All
Platform: PC
Acceptance / Success Criteria
None
Attachments
1
Lucidchart Diagrams
Activity
Show:
Former user June 3, 2010 at 6:25 PM
Fixed in commit 938c92387cb0a67f443183c950aeb021cd012c1e
Tested as well.
Tarus Balog June 1, 2010 at 3:53 PM
Created an attachment (id=1014) Screenshot of deleted services/interface
In testing the replacement of capsd with provisioned, I enabled provisiond to handle newSuspect events and disabled capsd in service-configuration.xml.
When I rescanned a node (that was originally autodiscovered) all services and interfaces were deleted from the node and the scan ended.
2010-06-01 15:54:19,549 DEBUG [scanExecutor-7] EventUtils: createServiceDeletedEvent for nodeid/ipaddr/service: 27/172.20.1.6
2010-06-01 15:54:19,549 DEBUG [scanExecutor-7] EventUtils: createServiceDeletedEvent for nodeid/ipaddr/service: 27/172.20.1.6
2010-06-01 15:54:19,550 DEBUG [scanExecutor-7] EventUtils: createServiceDeletedEvent for nodeid/ipaddr/service: 27/172.20.1.6
2010-06-01 15:54:19,552 DEBUG [scanExecutor-7] EventUtils: createServiceDeletedEvent for nodeid/ipaddr/service: 27/172.20.1.6
2010-06-01 15:54:19,553 DEBUG [scanExecutor-7] EventUtils: createInterfaceDeletedEvent for nodeid/ipaddr: 27/172.20.1.6
2010-06-01 15:54:19,634 DEBUG [scanExecutor-7] RunnableConsumerThreadPool$SizingFifoQueue: adjust: started fiber EventHandlerPool-fiber0 ratio = 2.0, alive = 1
2010-06-01 15:54:19,635 DEBUG [scanExecutor-7] RunnableConsumerThreadPool$SizingFifoQueue: adjust: started fiber EventHandlerPool-fiber1 ratio = 1.5, alive = 2
2010-06-01 15:54:19,635 DEBUG [scanExecutor-7] RunnableConsumerThreadPool$SizingFifoQueue: adjust: started fiber EventHandlerPool-fiber3 ratio = 1.3333334, alive = 3
2010-06-01 15:54:19,636 DEBUG [scanExecutor-7] NodeScan$NoAgentScan: Finished phase batch task
2010-06-01 15:54:19,638 DEBUG [pool-1-thread-9] NodeScan: Finished scanning node (default/null)
This, I assume, is less than optimal. (grin)