Using Deprecated --whymatch Dgraph Option Causes CPU Usage to Spike and Remain at 100% Utilization
Last updated on NOVEMBER 01, 2017
Applies to:Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 6.2.2 and later
Information in this document applies to any platform.
Using the deprecated --whymatch Dgraph option in MDEX 6.4.0 causes CPU to spike and remain at 100% utilization when queries are issued.
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