Memory Backend TTL doesn't work

2013-10-14 Thread 성동찬_Chan
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, 8192},
  {ttl, 1}
   ]},
...
]},

-

TTL isn't supported on riak_kv_memory_backend?
I changed riak_kv_memory_backend to riak_kv_bitcask_backend, that's fine.

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


Re: Memory Backend TTL doesn't work

2013-10-14 Thread Alex Moore
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, [
{max_memory, 8192}, %% 8GB
{ttl, 1}
]}
]},
Also, for future reference, the max_memory field is in MB per vnode, so your 
current setting is 8GB per vnode.  Unless you have a ridiculous amount of RAM, 
you might want to reduce that setting a bit :)

Thanks, 

Alex

-- 
Alex Moore
Sent with Airmail

On October 14, 2013 at 7:32:03 AM, 성동찬_Chan (c...@kakao.com) wrote:

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, 8192}, 
{ttl, 1} 
]}, 
... 
]}, 

- 

TTL isn't supported on riak_kv_memory_backend? 
I changed riak_kv_memory_backend to riak_kv_bitcask_backend, that's fine. 

Thanks. 
Chan. 
___ 
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: Connection attempt from disallowed node

2013-10-14 Thread Luke Bakken
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:get_cookie().

--
Luke Bakken
CSE
lbak...@basho.com


On Fri, Oct 11, 2013 at 7:42 PM, raghwani sohil sohil4...@gmail.com wrote:

 Hi Luke ,
 It's same on all nodes. I didn't change *-cookie *parameter in vm.args
 file ,

 Thanks,
 Sohil


 On Fri, Oct 11, 2013 at 8:44 PM, Luke Bakken lbak...@basho.com wrote:

 Hello Sohil,

 Could you please check the `vm.args' file on your existing node and your
 new node to ensure that the `-cookie' parameter is the same on each?

 --
 Luke Bakken
 CSE
 lbak...@basho.com


 On Fri, Oct 11, 2013 at 7:02 AM, raghwani sohil sohil4...@gmail.comwrote:

 Hi ,

 I have three node riak(0.14.2) cluster on production(all nodes running
 on RHEL OS).

 I have one CentOS system on which one riak node(0.14.2) is setup using
 RHEL binary.

 When I m trying add CentOS riak node to existing cluster then I am
 getting

 error *Node r...@a.b.c.xxx is not reachable!  *and in sasl-error.log
 file it's showing

 *Connection attempt from disallowed node 'riak@**a.d.c.YYY**'*
 *
 *
 can any one help on the same?
 *
 *
 thanks,
 Sohil


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


[ANN] Riak CS 1.4.2 (and reorganized docs)

2013-10-14 Thread John Daily
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 deleted.

We've also significantly reorganized the Riak CS content on docs.basho.com to 
differentiate operational from development concerns, mirroring recent changes 
to Riak documentation.

Release notes: 
http://docs.basho.com/riakcs/latest/cookbooks/Riak-CS-Release-Notes/
Downloads: http://docs.basho.com/riakcs/latest/riakcs-downloads/

Thanks.

-John Daily
Technical Evangelist, Basho



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


Re: distribution of data among riak cluster physical nodes

2013-10-14 Thread John Daily
Responses inline.

On Oct 11, 2013, at 7:10 PM, kzhang kzh...@wayfair.com 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, necessarily, but how many need to respond before an answer is given 
to the client.

 pr - how many primary replicas need to be online when doing the read
 (default is defined by the bucket)

Again, how many need to respond.

 basic_quorum - whether to return early in some failure cases (eg. when r=1
 and you get 2 errors and a success basic_quorum=true would return an error)
 (default is defined by the bucket)

 notfound_ok - whether to treat notfounds as successful reads for the
 purposes of R (default is defined by the bucket)
 

Correct.


The various notfound_ok/basic_quorum/R combinations are captured in a table 
here: http://basho.com/riaks-config-behaviors-part-3/

 If I have:
 
 r = 1
 notfound_ok=true
 basic_quorum = true
 
 does the client get notfound after 1 reply (since notfound_ok=true and r =
 1) or after 2 replies (since basic_quorum = true)?
 

Client will get notfound after 1 reply.


 Or if I have:
 
 r = 1
 notfound_ok=false
 basic_quorum = true
 
 the client gets notfound if the first two replies are notfound? if the first
 reply is found, the client gets found? if the first reply is notfound, the
 second is found, does the client get found, or have to wait for the third
 vnode (in my environment, N=3) to reply?

notfound will be returned only if both servers return notfound, and the request 
will not wait for a 3rd server in any sequence of events.

 
 In the next setup:
 
 r = 1
 notfound_ok=false
 basic_quorum = false
 
 only when all three replies are notfound, then the client gets notfound?
 otherwise, it is found.

Correct.

 
 The last one:
 
 r = 1
 notfound_ok=true
 basic_quorum = false
 
 which is the default. if the first reply is found, then client gets found.
 if the first reply is notfound, clients gets notfound. 

Correct.

-John


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


Yokozuna: Riak Python client PB error with Solr stored boolean fields

2013-10-14 Thread Dave Martorana
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.

In my schema, I have:

field name=banned type=boolean indexed=true stored=true /

With that (or any named field of type boolean that is set to
stored=true) I receive the following stack trace:

http://pastebin.com/ejCixPEZ

In the error.log file on the server, I see the following repeated:

2013-10-15 01:21:17.480 [error] 0.2872.0@yz_pb_search:maybe_process:95
function_clause
[{yz_pb_search,to_binary,[false],[{file,src/yz_pb_search.erl},{line,154}]},{yz_pb_search,encode_field,2,[{file,src/yz_pb_search.erl},{line,152}]},{lists,foldl,3,[{file,lists.erl},{line,1197}]},{yz_pb_search,encode_doc,1,[{file,src/yz_pb_search.erl},{line,144}]},{yz_pb_search,'-maybe_process/3-lc$^0/1-0-',1,[{file,src/yz_pb_search.erl},{line,76}]},{yz_pb_search,maybe_process,3,[{file,src/yz_pb_search.erl},{line,76}]},{riak_api_pb_server,process_message,4,[{file,src/riak_api_pb_server.erl},{line,383}]},{riak_api_pb_server,connected,2,[{file,src/riak_api_pb_server.erl},{line,221}]}]

Does anyone have any insight? I'm not a Solr expert, so perhaps storing
boolean fields for retrieval is not a good idea? I know if I index but
don't store, I can still successfully search against a boolean value.

Thanks!

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


Re: Memory Backend TTL doesn't work

2013-10-14 Thread 성동찬_Chan
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 amo...@basho.commailto:amo...@basho.com 
작성:

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, [
{max_memory, 8192}, %% 8GB
{ttl, 1}
]}
]},


Also, for future reference, the max_memory field is in MB per vnode, so your 
current setting is 8GB per vnode.  Unless you have a ridiculous amount of RAM, 
you might want to reduce that setting a bit :)

Thanks,

Alex

--
Alex Moore
Sent with Airmailhttp://airmailapp.info/tracking


On October 14, 2013 at 7:32:03 AM, 성동찬_Chan 
(c...@kakao.commailto://c...@kakao.com) wrote:

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, 8192},
{ttl, 1}
]},
...
]},

-

TTL isn't supported on riak_kv_memory_backend?
I changed riak_kv_memory_backend to riak_kv_bitcask_backend, that's fine.

Thanks.
Chan.
___
riak-users mailing list
riak-users@lists.basho.commailto: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: Unit testing, Riak buckets

2013-10-14 Thread Daniil Churikov
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
misconfiguration of this environment or if the node crashes b/c of disk
fullness how well your cluster tolerate this fault.



--
View this message in context: 
http://riak-users.197444.n3.nabble.com/Unit-testing-Riak-buckets-tp4029451p4029464.html
Sent from the Riak Users mailing list archive at Nabble.com.

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