hello. As I see in sources now when starting a GridSystemViewManager [1] JmxSystemViewExporterSpi SPI is always added [2][3] regardless of what is specified in the configuration. There is no any way to change its behavior. Also, I have found a ticket where it was implemented [4].
Ilya [1] https://github.com/apache/ignite/blob/ignite-2.10/modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java#L1184 [2] https://github.com/apache/ignite/blob/ignite-2.10/modules/core/src/main/java/org/apache/ignite/internal/managers/systemview/GridSystemViewManager.java#L85 [3] https://github.com/apache/ignite/blob/ignite-2.10/modules/core/src/main/java/org/apache/ignite/internal/managers/systemview/GridSystemViewManager.java#L295 [4] https://issues.apache.org/jira/browse/IGNITE-12921 пт, 9 апр. 2021 г. в 02:57, tsipporah22 <[email protected]>: > Hi experts, > > I have a question regarding setting system view JMX exporter via > configuration. > > When I was using ignite 2.8.0 I had problem using prometheus jmx exporter > to > export metrics, with same issue described here > https://issues.apache.org/jira/browse/IGNITE-13996 . And the workaround > provided in this link was working for me: > > http://apache-ignite-users.70518.x6.nabble.com/prometheus-jmx-scrape-failed-td32000.html > > Basically the workaround was to disable JmxSystemViewExporterSpi via > configuration IgniteConfiguration#setSystemViewExporterSpi. But after > upgrading to 2.10.0 I can no longer use SqlViewExporterSpi since it's been > removed from ignite-indexing package for reason described here: > > https://issues.apache.org/jira/browse/IGNITE-12921?filter=-4&jql=text%20~%20%22systemviewexporterspi%22%20order%20by%20created%20DESC > . > So I tried to disable JmxSystemViewExporterSpi as below: > > SystemViewExporter systemViewExporter = new JmxSystemViewExporterSpi(); > systemViewExporter.setExportFilter( i -> false); > IgniteConfiguration.setSystemViewExporterSpi(systemViewExporter) > > But then I got "Duplicate SPI name" Error. So it looks like I can no longer > disable JmxSystemViewExporterSpi in 2.10.0? Is there any workaround to > address this issue? > > > 2021-04-06T19:34:27.129 [query-activatorhread] INFO > org.apache.ignite.internal.processors.failure.FailureProcessor - Configured > failure handler: [hnd=StopNodeOrHaltFailureHandler [tryStop=false, > timeout=0, super=AbstractFailureHandler > [ignoredFailureTypes=UnmodifiableSet > [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]]] > 2021-04-06T19:34:27.226 [query-activatorhread] ERROR > org.apache.ignite.internal.IgniteKernal%shared-grid - Failed to start > manager: GridManagerAdapter [enabled=true, > name=o.a.i.i.managers.systemview.GridSystemViewManager] > class org.apache.ignite.IgniteCheckedException: Duplicate SPI name (need to > explicitly configure 'setName()' property): JmxSystemViewExporterSpi > at > > org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:268) > at > > org.apache.ignite.internal.managers.systemview.GridSystemViewManager.start(GridSystemViewManager.java:93) > at > > org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1968) > at > org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1184) > at > > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2112) > at > > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1758) > at > org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1143) > at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:663) > at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:604) > at org.apache.ignite.Ignition.getOrStart(Ignition.java:419) > at > > com.rta.spark.framework.ignite.IgniteSystem.igniteConfig(IgniteSystem.java:124) > > > Thanks, > Tsippo > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
