Luke,
Thank you so much for in-depth instructions for setting up multi-node dev
cluster on the same server. I have confirmed that the precommit hook now
works, with your instructions, as non-root user.
Especially, the instructions on doing dev build for 3 nodes were very
helpful! I will run a dif
Hello everyone -
I have confirmed that precommit hooks are correctly called in a 3-node
environment, running on the same VM. Riak was both started by and is
running as a local user account (no "root" permissions necessary).
Overview of the verification process can be found here:
https://gist.gith
Riak users subscribers -
I would like to add the caveat that this workaround indicates an
environment-specific issue and not (at this point) a bug in Riak. I am
working to get to the root cause (pun intended)
Thanks,
Luke
lbak...@basho.com
On May 17, 2016 10:54 AM, "Sanket Agrawal" wrote:
>
> A
All, the issue is fixed now - the problem is that Riak precommit and
postcommit hooks seem to work only in root user mode. On AWS, switching
from ec2-user to root user fixed the precommit trigger issue.
That does raise the question of whether Riak should really be using root
user account. For examp
Luke, just tested and confirmed that precommit hooks are still not
triggered for normal buckets. Objects get written but precommit hooks don't
trigger. Manually simulating a trigger by executing the function on riak
console works fine.
Since sasl log is not being written despite being turned on, i
Sanket,
I can't speak to the output of cluster-info with regard to the precomit hook.
If you save an object to the "test_kv" bucket, does
rtriggers:pre_all() get called?
I have confirmed that precommit hooks are *NOT* triggered for buckets
where "write_once" is true, and filed the following docs
Shouldn't precommit body show up in cluster-info first before we try to
test it with an object? I just set the precommit hook for test_kv bucket
type which has no custom property set. Curl on props shows precommit, but
cluster-info doesn't (took another dump after 5 minutes of precommit hook
creati
Hi Sanket,
Thanks for providing that information, this is the first time that the
"write_once" bucket type property was mentioned.
If you set the precommit hook on a different bucket type where there
are *no other* custom bucket type properties set, does the precommit
hook run successfully?
--
L
Hi Luke,
I renamed precommit to pre_triggers, and then re-associated the hook to
bucket type instead of bucket as you suggested. Also, started redbug on all
three consoles, and confirmed that it started. Then, I made the call that
should trigger the hooks, but nothing triggered. The module shows u
Hi Sanket -
Could you please try *removing* the precommit hook from the "uuid_log"
bucket and define it on the "test_kv_wo" bucket type instead?
Removal:
curl -4vvv -H 'Content-Type: application/json' -X PUT
localhost:8098/types/test_kv_wo/buckets/uuid_log/props -d
'{"props":{"precommit":[]}}'
C
Sanket -
One other thought. Could you please change the name of your module to
something other than "precommit"? That is the atom being used for
precommit hooks and maybe that's causing an issue.
--
Luke Bakken
Engineer
lbak...@basho.com
On Fri, May 13, 2016 at 7:05 AM, Luke Bakken wrote:
> Hi
Luke, yep, that is right. I did that smoke test when debugging precommit
issue. Each of the three nodes has access to compiled beam files it needs
(in a shared folder that each node is configured for, via add_paths in
advanced config, to make sure they have same beam files). I verified it
manually
Hi Sanket,
Another thing I'd like to confirm - you have installed your compiled
.beam file on all Riak nodes and can confirm via "m(precommit)" that
the code is available?
--
Luke Bakken
Engineer
lbak...@basho.com
On Wed, May 11, 2016 at 12:12 PM, Sanket Agrawal
wrote:
> Yep, I can always load
Yep, I can always load the module in question in riak console fine. I did
all my testing in riak console, before trying to turn on precommit hook.
Here is the output for loading the module that you asked for - if sasl
logging is not working, perhaps something is broken about commit hooks then:
$ ~
Huh - I get a huge amount of logging when I turn on sasl using
advanced.config - specifically, I have:
{sasl,[{sasl_error_logger,{file, "/tmp/sasl-1.log"}}]}
in my advanced.config, and for just a startup/shutdown cycle I get a 191555
byte file.
Just to confirm that you can, in fact, load the mod
Thanks, Doug. I have enabled sasl logging now through advanced.config
though it doesn't seem to be creating any log yet.
If this might help you folks with debugging precommit issue, what I have
observed is that erl-reload command doesn't load the precommit modules for
any of the three nodes (thoug
As to the SASL logging, unfortunately it's not "on by default" and the
setting in riak.conf, as you found out, doesn't work correctly. However,
you can enable SASL via adding a setting to your advanced.config:
{sasl,[{sasl_error_logger,tty}]} %% Enable TTY output for the SASL app
{sasl,[{sasl_erro
Hi Luke,
This is on a three-node cluster on Amazon EC2 Linux. I built it from 2.1.4
KV source using erlang interpreter that Basho provided (REPL header: Erlang
R16B02_basho8 (erts-5.10.3) [source] [64-bit] [async-threads:10] [hipe]
[kernel-poll:false]).
Also, riak-admin output below to confirm it
Hi Sanket -
I'd like to confirm some details. Is this a one-node cluster? Did you
install an official package or build from source?
Thanks -
--
Luke Bakken
Engineer
lbak...@basho.com
On Tue, May 10, 2016 at 6:49 PM, Sanket Agrawal
wrote:
> One more thing - I set up the hooks by bucket, not buc
One more thing - I set up the hooks by bucket, not bucket type. The
documentation for 2.1.4 says that hooks are defined on the bucket level.
Here is how I set up precommit hook (derived from "Riak Handbook" p95):
curl -X PUT localhost:8098/types/test_kv_wo/buckets/uuid_log/props -H
'Content-Type:
I just set up a precommit hook function in dev environment (KV 2.1.4) which
doesn't seem to be triggering off at all. The object is being stored in the
bucket, but the precommit logic is not kicking off. I checked couple of
things as listed below but came up with no error - so, it is a
head-scratch
21 matches
Mail list logo
