I run 1.3TB of active indices on a single node (64 GB ram with 12GB heap size, and 15 small disks in a raid 5), with most of my messages quite small, which makes it looks similar to your case in volume, although I have a significantly lower (about 5K) indexing rate.
I suspect that the single disk on each node may be limiting your capacity here. Try measuring some metrics of disk utilization (read and write rates, latency, and queue lengths). If those all look fine while you're loading the dashboard, then I'm incorrect. If they look like the disk is being thrashed, consider moving to more smaller nodes, or adding additional disks to these nodes to boost the IO rates. -- The information transmitted in this email is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this email in error, please contact the sender and permanently delete the email from any computer. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/cc91b9f2-72b7-455d-b2d3-a1018d9ce919%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
