Ah. 2.0.4 does not have the configurable timeout and semi-sync setup. You can
write a poll function to wait and check for index creation and some of the
clients have something similar as well.
Zeeshan Lakhani
programmer |
software engineer at @basho |
org. member/founder of @papers_we_love |
By the way, it's worth pointing out: if you can avoid it, don't set search
indexes on buckets. Use bucket types instead.
Custom bucket properties (like search indexes) are a lot more
resource-intensive to use than bucket type properties. You're going to see
a slowdown for each new custom bucket
v. 2.0.4. I think I know what might be causing the wrong. I forgot to
add the my custom extractor into riak. Will test it out.
Thanks,
-Hao
On 09/02/2015 11:36 PM, Alex Moore wrote:
netease mail Hao,
What version of Riak are you using?
Thanks,
Alex
On Sep 2, 2015, at 11:26 AM, Fred
I apologize, I was wrong about the timeouts -- they are configurable, either
through the client, or in the advanced config on the Riak server(s).
The timeout gets set in the server here:
https://github.com/basho/yokozuna/blob/2.1.1/src/yz_pb_admin.erl#L114
Hao,
What version of Riak are you using?
Thanks,
Alex
> On Sep 2, 2015, at 11:26 AM, Fred Dushin wrote:
>
> I apologize, I was wrong about the timeouts -- they are configurable, either
> through the client, or in the advanced config on the Riak server(s).
>
> The timeout
Hi,
What's the maximum seconds to wait after creating an search index and
before setting it on the bucket?
On my local machine, I only need to wait 1 second, sometimes I feel I
don't need to wait at all, but on a production server which is basically
zero traffic, I have to wait about 10
What is the return value you are getting from
rick_pb_socket:create_search_index? If it's ok, then the Solr cores should
have been created on all nodes. Otherwise, you should check the logs for
timeout messages, e.g.,
https://github.com/basho/yokozuna/blob/2.1.1/src/yz_index.erl#L443