Hi @Ankur_Khare ,I realize that I have typo will putting the heading. Its not 10000 nodes its 100000 nodes actually. Regards,@AmanK24 

Thank you @Ankur_Khare , We have referred http://oakutils.appspot.com/generate/index and generated the index. Our system currently hold 11TB+ data which results in the total number of  1.1 millions assets.And when we perform search, we have to perform on the entire assets.        These assets are ca...

@lukasz-m ,Please find the state of the custom index as below.Type : luceneAsync : trueAsync lane name : asyncLast indexed up to : 2021-10-17T03:06:48.112ZLast updated time : 2021-10-15T23:08:43.111ZSize : 501.3 MBEstimated entry count : 1184743 Note: The core application functionality of the applic...

Hi @lukasz-m  No I am getting issue even after creating custom index. As i am saying we have already more than 100000 assets.Yes, the custom index is only picked.Also yes re index after creation of custom index.What i feel is my index count might be more than 100000.

Thank you @lukasz-m  for approaches.I have few constraint here:1. Assets Share Commons is used for generation of Query.2. I need to make query with all the number of asset present that's the req. as we cant afford of skipping any search result.3. I have already create custom Lucene index for dam:ass...

Hi Team,                We are facing search query traversal issue i.e. “The query read or traversed more than 100000 nodes. To avoid affecting other tasks, processing was stopped.”We have assets stored under the “/content/dam/<project>/<sub-module>”. We are also using Asset share commons 1.94. vers...