K6 Cloud emits Logs that I don't understand and searching turns up nothing

Grafana k6 Cloud Support
1 
---------------------------------LOG START---------------------------------
Nov 16, 19:10:23		Columbus, US		instance ID: #3		Executor 'Scenario1' is disabled for segment 3/4:1 due to lack of work!		test_run_id: 2092102
Nov 16, 19:10:23		Columbus, US		instance ID: #3		Executor 'Scenario2' is disabled for segment 3/4:1 due to lack of work!		test_run_id: 2092102
Nov 16, 19:10:23		Columbus, US		instance ID: #3		Executor 'Scenario3' is disabled for segment 3/4:1 due to lack of work!		test_run_id: 2092102
Nov 16, 19:10:23		Columbus, US		instance ID: #3		Executor 'Scenario4' is disabled for segment 3/4:1 due to lack of work!		test_run_id: 2092102
Nov 16, 19:10:23		Columbus, US		instance ID: #2		Executor 'Scenario1' is disabled for segment 1/2:3/4 due to lack of work!		test_run_id: 2092102
Nov 16, 19:10:23		Columbus, US		instance ID: #2		Executor 'Scenario2' is disabled for segment 1/2:3/4 due to lack of work!		test_run_id: 2092102
Nov 16, 19:10:23		Columbus, US		instance ID: #2		Executor 'Scenario3' is disabled for segment 1/2:3/4 due to lack of work!		test_run_id: 2092102
Nov 16, 19:10:23		Columbus, US		instance ID: #2		Executor 'Scenario4' is disabled for segment 1/2:3/4 due to lack of work!		test_run_id: 2092102
Nov 16, 19:10:24		Columbus, US		instance ID: #1		Executor 'Scenario1' is disabled for segment 1/4:1/2 due to lack of work!		test_run_id: 2092102
Nov 16, 19:10:24		Columbus, US		instance ID: #1		Executor 'Scenario2' is disabled for segment 1/4:1/2 due to lack of work!		test_run_id: 2092102
Nov 16, 19:10:24		Columbus, US		instance ID: #1		Executor 'Scenario3' is disabled for segment 1/4:1/2 due to lack of work!		test_run_id: 2092102
Nov 16, 19:10:24		Columbus, US		instance ID: #1		Executor 'Scenario4' is disabled for segment 1/4:1/2 due to lack of work!		test_run_id: 2092102

It looks like these scenarios run, but the log message is concerning.
The scenarios are using constant-vus and constant-arrival-rate executors

Just looking to understand these log messages a bit, thank you.

3

Hi @rickguyton, welcome to the community forum!

Could you share the scenario settings with us?

4

@bandorko sure.
Scenario1, Scenario2, Scenario3 have these settings

{
  executor: 'constant-vus',
  exec: funcName,
  vus: 1,
  duration: '30m'
}

Scenario4 has these settings

{
  executor: 'constant-arrival-rate',
  exec: funcName,
  preAllocatedVUs: 1,
  duration: '30m',
  timeUnit: '1s',
  rate: 1
}
5

@rickguyton

It happens because all of your scenarios runs on 1 VU. K6 tries to distribute the job among 4 instances, but 1 VU can’t be distributed, so the 1st instance will work, the other 3 has no work.

The constant-vus scenario is set to 1 VU
The constant-arrival-rate scenario will also run on 1 VU because maxVUs is not set, and the default value for maxVUs is the value of the preallocatedVUs.

If you increase the vus and the preallocatedVUs to 4, then these logs should disappear.

1 Like