2.0 known issues

This page contains a list of known issues with Riak 2.0.

• Bitcask merges crash due to bitcask#185. Until this is resolved, a patch is available here to fix the cause of the crashes
• Related to riak_kv#782, in clusters that have downgraded from 2.0, objects written with DVV enabled will break JavaScript MapReduce and precommit hooks.
• riak_ee-issues#14 - Realtime replication processes are left running after realtime replication has been stopped and disabled.
• node_package/150: Bad SOLR temp directory on FreeBSD 10
• node_package/162: Ctrl-C causes unexpected behavior in riak-admin top and more
• cuttlefish#158 An erroneously formatted advanced.config file will cause a crash with an inscrutable error message.
• cuttlefish#153 A syntax error before the end of the riak.conf file can result in a crash with an inscrutable error message.
• cuttlefish#145 Some configuration errors are swallowed when other errors are encountered.
• riak_dt#98 Reset-Remove semantic not fully supported for counters in Maps.
• riak_dt#99 Deferred operations may be lost before delivery in some cases.
• riak_api#65 CRL handling is overly aggressive
• riak_pb#96 young_vclock bucket property can be set to -1, but is uint32 in PB message.