Re: What's the maximum seconds to set index on bucket after creating the index

[zlakhani]

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 |
twitter => @zeeshanlakhani

> On Sep 2, 2015, at 8:31 AM, Hao  wrote:
> 
> 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:
>> 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 gets set in the server here:
>>> 
>>> https://github.com/basho/yokozuna/blob/2.1.1/src/yz_pb_admin.erl#L114
>>> 
>>> This means you can set the timeout in the PB client, as in
>>> 
>>> riakc_pb_socket:create_search_index(Pid, Index, Schema, [{timeout, 
>>> Timeout}, ...])
>>> 
>>> where timeout is in milliseconds (or the atom 'infinity').
>>> 
>>> cf. http://basho.github.io/riak-erlang-client/
>>> 
>>> The order of precedence is:
>>> 
>>> 1. client-defined
>>> 2. riak config
>>> 3. default (45 seconds)
>>> 
>>> -Fred
>>> 
 On Sep 2, 2015, at 8:13 AM, Fred Dushin  wrote:
 
 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
 
 If you are getting timeouts, instead of sleeping, you should probably 
 query your cluster for the search index, along the lines of what is done 
 in one of the riak tests, e.g.,
 
 https://github.com/basho/yokozuna/blob/2.1.1/riak_test/yz_pb.erl#L100
 
 If necessary, you might want to fold over all nodes in your cluster, to 
 ensure the index has been propagated to all nodes, and possibly use the 
 wait_for patterns used in the tests.
 
 Unfortunately, it looks like the internal timeout used to wait for 
 propagation of indexes to all nodes is not configurable -- it defaults to 
 45 seconds:
 
 https://github.com/basho/yokozuna/blob/2.1.1/include/yokozuna.hrl#L134
 
 I hope that helps,
 
 -Fred
 
> On Sep 2, 2015, at 6:27 AM, Hao  wrote:
> 
> 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 seconds(definitely over 5s) before 
> I can set the index on a bucket.
> 
> I am using riakc_pb_socket client. At first I thought something wrong 
> with my function to "create" and "set" the index but then when I split 
> the process, it's fine. So seems it's the interval in between that 
> matters.
> 
> I need to know how long is the maximum because I need to restore a lot of 
> buckets and set index on them via a script. I don't care how long it 
> takes but I don't want it to miss any index not being set on the bucket.
> 
> The exact error on the console when I set the index on a bucket is
> 
> <<"Invalid bucket properties: [{search_index,\n 
> <<\"application_test_player_idx does not exist\">>}]">>
> 
> 
> 
> 
> Thanks,
> 
> 
> 
> -- 
> Hao
> 
> 
> 
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>> 
>>> ___
>>> riak-users mailing list
>>> riak-users@lists.basho.com
>>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>> 
>> 1 attachments
>> signature.asc(1K)
>> download preview
> 
> -- 
> Hao
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: What's the maximum seconds to set index on bucket after creating the index

[Dmitri Zagidulin]

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 you create, after a while.

On Wed, Sep 2, 2015 at 11:31 AM, Hao  wrote:

> 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:
>
> 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 gets set in the server here:
>
> https://github.com/basho/yokozuna/blob/2.1.1/src/yz_pb_admin.erl#L114
>
> This means you can set the timeout in the PB client, as in
>
> riakc_pb_socket:create_search_index(Pid, Index, Schema, [{timeout,
> Timeout}, ...])
>
>
> where timeout is in milliseconds (or the atom 'infinity').
>
> cf. http://basho.github.io/riak-erlang-client/
>
> The order of precedence is:
>
> 1. client-defined
> 2. riak config
> 3. default (45 seconds)
>
> -Fred
>
> On Sep 2, 2015, at 8:13 AM, Fred Dushin  wrote:
>
> 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
>
> If you are getting timeouts, instead of sleeping, you should probably
> query your cluster for the search index, along the lines of what is done in
> one of the riak tests, e.g.,
>
> https://github.com/basho/yokozuna/blob/2.1.1/riak_test/yz_pb.erl#L100
>
> If necessary, you might want to fold over all nodes in your cluster, to
> ensure the index has been propagated to all nodes, and possibly use the
> wait_for patterns used in the tests.
>
> Unfortunately, it looks like the internal timeout used to wait for
> propagation of indexes to all nodes is not configurable -- it defaults to
> 45 seconds:
>
> https://github.com/basho/yokozuna/blob/2.1.1/include/yokozuna.hrl#L134
>
> I hope that helps,
>
> -Fred
>
> On Sep 2, 2015, at 6:27 AM, Hao  wrote:
>
> 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 seconds(definitely over 5s) before I
> can set the index on a bucket.
>
> I am using riakc_pb_socket client. At first I thought something wrong with
> my function to "create" and "set" the index but then when I split the
> process, it's fine. So seems it's the interval in between that matters.
>
> I need to know how long is the maximum because I need to restore a lot of
> buckets and set index on them via a script. I don't care how long it takes
> but I don't want it to miss any index not being set on the bucket.
>
> The exact error on the console when I set the index on a bucket is
>
> <<"Invalid bucket properties: [{search_index,\n
> <<\"application_test_player_idx does not exist\">>}]">>
>
>
>
>
> Thanks,
>
>
>
> --
> Hao
>
>
>
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
>
>
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
>
> *1* attachments
> signature.asc(1K) download
> 
> preview
> 
>
>
> --
> Hao
>
>
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
>
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: What's the maximum seconds to set index on bucket after creating the index

[Hao]

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 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 gets set in the server here:

https://github.com/basho/yokozuna/blob/2.1.1/src/yz_pb_admin.erl#L114

This means you can set the timeout in the PB client, as in

riakc_pb_socket:create_search_index(Pid, Index, Schema,
[{timeout, Timeout}, ...])


where timeout is in milliseconds (or the atom 'infinity').

cf. http://basho.github.io/riak-erlang-client/

The order of precedence is:

1. client-defined
2. riak config
3. default (45 seconds)

-Fred

On Sep 2, 2015, at 8:13 AM, Fred Dushin > wrote:


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

If you are getting timeouts, instead of sleeping, you should 
probably query your cluster for the search index, along the lines of 
what is done in one of the riak tests, e.g.,


https://github.com/basho/yokozuna/blob/2.1.1/riak_test/yz_pb.erl#L100

If necessary, you might want to fold over all nodes in your cluster, 
to ensure the index has been propagated to all nodes, and possibly 
use the wait_for patterns used in the tests.


Unfortunately, it looks like the internal timeout used to wait for 
propagation of indexes to all nodes is not configurable -- it 
defaults to 45 seconds:


https://github.com/basho/yokozuna/blob/2.1.1/include/yokozuna.hrl#L134

I hope that helps,

-Fred

On Sep 2, 2015, at 6:27 AM, Hao > wrote:


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 seconds(definitely 
over 5s) before I can set the index on a bucket.


I am using riakc_pb_socket client. At first I thought something 
wrong with my function to "create" and "set" the index but then 
when I split the process, it's fine. So seems it's the interval in 
between that matters.


I need to know how long is the maximum because I need to restore a 
lot of buckets and set index on them via a script. I don't care how 
long it takes but I don't want it to miss any index not being set 
on the bucket.


The exact error on the console when I set the index on a bucket is

<<"Invalid bucket properties: [{search_index,\n 
<<\"application_test_player_idx does not exist\">>}]">>





Thanks,



--
Hao



___
riak-users mailing list
riak-users@lists.basho.com 
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com




___
riak-users mailing list
riak-users@lists.basho.com 
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


*1* attachments

signature.asc(1K)
download


preview






--
Hao

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: What's the maximum seconds to set index on bucket after creating the index

[Fred Dushin]

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 


This means you can set the timeout in the PB client, as in

riakc_pb_socket:create_search_index(Pid, Index, Schema, [{timeout, Timeout}, 
...])

where timeout is in milliseconds (or the atom 'infinity').

cf. http://basho.github.io/riak-erlang-client/ 


The order of precedence is:

1. client-defined
2. riak config
3. default (45 seconds)

-Fred

> On Sep 2, 2015, at 8:13 AM, Fred Dushin  wrote:
> 
> 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 
> 
> 
> If you are getting timeouts, instead of sleeping, you should probably query 
> your cluster for the search index, along the lines of what is done in one of 
> the riak tests, e.g.,
> 
> https://github.com/basho/yokozuna/blob/2.1.1/riak_test/yz_pb.erl#L100 
> 
> 
> If necessary, you might want to fold over all nodes in your cluster, to 
> ensure the index has been propagated to all nodes, and possibly use the 
> wait_for patterns used in the tests.
> 
> Unfortunately, it looks like the internal timeout used to wait for 
> propagation of indexes to all nodes is not configurable -- it defaults to 45 
> seconds:
> 
> https://github.com/basho/yokozuna/blob/2.1.1/include/yokozuna.hrl#L134 
> 
> 
> I hope that helps,
> 
> -Fred
> 
>> On Sep 2, 2015, at 6:27 AM, Hao > 
>> wrote:
>> 
>> 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 seconds(definitely over 5s) before I can 
>> set the index on a bucket.
>> 
>> I am using riakc_pb_socket client. At first I thought something wrong with 
>> my function to "create" and "set" the index but then when I split the 
>> process, it's fine. So seems it's the interval in between that matters.
>> 
>> I need to know how long is the maximum because I need to restore a lot of 
>> buckets and set index on them via a script. I don't care how long it takes 
>> but I don't want it to miss any index not being set on the bucket.
>> 
>> The exact error on the console when I set the index on a bucket is
>> 
>> <<"Invalid bucket properties: [{search_index,\n 
>> <<\"application_test_player_idx does not exist\">>}]">>
>> 
>> 
>> 
>> 
>> Thanks,
>> 
>> 
>> 
>> -- 
>> Hao
>> 
>> 
>> 
>> ___
>> riak-users mailing list
>> riak-users@lists.basho.com 
>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
> 

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: What's the maximum seconds to set index on bucket after creating the index

[Alex Moore]

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 gets set in the server here:
> 
> https://github.com/basho/yokozuna/blob/2.1.1/src/yz_pb_admin.erl#L114 
> 
> 
> This means you can set the timeout in the PB client, as in
> 
> riakc_pb_socket:create_search_index(Pid, Index, Schema, [{timeout, Timeout}, 
> ...])
> 
> where timeout is in milliseconds (or the atom 'infinity').
> 
> cf. http://basho.github.io/riak-erlang-client/ 
> 
> 
> The order of precedence is:
> 
> 1. client-defined
> 2. riak config
> 3. default (45 seconds)
> 
> -Fred
> 
>> On Sep 2, 2015, at 8:13 AM, Fred Dushin > > wrote:
>> 
>> 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 
>> 
>> 
>> If you are getting timeouts, instead of sleeping, you should probably query 
>> your cluster for the search index, along the lines of what is done in one of 
>> the riak tests, e.g.,
>> 
>> https://github.com/basho/yokozuna/blob/2.1.1/riak_test/yz_pb.erl#L100 
>> 
>> 
>> If necessary, you might want to fold over all nodes in your cluster, to 
>> ensure the index has been propagated to all nodes, and possibly use the 
>> wait_for patterns used in the tests.
>> 
>> Unfortunately, it looks like the internal timeout used to wait for 
>> propagation of indexes to all nodes is not configurable -- it defaults to 45 
>> seconds:
>> 
>> https://github.com/basho/yokozuna/blob/2.1.1/include/yokozuna.hrl#L134 
>> 
>> 
>> I hope that helps,
>> 
>> -Fred
>> 
>>> On Sep 2, 2015, at 6:27 AM, Hao > 
>>> wrote:
>>> 
>>> 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 seconds(definitely over 5s) before I can 
>>> set the index on a bucket.
>>> 
>>> I am using riakc_pb_socket client. At first I thought something wrong with 
>>> my function to "create" and "set" the index but then when I split the 
>>> process, it's fine. So seems it's the interval in between that matters.
>>> 
>>> I need to know how long is the maximum because I need to restore a lot of 
>>> buckets and set index on them via a script. I don't care how long it takes 
>>> but I don't want it to miss any index not being set on the bucket.
>>> 
>>> The exact error on the console when I set the index on a bucket is
>>> 
>>> <<"Invalid bucket properties: [{search_index,\n 
>>> <<\"application_test_player_idx does not exist\">>}]">>
>>> 
>>> 
>>> 
>>> 
>>> Thanks,
>>> 
>>> 
>>> 
>>> --
>>> Hao
>>> 
>>> 
>>> 
>>> ___
>>> riak-users mailing list
>>> riak-users@lists.basho.com 
>>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com 
>>> 
>> 
> 
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: Riak Recap - August 31, 2015

[Christopher Meiklejohn]

On Tue, Sep 1, 2015 at 11:52 AM, Matthew Brender  wrote:
> Hey Christopher,
>
> You're running into the fact that this project is an experimental
> demo. Please continue down the right steps by using issues on the
> repo, as you've done with #60 [0]. It may help to know the Vagrantfile
> in the project spins up without issue [1].
>
> [0] https://github.com/basho-labs/riak-mesos/issues/60
> [1] 
> https://github.com/basho-labs/riak-mesos/blob/master/build/ubuntu/Vagrantfile

Hi Matthew,

The link you provided to the Vagrant file returns a 404.

Thanks,
- Christopher

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: Riak Recap - August 31, 2015

[Drew Kerrigan]

Hi Christopher, the Vagrantfile was moved to a separate repo:
https://github.com/basho-labs/vagrant-riak-mesos

That being said, this project is a moving target, and you can expect
changes over the next few days. I intend to upload the precompiled
artifacts this week to enable builds to happen on other platforms (such as
Mac OSX).

Thanks,
Drew

On Wed, Sep 2, 2015 at 2:09 PM Christopher Meiklejohn <
christopher.meiklej...@gmail.com> wrote:

> On Tue, Sep 1, 2015 at 11:52 AM, Matthew Brender 
> wrote:
> > Hey Christopher,
> >
> > You're running into the fact that this project is an experimental
> > demo. Please continue down the right steps by using issues on the
> > repo, as you've done with #60 [0]. It may help to know the Vagrantfile
> > in the project spins up without issue [1].
> >
> > [0] https://github.com/basho-labs/riak-mesos/issues/60
> > [1]
> https://github.com/basho-labs/riak-mesos/blob/master/build/ubuntu/Vagrantfile
>
> Hi Matthew,
>
> The link you provided to the Vagrant file returns a 404.
>
> Thanks,
> - Christopher
>
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

What's the maximum seconds to set index on bucket after creating the index

[Hao]

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 seconds(definitely over 5s) before 
I can set the index on a bucket.


I am using riakc_pb_socket client. At first I thought something wrong 
with my function to "create" and "set" the index but then when I split 
the process, it's fine. So seems it's the interval in between that matters.


I need to know how long is the maximum because I need to restore a lot 
of buckets and set index on them via a script. I don't care how long it 
takes but I don't want it to miss any index not being set on the bucket.


The exact error on the console when I set the index on a bucket is

<<"Invalid bucket properties: [{search_index,\n 
<<\"application_test_player_idx does not exist\">>}]">>





Thanks,



--
Hao



___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: What's the maximum seconds to set index on bucket after creating the index

[Fred Dushin]

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 


If you are getting timeouts, instead of sleeping, you should probably query 
your cluster for the search index, along the lines of what is done in one of 
the riak tests, e.g.,

https://github.com/basho/yokozuna/blob/2.1.1/riak_test/yz_pb.erl#L100 


If necessary, you might want to fold over all nodes in your cluster, to ensure 
the index has been propagated to all nodes, and possibly use the wait_for 
patterns used in the tests.

Unfortunately, it looks like the internal timeout used to wait for propagation 
of indexes to all nodes is not configurable -- it defaults to 45 seconds:

https://github.com/basho/yokozuna/blob/2.1.1/include/yokozuna.hrl#L134

I hope that helps,

-Fred

> On Sep 2, 2015, at 6:27 AM, Hao  wrote:
> 
> 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 seconds(definitely over 5s) before I can set 
> the index on a bucket.
> 
> I am using riakc_pb_socket client. At first I thought something wrong with my 
> function to "create" and "set" the index but then when I split the process, 
> it's fine. So seems it's the interval in between that matters.
> 
> I need to know how long is the maximum because I need to restore a lot of 
> buckets and set index on them via a script. I don't care how long it takes 
> but I don't want it to miss any index not being set on the bucket.
> 
> The exact error on the console when I set the index on a bucket is
> 
> <<"Invalid bucket properties: [{search_index,\n 
> <<\"application_test_player_idx does not exist\">>}]">>
> 
> 
> 
> 
> Thanks,
> 
> 
> 
> -- 
> Hao
> 
> 
> 
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com