Hi Toby, Invalid hint files won't cause Riak to fail requests - there must have been something else happening. Hint files are used by Riak to speed start time when loading a large key set.
You mentioned a "load-balancer pool" - are you using something like HAProxy to load-balance requests to your Riak CS cluster? The "error: disconnected" message is a good clue. If you can provide log files that may point to the cause. -- Luke Bakken CSE lbak...@basho.com On Wed, Sep 18, 2013 at 4:29 PM, Toby Corkindale <toby.corkind...@strategicdata.com.au> wrote: > I found one Riak server was reporting a lot of errors like > [error] <0.808.0> Hintfile > '/var/lib/riak/bitcask/68507889249886074290797726533575766546371837952/3.bitcask.hint' > invalid > > And the Riak CS logs contained a lot of messages about being unable to > retrieve s3 user details because "error: disconnected" > > I think I've blown away the bad hintfiles and have had them repaired from > other replicas now, and I haven't seen any more errors for a little while. > > I'm not sure what caused those to become invalid. > Just a thought, but would be good if Riak could automatically repair them > rather than failing requests. > > Cheer,s > Toby > > On 19/09/13 08:42, Toby Corkindale wrote: >> >> Ah, hold on.. have just discovered that rather than it being deletion >> calls, it seems to just be every X calls of any sort.. sounds like one >> of the servers in the load-balancer pool must be misconfigured somehow, >> but the rest are OK. >> >> On 19/09/13 08:34, Toby Corkindale wrote: >>> >>> I've just upgraded from Riak CS 1.3.1 to 1.4.1 >>> >>> Using s3cmd to test a few things, I've found some odd behaviour. >>> Creating a bucket and putting a file works just fine, eg: >>> >>> s3cmd mb s3://test >>> s3cmd put README s3://test >>> s3cmd get s3://test/README >>> >>> However if I try to delete a file or bucket, it throws an error: >>> >>> s3cmd del s3://test/README >>> ERROR: S3 error: 403 (InvalidAccessKeyId): The AWS Access Key Id you >>> provided does not exist in our records. >>> >>> s3cmd rb s3://test >>> ERROR: S3 error: 403 (InvalidAccessKeyId): The AWS Access Key Id you >>> provided does not exist in our records. >>> >>> >>> Have I messed something up during the upgrade, or is this a bug in 1.4.1? >>> >>> ta >>> Toby >>> >>> _______________________________________________ >>> riak-users mailing list >>> riak-users@lists.basho.com >>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >> >> >> >> _______________________________________________ >> riak-users mailing list >> riak-users@lists.basho.com >> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
