简体   繁体   English

在哪种情况下会生成点火诊断?

[英]In which scenario ignite diagnostics will be generated?

We are exploring apache ignite, and we want to understand the impact of keeping Ignite system property IGNITE_DIAGNOSTIC_ENABLED with default value true on production.我们正在探索 apache ignite,我们想了解将 Ignite 系统属性 IGNITE_DIAGNOSTIC_ENABLED 保持为默认值 true 对生产的影响。

With this setting an Ignite node conditionally checks internal structures in order to find long-running operations and print a log message.使用此设置,Ignite 节点有条件地检查内部结构,以查找长时间运行的操作并打印日志消息。 There's also a property IGNITE_LONG_OPERATIONS_DUMP_TIMEOUT controlling the threshold for duration of operations, by default it's 60_000 ms (operations longer than that are considered long-running).还有一个属性IGNITE_LONG_OPERATIONS_DUMP_TIMEOUT控制操作持续时间的阈值,默认为 60_000 毫秒(超过该时间的操作被认为是长时间运行的)。 I believe that this diagnostics machinery in almost harmless in terms of performance and stability and should be always enabled.我相信这种诊断机制在性能和稳定性方面几乎是无害的,应该始终启用。 It could serve two main purposes: troubleshooting and monitoring (alerting).它可以用于两个主要目的:故障排除和监控(警报)。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM