Sometimes I got this error from my client node, is there any ideas to fix this?
search_phase_execution_exception: \n at onBody (/var/server/app/node_modules/es7/lib/Transport.js:367:23)\n at IncomingMessage.onEnd (/var/server/app/node_modules/es7/lib/Transport.js:291:11)\n at IncomingMessage.emit (events.js:327:22)\n at IncomingMessage.EventEmitter.emit (domain.js:482:12)\n at endReadableNT (_stream_readable.js:1221:12)\n at processTicksAndRejections (internal/process/task_queues.js:84:21) || {\"error\":{\"root_cause\":[],\"type\":\"search_phase_execution_exception\",\"reason\":\"\",\"phase\":\"fetch\",\"grouped\":true,\"failed_shards\":[],\"caused_by\":{\"type\":\"es_rejected_execution_exception\",\"reason\":\"rejected execution of org.elasticsearch.common.util.concurrent.TimedRunnable@6e1d4b05 on QueueResizingEsThreadPoolExecutor[name = my-client-node/search, queue capacity = 1000, min queue capacity = 1000, max queue capacity = 1000, frame size = 2000, targeted response rate = 1s, task execution EWMA = 95.4ms, adjustment amount = 50, org.elasticsearch.common.util.concurrent.QueueResizingEsThreadPoolExecutor@4686a537[Running, pool size = 4, active threads = 4, queued tasks = 1000, completed tasks = 5426155755]]\"}},\"status\":429}","time":"2022-01-11T09:16:49.770Z"
Should I add more data nodes / client nodes or increase the queue size?