our index data is over 10T, so not enough in memory. ( 10 machine, memory max 24g )
cpu is now 20 ~ 30%, wait cpu 20 ~ 25%. disk read 60m, write 6m cpu load 20 the problem... * disk read very high( no search ) -> cpu load high -> index slow... out goal disk read decrease. add question! our cluster 10 machine. but 1 ~ 2 machie converge bulk request. we use java TransportClinet 2014년 11월 5일 수요일 오후 5시 14분 54초 UTC+9, 이윤동 님의 말: > hi! my first question! > > if replica 0 bulk index, then disk read, write ratio same. > but batch finish after... disk read is high than write. > disk read = 10 X disk write... > > so cpu load is high, then batch index very slow.. T.T > > -- 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/91324af8-dc4a-449f-939a-1594c4a8e0fa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
