error parsing riak.conf with multi_backend and bitcask.expiry set

[pma]

Adding the following to riak.conf will cause an error:

multi_backend.bitcask_expiry_1d.bitcask.io_mode = erlang
multi_backend.bitcask_expiry_1d.bitcask.data_root = $(platform_data_dir)/bitcask_expiry_1d
multi_backend.bitcask_expiry_1d.bitcask.expiry = 1d
multi_backend.bitcask_expiry_1d.bitcask.expiry.grace_time = 1

The problematic line is the one adding expiry. If commented 'riak config generate -l debug' will run ok. But when included it will fail with:

04:10:58.186 [error] Error generating configuration in phase apply_translations
04:10:58.186 [error] Error running translation for riak_kv.multi_backend, [error, badarg].

System used:

Linux node1 3.15.4-x86_64-linode45 #1 SMP Mon Jul 7 08:42:36 EDT 2014 x86_64 GNU/Linux
Riak 2.0.0RC1 (.deb for Debian Wheezy)

[seancribbs]

Our bitcask experts tell me that bitcask.expiry.grace_time is only settable globally. What happens if you just comment the final line?

[pma]

Commenting the grace_time line produces the same error:

multi_backend.bitcask_expiry_1d.bitcask.io_mode = erlang
multi_backend.bitcask_expiry_1d.bitcask.data_root = $(platform_data_dir)/bitcask_expiry_1d
multi_backend.bitcask_expiry_1d.bitcask.expiry = 1d
# multi_backend.bitcask_expiry_1d.bitcask.expiry.grace_time = 1d

$ riak config generate -l debug

...
21:55:37.008 [error] Error generating configuration in phase apply_translations
21:55:37.008 [error] Error running translation for riak_kv.multi_backend, [error, badarg].

[seancribbs]

@pma Sorry about this bug. I will be writing a test and the fix should land by 2.0.1. In the meantime, you can configure multi_backend in advanced.config.

[angrycub]

Of note, it's one of the settings that has a translation. For more understanding, I created a similar setting that didn't use the translation and it worked as expected. On further inspection looks to be related to the fact that it's a duration.

[angrycub]

Intentionally broke that catch statement so that we could see the actual error. Looks like the cascading unit requirement is causing sad.

in riak.conf

multi_backend.bitcask_multi.bitcask.expiry = 36000s

...
09:04:13.416 [debug] Running translation for riak_kv.multi_backend
09:04:13.418 [debug] Adding Defaults
09:04:13.419 [debug] Right Hand Side Substitutions
09:04:13.419 [debug] Applying Datatypes
escript: exception error: bad argument
  in function  list_to_atom/1
     called as list_to_atom(36000)
  in call from cuttlefish_datatypes:from_string/2 (src/cuttlefish_datatypes.erl, line 198)
  in call from cuttlefish_generator:transform_supported_type/4 (src/cuttlefish_generator.erl, line 519)
  in call from cuttlefish_generator:transform_extended_type/4 (src/cuttlefish_generator.erl, line 538)
  in call from cuttlefish_generator:'-transform_datatypes/2-fun-3-'/3 (src/cuttlefish_generator.erl, line 405)
  in call from lists:foldl/3 (lists.erl, line 1248)
  in call from cuttlefish_generator:map_transform_datatypes/2 (src/cuttlefish_generator.erl, line 77) 

[seancribbs]

@angrycub I think we've found the source of this. Thanks for the backtrace.