exception:
org.elasticsearch.indices.TypeMissingException: [friends]
type[friends] missing
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGetAction.java:
87)
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGetAction.java:
59)
at
org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction
$AsyncSingleAction$1.run(TransportShardSingleOperationAction.java:130)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
exception:
org.elasticsearch.indices.TypeMissingException: [friends]
type[friends] missing
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGet Action.java:
87)
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGet Action.java:
59)
at
org.elasticsearch.action.support.single.shard.TransportShardSingleOperation Action
$AsyncSingleAction$1.run(TransportShardSingleOperationAction.java:130)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
exception:
org.elasticsearch.indices.TypeMissingException: [friends]
type[friends] missing
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGet Action.java:
87)
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGet Action.java:
59)
at
org.elasticsearch.action.support.single.shard.TransportShardSingleOperation Action
$AsyncSingleAction$1.run(TransportShardSingleOperationAction.java:130)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
exception:
org.elasticsearch.indices.TypeMissingException: [friends]
type[friends] missing
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGet Action.java:
87)
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGet Action.java:
59)
at
org.elasticsearch.action.support.single.shard.TransportShardSingleOperation Action
$AsyncSingleAction$1.run(TransportShardSingleOperationAction.java:130)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
Don't want to complicate things :), but it might still be an issue with ES as probably rubberband sends the requests faster then the curl script. If you add delays between operations, does it still happen?
On Thursday, February 3, 2011 at 12:01 AM, Ryan wrote:
excellent idea. my curl script is unable to reproduce the issue which
means that this is most likely an issue with rubberband sigh elasticsearch_testcase.sh · GitHub
exception:
org.elasticsearch.indices.TypeMissingException: [friends]
type[friends] missing
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGet Action.java:
87)
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGet Action.java:
59)
at
org.elasticsearch.action.support.single.shard.TransportShardSingleOperation Action
$AsyncSingleAction$1.run(TransportShardSingleOperationAction.java:130)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
After spending the last day ripping out rubberband and using straight
up ruby requests, I'm still able to reproduce the issue, but i've also
learned more about how to more-correctly integrate with elasticsearch.
My workaround for now is to not delete the entire index between test
runs. removing the mapping + documents and reindexing my test
fixtures is really all i need to do. Coming from a solr background,
the elasticsearch concept of one index with multiple types is easy to
overlook. i'm so used to nuking and repopulating the index between
test runs. any other recommendations or gotcha's for using
elasticsearch in a test environment would be appreciated!
Don't want to complicate things :), but it might still be an issue with ES as probably rubberband sends the requests faster then the curl script. If you add delays between operations, does it still happen?
On Thursday, February 3, 2011 at 12:01 AM, Ryan wrote:
excellent idea. my curl script is unable to reproduce the issue which
means that this is most likely an issue with rubberband sigh elasticsearch_testcase.sh · GitHub
exception:
org.elasticsearch.indices.TypeMissingException: [friends]
type[friends] missing
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGet Action.java:
87)
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGet Action.java:
59)
at
org.elasticsearch.action.support.single.shard.TransportShardSingleOperation Action
$AsyncSingleAction$1.run(TransportShardSingleOperationAction.java:130)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
In elasticsearch tests I delete an index and create it each time. I think that we should solve this problem, lemme ping you back when I have a solution. I think, for a testing perspective, deleting an index and creating it is the correct approach, so its a shame you won't be able to do it.
-shay.banon
On Thursday, February 3, 2011 at 8:40 PM, Ryan wrote:
After spending the last day ripping out rubberband and using straight
up ruby requests, I'm still able to reproduce the issue, but i've also
learned more about how to more-correctly integrate with elasticsearch.
My workaround for now is to not delete the entire index between test
runs. removing the mapping + documents and reindexing my test
fixtures is really all i need to do. Coming from a solr background,
the elasticsearch concept of one index with multiple types is easy to
overlook. i'm so used to nuking and repopulating the index between
test runs. any other recommendations or gotcha's for using
elasticsearch in a test environment would be appreciated!
Don't want to complicate things :), but it might still be an issue with ES as probably rubberband sends the requests faster then the curl script. If you add delays between operations, does it still happen?
On Thursday, February 3, 2011 at 12:01 AM, Ryan wrote:
excellent idea. my curl script is unable to reproduce the issue which
means that this is most likely an issue with rubberband sigh elasticsearch_testcase.sh · GitHub
exception:
org.elasticsearch.indices.TypeMissingException: [friends]
type[friends] missing
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGet Action.java:
87)
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGet Action.java:
59)
at
org.elasticsearch.action.support.single.shard.TransportShardSingleOperation Action
$AsyncSingleAction$1.run(TransportShardSingleOperationAction.java:130)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
I just pushed an improvement to the introduction of a type in elasticsearch through an index operation. Can you give it a go and see if it solves your problem? (I can't recreate your problem locally...).
On Thursday, February 3, 2011 at 8:47 PM, Shay Banon wrote:
Heya,
In elasticsearch tests I delete an index and create it each time. I think that we should solve this problem, lemme ping you back when I have a solution. I think, for a testing perspective, deleting an index and creating it is the correct approach, so its a shame you won't be able to do it.
-shay.banon
On Thursday, February 3, 2011 at 8:40 PM, Ryan wrote:
After spending the last day ripping out rubberband and using straight
up ruby requests, I'm still able to reproduce the issue, but i've also
learned more about how to more-correctly integrate with elasticsearch.
My workaround for now is to not delete the entire index between test
runs. removing the mapping + documents and reindexing my test
fixtures is really all i need to do. Coming from a solr background,
the elasticsearch concept of one index with multiple types is easy to
overlook. i'm so used to nuking and repopulating the index between
test runs. any other recommendations or gotcha's for using
elasticsearch in a test environment would be appreciated!
Don't want to complicate things :), but it might still be an issue with ES as probably rubberband sends the requests faster then the curl script. If you add delays between operations, does it still happen?
On Thursday, February 3, 2011 at 12:01 AM, Ryan wrote:
excellent idea. my curl script is unable to reproduce the issue which
means that this is most likely an issue with rubberband sigh elasticsearch_testcase.sh · GitHub
exception:
org.elasticsearch.indices.TypeMissingException: [friends]
type[friends] missing
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGet Action.java:
87)
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGet Action.java:
59)
at
org.elasticsearch.action.support.single.shard.TransportShardSingleOperation Action
$AsyncSingleAction$1.run(TransportShardSingleOperationAction.java:130)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.