perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

pScheduler detects the changes right away, but it will not retroactively apply to tasks that are already on the schedule. For example, any new tests you ran at the command-line should have seen the change as soon as Ansible pushed out the new limits.  Your regular-occurring tests already on the schedule though would not have the limits applied. By default, pSConfig (the component that sets-up your regular occurring tests) asks pScheduler to schedule the next 24 hours of tests. When these tests expired the next day, pSconfig asked for them to be recreated and new limits were applied, hence the lag of about a day.

Andy

On May 15, 2020 at 4:17:08 AM, Tadeja Saje () wrote:

Hello,

I installed 5 perfsonar servers with the limits.conf file.

Throughput limit was set up to 8Gbits/s. Then  I changed to 5Gbit /s
with ansible for all perfsonar servers. It took a day that changes took
effect for all servers. The  measurement interval is 1 hour.

The documentation says: "pScheduler server automatically detects changes
to the limit configuration and put them into effect upon the arrival of
the first request that requires checking limits or 15 seconds, whichever
is longer".

What is average time that pScheduler server detects change?

Best regards,

Tadeja


--
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user