Slow discovery

Hi Team,

 

We have 5 probes connected to a UCMDB 10.10 server and find discovery happening but very slowly.

 

We have tried various options with HP's guidance and also increased the Java Heap size, diabled all location probes and ran just 1 probe which has many subnets to be scanned.

 

We then stopped the probe services and the ucmdb server services and restarted the jobs and found in 30 mins (100 CI's were added). This again stopped in sometime.

 

Please find the errors attached from the probe.

 

Request your thoughts.

 

Regards

Mathew

Parents
  • We find .hprof files gathering in the bin folder.

     

    Is there a way to eliminate this completely so we get our desired discovery results.

     

    Please advice

  • Hi ,

     

    What are the jobs that is taking alot of time to finish?

    Did you tried customizing those Jobs?

     

    Normally when hprof files are created is because there is OOM issues on the Probe, normaly to figure what is causing this issue we should investigate the hprof file.

     

    Other recommendation is to customize the Jobs schedule to run in different time and not at the same time to avoit that Probe memory get overload.

    Also a huge ip ranges cause OOM on Probe, so please try to customize the ranges if is posible.

     

    Increasing java heap Memory willbe a good WR but firts you should take in count the last customizations after that you can increase heap M in chunk in order to avoid any Probe crash.

     

    Hope it helps.

     

    Best regards,

Reply
  • Hi ,

     

    What are the jobs that is taking alot of time to finish?

    Did you tried customizing those Jobs?

     

    Normally when hprof files are created is because there is OOM issues on the Probe, normaly to figure what is causing this issue we should investigate the hprof file.

     

    Other recommendation is to customize the Jobs schedule to run in different time and not at the same time to avoit that Probe memory get overload.

    Also a huge ip ranges cause OOM on Probe, so please try to customize the ranges if is posible.

     

    Increasing java heap Memory willbe a good WR but firts you should take in count the last customizations after that you can increase heap M in chunk in order to avoid any Probe crash.

     

    Hope it helps.

     

    Best regards,

Children
No Data