Re: RiakCS large file uploads fail with 403/AccessDenied and 400/InvalidDigest
Congrats :) Just my two cents, > tcpdump 'host 172.16.3.21' -s 65535 -i eth0 > /opt/dump.pcap tcpdump's option "-w file.pcap" is helpful because dump contains not only header information but raw packet data. How about "403 - AccessDenied" case? Is it also solved by version up or still an issue? Thanks, Shino ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Storage statistic calculation errors
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 ''.
Reason: {error,{timeout,[]}}
2015-03-11 01:37:36.212 [info]
<0.485.0>@riak_cs_storage_d:calculating:150 Finished storage
calculation in 5794 seconds.
This bucket contains over 500 files. It could be the cause of this
error, but several days ago, after cluster restart, all storage
statistic was calculated without errors:
2015-02-27 01:23:59.777 [info]
<0.483.0>@riak_cs_storage_d:calculating:150 Finished storage
calculation in 1138 seconds.
Please advise anything to fix it
Our node config files and last logs can be found at http://ovh.to/MuavQVP
12 nodes in cluster, node hardware configuration:
CPU: 6 cores of Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz
RAM: 60G
--
Stanislav
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: RiakCS large file uploads fail with 403/AccessDenied and 400/InvalidDigest
I was testing some more.. and now the 400 issue (files from 1024-8191K) is solved .. the 403 issue indeed is not yet solved (files > 8192K) so indeed still an issue :-( here a pcap of the 403 issue (with -w option this time :-) http://we.tl/AFhslBBhGo On Wed, Mar 11, 2015 at 8:02 AM, Shunichi Shinohara wrote: > Congrats :) > > Just my two cents, > > > tcpdump 'host 172.16.3.21' -s 65535 -i eth0 > /opt/dump.pcap > > tcpdump's option "-w file.pcap" is helpful because dump contains > not only header information but raw packet data. > > How about "403 - AccessDenied" case? Is it also solved by version > up or still an issue? > > Thanks, > Shino > ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
putObjectPolicy fails due to wrong Content-Type
Hi, Hi, I'm trying to use node-aws-sdk to set bucket policies but the SDK sends the request with the wrong Content-Type, "application/octet-stream". I'm not sure if there is something wrong on my side or if AWS S3 also supports this since it is its SDK. To find the problem I was digging in the SDK code because the server response is just a 500 Internal Server Error. It could be nice to return at least something like "Unaccepted Content-Type in request". Regards, Patrick Marques ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
