as the concurrency number increasingly, the code is still passing successfully after requestTimeOutms

[wang-xiaowu]

🐛 Bug Report

To Reproduce

• init es client

global.es = new Client({
  node: '',
  auth: {
    username: '',
    password: '',
  },
  compression: 'gzip', // Default: false
  requestTimeout: 50, // Default: 30000
});

• use it in code

const now = Date.now();
// here is the initial consumption time, 1ms
logger.warn(`total time：${Date.now() - now} ms`);
await es.search(queryCondition);
// here is the consumption time after searching es, as the concurrency number increasingly, maybe can be more than 1500ms 
logger.warn(`total time：${Date.now() - now} ms`);

Expected behavior

A clear and concise description of what you expected to happen.

Your Environment

• node version: 16.15.0
• @elastic/elasticsearch version: 7.17.13
• os: Linux
• any other relevant information

[JoshMock]

Sounds like same problem that was addressed in #2159. Are you able to test with the 8.13 client rather than 7.x to see if that resolves your issue? It would take some effort to backport the fix to 7.17, so I want to make sure I'm on the right track first.

[wang-xiaowu]

ResponseError: {\"error\":\"Content-Type header [application/vnd.elasticsearch+json; compatible-with=8] is not supported\",\"status\":406}

is there any way to compatible with 7.x.
otherwise i need to set up a new elasticsearch server?

[JoshMock]

I'll keep this ticket open and address it as time allows.

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove the stale label, or leave a comment, or this will be closed in 14 days.

[wang-xiaowu]

This issue is stale because it has been open 90 days with no activity. Remove the stale label, or leave a comment, or this will be closed in 14 days.

to remove stale label