That did it. Thanks! As a side note for anyone else who might run into this problem, I did have to make sure this change was made on all nodes and then restart before the problem went away. Not unexpected, but worth noting.
On Mon, Dec 17, 2012 at 12:51 PM, Sean Cribbs <[email protected]> wrote: > Michael, > > Make sure the mapred_name and stats_urlpath values are strings, not atoms. > e.g.: > > {mapred_name, "mapred"}, > {stats_urlpath, "stats"} > > On Mon, Dec 17, 2012 at 2:48 PM, Michael Johnson <[email protected]>wrote: > >> For some reason, I am not able to get the riak stats via the http >> interface. Here is what I get: >> >> -bash-4.1$ curl -k https://127.0.0.1:8091/stats/ -E 'text/plain' -D - >> HTTP/1.1 400 Bad Request >> Server: MochiWeb/1.1 WebMachine/1.9.0 (someone had painted it blue) >> Date: Mon, 17 Dec 2012 20:35:25 GMT >> Content-Type: text/plain >> Content-Length: 150 >> >> This resource accepts POSTs with bodies containing JSON of the form: >> { >> "inputs":[...list of inputs...], >> "query":[...list of map/reduce phases...] >> } >> >> And here is the riak_kv section of my app.config: >> >> {riak_kv, [ >> {hook_js_vm_count, 2}, >> {http_url_encoding, on}, >> {js_max_vm_mem, 8}, >> {js_source_dir, "/tmp/js_source"}, >> {js_thread_stack, 16}, >> {legacy_keylisting, false}, >> {legacy_stats, true}, >> {listkeys_backpressure, true}, >> {map_cache_size, 10000}, >> {map_js_vm_count, 8}, >> {mapper_batch_size, 5}, >> {mapred_2i_pipe, true}, >> {mapred_name, mapred}, >> {mapred_queue_dir, "/var/lib/riak/mr_queue"}, >> {mapred_system, pipe}, >> {raw_name, "riak"}, >> {reduce_js_vm_count, 6}, >> {riak_kv_stat, true}, >> {stats_urlpath, stats}, >> {storage_backend, riak_kv_eleveldb_backend}, >> {vnode_vclocks, true} >> ]}, >> >> I have tried single and double quoting 'stats' in the stats_urlpath >> value, and I have tried commenting that out as well as setting legacy_stats >> to false and simply commenting out the legacy_stats declaration. The >> result is always the same. I originally was running riak 1.2.0. Thinking >> this might be and issue that was resolved in riak 1.2.1, I upgraded and >> restarted all the nodes, but continue the get the exact same results. >> >> In all cases I can run 'riak-admin status' and get the data that way. Is >> this a known issue, or am I missing something? I found some bug reports >> that might be related be related, but nothing that I can say for sure. >> >> If someone else can let me know if they have the same problem, that would >> be immensely helpful as it would confirm I an not just missing something. >> I've read over the docs several times and have not been able to find >> anything that indicates I am doing anything wrong, so I am at a bit of a >> loss right now. >> >> Thanks! >> >> _______________________________________________ >> riak-users mailing list >> [email protected] >> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >> >> > > > -- > Sean Cribbs <[email protected]> > Software Engineer > Basho Technologies, Inc. > http://basho.com/ > >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
