im pretty sure i am doing something wrong here as it doesnt make sense. can
someone tell what it is?
my ES client is taking 100% cpu on a dual core ec2 m1.large instance (so
effectively 50%). while the actual elasticsearch process is hardly taking
my client is designed in the following way - there is one ES client worker
thread which instantiates ES Client once in its constructor. Inside the run
method, it dequeue messages from a local java blockingqueue and uses the
client to do 2 things - a prepareGet and then prepareIndex. if it gets
something from prepareget, it uses the sourcefield map to update the new
document along with new fields that it wants to update. and then does
there is only 1 thread talking to ES service. is this expected?