"Palo Alto" query causes server request to "hang"
Closed this issue · 2 comments
dkling commented
These queries work just fine:
- http://...:8081/?query=Palo%20Negro
- http://...:8081/?query=Palo%20Alto,%20CA
But if I try to search for Palo Alto
like this:
http://...:8081/?query=Palo%20Alto
the the request to the server takes forever and I receive no response whatsoever!
dkling commented
The strange thing... it works with the demo server
http://demo.twofishes.net/?autocomplete=true&maxInterpretations=4&query=Palo%20Alto
But with local server which is using HEAD version of the master branch, it does not work...
Does anyone having the same issue?
dkling commented
False alarm. Sorry! I justed restored index data from a backup and it works. It seems that index data got corrupted on the ram disk of an amazon EC2 instance...
BTW, is there any way to check the integrity of index data?
What are the the .CRC files for?
.
├── [ 120] features
│ ├── [1.4G] data
│ ├── [ 11M] .data.crc
│ ├── [ 23M] index
│ └── [181K] .index.crc
├── [ 120] geometry
│ ├── [ 301] data
│ ├── [ 12] .data.crc
│ ├── [ 343] index
│ └── [ 12] .index.crc
├── [ 120] id-mapping
│ ├── [ 16M] data
│ ├── [125K] .data.crc
│ ├── [2.2M] index
│ └── [ 18K] .index.crc
├── [ 92] index-gen-info-2014-06-10-12-36-05.226813
├── [342M] name_index.hfile
├── [2.7M] .name_index.hfile.crc
└── [ 120] prefix_index
├── [108M] data
├── [866K] .data.crc
├── [ 13M] index
└── [100K] .index.crc