Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

slotBuffer is all ZEROs for a specific key #35

Open
muthumadi opened this issue Dec 12, 2018 · 1 comment
Open

slotBuffer is all ZEROs for a specific key #35

muthumadi opened this issue Dec 12, 2018 · 1 comment

Comments

@muthumadi
Copy link

muthumadi commented Dec 12, 2018

We recently ran into strange issue where a StoreReader.get(Object key) given the key returned a null, but when we do StoreReader.iterable() we could see the key and the value printer correctly.

This happened only for one particular key. Debugging in the paldb library and see that the slotBuffer is loaded with ZERO’s for that particular key and offset results in a ZERO.

I have attached screenshot of the debug point. I am unable to re-produce this with the same key and dataset.

paldbissue

@muthumadi
Copy link
Author

muthumadi commented Jan 27, 2019

Can someone please tell me why the offset would be ZERO or why we have this check

            if (offset == 0L) {
                return null;
            }

This issue still continues to happen at various intervals and random keys. I am unable to even re-produce it.

As I mentioned in the original post, if I use the StoreReader.iterable() I could see the key and the value correctly from the same paldb file.

Its only that StoreReader.get(Object key) returns a null. Any help with debugging this issue will be of great help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant