DEBUG message "jobs of type ... not available", but workflow deploys and completes

Camunda 8 Topics Discussion & Questions
1

Using Zeebe cluster (default configuration from docker-compose project, but also seeing this on a local single-instance configuration provided by simple-monitor docker-compose config), I’m getting lots of errors like this, running the test at zeebe-performance-tests (0.22 branch):

[Broker-0-StreamProcessor-1] [Broker-0-zb-actors-1] DEBUG io.zeebe.broker.workflow.repository - Pushed deployment 2251799813685268 to all partitions.
zeebe_broker_2 | 2020-02-27 10:38:46.864 [Broker-1-ManagementRequestHandler] [Broker-1-zb-actors-0] DEBUG io.zeebe.broker.workflow.repository - Deployment CREATE command for deployment     2251799813685268 was written on partition 2
zeebe_broker_1 | 2020-02-27 10:38:46.908 [Broker-0-StreamProcessor-1] [Broker-0-zb-actors-0] DEBUG io.zeebe.broker.workflow.repository - Deployment 2251799813685268 distributed to all partitions successfully.
zeebe_broker_1 | 2020-02-27 10:38:47.360 [GatewayLongPollingJobHandler] [Broker-0-zb-actors-0] DEBUG io.zeebe.gateway - Jobs of type task1 not available. Blocking request BrokerActivateJobsRequest{requestDto={"type":"task1","worker":"da2320bf-4d6f-44d5-9ac0-353e9eb4b12e","timeout":60000,"maxJobsToActivate":31,"jobKeys":[],"jobs":[],"variables":[],"truncated":false}}
zeebe_broker_1 | 2020-02-27 10:38:47.711 [GatewayLongPollingJobHandler] [Broker-0-zb-actors-1] DEBUG io.zeebe.gateway - Jobs of type task2 not available. Blocking request BrokerActivateJobsRequest{requestDto={"type":"task2","worker":"51ab10e7-8e00-4358-b1c4-769f308d813c","timeout":60000,"maxJobsToActivate":31,"jobKeys":[],"jobs":[],"variables":[],"truncated":false}}

As you can see, deployment was successful, and the jobs finished (not sure if the result was OK but the test showed timings and no errors).

In this case, I’m using an AWS t2.xlarge instance, but this also happens locally in a single node configuration, with my own simple workflow.

2

Hey @grexe,

this is not an error it just shows that no more jobs are available and the worker tried to activate/claim some.
The long polling will kick in and will send an response(activate an job) when there is a new one available.

We know the msg might be a bit misleading. We have an issue to reword that https://github.com/zeebe-io/zeebe/issues/3890

Greets
Chris

3 Likes
3

thanks for clearing this up @Zelldon, i’ve also commented on the ticket.

1 Like
4