terminating, wrongly, after 5 minutes

[zeph]

not all the requests are being performed... it stops at 5minutes
(I used the latest binary 2.0.0-rc1x available at https://github.com/goadapp/goad/releases )

$ ~/Downloads/goad -n 1000000 https://<removed>/
Regional results

Region: us-east-1
   TotReqs   TotBytes    AvgTime   AvgReq/s  AvgKbps/s
     10327     420 MB     0.086s      34.42 1401038.50
   Slowest    Fastest   Timeouts  TotErrors
    0.540s     0.075s          0          0
Region: eu-west-1
   TotReqs   TotBytes    AvgTime   AvgReq/s  AvgKbps/s
      9999     407 MB     0.088s      33.23 1352875.75
   Slowest    Fastest   Timeouts  TotErrors
    0.570s     0.078s          0          0
Region: ap-northeast-1
   TotReqs   TotBytes    AvgTime   AvgReq/s  AvgKbps/s
     10497     427 MB     0.084s      34.96 1423353.75
   Slowest    Fastest   Timeouts  TotErrors
    1.177s     0.073s          0          0

Overall

   TotReqs   TotBytes    AvgTime   AvgReq/s  AvgKbps/s
     30823     1.3 GB     0.086s     102.61 4177268.00
   Slowest    Fastest   Timeouts  TotErrors
    1.177s     0.073s          0          0
HTTPStatus   Requests
       200      30823

[cwaltken-edrans]

@zeph have you checked the IAM role in your account? I'm just running the specified version of goad for more then 5 minutes without any trouble, still receiving data from the lambda functions.

Also note that if you're experiencing connection losses or spikes of more then 15 seconds the cli aborts.

[cwaltken-edrans]

Ah it seems like it's not working when we launch the lambda function for the second time at the 10 minute barrier... That's rare...

[zeph]

seems still occurring

$ time ~/Downloads/goad -n 100000 https://<url>/
Regional results

Region: ap-northeast-1
   TotReqs   TotBytes    AvgTime    AvgReq/s  AvgBytes/s
     10517     428 MB     0.084s      35.06     1.4 MB/s
   Slowest    Fastest   Timeouts  TotErrors
    1.172s     0.077s          0          0
Region: eu-west-1
   TotReqs   TotBytes    AvgTime    AvgReq/s  AvgBytes/s
     10416     424 MB     0.085s      34.61     1.4 MB/s
   Slowest    Fastest   Timeouts  TotErrors
    0.559s     0.078s          0          0
Region: us-east-1
   TotReqs   TotBytes    AvgTime    AvgReq/s  AvgBytes/s
     10267     418 MB     0.086s      34.14     1.4 MB/s
   Slowest    Fastest   Timeouts  TotErrors
    0.574s     0.074s          0          0

Overall

   TotReqs   TotBytes    AvgTime    AvgReq/s  AvgBytes/s
     31200     1.3 GB     0.085s     103.81     4.2 MB/s
   Slowest    Fastest   Timeouts  TotErrors
    1.172s     0.074s          0          0
HTTPStatus   Requests
       200      31200


real	5m35.390s
user	0m3.855s
sys	0m0.545s

[gserra-olx]

@cwaltken-edrans IAM updated but... count != total

$ time ~/Downloads/goad -n 100000 https://<url>
Regional results

Region: ap-northeast-1
   TotReqs   TotBytes    AvgTime    AvgReq/s  AvgBytes/s
     17143     698 MB     0.159s      25.33     1.0 MB/s
   Slowest    Fastest   Timeouts  TotErrors
    1.519s     0.074s          0          0
Region: eu-west-1
   TotReqs   TotBytes    AvgTime    AvgReq/s  AvgBytes/s
     33333     1.4 GB     0.031s     325.14      13 MB/s
   Slowest    Fastest   Timeouts  TotErrors
    0.584s     0.003s          0          0
Region: us-east-1
   TotReqs   TotBytes    AvgTime    AvgReq/s  AvgBytes/s
     31544     1.3 GB     0.087s      33.99     1.4 MB/s
   Slowest    Fastest   Timeouts  TotErrors
    0.622s     0.074s          0          0

Overall

   TotReqs   TotBytes    AvgTime    AvgReq/s  AvgBytes/s
     82020     3.3 GB     0.079s     384.47      16 MB/s
   Slowest    Fastest   Timeouts  TotErrors
    1.519s     0.003s          0          0
HTTPStatus   Requests
       200      82020


real	25m0.538s
user	0m1.859s
sys	0m0.467s

[zeph]

@p.s. I left it running while I left the workstation, might be also terminating due to
the laptop going in freeze (it shouldn't do it.. but ok... ) [re-running]

[zeph]

closing

$ time ~/Downloads/goad -n 100000 https://<url>/
Regional results

Region: eu-west-1
   TotReqs   TotBytes    AvgTime    AvgReq/s  AvgBytes/s
     33333     1.4 GB     0.031s     291.91      12 MB/s
   Slowest    Fastest   Timeouts  TotErrors
    1.051s     0.003s          0          0
Region: ap-northeast-1
   TotReqs   TotBytes    AvgTime    AvgReq/s  AvgBytes/s
     33334     1.4 GB     0.212s      17.90     728 kB/s
   Slowest    Fastest   Timeouts  TotErrors
    1.582s     0.069s          0          1
Region: us-east-1
   TotReqs   TotBytes    AvgTime    AvgReq/s  AvgBytes/s
     33333     1.4 GB     0.085s      34.77     1.4 MB/s
   Slowest    Fastest   Timeouts  TotErrors
    1.213s     0.069s          0          0

Overall

   TotReqs   TotBytes    AvgTime    AvgReq/s  AvgBytes/s
    100000     4.1 GB     0.109s     344.57      14 MB/s
   Slowest    Fastest   Timeouts  TotErrors
    1.582s     0.003s          0          1
HTTPStatus   Requests
       200      99999
       408          1


real	40m33.286s
user	0m3.980s
sys	0m0.870s

[CraigKennedy]

I'm seeing a similar issue. The application continues to function beyond the 5 minute window, but starts receiving 401 errors at the 5 minute mark (every test). I'm passing an authorization header (-H 'Authorization: bearer <>' on the command line. It works for 5 minutes, then starts failing with 401. It seems like it no longer sends the header token after this amount of time. Do you have any thoughts regarding this issue?

Tested using version 2.0.4

[cwaltken-edrans]

Might be that the authorization header is not passed correctly to the invoked lambda function. Lambda functions have a maximum lifetime of 5 minutes. To circumvent that goad launches a followup lambda function when reaching the time-limit. The error is probably located there and should be easy to fix. Let's track here: #187