panic: slice bounds out of range
Fynnss opened this issue · comments
When a 2GB key appears in Pebble, what could be the situation? Below is the error message for the faulty SST:
size
file 2.0GB
data 2.0GB
blocks 1
index 31B
blocks 1
top-level 0B
filter 69B
raw-key 39B
raw-value 2.0GB
pinned-key 0
pinned-val 0
point-del-key-size 0
point-del-value-size 0
records 2
set 2
delete 0
delete-sized 0
range-delete 0
range-key-set 0
range-key-unset 0
range-key-delete 0
merge 0
pinned 0
index
key value comparer leveldb.BytewiseComparator
merger pebble.concatenate
filter rocksdb.BuiltinBloomFilter
compression Snappy
options window_bits=-14; level=32767; strategy=0; max_dict_bytes=0; zstd_max_train_bytes=0; enabled=0;
user properties
collectors []
rocksdb.block.based.table.prefix.filtering 0
rocksdb.block.based.table.whole.key.filtering 1
rocksdb.prefix.extractor.name nullptr