The possible racing condition could be that the UTF8StringSerializerDeserializer now is not a singleton method any more. It was implemented to reuse the byte[] that serialize/deserialize the string object. Let me look into this issue.
> On Nov 11, 2015, at 8:37 AM, abdullah alamoudi <[email protected]> wrote: > > Highly probable. > Please, let's fix this soon. > > Amoudi, Abdullah. > > On Wed, Nov 11, 2015 at 7:32 PM, Till Westmann <[email protected]> wrote: > >> https://issues.apache.org/jira/browse/ASTERIXDB-1164 >> might be related. >> >> Cheers, >> Till >> >> On 11 Nov 2015, at 8:25, abdullah alamoudi wrote: >> >>> Hi all, >>> I am having a hard time figuring this out. Here are the symptoms I am >>> seeing in case one has an idea what this could be. >>> >>> I have a feed running ingesting data into a dataset. sporadically, I get >>> duplicate key exception errors (The key is of a string type) and I am >> 100% >>> sure that I don't have duplicate records. >>> >>> Moreover, I am printing the content of the frames about to be inserted >> into >>> the primary index and there are no duplicate records. >>> >>> There are three reasons why I am suspecting the String implementation: >>> 1. It is fairly recent change. >>> 2. When I run on a single node, or run one thread at a time, I never get >>> this exception. >>> 3. the key is a String. >>> >>> I have looked at the change trying to figure out where a race condition >>> might take place but it is well hidden (if it is true at all.). >>> >>> Let me know if you have seen something similar. >>> >>> Cheers, >>> Abdullah. >> Best, Jianfeng Jia PhD Candidate of Computer Science University of California, Irvine
