Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-6252

There is no way to know how the Thread Pool in Pollerd is behaving

    XMLWordPrintable

    Details

      Description

      In 1.10, it is possible to have an idea about how the thread pool configured for Pollerd in poller-configuration.xml is behaving by enabling DEBUG for Pollerd in general or at least for RunnableConsumerThreadPool.

      The information looks like the following:

      2013-11-20 08:57:11,221 DEBUG [PollerScheduler-30 Pool] RunnableConsumerThreadPool$SizingFifoQueue: adjust: started fiber PollerScheduler-30 Pool-fiber0 ratio = 2.0, alive = 1
      2013-11-20 08:57:11,222 DEBUG [PollerScheduler-30 Pool] RunnableConsumerThreadPool$SizingFifoQueue: adjust: started fiber PollerScheduler-30 Pool-fiber1 ratio = 1.5, alive = 2
      2013-11-20 08:57:11,222 DEBUG [PollerScheduler-30 Pool] RunnableConsumerThreadPool$SizingFifoQueue: adjust: started fiber PollerScheduler-30 Pool-fiber2 ratio = 1.3333334, alive = 3
      2013-11-20 08:57:11,222 DEBUG [PollerScheduler-30 Pool] RunnableConsumerThreadPool$SizingFifoQueue: adjust: started fiber PollerScheduler-30 Pool-fiber3 ratio = 1.25, alive = 4
      2013-11-20 08:57:12,226 DEBUG [PollerScheduler-30 Pool] RunnableConsumerThreadPool$SizingFifoQueue: adjust: started fiber PollerScheduler-30 Pool-fiber0 ratio = 2.0, alive = 1
      

      Unfortunately, RunnableConsumerThreadPool has been removed and now the LegacyScheduler is using Java's ExecutorService, which doesn't expose their statistics by default on the logs.

      For this reason, if there is a thread contention, which means that Pollerd is not able to do its job, it is impossible to know about it in 1.12 (basically we're blind).

      This is the equivalent of what we have with the ILR for Collectd, so it is extremely useful to have at least something on the logs to detect possible issues with the amount of work and/or threads configured for Pollerd.

        Attachments

          Activity

            People

            • Assignee:
              agalue Alejandro Galue
              Reporter:
              agalue Alejandro Galue
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: