You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When load is triggered, the application crashes at some point stating the below error without any stack trace. The application has 2 core Cpu, 6GB of Memory and increased zilla worker capacity of 1024 (as suggested in one of the threads) java.lang.IllegalArgumentException: invalid offset: -65536 stopped
To Reproduce
Steps to reproduce the behavior:
Trigger a load of 1200/sec (adjust the users to 12000)
Expected behavior
The resources are sufficient(as compared to the previous Runs), and the application is healthy. It should result in a successful completion of the load run.
Screenshots
Describe the Host environment including:
Zilla is running on aws ecs with EC2 backing. we are using m5dn.xlarge instance to accommodate the resource.
./zilla start -v -e -Pzilla.engine.worker.capacity=1024
Kafka Environment:
Kafka is running on confluent cloud environment
The text was updated successfully, but these errors were encountered:
Describe the bug
When load is triggered, the application crashes at some point stating the below error without any stack trace. The application has 2 core Cpu, 6GB of Memory and increased zilla worker capacity of 1024 (as suggested in one of the threads)
java.lang.IllegalArgumentException: invalid offset: -65536 stopped
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Screenshots
Describe the Host environment including:
Zilla is running on aws ecs with EC2 backing. we are using m5dn.xlarge instance to accommodate the resource.
./zilla start -v -e -Pzilla.engine.worker.capacity=1024
Kafka Environment:
Kafka is running on confluent cloud environment
The text was updated successfully, but these errors were encountered: