nickva commented on issue #5342: URL: https://github.com/apache/couchdb/issues/5342#issuecomment-2498535318
Thanks for reaching out, Antoine. Do you see any crashes or errors in the logs? QuickJS can build indexes a bit faster but that could mean putting more pressure on the disk or other resources. Do you see increased cpu, disk(I/O quota reaching a limit?) or memory usage during that time? If you your design documents or documents are large sometimes it's possible to hit the maximum stack size in the JS engine for QuickJS that can be adjusted with [memory_limit_bytes](https://docs.couchdb.org/en/stable/config/quickjs.html#quickjs). Though in that case I'd expect to see repeated crashes in the logs with segfault or a memory limit error. Before killing the process try to gather some stats if you an remsh in: That should give us some idea what the the process is doing ``` erlang:process_info(Pid). ``` These three commands will show the top 3 busiest process, message queue lengths and memory users: ``` recon:proc_window(reductions, 3, 5000). recon:proc_window(message_queue_len, 3, 5000). recon:proc_window(memory, 3, 5000). ``` Another option if you see you have reached the [os_process_limit](https://docs.couchdb.org/en/stable/config/query-servers.html#query_server_config/os_process_limit) on any node with the number of couchjs processes, could consider increasing that a bit. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
