Hello!
I’m using Camunda 8.5
Recently, I’ve faced an issue.
Operate displays running process, but when I try to cancel it, nothing changes, it shows that the process is still running.
In fact process doesn’t exist in Zeebe.
I found this process in elastic with the following error message
“errorMessage”: “Unable to process operation: Command ‘CANCEL’ rejected with code ‘NOT_FOUND’: Expected to cancel a process instance with key ‘2251799868031394’, but no such process was found”,
Could you, please, help.
How can I synchronize Operate( Elastic ) with actual Zeebe state ? I haven’t found any instruction or similar issues in the forum.
Besides similar issues happen periodically. So, there has to be solution.
I hope somebody can help be.
Thank you!
zeebe: # Docker | Camunda 8 Docs
image: camunda/zeebe:${CAMUNDA_PLATFORM_VERSION}
container_name: zeebe
ports:
- “26500:26500”
- “9600:9600”
- “8088:8080”
environment: # Environment variables | Camunda 8 Docs
# This setting controls the maximum number of jobs that can be activated and processed simultaneously by a job worker
# It’s important to note that this setting affects the job worker’s behavior. As explained in the
# Camunda 8 Java client documentation, when you set maxJobsActive, the job worker will first pull
# that many jobs and begin executing them. After a certain threshold of completed jobs
# is reached (30% of maxJobsActive rounded up), the worker will poll for more jobs.
# Default value is 32
- ZEEBE_CLIENT_WORKER_MAX_JOBS_ACTIVE=32
# Job workers are designed to regularly poll and activate jobs.
# It’s also possible to use them in a streaming fashion, such that jobs are automatically activated and
# pushed downstream to workers without requiring an extra round of polling.
# This greatly cuts down on overall activation latency by completely removing the poll request.
- CAMUNDA_CLIENT_ZEEBE_DEFAULTS_STREAM-ENABLED=false
- ZEEBE_BROKER_EXPORTERS_ELASTICSEARCH_CLASSNAME=io.camunda.zeebe.exporter.ElasticsearchExporter
- ZEEBE_BROKER_EXPORTERS_ELASTICSEARCH_ARGS_URL=http://elasticsearch:9200
# Export “zeebe-record” metrics
- ZEEBE_BROKER_EXECUTION_METRICS_EXPORTER_ENABLED=true
# Sets the number of threads the gateway will use to communicate with the broker cluster.
- ZEEBE_BROKER_GATEWAY_THREADS_MANAGEMENTTHREADS=4
# Controls the number of non-blocking CPU threads to be used
- ZEEBE_BROKER_THREADS_CPUTHREADCOUNT=4
# Controls the number of io threads to be used. These threads are used for workloads that write data to disk.
# While writing, these threads are blocked which means that they yield the CPU.
- ZEEBE_BROKER_THREADS_IOTHREADCO=3
# This environment variable sets the delay for the Elasticsearch exporter in Zeebe.
# This configuration affects how quickly data is exported from Zeebe to Elasticsearch
- ZEEBE_BROKER_EXPORTERS_ELASTICSEARCH_ARGS_BULK_DELAY=60
# This environment variable sets the batch size for the Elasticsearch exporter in Zeebe to N records.
# This means that when the exporter has collected N records, it will send them as a bulk request to Elasticsearch.
- ZEEBE_BROKER_EXPORTERS_ELASTICSEARCH_ARGS_BULK_SIZE=100
# This environment variable sets the memory limit (in bytes) for the Elasticsearch exporter
- ZEEBE_BROKER_EXPORTERS_ELASTICSEARCH_ARGS_BULK_MEMORYLIMIT=52428800
# This environment variable specifies the minimum amount of free disk space required for the broker to continue processing commands. When the available free space falls below this threshold, the broker will:
# 1) Reject all client commands
# 2) Pause processing
- ZEEBE_BROKER_DATA_DISK_FREESPACE_PROCESSING=2GB
# This environment variable sets a threshold for free disk space that controls replication behavior in Zeebe brokers. According to the Camunda documentation, when the available free disk space falls below this value
# 1) The broker stops receiving replicated events.
# 2) This helps prevent the broker from running out of disk space due to incoming replicated data.
- ZEEBE_BROKER_DATA_DISK_FREESPACE_REPLICATION=1GB
# Automatically clean up the “zeebe-record_variable” index for Elasticsearch
- ZEEBE_BROKER_EXPORTERS_ELASTICSEARCH_ARGS_RETENTION_ENABLED=true
- ZEEBE_BROKER_EXPORTERS_ELASTICSEARCH_ARGS_RETENTION_MINIMUMAGE=8h #This environment variable sets the maximum number of commands that are processed within one batch.
- ZEEBE_BROKER_PROCESSING_MAXCOMMANDSINBATCH=10 #This environment variable sets the maximum size of the incoming and outgoing messages for zeebe brokert.
- ZEEBE_BROKER_NETWORK_MAXMESSAGESIZE=20MB
# This environment variable sets the maximum size of the incoming and outgoing messages for zeebe gateway.
- ZEEBE_GATEWAY_NETWORK_MAXMESSAGESIZE=20MB
- “JAVA_TOOL_OPTIONS=-XX:MaxRAMPercentage=50.0 -XX:InitialRAMPercentage=25.0 -XX:+ExitOnOutOfMemoryError -XX:+HeapDumpOnOutOfMemoryError”
restart: unless-stopped
healthcheck:
test: [ “CMD-SHELL”, “timeout 10s bash -c ‘:> /dev/tcp/127.0.0.1/9600’ || exit 1” ]
interval: 30s
timeout: 5s
retries: 5
start_period: 30s
volumes:
- zeebe:/usr/local/zeebe/data
networks:
- camunda-platform
depends_on:
- elasticsearch