Re: Riak 2.0 Search Issues

Ok thanks. I'll wait for the patch. Steve On 5 March 2015 at 12:28, Zeeshan Lakhani wrote: > Hey Steve, > > Your data will remain in Riak, but Search will then use AAE to rebuild the > data on the Solr side. This is only to fix Solr’s core data issues. If > you’re worried about an interruptio

Re: Riak 2.0 Search Issues

Hey Steve, Your data will remain in Riak, but Search will then use AAE to rebuild the data on the Solr side. This is only to fix Solr’s core data issues. If you’re worried about an interruption on the SOLR side, as there would be one to reindex the data, you could then wait until things are sur

Re: Riak 2.0 Search Issues

Does deleting core.properties or moving search-root/index deletes any of my index data? Will that cause any interruption to SOLR? Cause I'm having problems on a production cluster and I really don't want to have to backup 300 millions keys again or cause any interruptions to the system ... Steve

Re: Riak 2.0 Search Issues

Hey Steve, We’re currently tracking this issue, https://github.com/basho/yokozuna/issues/442 , and are working on testing out a patch internally. I will update you as soon as we get clarity there. As a possible workaround, I would attempt to delete

Re: Riak 2.0 Search Issues

In solr.log, the kind of exceptions that I'm getting right now is the following: 1. IO Error while trying to get the size of the Directory:java.io.FileNotFoundException: SOME_RAMDOM_FILE* (.doc, .pos, .fnm, .si, .nv, .gen extensions)* 2. SolrException.java:120 null:org.apache.sorl.common.SolrExcep

Re: Riak 2.0 Search Issues

Yes I do have yz_events,handle_info in crash log. Tons of them actually and they have a big ass strack trace attached to each of them. It would be hard for me to provide you with logs. If you have specific questions you want answers to I'd be happy to help though. Steve On 4 March 2015 at 14:20

Re: Riak 2.0 Search Issues

Hey Steve, Sorry to see you’re having new issues. We’ll have the fix for “space in the key” out soon; it’s currently under review. And, I know that this issue is unrelated. I have a few different routes/thoughts for you, but are you seeing anything related to `yz_events,handle_info` in your cr

Riak 2.0 Search Issues

Hey all, We were having the "space in the key" bug in our cluster so we went through the whole dataset, backing it up to json file and removing the spaces in the keys. Then we trashed our whole cluster and restart from scratch reimporting the whole data. Everything worked like a charm for two week