Hi Claudio,
The "indexes_not_supported" error means you attempted to write
secondary index information to a bucket that is stored in a backend
that does not support indexes.
Could you please confirm that the bucket you're using for this data is
set to use the "eleveldb_mult" backend? You will have to check the
bucket's properties, or the parent bucket type's properties. The
property name is "backend".
For instance, if your bucket is named my_bucket and you are not using
bucket types, this will get the properties:
curl riak-host:8098/buckets/my_bucket/props
--
Luke Bakken
Engineer
lbak...@basho.com
On Wed, Jan 14, 2015 at 10:56 AM, Claudio Cesar Sanchez Tejeda
<demoncc...@gmail.com> wrote:
> Hi,
>
> I upgraded Riak from 1.4.12 to 2.0.2. The tomcat application doesn't
> work correctly...
>
> We have 2 issues:
>
> - We are using mapreduce with javascript. The meta data is saved in
> Riak with low case, for example: x-test-lala, but the javascript
> object that the mapreduce function returns is in camel case
> (X-Test-Lala).
>
> - Some internal functions are failing with this error:
> Caused by: java.io.IOException:
> {"phase":"index","error":"{indexes_not_supported,riak_kv_multi_backend}"
>
> This is the configuration file:
>
> log.console = file
> log.console.level = info
> log.console.file = /var/log/riak/console.log
> log.error.file = /var/log/riak/error.log
> log.syslog = off
> log.crash.file = /var/log/riak/crash.log
> log.crash.maximum_message_size = 64KB
> log.crash.size = 10MB
> log.crash.rotation.keep = 5
> log.crash.rotation = $D0
> log.crash = on
> nodename = r...@riak0.example.com
> distributed_cookie = riak
> erlang.async_threads = 64
> erlang.max_ports = 65536
> erlang.schedulers.force_wakeup_interval = 500
> erlang.schedulers.compaction_of_load = false
> ring_size = 64
> transfer_limit = 2
> dtrace = off
> platform_bin_dir = /usr/sbin
> platform_data_dir = /var/lib/riak
> platform_etc_dir = /etc/riak
> platform_lib_dir = /usr/lib/riak/lib
> platform_log_dir = /var/log/riak
> strong_consistency = off
> listener.http.internal = 10.8.5.41:8098
> listener.protobuf.internal = 10.8.5.41:8087
> protobuf.backlog = 128
> anti_entropy = active
> storage_backend = multi
> object.format = 1
> object.size.warning_threshold = 5MB
> object.size.maximum = 50MB
> object.siblings.warning_threshold = 25
> object.siblings.maximum = 100
> bitcask.data_root = $(platform_data_dir)/bitcask
> bitcask.io_mode = erlang
> riak_control = on
> riak_control.auth.mode = off
> leveldb.maximum_memory.percent = 70
> search = off
> search.solr.start_timeout = 30s
> search.solr.port = 8093
> search.solr.jmx_port = 8985
> search.solr.jvm_options = -d64 -Xms1g -Xmx1g -XX:+UseStringCache
> -XX:+UseCompressedOops
> multi_backend.default = bitcask_mult
> multi_backend.bitcask_mult.storage_backend = bitcask
> multi_backend.bitcask_mult.bitcask.data_root = /var/lib/riak/bitcask_mult
> multi_backend.eleveldb_mult.storage_backend = leveldb
> multi_backend.eleveldb_mult.leveldb.data_root = /var/lib/riak/eleveldb_mult
> multi_backend.bitcask_expiry_mult.storage_backend = bitcask
> multi_backend.bitcask_expiry_mult.bitcask.data_root =
> /var/lib/riak/bitcask_expiry_mult
> multi_backend.bitcask_expiry_mult.bitcask.expiry = 1h
> multi_backend.memory_expiry_mult.storage_backend = memory
> multi_backend.memory_expiry_mult.memory_backend.max_memory_per_vnode = 16MB
> multi_backend.memory_expiry_mult.memory_backend.ttl = 1h
>
> Do you have any clue how I can resolve these issues?
>
> The only solution that I have now is downgrade Riak to 1.4.12...
>
> Regards.
>
> _______________________________________________
> 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
