57744018578214912: the number that causes a IndexShardMissingException

hi,

whenever we index a document with the number 57744018578214912 a
IndexShardMissingException is being raised.
we can reproduce this on 0.17.6 on OSX (snow leopard, lion) and CentOS
5.6

test.json:
{"create":{"_index":"test","_type":"test","_id":"57744018578214912"}}
{}

curl -XPUT localhost:9200/_bulk --data-binary @test.json

{"error":"IndexShardMissingException[[test][-3] missing]","status":
500}

any idea what's causing that? and how to circumvent?

thanks

jodok

:), opened an issue:
Using 57744018578214912 as an id can cause failure to route to the correct shard · Issue #1294 · elastic/elasticsearch · GitHub.

On Thu, Sep 1, 2011 at 3:38 PM, Jodok Batlogg jodok@batlogg.com wrote:

hi,

whenever we index a document with the number 57744018578214912 a
IndexShardMissingException is being raised.
we can reproduce this on 0.17.6 on OSX (snow leopard, lion) and CentOS
5.6

test.json:
{"create":{"_index":"test","_type":"test","_id":"57744018578214912"}}
{}

curl -XPUT localhost:9200/_bulk --data-binary @test.json

{"error":"IndexShardMissingException[[test][-3] missing]","status":
500}

any idea what's causing that? and how to circumvent?

thanks

jodok