UnavailableShardsException[[index1][0] [1] shardIt, [0] active : Timeout waiting for [1m]


(Ramchandra Phadake) #1

Hi,

I am using 0.90.1 with single node cluster without replicas & with 4 shards.

I am getting following error when trying to create 300+ indexes in single
ES batch request.

Error: UnavailableShardsException[[index1][0] [1] shardIt, [0] active :
Timeout waiting for [1m], request:
org.elasticsearch.action.bulk.BulkShasrdRequest@1052336]

300+ indexes are created in a worst case scenario for data load process.
Normally we don't need to create more than 1/2 indexes in a batch call of
500 requests.
The node status becomes red and remains in that state till
"unassigned_shards" : 0. After some time it becomes green.

I did try with bulkResponse =
bulkRequest.execute().actionGet(indexTimeOutMillis) and giving 2/3 minutes
but its not waiting for that much time.
The call returns in around 100 sec. Any idea why this call is not honoring
the wait time.

Thanks,
Ram

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Ramchandra Phadake) #2

I am seeing that indexes are getting created with zero entries in such
case.
So 100 indexes are getting created correctly with 1 entry each but for
other 100+ only index names are created with zero entries.
No error mentioned in ES log file.

Is there any max limit on number of index creation from single bulk request?

Thanks,
Ram

On Tuesday, November 26, 2013 8:07:41 PM UTC+5:30, Ramchandra Phadake wrote:

Hi,

I am using 0.90.1 with single node cluster without replicas & with 4
shards.

I am getting following error when trying to create 300+ indexes in single
ES batch request.

Error: UnavailableShardsException[[index1][0] [1] shardIt, [0] active :
Timeout waiting for [1m], request:
org.elasticsearch.action.bulk.BulkShasrdRequest@1052336]

300+ indexes are created in a worst case scenario for data load process.
Normally we don't need to create more than 1/2 indexes in a batch call of
500 requests.
The node status becomes red and remains in that state till
"unassigned_shards" : 0. After some time it becomes green.

I did try with bulkResponse =
bulkRequest.execute().actionGet(indexTimeOutMillis) and giving 2/3 minutes
but its not waiting for that much time.
The call returns in around 100 sec. Any idea why this call is not
honoring the wait time.

Thanks,
Ram

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/830b4e88-8cdc-40d1-87be-d0a8a2e21b97%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #3