Can you provide a detailed explanation of command.log in tracelogs?

Hi Team,

Can you provide a detailed explanation of ‘command.log’ in tracelogs?

The explanation in the documentation(docs) is very simple.

In addition to the memsql.log file, SingleStore DB maintains a command.log file for the code compilation process, which is separate from the memsqld process. The command.log file is also located in the tracelogs directory.

I tried several tests (execution of commands, etc.) for logging, but failed.

Please explain to me.

Hi Kyoungho! :wave: Happy to find a team member to help with this. Looks like you’re running on the self-hosted service. What’s the exact version number?

Hi MariaSilverhardt,

Yes, it is a self-hosted service, version 7.6.13 (latest).

Hi,

This question is still valid.
explain it to me please.

Hi

The command.log file is for tracing errors/warnings from the external process that runs LLVM for code-generation (among other things). It sometimes needed by customer support to debug code-generation errors. It typically has very little of interest in it.

-Adam

2 Likes