Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To clear it (and all other limits that were set for the jobsite):

  • Click Put "true" in the parameter box for "userClearLimits" (in the same widget.Note: There may ) and then click the button.  However, there seems to be a bug here. , and this may not work.  According to Brian userClearLimits will clean out a file that is stored, but it won't clear out the in-memory state. The parameter userStoreLimits is what writes the file, persisting the in memory state. Without the file, it will forget limits that are set in the pipeline in the memory on restart. 
  • If just setting it to "true" doesn't restart processing:
    • Use the admin page to restart the pipeline server.  According to Brian userClearLimits with "true" and a restart works because you delete the files and pick up database configs on restart.
    • You can also try putting "false" in the box, and then "true".
    • Alternatively, set
    • If processes don't start running after you reset userClearLimits, you may need to put "true" in its parameter box and click the button again. 
    • Restart the pipeline
    • Alternatively; Set the limit to something high/reasonable, such as 6000.

...