Using "localhost" as ITLHost name in a Distributed MDEX Architecture Causes DistributeIndexAndApply() Failures
Last updated on DECEMBER 08, 2016
Applies to:Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 6.1.0 and later
Information in this document applies to any platform.
In a distributed Endeca architecture where the ITLHost and MDEX hosts reside on different machines, the baseline update step DistributeIndexAndApply() is failing to distribute the index to the MDEX hosts. For example, the index copy job copy_index_to_host_MDEXHost1_LiveDgraph1 that runs on MDEXHost1 is trying to copy dgidx_output from a local dgidx_output directory on the MDEXHost instead of from the dgidx_output directory on the remote ITLHost. A dgidx_output directory should not normally exist on an MDEX host that is remote from the ITLHost.
As a test, if files are put into the "bad" dgidx_output directory on the MDEXHost and only the DistributeIndexAndApply() step is run, the files are successfully distributed to dgraph_input. Manually putting the index files in the bad dgidx_output has been a workaround until we figure out why the network index copy from the remote ITLHost is not working correctly.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms