{riak, [
         %% storage_backend specifies the Erlang module defining the storage
mechanism
         %%  that will be used on this node.
         %% {storage_backend, riak_dets_backend},
         {storage_backend, innostore_riak},

         %% Different storage backends can use other configuration
variables.  For
         %%  instance, riak_dets_backend_root determines the directory under
which
         %%  dets files will be placed.
         {riak_dets_backend_root, "/riak/backendroot"},

         %% Default location of ringstate
         {ring_state_dir, "/riak/ringstate"},

         %% riak_web_ip is the IP address that Riak's HTTP interface will
bind to.
         %%  If this is undefined, the HTTP interface will not run.
         {riak_web_ip, "127.0.0.1"},

         %% riak_web_port is the TCP port that Riak's HTTP interface will
bind to.
         {riak_web_port, 8098},

         %% riak_handoff_port is the TCP port that Riak uses for
intra-cluster
         %% data handoff.
         {riak_handoff_port, 8099},

         %% mapred_name is URL used to submit map/reduce requests to Riak.
         {mapred_name, "mapred"},

         %% js_vm_count is the number of Javascript VMs to start per Riak
node.
         %% 8 is a good default for smaller installations. A larger number
like
         %% 12 or 16 is appropriate for installations handling lots of
map/reduce
         %% processing.
         {js_vm_count, 8},

         %% js_source_dir should point to a directory containing Javascript
source
         %% files which will be loaded by Riak when it initializes
Javascript VMs.
         %{js_source_dir, "/tmp/js_source"}


         %% riak_stat enables the use of the "riak-admin status" command to
         %% retrieve information the Riak node for performance and debugging
needs
         {riak_stat, true}
        ]},

         %% SASL config
         {sasl, [
                 {sasl_error_logger, {file, "log/sasl-error.log"}},
                 {errlog_type, error},
                 {error_logger_mf_dir, "log/sasl"},      % Log directory
                 {error_logger_mf_maxbytes, 10485760},   % 10 MB max file
size
                 {error_logger_mf_maxfiles, 5}           % 5 files max
                 ]},

        {innostore, [
            {data_home_dir, "/riak/data"}, %% Where data files go
            {log_group_home_dir, "/riak/logs"}, %% Where log files go,
ideally the logs and data are on separate drives for performance...maybe
later
            {buffer_pool_size, 268435456} %% 256MB in-memory buffer in bytes
        ]}
].


Sorry for the confusion, that is the config file, I hope it helps.

Sincerely,
Tyler

On Tue, Apr 13, 2010 at 1:27 PM, Tyler Smart <[email protected]> wrote:

> Hi all!
>
> I have installed Riak on an Ubuntu 8.04 EC-2 instance and it stores all of
> its' data on an EBS block (10GB). The machine is 32 bit (small).  It will
> accept information in a bucket easily with a curl request like this:
>
> curl -X PUT -H "content-type: text/plain"
> https://127.0.0.1/riak/example/foo --data "I have a document."
>
> If I query the data like this:
>
>  curl -i -k https://127.0.0.1/riak/example/foo
>
> I get back the data, it works perfectly. (It sits behind nginx as a reverse
> proxy that adds SSL).
>
> However, if I perform this query:
>
> https://127.0.0.1/riak/example
>
> it never finishes executing, nor if I try https://127.0.0.1/riak/test
>
> I have attached the conf file, if it will help, and I appreciate any time
> you guys have!
>
> Sincerely,
> Tyler
>
>
> The problem I am having is that I can
>
_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Reply via email to