Issue while building the code from maven

[sidharthk]

Please help in resolving below issue. I am hitting below error while maven build

[ERROR] Failed to execute goal de.m3y.maven:inject-maven-plugin:1.1:inject (default) on project fsimage-exporter: Value is null for injection Injection{value='null', pointCut='de.m3y.prometheus.exporter.fsimage.BuildInfoExporter.getBuildScmVersion', pointCuts=null} -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal de.m3y.maven:inject-maven-plugin:1.1:inject (default) on project fsimage-exporter: Value is null for injection Injection{value='null', pointCut='de.m3y.prometheus.exporter.fsimage.BuildInfoExporter.getBuildScmVersion', pointCuts=null}

Caused by: org.apache.maven.plugin.MojoFailureException: Value is null for injection Injection{value='null', pointCut='de.m3y.prometheus.exporter.fsimage.BuildInfoExporter.getBuildScmVersion', pointCuts=null}

[marcelmay]

During the Maven build, the current Git version gets injected so that the exporter can report its own version. This seems to fail, as you probably did not do a Git clone?

[sidharthk]

Hi, Yes, I have downloaded the zip and building it. So should i do a git clone and try to do maven build?

[marcelmay]

That would be better (you get the correct build meta data like Git commit etc into the exporter).

Alternatively, you could try to set/override the the missing property:

mvn clean install -DbuildNumber="not available"

[sidharthk]

thanks @marcelmay for your help. The above parameter dint work, I did a git clone and its done. Now when i am trying to run the jar, i am unable to see any logs for it even after passing -Dlog4j.rootLogger=DEBUG and cannot see any service running on 7772 port. Could you please help me to enable logging and debug the issue.

[marcelmay]

By default everything gets logged to STDOUT using Log level INFO.

This should look like this (using provided example config)

> mvn clean package
> ./run_example.sh
2019-10-23 23:58:50,697 [pool-1-thread-1] INFO  org.apache.hadoop.hdfs.server.namenode.FSDirectory  - GLOBAL serial map: bits=29 maxEntries=536870911
2019-10-23 23:58:50,698 [pool-1-thread-1] INFO  org.apache.hadoop.hdfs.server.namenode.FSDirectory  - USER serial map: bits=24 maxEntries=16777215
2019-10-23 23:58:50,698 [pool-1-thread-1] INFO  org.apache.hadoop.hdfs.server.namenode.FSDirectory  - GROUP serial map: bits=24 maxEntries=16777215
2019-10-23 23:58:50,698 [pool-1-thread-1] INFO  org.apache.hadoop.hdfs.server.namenode.FSDirectory  - XATTR serial map: bits=24 maxEntries=16777215
2019-10-23 23:58:50,700 [pool-1-thread-1] INFO  de.m3y.hadoop.hdfs.hfsa.core.FSImageLoader  - Loaded 5 strings into string table
2019-10-23 23:58:50,700 [pool-1-thread-1] INFO  de.m3y.hadoop.hdfs.hfsa.core.FSImageLoader  - Loaded fsimage section STRING_TABLE in 30ms
2019-10-23 23:58:50,702 [pool-1-thread-1] INFO  de.m3y.hadoop.hdfs.hfsa.core.FSImageLoader  - Loaded 0 inode references 
2019-10-23 23:58:50,702 [pool-1-thread-1] INFO  de.m3y.hadoop.hdfs.hfsa.core.FSImageLoader  - Loaded fsimage section INODE_REFERENCE in 1ms
2019-10-23 23:58:50,704 [pool-1-thread-1] INFO  de.m3y.hadoop.hdfs.hfsa.core.FSImageLoader  - Loaded 30 inodes [2ms]
2019-10-23 23:58:50,704 [pool-1-thread-1] INFO  de.m3y.hadoop.hdfs.hfsa.core.FSImageLoader  - Sorted 30 inodes [0ms]
2019-10-23 23:58:50,704 [pool-1-thread-1] INFO  de.m3y.hadoop.hdfs.hfsa.core.FSImageLoader  - Loaded fsimage section INODE in 2ms
2019-10-23 23:58:50,717 [pool-1-thread-1] INFO  de.m3y.hadoop.hdfs.hfsa.core.FSImageLoader  - Loaded 10 directories
2019-10-23 23:58:50,717 [pool-1-thread-1] INFO  de.m3y.hadoop.hdfs.hfsa.core.FSImageLoader  - Loaded fsimage section INODE_DIR in 11ms
2019-10-23 23:58:50,723 [pool-1-thread-1] INFO  de.m3y.prometheus.exporter.fsimage.FsImageUpdateHandler  - Loaded /Users/mm/projects/hadoop-fsimage-exporter/src/test/resources/fsimage_0001 with 0.0MiB in 73ms
2019-10-23 23:58:50,747 [pool-1-thread-1] INFO  de.m3y.prometheus.exporter.fsimage.FsImageReporter  - Finished computing overall/group/user stats in 16ms
2019-10-23 23:58:50,748 [pool-1-thread-1] WARN  de.m3y.prometheus.exporter.fsimage.FsImageReporter  - No matches found for /tmp
2019-10-23 23:58:50,748 [pool-1-thread-1] INFO  de.m3y.prometheus.exporter.fsimage.FsImageReporter  - Expanded paths [/datalake/asset3, /datalake/asset1, /datalake/asset2, /user/mm] for path stats [/tmp, /datalake/a.*, /user/m.*]
2019-10-23 23:58:50,750 [pool-1-thread-1] INFO  de.m3y.prometheus.exporter.fsimage.FsImageReporter  - Finished 4 path stats in 2ms
2019-10-23 23:58:50,751 [pool-1-thread-1] INFO  de.m3y.prometheus.exporter.fsimage.FsImageReporter  - Expanded paths [/datalake/asset1, /datalake/asset2] for path set stats datalakeAsset1and2
2019-10-23 23:58:50,752 [ForkJoinPool.commonPool-worker-2] WARN  de.m3y.prometheus.exporter.fsimage.FsImageReporter  - No matches found for /user/foo
2019-10-23 23:58:50,752 [ForkJoinPool.commonPool-worker-2] INFO  de.m3y.prometheus.exporter.fsimage.FsImageReporter  - Expanded paths [/datalake/asset3, /user/mm] for path set stats userMmAndFooAndAsset1
2019-10-23 23:58:50,752 [pool-1-thread-1] INFO  de.m3y.prometheus.exporter.fsimage.FsImageReporter  - Finished 2 path set stats in 2ms

[marcelmay]

Just added a new feature to toggle the log level when starting the exporter : #29

Here's an example: [run_example.sh]

Do you see any output at all?