perfSONAR User Q&A and Other Discussion

[Murilo Vetter <>]

Hi Mark,

Thanks for the reply. One thing that we are having trouble too is that when trying to schedule long time period test, like:

--

Nov 27 08:12:25 90bfb2bfc852 runner INFO     14: With iperf3: throughput --bandwidth 100000000 --duration PT23H50M --source 10.39.2.2 --dest 10.39.2.6 --interval PT1M --buffer-length 1472 --udp
Nov 28 02:12:06 90bfb2bfc852 runner INFO     14: Run succeeded.

--

It does not show the result of the test as expected:

# pscheduler schedule
2019-11-27T06:12:15-05:00 - 2019-11-28T06:02:21-05:00  (Running)
rtt --count 85800 --dest 10.39.2.6 --source 10.39.2.2 (Run with tool 'ping')
https://localhost/pscheduler/tasks/8e410289-449a-4ada-824d-a96b5d338ebc/runs/84df8ac8-a5e4-4053-b9af-3d73a5c36d13


2019-11-27T06:12:25-05:00 - 2019-11-28T06:02:34-05:00  (Cleanup)
throughput --bandwidth 100000000 --duration PT23H50M --source 10.39.2.2 --dest 10.39.2.6 --interval PT1M --buffer-length 1472 --udp (Run with tool 'iperf3')
https://localhost/pscheduler/tasks/2813165e-d957-4dc5-a5c3-67cb8f0ed608/runs/755d77d7-44fa-4ca3-810b-8321db262b4c

# pscheduler result https://localhost/pscheduler/tasks/2813165e-d957-4dc5-a5c3-67cb8f0ed608/runs/755d77d7-44fa-4ca3-810b-8321db262b4c
2019-11-27T06:12:25-05 on 10.39.2.2 and 10.39.2.6 with iperf3:

throughput --bandwidth 100000000 --duration PT23H50M --source 10.39.2.2 --dest 10.39.2.6 --interval PT1M --buffer-length 1472 --udp

Run has not completed.

Is something that we are missing? We know that it is working because looking at router interfaces we see expected traffic.

Regards,

--
Murilo Vetter
Analista de Tecnologia da Informação
REMEP-FLN - Rede Metropolitana Comunitária de Educação e Pesquisa da Região de Florianópolis
PoP-SC - Ponto de Presença da RNP em Santa Catarina
RNP - Rede Nacional de Ensino e Pesquisa
+55 (48) 3721-3000
www.pop-sc.rnp.br | www.rnp.br

---

De: "Mark Feit" <>
Para: "Murilo Vetter" <>, "perfsonar-user" <>, "monipe-des" <>
Enviadas: Quarta-feira, 27 de novembro de 2019 16:11:48
Assunto: Re: [perfsonar-user] PSCHEDULER BUG: Pscheduler maximum limit amount of time to schedule a task

(Sorry for the delay in responding; I was tied up with SC and brought back a cold.)

 

Murilo Vetter writes:

 

When trying to schedule a long period test (like 1 day = 86400 sec), it is failing to schedule.

The maximum amount of time that it passes is 86090 seconds, missing 310 seconds.

Is there some reason to occur this?

 

IT IS WORKING:

pscheduler task throughput -s 10.39.2.2 -d 10.39.2.6 -u -t 86090 -b 100m -l 1472

...

Starts 2019-11-21T07:13:46-05 (~7 seconds)

Ends   2019-11-22T07:08:45-05 (~86098 seconds)

 

IT IS NOT WORKING:

pscheduler task throughput -s 10.39.2.2 -d 10.39.2.6 -u -t 86091 -b 100m -l 1472

...

No runs scheduled for this task.

 

This is indeed a bug, and I’ve opened a ticket on it:  https://github.com/perfsonar/pscheduler/issues/945.  It should be easy to fix and will be corrected in the next bugfix release.

 

--Mark