I have a piece of code that was scanning the entire range from ‘’ to “\xFF” and db is loaded with my own test data. None of my keys are larger than 40 bytes. However, on a read of 10 million keys, I received 3 bad keys of size 1k to 5k bytes.
Unfortunately, I was testing with the head version - so it is hard to say what version it was referring to. I thought of setting up the environment again using the 6.3.9 release and running my Go client with the race detector turned on. Then I discovered this issue FDB go bindings fail go 1.14's unsafe pointer check · Issue #2843 · apple/foundationdb · GitHub - the 6.3.x release version also does not have the fix for that one. So I went back to attempting to build the latest master. I will update here with what I find.
However I wanted to clarify one thing before I dig deeper… On a range-scan using
GetRange(), are their any special keys (like the status/json or something internal) that I should skip over?
It could very well be my client code and some race condition I am not accounting for.