It depends on tests, but our test do allow us not to clean riak after tests
at all. is it so bad? Just pick random bucket name and leave data there.
Test environment could be nuked any time. Also as time goes more data
stashes in riak and you could reveal some interesting facts: like
misconfigurati
Thank you!! I've got it!! :)
Then, if I started server with ring size 32, I need to change max_memory to
256(8192/32). Is it right?
Chan.
2013. 10. 14., 오후 9:35, Alex Moore mailto:amo...@basho.com>>
작성:
Hi Chan,
Instead of:
{storage_backend, riak_kv_memory_backend},
{memory_backend, [
{max_mem
I studied the problem I was having with using the Python client's
.fulltext_search(...) method and got it down to this - it seems that I get
an error when searching against Solr using the Python client's
.fulltext_search(...) method (using protocol buffers) whenever I have a *
stored* boolean field
Responses inline.
On Oct 11, 2013, at 7:10 PM, kzhang wrote:
> I read the documentation again
> (http://docs.basho.com/riak/latest/dev/references/http/fetch-object/).
>
> r - (read quorum) how many replicas need to agree when retrieving the object
> (default is defined by the bucket)
Not agree
Hi Siddhu,
I've opened an issue to track this feature request:
https://github.com/basho/riak_cs_control/issues/41
Thank you!
- Chris
--
Christopher Meiklejohn
Software Engineer
Basho Technologies, Inc.
On Monday, October 14, 2013 at 12:01 PM, Dmitri Zagidulin wrote:
> On Thu, Oct 10, 20
We're pleased to announce a new minor release of Riak CS, including both bug
fixes and minor enhancements.
Highlights include addressing a stats bug, fixing downloads of objects written
via Riak CS prior to 1.3, and improvements to garbage collection to minimize
cluster impact when objects are
On Thu, Oct 10, 2013 at 5:21 AM, Siddhu Warrier (siwarrie) <
siwar...@cisco.com> wrote:
> Btw, a related question: can I protect Riak CS Control from
> unauthenticated access, by requiring users to enter the admin credentials
> before they are allowed to view or edit information?
>
Not at the mom
Sohil -
That's surprising since that's the standard reason for that error. I would
recommend checking your vm.args files using "diff" or a hex editor to
ensure they are identical.
You can then use "riak attach" to attach to your nodes and retrieve the
cookie value using this statement:
erlang:ge
Hi Chan,
Instead of:
{storage_backend, riak_kv_memory_backend},
{memory_backend, [
{max_memory, 8192},
{ttl, 1}
]},
Try:
{multi_backend_default, <<"expiring_memory_backend">>},
{multi_backend, [
{<<"expiring_memory_backend">>, riak_kv_memory_backend, [
Hi~!
I'm checking riak to use as a cache like memcached.
But I found some strange situation.
I set "ttl" like this to expire data, but failed.
-
{riak_kv, [
...
{storage_backend, riak_kv_memory_backend},
{memory_backend, [
{max_memory, 819
10 matches
Mail list logo
