Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Job activation delayed by 10 seconds under stable network conditions #9658

Closed
lenaschoenburg opened this issue Jul 1, 2022 · 0 comments · Fixed by #9669
Closed

Job activation delayed by 10 seconds under stable network conditions #9658

lenaschoenburg opened this issue Jul 1, 2022 · 0 comments · Fixed by #9669
Labels
kind/bug Categorizes an issue or PR as a bug version:8.1.0-alpha3 Marks an issue as being completely or in parts released in 8.1.0-alpha3 version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0

Comments

@lenaschoenburg
Copy link
Member

Describe the bug

Sometimes jobs are activated exactly 10 seconds after the corresponding service task is activated. In general this can happen for various reasons, for example connection issue between worker, gateway and broker. 10 seconds is also the default request timeout for clients.

We've recently started to observe this in our QA runs, where these delays cause test failures. Since the network should be in a stable condition and this has only recently become an issue, it seems likely that this is actually a regression that we need to fix.

To Reproduce

With a current snapshot version of Zeebe and a spring-zeebe 8.0.5 this was at least not trivially reproducible.

Expected behavior

Under stable network conditions and barring any other issues, there should be virtually no delay between service task activation and job activation.

Log/Stacktrace

{
  "partitionId": 1,
  "value": {
    "version": 1,
    "processDefinitionKey": 2251799813685372,
    "bpmnProcessId": "sequential-test-process",
    "processInstanceKey": 4503599627370626,
    "parentElementInstanceKey": -1,
    "flowScopeKey": 4503599627370626,
    "parentProcessInstanceKey": -1,
    "elementId": "step-0",
    "bpmnElementType": "SERVICE_TASK"
  },
  "key": 4503599627370633,
  "timestamp": 1656635590315,
  "position": 393,
  "valueType": "PROCESS_INSTANCE",
  "intent": "ELEMENT_ACTIVATED",
  "recordType": "EVENT",
  "rejectionType": "NULL_VAL",
  "rejectionReason": "",
  "brokerVersion": "8.1.0",
  "sourceRecordPosition": 390
}
{
  "index": 176,
  "term": 1,
  "entries": [
    {
      "partitionId": 1,
      "value": {
        "type": "test-job",
        "worker": "default",
        "truncated": false,
        "timeout": 10000,
        "maxJobsToActivate": 32,
        "jobKeys": [],
        "jobs": []
      },
      "key": -1,
      "timestamp": 1656635600418,
      "position": 394,
      "valueType": "JOB_BATCH",
      "intent": "ACTIVATE",
      "recordType": "COMMAND",
      "rejectionType": "NULL_VAL",
      "rejectionReason": "",
      "brokerVersion": "8.1.0",
      "sourceRecordPosition": -1
    }
  ]
}

Environment:

  • OS:
  • Zeebe Version:
  • Configuration:
@lenaschoenburg lenaschoenburg added the kind/bug Categorizes an issue or PR as a bug label Jul 1, 2022
@lenaschoenburg lenaschoenburg added the version:8.1.0-alpha3 Marks an issue as being completely or in parts released in 8.1.0-alpha3 label Jul 5, 2022
@Zelldon Zelldon added the version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0 label Oct 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes an issue or PR as a bug version:8.1.0-alpha3 Marks an issue as being completely or in parts released in 8.1.0-alpha3 version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants