Is there any plan to better manage the memsql server logs? Currently logs in nodes//logs/trace (e.g memsql.log) will grow forever eventually causing disk space issues.
The documentation advises to use logrotate but this is very impractical and requires root access which in some companies is not an option.
The software should really provide a way to manage its own logging.
Same issue applies to memsql studio.
Hi,
Not sure I understand the relevance of this response. This doesn’t answer the question or address the issue.
Regards
Thank you for the feedback.
As you said, the user has to use logrotate to prevent logs from becoming too large. However, there is an open feature request DB-35290 to have the engine manage its own logs.
Thanks for the update. Glad to see there is an open feature request for this. Is there a way to follow/watch such request?
Unfortunately, no. The feature request is in our internal tracking system, which is only available to SingleStore employees.
However you’re welcome to check back about the status in the future.