Solace Community is getting a facelift!
On March 3rd we will be starting the process of migrating Solace Community to a new platform. As a result, Solace Community will go in to a temporary read-only state. You will still be able to come onto Solace Community and search through posts to find answers, but you won't be able to ask questions, post comments, or react in any way.
We hope to have the migration complete by Wednesday March 5th (or sooner), so please keep an eye out!
Why the disk is full while only few messages are spooled when using internal disk?
Can anybody explain? What other stuff takes the disk space?
Best Answer
-
If an external block device is not available, the message-spool, configuration database, logs, diagnostics information, OS etc all share the same disk space. We reserve the bulk of the disk for the OS and configuration database, leaving limited space for the message-spool, logs and diagnostics. It is possible to have disk free and no spool space left, despite having very few messages-spooled. To resolve it, you can delete old log files, backup files to free up some spaces. Ultimately, it is recommended to use a separate disk for message-spool data.
5
Answers
-
If an external block device is not available, the message-spool, configuration database, logs, diagnostics information, OS etc all share the same disk space. We reserve the bulk of the disk for the OS and configuration database, leaving limited space for the message-spool, logs and diagnostics. It is possible to have disk free and no spool space left, despite having very few messages-spooled. To resolve it, you can delete old log files, backup files to free up some spaces. Ultimately, it is recommended to use a separate disk for message-spool data.
5 -
@emyrpetersen you can have look on https://solace.community/discussion/111/delete-old-messages-on-solace
0
Categories
