cassandra exporter (0.9.12) gives warning IllegalArgumentException: 'xxx.xxx.xxx.xxx_7001' is not an IP string literal message for cassandra 4.1 #112
Comments
rajesh-sapkale
changed the title
|
Hi ! BUMP, i got the same issue with cassandra 4.0.10 : WARN [cassandra-exporter-harvester-defer-0] 2023-06-26 15:52:06,520 Harvester.java:191 - Failed to register collector for MBean org.apache.cassandra.metrics:type=Connection,scope=7000,name=GossipMessageDroppedTasks. |
|
hi, The name might be different -> name=Timeouts | LargeMessageCompletedTasks | GossipMessageDroppedTasks | SmallMessagePendingTasks ... |
|
Same issue here - tried it on Cassandra 4.1.3: |
|
After this WARN the exporter stops giving results, at lease un my case: |
|
The stop is related to #83 I guess. |
|
@sonman You are on the right track, although you could condense the patch to something like this. This way only connection mbeans are affected. Although this will mean that one loses statistics if two nodes are connecting from different ports but the same IP. Which I suspect was the whole idea with including the ports to begin with on the Cassandra side. A small price to pay though as having two Cassandras on the same node doesn't seem like a common use case in production systems. |
|
when I try to compile the master branch I hit an error ! #117 |
|
I tried to switch to the standalone to avoid this not an IP string literal error mode but I got another error: I finally rolled back to using the old cassandra_exporter from criteo : it stills work with 4.1.3 despite not being actively maintained |
Getting below error for cassandra exporter (0.9.12) with Cassandra 4.1. I am using cassandra-exporter in agent mode
WARN [cassandra-exporter-harvester-defer-0] 2023-05-29 11:40:46,959 Harvester.java:191 - Failed to register collector for MBean org.apache.cassandra.metrics:type=Connec tion,scope=xxx.xxx.xxx.xxx_7001,name=GossipMessageDroppedTasks. java.lang.IllegalArgumentException: '139.144.217.245_7001' is not an IP string literal. at com.google.common.net.InetAddresses.formatIllegalArgumentException(InetAddresses.java:987) at com.google.common.net.InetAddresses.forString(InetAddresses.java:143) at com.zegelin.cassandra.exporter.MetadataFactory.endpointLabels(MetadataFactory.java:71) at com.zegelin.cassandra.exporter.FactoriesSupplier.lambda$connectionMetric$17(FactoriesSupplier.java:474) at com.zegelin.cassandra.exporter.FactoriesSupplier$FactoryBuilder.lambda$withLabelMaker$0(FactoriesSupplier.java:73) at com.zegelin.cassandra.exporter.FactoriesSupplier$FactoryBuilder.lambda$build$1(FactoriesSupplier.java:99) at com.zegelin.cassandra.exporter.Harvester.lambda$registerMBean$0(Harvester.java:174) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829)The text was updated successfully, but these errors were encountered: