Magento 2 .4.6 i have 50000 products when i added 10 products in add to cart usig jmeter that time elasticsearch is kill?

Elastic Search
1

Elastic Search Status
Elastic Search Status1157×312 7.06 KB

2

Please do not post images of text as they can be very hard to read. Also elaborate on your setup and exactly what you are foung and what happens. Is there snything in the Elasticsearch logs? Why would you use Jmeter to add 10 products?

3

Whats the specs of the system(s) where elasticsearch is running? is anything else running on same system(s) ?

The pic shows the process was killed by OOM killer. That suggests, can be 101 other things too, the system might be too constrained.

Output (text please) of

journalctl -u elasticsearch.service
4

Case: Concurrent users (registered users) performing sign in, add to cart where 10 users per second will perform Sign in and add to cart activity on website through JMeter.

JMeter Scrip Details
No of Users : 6000
Duration: : 600 Seconds

Enviornment: AWS
B2C Server Memory: 32GB & Core 16
JVM Memory Assign: 20GB

Actual Result: After completion of run, while analyzing the result, it was observed that 58.92% requests were rejected with
502/Bad Gateway ,401/Unauthorized

Note:

  1. Elasticsearch service was up and running through the run.

  2. Same run was conducted with 1 user per second and 5 users per second performing Sign in and add to cart activity where run completed successfully with 99% request were passed.

  3. Same set of issue occurs while same run was kept on On prim enviornment.

Memory CPU Details
Elasticsearch : CPU=20% ,Memory=20GB (Peak=30GB)
FPM: 3.9% 250 MB
nginx: 0.2%4 MB

Note: same in local machine(onprem) working fine there was not getting any issue.

5

Thanks for added context.

So a 1-node Elasticsearch cluster, and your are doing some load testing, got it.

Can you paste output as requested above, it might help

journalctl -u elasticsearch.service

and confirm if there are other things running on same system as elasticsearch.

6

What type of instance are you using? Is it by any chance an instance type with CPU credits, e.g. a t3? What type and size of storage are you using?

Note that you should not set the heap size to more than 50% of the amount of RAM available to Elasticsearch as it also uses off- heap memory. If you have other components running on the host any memory used by these need to be excluded when calculating the Elasticsearch heap size.

7

Enviornment: AWS
B2C Server Memory: 32GB & Core 16
JVM Memory Assign: 20GB

Actual Result: After completion of run, while analyzing the result, it was observed that 58.92% requests were rejected with
502/Bad Gateway ,401/Unauthorized

Note:

  1. Elasticsearch service was up and running through the run.
  2. Same run was conducted with 1 user per second and 5 users per second performing Sign in and add to cart activity where run completed successfully with 99% request were passed.
  3. Same set of issue occurs while same run was kept on On prim enviornment.

Memory CPU Details
Elasticsearch : CPU=20% ,Memory=20GB (Peak=30GB)
FPM: 3.9% 250 MB
nginx: 0.2%4 MB

Note: same in local machine(onprem) working fine there was not getting any issue.

8

Why ate you reposting the same information without answering any of the questions asked?