关于Corda Enterprise的details-node-.log日志性能影响与配置调整的问询

Great question—let’s break this down clearly for Corda Enterprise, since its logging setup differs from the open-source version:

Performance Impact #

Yes, the details-node-.log file running at TRACE level can absolutely impact Cordapp performance, especially in high-throughput environments. Here’s why:

• TRACE-level logs generate an enormous volume of granular data, including low-level internal operations, stack traces, and frequent state updates.
• This leads to increased disk I/O overhead (constant writing to the log file) and CPU usage (string formatting, log event processing).
• Over time, bloated log files can also cause disk space exhaustion, which will further degrade node performance or even trigger crashes.

Adjusting the Log Level for details-node-.log #

Corda Enterprise uses Logback for logging configuration, so you’ll need to modify the node’s logback config file (typically located at <your-node-directory>/config/logback.xml):

1. Open the logback.xml file in a text editor.
2. Locate the appender definition for the details log—it will look similar to this:

   <appender name="DETAILS" class="ch.qos.logback.core.rolling.RollingFileAppender">
       <file>${logDirectory}/details-node-${nodeName}.log</file>
       <!-- ... other config like rolling policy ... -->
       <filter class="ch.qos.logback.classic.filter.ThresholdFilter">
           <level>TRACE</level>
       </filter>
   </appender>
   

3. Change the <level> value inside the ThresholdFilter to your desired severity (e.g., WARN, INFO, ERROR). For example:

   <level>WARN</level>
   

4. If there’s a dedicated logger referencing this appender, adjust its level too (look for a <logger> entry with appender-ref="DETAILS").
5. Save the file and restart your Corda node for changes to take effect.

Disabling the details-node-.log File Entirely #

If you don’t need the details log at all, you can disable it by modifying the same logback.xml file:

• Option 1: Remove or comment out the entire DETAILS appender block (the <appender name="DETAILS"> section).
• Option 2: Remove the appender-ref="DETAILS" reference from the root logger or any specific loggers that use it. For example, if your root logger looks like this:

  <root level="INFO">
      <appender-ref ref="CONSOLE"/>
      <appender-ref ref="FILE"/>
      <appender-ref ref="DETAILS"/> <!-- Remove this line -->
  </root>
  

• After making changes, restart your node to stop the log file from being generated.

Key Notes #

• Always back up your original logback.xml file before making changes, in case you need to revert.
• Log configuration changes require a node restart—they won’t take effect dynamically.
• The exact structure of logback.xml might vary slightly between Corda Enterprise versions (e.g., 4.x vs. 5.x), but the core approach remains consistent.

内容的提问来源于stack exchange，提问作者Marcos Pupo