Error LLIST with non unique keys


#1

Hi there Im trying to create LDT list with non-unique integer keys, but after few inserts i get "Error Code 1400: /opt/aerospike/sys/udf/lua/ldt/lib_llist.lua:4380 LDT-Internal Error" and cant insert anything anymore.

I created my custom user module and made following adjustments:

function exports.adjust_settings( ldtMap )
    ldt_settings.use_package( ldtMap, "ListLargeObject" );
    ldt_settings.set_unique_key_false( ldtMap);
end

from client i`m doing inserts within a loop

for (int counter = 3; counter < 100; counter++) {
    Map<String,Value> map = new HashMap<String, Value>();
    map.put("key", Value.get(counter));
    Key key = new Key("test_project", "test_set", "test_key");
    LargeList event_list = client.getLargeList(policy, key, "llist_bin", "event_llist");
    event_list.add(Value.getAsMap(map));
    System.out.println(counter);
}

It takes 6 inserts til aerospike locks up with error from lib_llist

(/opt/aerospike/sys/udf/lua/ldt/lib_llist.lua::4496) [ERROR]<lib_llist_2014_12_20.B:computeDuplicateSplit()> NIL object list

You can find my log here -> https://gist.github.com/zlosim/8c4252ff2aaaf1adbc31

I`m using aerospike community edition 3.4.1 and JAVA client 3.0.33

Did I miss something from the configuration? thanks


Allow duplicate keys in Large List in aerospike server 3.5.12
#2

Hello mvince,

Your Configuration is fine this is a bug … Will be fixed in the next release …

– R


#3

thx raj

eagerly waiting! :smile:


#4

@mvince,

Thank you for posting about LDTs in our forum. Please see the LDT Feature Guide for current LDT recommendations and best practices.


#5

@mvince,

Effective immediately, we will no longer actively support the LDT feature and will eventually remove the API. The exact deprecation and removal timeline will depend on customer and community requirements. Instead of LDTs, we advise that you use our newer List and SortedMap APIs, which are now available in all Aerospike-supported clients at the General Availability level. Read our blog post for details.