Viewing the Endeca MDEX Engine Auditing page - Endeca JSP Reference application

To view the MDEX Engine Auditing page:
Access the following URL:
http://DgraphServerNameOrIP:DgraphPort/admin?op=audit
For example, if your Dgraph is running on your local machine and listening on port 15000, specify this:
http://localhost:15000/admin?op=audit


FYI:
The information on the MDEX Engine Auditing page is persistent and is valid across the MDEX Engine restarts.

Viewing Endeca MDEX Engine(Dgraph) Server Statistics - Endeca JSP Reference application

You can request the MDEX Engine Statistics page for the Dgraph with the URL listed below-

http://DgraphServerNameOrIP:DgraphPort/admin?op=stats

For example, if your Dgraph is running on your local machine and listening on port 15000, specify this:

http://localhost:15000/admin?op=stats

You can find Host and port in AppConfig.xml file 

How to reset stats?

http://DgraphServerNameOrIP:DgraphPort/admin?op=statsreset 

Endeca MDEX (Dgrpahs) - Few items on Endeca Dgrpah side to improve index and query time

   1) Thread configured should be equal to the Number of cores - 1

       Example:  If Cores are 4 then define it as 3

                  <arg>--threads</arg>

      <arg>3</arg>

    2)      Disable Why did it match on production

     Remove   <arg>--whymatch</arg> from Dgrpah Defaults

  

    3)      Remove Spell correction and Did you mean from Dgrpah defaults if it is not used on the front end

   <arg>--spl</arg>

    <arg>--dym</arg>

    4)      Remove Compound dimension if it is not used in the application from the DataIngest.xml

<dgidx id="Dgidx" host-id="ITLHost">

    <properties>

      <property name="numLogBackups" value="10" />

      <property name="numIndexBackups" value="3" />

    </properties>

    <args>

      <arg>-v</arg>

      <arg>--compoundDimSearch</arg>

      <arg>--lang</arg>

      <arg>${LANGUAGE_ID}</arg>

    </args>

    <log-dir>./logs/dgidxs/Dgidx</log-dir>

    <input-dir>./data/forge_output</input-dir>

    <output-dir>./data/dgidx_output</output-dir>

    <temp-dir>./data/temp</temp-dir>

    <run-aspell>true</run-aspell>

  </dgidx>

Component 'Forge' is already started - Endeca FORGE

Problem Statement:

When you try to run endeca baseline update you will see message as below:

 BASELINE SCRIPT STARTED
[07.11.15 11:38:32] INFO: Released lock 'update_lock'.
 Copy crawl files to incoming and processing folder
[07.11.15 11:38:33] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[07.11.15 11:38:34] INFO: Definition has not changed.
[07.11.15 11:38:34] INFO: Starting baseline update script.
[07.11.15 11:38:34] INFO: Acquired lock 'update_lock'.
[07.11.15 11:38:34] INFO: [ITLHost] Starting shell utility 'cleanDir_processing'.
[07.11.15 11:38:35] INFO: [ITLHost] Starting shell utility 'cleanDir_forge-output'.
[07.11.15 11:38:36] INFO: [ITLHost] Starting shell utility 'cleanDir_temp'.
[07.11.15 11:38:38] INFO: [ITLHost] Starting shell utility 'move_-_to_processing'.
[07.11.15 11:38:39] INFO: [ITLHost] Starting copy utility 'fetch_config_to_input_for_forge_Forge'.
[07.11.15 11:38:39] INFO: [ITLHost] Starting backup utility 'backup_log_dir_for_component_ConfigurationGeneratorForge'.
[07.11.15 11:38:40] INFO: [ITLHost] Starting component 'ConfigurationGeneratorForge'.
[07.11.15 11:39:10] INFO: [ITLHost] Starting backup utility 'backup_log_dir_for_component_Forge'.
[07.11.15 11:39:11] INFO: [ITLHost] Starting component 'Forge'.
[07.11.15 11:39:11] INFO: Component 'Forge' is already started.


Solution:
It will happen if someone killed baseline update process while forge is running. Easy way to release or kill process is to get into Endeca experience manager and stop Forge process.