3 Replies Latest reply on Dec 9, 2015 9:59 AM by Valerie Joyce

    backgrounder worker(s) will not stop running - always 'busy'

    Valerie Joyce

      What are the possibilities that would cause this?  We are on Tableau server 9.1.1

      When our half-hourly extracts are running, all 4 backgrounders are shown busy.  Once the half-hourly

      extracts are done, the last one changes to active but the other 3 are always 'spinning' (busy).

      I have not seen the other 3 change to 'Active'.

      Thanks,
      Valerie

       

       

      Tableau Status backgrounder busy.jpg

        • 1. Re: backgrounder worker(s) will not stop running - always 'busy'
          Valerie Joyce

          Rebooting the server seems to have cleared it up for now.

          • 2. Re: backgrounder worker(s) will not stop running - always 'busy'
            John Kuo

            How many CPU cores does worker2 have? Do you have a lot of scheduled tasks? Maybe you just need more backgrounder processes to handle all the jobs. Can you show us your server schedule? Log on to Tableau Server > server > schedule.

            • 3. Re: backgrounder worker(s) will not stop running - always 'busy'
              Valerie Joyce

              Hi John,

               

              We have 4 backgrounders that have been running flawlessly for months and they handle our schedules of up to 20 extracts fine.

              We do thousands of extracts a week without error.

               

              The situation where our backrounders got into a s a state of showing busy, even though they were doing no work,  was probably due to the primary server becoming unresponsive and being rebooted by operations  (which restarted the primary server) without the workers being brought down.

              (We verified that they were busy and doing no work by going to the “Background Tasks for Extracts” page and seeing that only 1 extract was being handled. Normally we would see four extracts in process if all four workers were spinning. The tabadmin status command showed everything was healthy during this time.).

               

              After the operations reboot of the primary Tableau server, Tableau came back up and was operating, in a deteriorated mode where only one of our 4 background processes was processing extracts, the other three just showing busy.

               

              Once we had an operational window to use tabadmin to stop the server(s) and start them again,  all background processes have been running as expected.

               

              Valerie