2015-03-13 7:08 GMT+05:00 Kota Uenishi :
> Which version of Riak CS are you using? If it's 1.5.3 or later,
> "storage_calc_timeout" in "riak_cs" section should be used instead of
> "mapred_timeout" because it won't work [1]. This is undocumented, but
> we should've documented this.
Already used af
2015-03-13 6:45 GMT+05:00 Kazuhiro Suzuki :
> You can change the timeout for a MapReduce job the storage calculation
> uses. Could you try to add riakc section which contains mapred_timeout
> into Riak CS's app.config like this ? :
> {riakc, [
> {mapred_timeout, 180}], %% ms
Which version of Riak CS are you using? If it's 1.5.3 or later,
"storage_calc_timeout" in "riak_cs" section should be used instead of
"mapred_timeout" because it won't work [1]. This is undocumented, but
we should've documented this.
Moreover, in CS 1.5.3 or later "mapred_timeout" or "timeout" in
Hi Stanislav,
You can change the timeout for a MapReduce job the storage calculation
uses. Could you try to add riakc section which contains mapred_timeout
into Riak CS's app.config like this ? :
```
[
%% riakc section
{riakc, [
{mapred_timeout, 180}], %% msec
},
[
%%
Our riak-cs cluster can't calculate storage statistic for some buckets
and all calculation takes too long:
riak-cs/console.log:
2015-03-11 01:25:56.791 [error]
<0.485.0>@riak_cs_storage:maybe_sum_bucket:75 failed to calculate
usage of bucket 'x' of user ''.
Reas
