ANALYZE operation causes a large number of write failures

When I run ANALYZE at more than 11 o’clock every night, it will be unstable for about a minute, and hundreds of write failures will occur. Later, I modified it to execute once every 48 hours, and it failed more every time I executed it.
Can I control the resources used by ANALYZE? Or is there any way to solve it?

Can you maybe share some more info on your current setup?
Which CrateDB version are you using?

Version: 4.3.2
Total Records: 102.6 Million

There are more than 30 tables totally, the largest table with 40 million data.

This seems strange. Are you actively triggering ANALYZE?
by default it would run at least once every 24h anyway.

Do you see anything in the logs?
Are you constantly inserting, updating, deleting data?
Could you maybe describe your usage patterns a bit more?

With CrateDB 4.4.1 there was a fix concering ANALYZE but I am unsure if this is related.

I turned off the automatic operation of analyze, and manually run it every 2-3 days. The following exceptions occurred during operation:
Write error:
Caused by: java.util.concurrent.TimeoutException: null
at com.ning.http.client.providers.netty.future.NettyResponseFuture.get(

Read error:
“JobKilledException[Job killed. Received data for job=dbb5a6fa-df9c-413b-aa57-5822c7653e42 but there is no job context present. This can happen due to bad network latency or if individual nodes are unresponsive due to high load]”