Jazz Register Log in

r1 - 2025-01-28 - 10:52:17 - NatarajanThirumeniYou are here: TWiki >  Deployment Web > DeploymentTroubleshooting > IntegrationsTroubleshooting > LQEIndexUpdateForETMDataSourceAppearsToBeHung

Topic title (use a lowercase style, which is known as "sentence-style" capitalization) todo.png

Authors: NatarajanThirumeni
Build basis: ELM (formally known CLM - Collaborative Life-cycle Management) 7.0.2/7.0.3.

Introduction

This document explains on how to troubleshoot LQE index update for ETM data source appears to be hung. This is for ELM v703 where the LQE is using jena indexing

Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph

We had to increase the JVM heap and underlying memory used by the LQE server. The LQE server's index size is approximately 2.4 TB. Our standard recommendation is that they should have max (Xmx and Xms) heap set to 25% of the LQE index size, so it would be 600G + enough free native memory to fit the index, so the total would be ~3TBs.

-Xmx600G -Xms600G

In addition to JVM and native memory tuning, we took the following steps to update the MIN data source.

1) Rebase in ETLM using /trsConsole

2) Reindex ETM data source in the LQE server once rebase completed

3) The ETM data-source re-index process consists of two main steps: removal and base processing. At times, the removal step may appear to be stalled, but it is not.

4) In some cases removal of 1000 of resources to be removed from the LQE_CONFIG_SELECT table. Since this is a single threaded delete call it could take some hours to complete. Continue to monitor until the completion. The status is reported in the ETM data-source in the LQE.

5) From step4) collect Java cores from the LQE server if you want to be sure to "remove" resources that aren't stalled.

6) Once removal and base processing are completed - the data source of ETM should be up-to-date.

While running ETM data-source ensure application and database servers must be up and running.

Heading 1 (use sentence-style capitalization)

Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text Section text

Heading 2 (use sentence-style capitalization)

Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text

Heading 2 (use sentence-style capitalization)

Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text

Heading 1

Related topics: Deployment web home, Deployment web home

External links:

Additional contributors: TWikiUser, TWikiUser

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | More topic actions
 
This site is powered by the TWiki collaboration platformCopyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.