New Ranks & Badges For The Community!
Notice something different? The ranks and associated badges have gone "Star Fleet". See what they all mean HERE
Highlighted
Absent Member.
Absent Member.
1304 views

Filr Lg - 1st search index took 2 days next 1 still running

Looking for suggestions or experience with the following:

Incrementing ever so slowly on each search server, but never seems to finish:

du -h /vastorage/search/kablink/

36G /vastorage/search/kablink/ node 1 (index that took 2 days)
34G /vastorage/search/kablink/ node 2 (index that is still running)


appserver.log shows current entries of:

2017-10-25 15:18:28,069 INFO [Sitescape_Worker-18] [com.novell.teaming.module.folder.impl.PlusFolderModule] - Folders cleaned up: success=607, fail=0, invalid=0
2017-10-25 15:28:12,927 INFO [Sitescape_Worker-4] [com.novell.teaming.module.folder.impl.PlusFolderModule] - Folders cleaned up: success=610, fail=0, invalid=0

Node 2 - being indexed is in write only.

Looking for suggestions on other things to check for progress - will it ever finish or will it crash eventually? Should we stop it and reboot? How long to monitor - swap is at 99% for several days... Don't want to stop if its almost done? Could it take
over a week to finish?
0 Likes
5 Replies
Highlighted
Knowledge Partner Knowledge Partner
Knowledge Partner

I'm no Filr expert, but I'm decent at Linux in general.

How much swap do you have set for this system? How much RAM? What do you
see from the following commands:


free
uptime
top -n 1


Has this always taken as long to run, or has something changed recently?
Which Filr version/patches, and how is it configured with regard to net
folders, indexing, etc.?

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
Highlighted
Absent Member.
Absent Member.

Interested in seeing if anyone had this issue and it eventually finished without being rebooted -
or if we need to reboot and stop waiting 🙂


Novell Filr Appliance 1.2.0.846-HP.871 for now

filr-search-02:~> free
total used free shared buffers cached
Mem: 16467896 15908632 559264 8 367004 1900400
-/+ buffers/cache: 13641228 2826668
Swap: 2097148 2097148 0

Search-02 is configured the same as Search-01.
Search-01 had filled up /dumps so was rebooted right before being re-indexed and took 2 days.

Search-02 has been up 75 days:

filr-search-02:~> top -n 1
top - 07:29:40 up 75 days, 22:27, 1 user, load average: 0.38, 0.38, 0.37
Tasks: 98 total, 1 running, 97 sleeping, 0 stopped, 0 zombie
Cpu(s): 1.5%us, 1.3%sy, 0.0%ni, 96.8%id, 0.1%wa, 0.0%hi, 0.3%si, 0.0%st
Mem: 16081M total, 15514M used, 566M free, 358M buffers
Swap: 2047M total, 2047M used, 0M free, 1835M cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3169 root 20 0 46.4g 10g 31m S 8 67.8 2715:11 java
3443 memcache 20 0 2082m 2.0g 692 S 4 12.8 2529:29 memcached
1 root 20 0 10560 680 652 S 0 0.0 0:57.23 init
2 root 20 0 0 0 0 S 0 0.0 0:01.08 kthreadd
3 root 20 0 0 0 0 S 0 0.0 5:01.56 ksoftirqd/0
0 Likes
Highlighted
Absent Member.
Absent Member.

Ended up rebooting search-02, alerts gone, normal stats now.
0 Likes
Highlighted
Absent Member.
Absent Member.

How much of the 16GB have you allocated to the JVM on Search servers? You could try: JVM Min = 4GB, JVM Max = 8GB

If you ever run a re-index, and you have to quit the browser, and have no way to see if the indexing ever completed, here's what you can do on the Filr server:

more /var/opt/novell/tomcat-filr/logs/appserver.log | grep "Administrative reindexing"

This should produce lines that look like this:

2017-11-09 19:33:08,146 INFO [http-apr-8443-exec-13] [com.novell.teaming.module.admin.impl.PlusAdminModule] - Administrative reindexing requested on binders [1]
2017-11-10 04:02:25,027 INFO [http-apr-8443-exec-13] [com.novell.teaming.module.admin.impl.PlusAdminModule] - Administrative reindexing completed on binders [1]

which tells you that it did actually complete.
0 Likes
Highlighted
Absent Member.
Absent Member.

Are you "content indexing" a lot of Net Folders or entire Net Folder Servers? If so, consider content indexing only areas where users MUST search for files based on their content. If that is not a requirement, you will greatly benefit by disabling content indexing.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.