Reply
Highlighted
Expert Contributor
Posts: 76
Registered: ‎05-09-2017
Accepted Solution

Error in Headlamp Debug Server Status

Updating indexes every3600 seconds
Location of indexes: /xxx/hadoop/cloudera-scm-headlamp

Exception occurred at November 16, 2018 9:01:16 PM +00:00

java.io.IOException: No sub-file with id .fnm found (fileName=_1d.cfs files: [])
at org.apache.lucene.index.CompoundFileReader.openInput(CompoundFileReader.java:155)
at org.apache.lucene.index.CompoundFileReader.openInput(CompoundFileReader.java:144)
at org.apache.lucene.index.FieldInfos.(FieldInfos.java:74)
at org.apache.lucene.index.SegmentCoreReaders.(SegmentCoreReaders.java:73)
at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:115)
at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:93)
at org.apache.lucene.index.DirectoryReader.(DirectoryReader.java:113)
at org.apache.lucene.index.ReadOnlyDirectoryReader.(ReadOnlyDirectoryReader.java:29)
at org.apache.lucene.index.DirectoryReader$1.doBody(DirectoryReader.java:81)
at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:754)
at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:75)
at org.apache.lucene.index.IndexReader.open(IndexReader.java:421)
at org.apache.lucene.index.IndexReader.open(IndexReader.java:281)
at org.apache.lucene.search.IndexSearcher.(IndexSearcher.java:89)
at com.cloudera.headlamp.HeadlampServiceImpl.setData(HeadlampServiceImpl.java:210)
at com.cloudera.headlamp.HeadlampIndex.loadNewSearchIndex(HeadlampIndex.java:220)
at com.cloudera.headlamp.HeadlampIndex.(HeadlampIndex.java:101)
at com.cloudera.headlamp.HeadlampIndexManager.getOrCreateIndex(HeadlampIndexManager.java:171)
at com.cloudera.headlamp.HeadlampIndexManager.reindexIndexes(HeadlampIndexManager.java:235)
at com.cloudera.headlamp.HeadlampIndexManager.access$100(HeadlampIndexManager.java:58)
at com.cloudera.headlamp.HeadlampIndexManager$1.run(HeadlampIndexManager.java:492)

Posts: 957
Topics: 1
Kudos: 227
Solutions: 121
Registered: ‎04-22-2014

Re: Error in Headlamp Debug Server Status

@desind,

 

It appears something went wrong while indexing the fsimage file and now the index is "corrupt".

The most common cause of such a problem is insufficient disk space on the volume where the indexes are stored.  Make sure there is at least 3 times the size of the fsimage space free (more is better, though).

 

To recover, you can remove the current index files and restart Reports Manager.

 

(1)

copy all child directories and their contents in /xxx/hadoop/cloudera-scm-headlamp to another location (you shouldn't need anything in that directory, but I prefer to not delete until everything is up.

 

(2)

delete all files and directories under /xxx/hadoop/cloudera-scm-headlamp

 

(3)

 

Restart Reports Manager

 

Reports Manager will see there are no indexes and then download the fsimage file from your NameNode; the fsimage will then be indexed.

 

 

Expert Contributor
Posts: 76
Registered: ‎05-09-2017

Re: Error in Headlamp Debug Server Status

Thank you @bgooley

Thats what i did and it worked. thank you and appreciate your response. 

Announcements