.sst file in spool

get-help
22

the spool directory also contains log files from rocksdb, those might also tell you something interesting

23

the rocksdb logs are quite long and verbose, and I’m doubtful that they can be effectively read via screenshot.

24

The size of the rocksdb seems unusual. Did you experience unusual circumstances leading up to this? eg: running out of disk space? Crazy load?

Rocksdb will generally manage and compact the sst files down as needed and I wouldn’t expect to see one so large when there are no messages (or just 78 that it found according to the screenshot)

25

If you restart the instance, does it compact the spool? And does it report that there are still some messages?

26

I have .sst logs for the date of 24 October

27

I hope you are referring to 78 message that of July

28

the count of .sst logs files are around 865

29

there should be a file named LOG in the spool directory. It is a human readable (but verbose!) log

30

I have

31

read through it to see if it is yelling about something bad

32

any specific keywords we are looking for?

33

no idea TBH

34

it’s mostly meaningful to the rocksdb developers

35

but if it is complaining about something, that might be useful to see. I’d suggest looking at the bottom

36

It has information on compaction stats, which may be insightful in this sort of situation

37

please have look

39

hoping you will find something, as I am unable understand

40

So, I’m not going to dig into a screenshot of this file right now

41

if you want me to dig in deeper, we can talk about purchasing support