Search on vCenter UI very slow and often do not show any results of existing objects
Article ID: 411345
Updated On:
Products
Issue/Introduction
Doing a search on vCenter UI is spinning in a loop with the "Searching...".
The Browser is latest version.
This happens only on using domain accounts logged in to vCenter, issue doesn't happen using [email protected].
localhost_access_logļ¼
127.0.0.1 ###.###.##.## - - [YYYY-MM-DDTHH:MM:SS] "GET /ui/search/quicksearch/?opId=:1769292260&query=051p HTTP/1.1" 200 231 200022 70002088 http-nio-127.0.0.1-5090-exec-42 59307
127.0.0.1 ###.###.##.## - - [YYYY-MM-DDTHH:MM:SS] "GET /ui/search/quicksearch/?opId=:1751538719&query=051 HTTP/1.1" 200 643 200022 70002083 http-nio-127.0.0.1-5090-exec-37 59899
127.0.0.1 ###.###.##.## - - [YYYY-MM-DDTHH:MM:SS] "GET /ui/search/quicksearch/?opId=:1414305137&query=0 HTTP/1.1" 200 1491 200022 70002080 http-nio-127.0.0.1-5090-exec-11 60409
dataservice.log
[YYYY-MM-DDTHH:MM:SS][WARN ] agw-httpclient-worker-13 ##### ##### ##### VapiApiProviderFactoryImpl$3 [queryId: q-1033:QuickSearch:1414305137:01:libitem01] Operation com.vmware.cis.data.provider.resource_model.query took too long on node https://vCenter.######.#####:443/cls/: 60403 ms
operation-input => {query_spec=com.vmware.cis.data.provider.resource_model.query_spec => {resource_models=[com.vmware.content.library.ItemModel], filter=com.vmware.cis.data.provider.resource_model.filter => {criteria=[com.vmware.cis.data.provider.resource_model.property_predicate => {ignore_case=true, comparable_value=*0*, property=com.vmware.content.library.ItemModel/name, operator=LIKE}], operator=AND}, sort_criteria=[com.vmware.cis.data.provider.resource_model.sort_criterion => {sort_direction=ASCENDING, property=@modelKey}], limit=10, properties=[@modelKey, @type, com.vmware.content.library.ItemModel/name], return_total_count=true}}
[YYYY-MM-DDTHH:MM:SS] [WARN ] p-nio-127.0.0.1-5090-exec-11 70002080 100124 200022 ProfilingLogService [queryId: q-1033:QuickSearch:#####] The Data Service detected slow execution:
The query batch execution took too long: 60405 milliseconds.
A DataProviderAdapter ([Adapter: com.vmware.vise.data.adapters.core.DataServiceCoreAdapter@7b1d550d, typeInfo: null]) execution took too long: 60405 milliseconds.
Invocation id: q-1033:QuickSearch:#####:DataServiceCoreAdapter:#####
Query names: [q-1033:QuickSearch:#####]
The queries in the batch sent to the Data Service are:
Query[0]:
QuerySpec
QueryName: q-1033:QuickSearch:#####
ResourceSpec
Constraint: PropertyConstraint
TargetType: QuickSearch
PropertyName: searchTerm
Comparator: EQUALS
ComparableValue: (java.lang.String) 0
PropertySpec[1]
ProviderType: QuickSearch
Relationship: null
Properties[5]
PropertyName: name
PropertyName: config.ftInfo[@type='FaultToleranceSecondaryConfigInfo'].primaryVM
PropertyName: config.managedBy
PropertyName: config.template
PropertyName: isPodVM
ResultSpec:
Offset: 0
MaxResultCount: 10
OrderingCriteria
OrderPropertySpec[1]
ProviderType: Object
Environment
vCenter Server with Active Directory identity source.
Cause
This is more related to IWA (Integrated Windows Authentication) for domains with multiple domain controllers where any domain controller can respond to the request instead of specific domain controllers near to the vCenter network.
Resolution
Considering IWA is being removed from newer versions (https://knowledge.broadcom.com/external/article/314324/)
Change the IWA to Active Directory over LDAP (or LDAPs) and define specific domain controllers accessible to the vCenter.
If not using IWA, make sure the domain controllers used are specific ones near to the vCenter to avoid timeouts.
Feedback
