yes that sounds plausible. those two jobs will both load entries to index. you can quickly test by disabling the incremental one (why do you need it anyway?) and try again
After more investigation, turned out this happens even when incremental job is not started simultanously. I found out what kind of time out it was, and found the following page: https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/performance/troubleshoot-query-timeouts
Is it possible to set SqlCommand.CommandTimeout in a overriding fashion for Episerver fullindex search building?
No, the setting would affect the whole site and would require site restart(s). could you look into your database to see why it's timed out? i.e. see the query and execution plan
Are you reffering to the execution plan for this?: ecf_CatalogEntrySearch_GetResults @quan
I am seeing the following error when the FullIndexJob fails:
"Mediachase.Search.IndexBuildException: Build Failed using "catalog" indexer. "Exception in ecf_CatalogEntrySearch_GetResults: " ---> System.Exception: Exception in ecf_CatalogEntrySearch_GetResults: ---> System.Data.SqlClient.SqlException: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception: The wait operation timed out"
At the exact time one the full index job fails the incremental index jobs is supose to start. Is it possible, under some circumstances, that they can interfere?