Object not found after successful PUT on S3 API

Daniel Miller dmiller at dimagi.com
Wed Mar 8 14:38:40 EST 2017


Thanks for taking the time to look into this Luke. I should have asked more
questions when I setup the configuration for leveldb backend since there is
no clear documentation for how configure CS with leveldb only.

In your current configuration, you are not using the expected prefix for
> the block data. My guess is that on very rare occasions your data happens
> to overwrite the manifest for a file. You may also have corrupted files at
> this point without noticing it at all.
>

> *IMPORTANT:* you can't switch from your current configuration to this new
> one without re-saving all of your data.
>

Do you have a recommendation to get my data to a new state? Like will it
work if I create new nodes and replace each existing node with a new node
configured correctly? Or do I need a more involved migration process?


On Tue, Mar 7, 2017 at 3:58 PM, Luke Bakken <lbakken at basho.com> wrote:

> Hi Daniel,
>
> Thanks for providing all of that information.
>
> You are missing important configuration for riak_kv that can only be
> provided in an /etc/riak/advanced.config file. Please see the following
> document, especially the section to which I link here:
>
> http://docs.basho.com/riak/cs/2.1.1/cookbooks/configuration/
> riak-for-cs/#setting-up-the-proper-riak-backend
>
> [
>     {riak_kv, [
>         *% NOTE: double-check this path for your environment:*
>         {add_paths, ["/usr/lib/riak-cs/lib/riak_cs-2.1.1/ebin"]},
>         {storage_backend, riak_cs_kv_multi_backend},
>         {multi_backend_prefix_list, [{<<"0b:">>, be_blocks}]},
>         {multi_backend_default, be_default},
>         {multi_backend, [
>             {be_default, riak_kv_eleveldb_backend, [
>                 {data_root, "/opt/data/ecryptfs/riak"}
>             ]},
>             {be_blocks, riak_kv_eleveldb_backend, [
>                 {data_root, "/opt/data/ecryptfs/riak_blocks"}
>             ]}
>         ]}
>     ]}
> ].
>
> Your configuration will look like the above. The contents of this file are
> merged with the contents of /etc/riak/riak.conf to produce the
> configuration that Riak uses.
>
> Notice that I chose riak_kv_eleveldb_backend twice because of the
> discussion you had previously about RAM usage and bitcask (
> http://lists.basho.com/pipermail/riak-users_lists.basho.
> com/2016-November/018801.html)
>
> In your current configuration, you are not using the expected prefix for
> the block data. My guess is that on very rare occasions your data happens
> to overwrite the manifest for a file. You may also have corrupted files at
> this point without noticing it at all.
>
> *IMPORTANT:* you can't switch from your current configuration to this new
> one without re-saving all of your data.
>
> --
> Luke Bakken
> Engineer
> lbakken at basho.com
>
> --
> Luke Bakken
> Engineer
> lbakken at basho.com
>
> On Tue, Mar 7, 2017 at 6:47 AM, Daniel Miller <dmiller at dimagi.com> wrote:
>
>> Responses inline.
>>
>> On Mon, Mar 6, 2017 at 3:04 PM, Luke Bakken <lbakken at basho.com> wrote:
>>
>>> Hi Daniel,
>>>
>>> Two questions:
>>>
>>> * Do you happen to have an /etc/riak/app.config file present?
>>>
>>
>> No.
>>
>> Not sure if relevant, but I did notice that /etc/riak-cs/advanced.config
>> does exist, which contradicts with what I said earlier. This is surprising
>> to me because I did not create this file. Maybe it was created by the riak
>> installer? Anyway, the content is:
>>
>> $ cat /etc/riak-cs/advanced.config
>> [
>>  {riak_cs,
>>   [
>>   ]}
>> ].
>>
>>
>>>
>>> * On one of your Riak nodes, could you please execute the following
>>> commands:
>>>
>>> riak attach
>>> rp(application:get_all_env(riak_kv)).
>>>
>>> Copy the output of the previous command and attach as a separate file
>>> to your response. Please note that the period is significant. Use
>>> CTRL-C CTRL-C to exit the "riak attach" session.
>>>
>>
>> Attached.
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20170308/5d781c2a/attachment-0002.html>


More information about the riak-users mailing list