Thank you. I am sorry but I was unfamiliar with 'riak attach' or 'riak
console' I used 'riak attach' and issued the command. But, I still need some
help interpreting the error:
2013-03-12 21:37:06.775 [debug]
<0.3338.0>@riak_kv_put_fsm:decode_precommit:707 Problem invoking pre-commit
hook riak_search_kv_hook:precommit -> error:badarg
[{ets,lookup,[schema_table,<<"buyseasons-orders">>],[]},{riak_search_config,
get_schema,1,[{file,"src/riak_search_config.erl"},{line,69}]},{riak_search_k
v_hook,make_indexed_doc,4,[{file,"src/riak_search_kv_hook.erl"},{line,206}]}
,{riak_search_kv_hook,index_object,2,[{file,"src/riak_search_kv_hook.erl"},{
line,182}]},{riak_search_kv_hook,precommit,1,[{file,"src/riak_search_kv_hook
.erl"},{line,103}]},{riak_kv_put_fsm,invoke_hook,4,[{file,"src/riak_kv_put_f
sm.erl"},{line,675}]},{riak_kv_put_fsm,precommit,2,[{file,"src/riak_kv_put_f
sm.erl"},{line,325}]},{gen_fsm,handle_msg,7,[{file,"gen_fsm.erl"},{line,494}
]}]
-----Original Message-----
From: Andrew Thompson [mailto:[email protected]]
Sent: Tuesday, March 12, 2013 9:14 PM
To: Kevin Burton
Cc: 'Jeremiah Peschka'; 'riak-users'
Subject: Re: Error interpretation
Riak does not log crashed pre/post commit hooks by default, this is to avoid
a bad hook or object from denial of servicing the cluster in production.
If you want to debug this, you can use a lager trace at the riak console
like this:
lager:trace_file("/tmp/put_fsm.log", [{module, riak_kv_put_fsm}], debug).
Then do whatever operation is failing and look at the /tmp/put_fsm.log file.
When you want to disable the trace simply do:
lager:clear_all_traces().
Andrew
_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
