Can't create index

Hi, guys:
These days we met a very strange thing. We can't create index in the
cluster. Once we inserted a simple doc, the cluster will become red and new
created index are showed unassigned.
Does anyone know how to resolve this problem?
Thank you very much!

-Regards-
-Jackie-

--
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.

Hi,

When create an index or insert that simple doc what do you see in your
logs? What ES version are you using?

martijn

On 4 February 2013 01:30, jackiedong jackiedong168@gmail.com wrote:

Hi, guys:
These days we met a very strange thing. We can't create index in the
cluster. Once we inserted a simple doc, the cluster will become red and new
created index are showed unassigned.
Does anyone know how to resolve this problem?
Thank you very much!

-Regards-
-Jackie-

--
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.

--
Met vriendelijke groet,

Martijn van Groningen

--
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.

Hi, Martijn:
There is no special log when inserting the simple doc.
The ES version is 0.20.4.
And through status api, I found some logs like:
failures:
[ { index: 'w235',
shard: 9,
reason: 'BroadcastShardOperationFailedException[[w235][9] ]; nested:
RemoteTransportException[Failed to deserialize exception response from
stream]; nested: TransportSerializationException[Failed to deserialize
exception response from stream]; nested:
StreamCorruptedException[unexpected end of block data]; ' },
{ index: 'w235',
shard: 16,
reason: 'BroadcastShardOperationFailedException[[w235][16] ];
nested: RemoteTransportException[Failed to deserialize exception response
from stream]; nested: TransportSerializationException[Failed to deserialize
exception response from stream]; nested:
StreamCorruptedException[unexpected end of block data]; ' } ],
failed: 2 }

在 2013年2月4日星期一UTC+8下午4时28分15秒,Martijn v Groningen写道:

Hi,

When create an index or insert that simple doc what do you see in your
logs? What ES version are you using?

martijn

On 4 February 2013 01:30, jackiedong <jackie...@gmail.com <javascript:>>wrote:

Hi, guys:
These days we met a very strange thing. We can't create index in the
cluster. Once we inserted a simple doc, the cluster will become red and new
created index are showed unassigned.
Does anyone know how to resolve this problem?
Thank you very much!

-Regards-
-Jackie-

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

--
Met vriendelijke groet,

Martijn van Groningen

--
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.

Can you show how you execute that index request with that simple json
document?

On 4 February 2013 16:10, jackiedong jackiedong168@gmail.com wrote:

Hi, Martijn:
There is no special log when inserting the simple doc.
The ES version is 0.20.4.
And through status api, I found some logs like:
failures:
[ { index: 'w235',
shard: 9,
reason: 'BroadcastShardOperationFailedException[[w235][9] ];
nested: RemoteTransportException[Failed to deserialize exception response
from stream]; nested: TransportSerializationException[Failed to deserialize
exception response from stream]; nested:
StreamCorruptedException[unexpected end of block data]; ' },
{ index: 'w235',
shard: 16,
reason: 'BroadcastShardOperationFailedException[[w235][16] ];
nested: RemoteTransportException[Failed to deserialize exception response
from stream]; nested: TransportSerializationException[Failed to deserialize
exception response from stream]; nested:
StreamCorruptedException[unexpected end of block data]; ' } ],
failed: 2 }

在 2013年2月4日星期一UTC+8下午4时28分15秒,Martijn v Groningen写道:

Hi,

When create an index or insert that simple doc what do you see in your
logs? What ES version are you using?

martijn

On 4 February 2013 01:30, jackiedong jackie...@gmail.com wrote:

Hi, guys:
These days we met a very strange thing. We can't create index in the
cluster. Once we inserted a simple doc, the cluster will become red and new
created index are showed unassigned.
Does anyone know how to resolve this problem?
Thank you very much!

-Regards-
-Jackie-

--
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 elasticsearc...@**googlegroups.com.

For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
Met vriendelijke groet,

Martijn van Groningen

--
Met vriendelijke groet,

Martijn van Groningen

--
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.

curl -XPOST localhost:9200/w235/type -d '{"test":"test"}'

在 2013年2月4日星期一UTC+8下午11时13分57秒,Martijn v Groningen写道:

Can you show how you execute that index request with that simple json
document?

On 4 February 2013 16:10, jackiedong <jackie...@gmail.com <javascript:>>wrote:

Hi, Martijn:
There is no special log when inserting the simple doc.
The ES version is 0.20.4.
And through status api, I found some logs like:
failures:
[ { index: 'w235',
shard: 9,
reason: 'BroadcastShardOperationFailedException[[w235][9] ];
nested: RemoteTransportException[Failed to deserialize exception response
from stream]; nested: TransportSerializationException[Failed to deserialize
exception response from stream]; nested:
StreamCorruptedException[unexpected end of block data]; ' },
{ index: 'w235',
shard: 16,
reason: 'BroadcastShardOperationFailedException[[w235][16] ];
nested: RemoteTransportException[Failed to deserialize exception response
from stream]; nested: TransportSerializationException[Failed to deserialize
exception response from stream]; nested:
StreamCorruptedException[unexpected end of block data]; ' } ],
failed: 2 }

在 2013年2月4日星期一UTC+8下午4时28分15秒,Martijn v Groningen写道:

Hi,

When create an index or insert that simple doc what do you see in your
logs? What ES version are you using?

martijn

On 4 February 2013 01:30, jackiedong jackie...@gmail.com wrote:

Hi, guys:
These days we met a very strange thing. We can't create index in the
cluster. Once we inserted a simple doc, the cluster will become red and new
created index are showed unassigned.
Does anyone know how to resolve this problem?
Thank you very much!

-Regards-
-Jackie-

--
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 elasticsearc...@**googlegroups.com.

For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
Met vriendelijke groet,

Martijn van Groningen

--
Met vriendelijke groet,

Martijn van Groningen

--
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.

By the way, it won't become failure for every index. For some indices, they
can be created successfully. But for some inices, it will show as
unassigned shards and make the cluster become to red.

在 2013年2月5日星期二UTC+8上午10时26分34秒,jackiedong写道:

curl -XPOST localhost:9200/w235/type -d '{"test":"test"}'

在 2013年2月4日星期一UTC+8下午11时13分57秒,Martijn v Groningen写道:

Can you show how you execute that index request with that simple json
document?

On 4 February 2013 16:10, jackiedong jackie...@gmail.com wrote:

Hi, Martijn:
There is no special log when inserting the simple doc.
The ES version is 0.20.4.
And through status api, I found some logs like:
failures:
[ { index: 'w235',
shard: 9,
reason: 'BroadcastShardOperationFailedException[[w235][9] ];
nested: RemoteTransportException[Failed to deserialize exception response
from stream]; nested: TransportSerializationException[Failed to deserialize
exception response from stream]; nested:
StreamCorruptedException[unexpected end of block data]; ' },
{ index: 'w235',
shard: 16,
reason: 'BroadcastShardOperationFailedException[[w235][16] ];
nested: RemoteTransportException[Failed to deserialize exception response
from stream]; nested: TransportSerializationException[Failed to deserialize
exception response from stream]; nested:
StreamCorruptedException[unexpected end of block data]; ' } ],
failed: 2 }

在 2013年2月4日星期一UTC+8下午4时28分15秒,Martijn v Groningen写道:

Hi,

When create an index or insert that simple doc what do you see in your
logs? What ES version are you using?

martijn

On 4 February 2013 01:30, jackiedong jackie...@gmail.com wrote:

Hi, guys:
These days we met a very strange thing. We can't create index in the
cluster. Once we inserted a simple doc, the cluster will become red and new
created index are showed unassigned.
Does anyone know how to resolve this problem?
Thank you very much!

-Regards-
-Jackie-

--
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 elasticsearc...@**googlegroups.com.

For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--
Met vriendelijke groet,

Martijn van Groningen

--
Met vriendelijke groet,

Martijn van Groningen

--
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.

On Mon, 2013-02-04 at 07:10 -0800, jackiedong wrote:

Hi, Martijn:
There is no special log when inserting the simple doc.
The ES version is 0.20.4.
And through status api, I found some logs like:
failures:
[ { index: 'w235',
shard: 9,
reason: 'BroadcastShardOperationFailedException[[w235][9] ];
nested: RemoteTransportException[Failed to deserialize exception
response from stream]; nested: TransportSerializationException[Failed
to deserialize exception response from stream]; nested:
StreamCorruptedException[unexpected end of block data]; ' },

Check all the instances of ES that you have running. This error message
is typical when you have mixed versions. All versions of ES must be the
same

clint

--
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.