Open youg9203 opened 2 years ago
Did you use the terraform-aws setup at https://github.com/apache/pulsar/tree/master/deployment/terraform-ansible ?
If so that has been updated in the last few days. You can try to update.
Also you can control memory in:
./deploy-pulsar.yaml
50: max_heap_memory: "12g"
51: max_direct_memory: "12g"
65: max_heap_memory: "512m"
66: max_direct_memory: "1g"
Yes, I have used terraform-aws, and these configurations are already in my deploy-pulsar.xml
file.
The issue had no activity for 30 days, mark with Stale label.
The issue had no activity for 30 days, mark with Stale label.
Describe the bug I have deployed the pulsar on AWS using infrastructure repo, and next, I tried the pulsar command in ec2 instance using ssh and I saw the ec2 instance is out of memory and throws below error:
I see the issue is swap memory but after restarting the instance swap is still 0k, and the issue is gone. This issue I have seen on the proxy (c5.2xlarge) and broker (c5.2xlarge) instances.
Expected behavior Should not go out of memory.
Desktop (please complete the following information):
Additional context I know add the
swapfile
solve the problem, but its not getting clear and that I believe not the right solution.