Hey Jason,
We’re working on performance issues with YZ filter queries, e.g.
https://github.com/basho/yokozuna/issues/392
https://github.com/basho/yokozuna/issues/392, and coverage plan
generation/caching, and our CliServ team has started doing a ton of benchmarks
as well.
You can bypass YZ,
Hi,
I'm need to use faceting for some of the data in Riak, I know we can use it
with Search.Options, but I couldn't find a decent way to use that. I was
looking at any test cases, but couldn't find any. If some body used it, can
you please post a gist or sample here.
I just need to use enable
Thanks Zeeshan for the info.
Is there a workaround in the mean time, or is the only option to handle queries
to the individual nodes ourselves?
Is there a planned timeframe for the 2.0.1 release?
Thanks,
Jason
On 21 Apr 2015, at 16:13, Zeeshan Lakhani zlakh...@basho.com wrote:
Hey Jason,
No real workaround other than what you described or looking into
config/fq-no-cache settings as mentioned in
http://lucidworks.com/blog/advanced-filter-caching-in-solr/
http://lucidworks.com/blog/advanced-filter-caching-in-solr/ and playing
around with those.
Riak is now at 2.1.0. I hope that
Ok, thanks Andrew! I’ll go ahead and migrate the data to a fresh cluster.
Jonathan Koff B.CS.
co-founder of Projexity
www.projexity.com http://www.projexity.com/
follow us on facebook at: www.facebook.com/projexity
http://www.facebook.com/projexity
follow us on twitter at: twitter.com/projexity
A couple things stand out here. If a node is left in leaving state, it's
likely that the system can't get quorum for the ensembles it's a part of.
Node's that leave wait until their peer membership is transferred via joint
consensus and they are removed from the ensembles in question so that
And I create the bucket type by myself:
riak-admin bucket-type create video '{props:{search_index:videos}}'
riak-admin bucket-type activate vide
-- Original --
From: ;44290...@qq.com;
Send time: Tuesday, Apr 21, 2015 9:49 PM
To:
Dear All,
I have many objects with the same tag:hot stored in Riak cluster with two
nodes, all with leveldb backend.
When I try to search with the same query condition, I just got one result
returned, and everytime with different result:
curl -v
Hi All,
I am currently using the Riak java client v1.4.4, but have also encountered
this issue in 2.0.x.
I am experiencing an issue where the underlying Riak load balancer IP
changes (AWS load balancer) but the DNS cache in the Java app does get
updated, even when the connection fails. I have
Jason,
Comment the filterCache .../ section in the bucket's solrconfig.xml and
restart riak. Now your queries will be fast again :-)
Steve
On 21 April 2015 at 04:24, Zeeshan Lakhani zlakh...@basho.com wrote:
No real workaround other than what you described or looking into
config/fq-no-cache
That is really weird, I tried that before posting, yet it seems to fix things
now.
Oh well, I'll try rolling it out across the cluster, hopefully it works.
Maybe someone with more Solr knowledge can enlighten me though, does disabling
the filter cache change behaviour as well?
For example,
Nice Steve.
Zeeshan Lakhani
programmer |
software engineer at @basho |
org. member/founder of @papers_we_love | paperswelove.org
twitter = @zeeshanlakhani
On Apr 21, 2015, at 3:57 PM, Steve Garon steve.ga...@gmail.com wrote:
Jason,
Comment the filterCache .../ section in the bucket's
Sorry, still running into issues.
So I've disabled cache on all solr nodes, but the yokozuna query times are
still high.
Oddly, running queries against any one node completes in a few ms. So I
injected nginx between riak and solr so I could log queries, and now I'm even
more confused.
There
Zeeshan,
For that specific case, you guys should add *{!cache=false}* in front on
your query plan. Therefore, queries on large index won't be slowed down.
I'd really like to see some of the solrconfig.xml config to be exported to
the riak bucket properties. The caching flag could be a property on
Hey Steve,
Yep, that’s the specific reference point I was referring to in the link I
shared.
We’re working on cleaning-up some stuff to help perf for large indexes within
the yz code itself. We’ve also discussed how to improve configuring specific
solrconfig tunable items as a property of
15 matches
Mail list logo
