Trying to use Luke 3.4.0 to debug some Lucene indexes, and having no luck. Getting this error.
"No valid directory at this location, try another location."
Using this command.
java -cp lukeall-3.4.0_1.jar org.getopt.luke.Luke -index /tmp/2/media_2011_44/2/index/
Any advice?
Forgot to mention i'm using ElasticSearch 18.4
yes , i tried and failed.
在 2011年12月9日星期五，phobos182 写道：
Trying to use Luke 3.4.0 to debug some Lucene indexes, and having no luck.
Getting this error."No valid directory at this location, try another location."
Using this command.
java -cp lukeall-3.4.0_1.jar org.getopt.luke.Luke -index
/tmp/2/media_2011_44/2/index/Any advice?
--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Luke-with-Lucene-3-5-0-tp3571556p3571556.html
Sent from the Elasticsearch Users mailing list archive at Nabble.com.
This should work for ES 0.18.4 (I tried yesterday 
- I tried via UI
and open dir)
Be sure you are opening one index and the correct folder:
es-installation/data/yourcluster/nodes/0/indices/yourindex
Regards,
Peter.
On 9 Dez., 10:40, goog cheng googch...@gmail.com wrote:
yes , i tried and failed.
在 2011年12月9日星期五，phobos182 写道：
Trying to use Luke 3.4.0 to debug some Lucene indexes, and having no luck.
Getting this error."No valid directory at this location, try another location."
Using this command.
java -cp lukeall-3.4.0_1.jar org.getopt.luke.Luke -index
/tmp/2/media_2011_44/2/index/Any advice?
--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Luke-with-Lucene-3-5-...
Sent from the Elasticsearch Users mailing list archive at Nabble.com.
BTW: what has this todo with lucene 3.5 ?
Hmmh, I originally just wanted to confirm it but it really does not
work. The version where it worked was 0.18.3. Strange, I'll check
Peter.
On 9 Dez., 10:44, Karussell tableyourt...@googlemail.com wrote:
BTW: what has this todo with lucene 3.5 ?
Uhm, stupid me - the folder is:
es-installation/data/yourcluster/nodes/0/indices/yourindex/0
not
es-installation/data/yourcluster/nodes/0/indices/yourindex/
Peter.
On 9 Dez., 10:51, Karussell tableyourt...@googlemail.com wrote:
Hmmh, I originally just wanted to confirm it but it really does not
work. The version where it worked was 0.18.3. Strange, I'll checkPeter.
On 9 Dez., 10:44, Karussell tableyourt...@googlemail.com wrote:
BTW: what has this todo with lucene 3.5 ?
Note, Lucene 3.5.0 is part of 0.18.5, 0.18.4 works with lucene 3.4.0. Luke
works well.
On Fri, Dec 9, 2011 at 11:57 AM, Karussell tableyourtime@googlemail.comwrote:
Uhm, stupid me - the folder is:
es-installation/data/yourcluster/nodes/0/indices/yourindex/0
not
es-installation/data/yourcluster/nodes/0/indices/yourindex/
Peter.
On 9 Dez., 10:51, Karussell tableyourt...@googlemail.com wrote:
Hmmh, I originally just wanted to confirm it but it really does not
work. The version where it worked was 0.18.3. Strange, I'll checkPeter.
On 9 Dez., 10:44, Karussell tableyourt...@googlemail.com wrote:
BTW: what has this todo with lucene 3.5 ?
I just tried again, and it's not working for me. I am opening the correct folder. I am using data.path, and have my data in ES striped across multiple hard drives on a node. I'm wondering if that has anything to do with the problem.
Receiving this error.
java.io.FileNotFoundException: /data/0/elasticsearch/es_cluster1/nodes/0/indices/media_2011_36/14/index/_wue.fnm (No such file or directory)
Yes, if you stripe the data over several directories, then luke will not
work since the different index files are placed on different directories.
On Sat, Dec 10, 2011 at 1:33 AM, phobos182 phobos182@gmail.com wrote:
Receiving this error.
java.io.FileNotFoundException:
/data/0/elasticsearch/es_cluster1/nodes/0/indices/media_2011_36/14/index/_wue.fnm
(No such file or directory)--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Luke-with-Lucene-3-5-0-tp3571556p3574418.html
Sent from the Elasticsearch Users mailing list archive at Nabble.com.
I have found a solution for this. Basically look for all instances of a index in the data.path, and copy them to a working directory. Then you have it all basically merged down to one copy.
Example.
find %{data.path} -type d -name '%{index}' | grep %{shard} | xargs -I{} cp -rp {} /tmp/2/
Working
find . -type d -name '2011-11-14' | grep 14 | xargs -I{} cp -rp {} /tmp/2/
Then use luke on /tmp/2/14
Copying over several shards to teh same location will override each other
and might create a corrupted index, just look at the single level shard
index.
On Mon, Dec 12, 2011 at 6:03 PM, phobos182 phobos182@gmail.com wrote:
I have found a solution for this. Basically look for all instances of a
index
in the data.path, and copy them to a working directory. Then you have it
all
basically merged down to one copy.Example.
find %{data.path} -type d -name '%{index}' | grep %{shard} | xargs -I{} cp
-rp {} /tmp/2/Working
find . -type d -name '2011-11-14' | grep 14 | xargs -I{} cp -rp {} /tmp/2/Then use luke on /tmp/2/14
--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Luke-with-Lucene-3-5-0-tp3571556p3579833.html
Sent from the Elasticsearch Users mailing list archive at Nabble.com.
© 2020. All Rights Reserved - Elasticsearch
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.