Submit a ticketCall us

Virtualization Manager 7.0 is here!
Read the Upgrade Guide and learn how to use new features in the Getting Started Guide.

 

 

 

 

Home > Success Center > Virtualization Manager (VMAN) > Facets are missing when Shallow indexing is enabled

Facets are missing when Shallow indexing is enabled

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 532 Votes: 0 Revisions: 10

Issue

Shallow indexing is used to alleviate performance problems experienced on large virtual environments. However, if Shallow indexing is enabled, some non-critical facets are missing, and the search results cannot be sorted by the affected remote entities either.

This is the expected behavior if shallow indexing is enabled.

For example, as the attached image shows, if you search for all VMs, it is not possible to sort the search results by their related configuration items (such as vm.host.origin).
To be able to sort search results by these configuration item parameters, make sure that the Shallow indexing property is set to false.

The attachment contains the list of missing facets. Please note that the facets in the list are not used in default alerts or trends.

To determine whether Shallow indexing is turned on, check the configuration in /etc/hyper9/hyper9-config.xml, or look for 'index.lucene.shallowIndex' in the log file listing all system properties when Virtualization Manager starts up. After turning Shallow indexing on or off, and restarting Virtualization Manager, the data will be reindexed according to the current Shallow index setting.

Resolution

To turn on Shallow indexing:

 

  1. Open the /etc/hyper9/hyper9-config.xml file, and add <entry key="index.lucene.shallowIndex">true</entry> in the properties section.
  2. Restart Tomcat by typing sudo /sbin/service tomcat restart in the command line.

To turn off Shallow indexing:

  1. Open the /etc/hyper9/hyper9-config.xml file, and add <entry key="index.lucene.shallowIndex">false</entry> in the properties section.
  2. Restart Tomcat by typing sudo /sbin/service tomcat restart in the command line.
Last modified
04:09, 23 Jun 2016

Tags

Classifications

Public