Here are some more details about the cluster.
{ring_creation_size, 1024},
{default_bucket_props, [
{n_val, 2},
{r, 1},
{w, 1},
{allow_mult, false},
{last_write_wins, false},
{precommit, []},
{postcommit, []},
{chash_keyfun, {riak_core_util, chash_std_keyfun}},
{linkfun, {modfun, riak_kv_wm_link_walker, mapreduce_linkfun}}
]},
{storage_backend, riak_kv_multi_backend},
{multi_backend_default, <<"store">>},
{multi_backend, [
{<<"store">>, riak_kv_bitcask_backend, [
{data_root, "/var/lib/riak/bitcask/store"}
]},
{<<"cache">>, riak_kv_bitcask_backend, [
{data_root, "/var/lib/riak/bitcask/cache"},
{expiry_secs, 21600}
]}
]},
On using Riaknostic I am seeing these errors.
[warning] The following preflists do not satisfy the n_val:
[[{973382926425464638881751031164555683013033197568,'riak@178.238.237.241'},.....
a big list similar to this...]
Please help. We are stuck.
Praveen
On Mon, Sep 17, 2012 at 4:18 AM, Praveen Baratam
<praveen.bara...@gmail.com>wrote:
> Hello Everybody,
>
> We are currently alpha testing out our Webapp which uses Riak for storing
> binary files (< 2 MB) with n_val as 2. We currently have 3 nodes in the
> cluster and all files are stored in the same bucket. We are using Bitcask
> engine.
>
> Sometimes we see 404 error cropping up when accessing these keys. This
> happens only once in a day or so and all existing keys are accessible most
> of the time. We are only trying to access the keys that we have put in
> Riak so there is no doubt of their existence.
>
> Can a network split cause such an error? Is there anything we can do to
> avoid such corner cases.
>
> Thank you
>
> Praveen
>
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
