You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2020/02/13 14:30:39 UTC

[GitHub] [skywalking] aderm commented on issue #4353: Optimizing performance reduces es index queries scope by timebucket

aderm commented on issue #4353: Optimizing performance reduces es index queries scope by timebucket
URL: https://github.com/apache/skywalking/pull/4353#issuecomment-585783014
 
 
   There is indeed a problem that needs to determine whether the index exists. The better way I thought at the time was if it was found that the query part of the index does not exist, if ES can query part of the index, and there is a configuration that can be set to not report an error.
   
   Regarding the narrow gap time, this commit has optimization is that if it is not found in the cache, it will query ES again to ensure that the index name list is up to date. If you want to be more precise in fine-grained time, for example ms level, the index change after index query, it may be that the current query will report an error(currently this situation will only occur in the early morning). It will have correct result query again without affecting subsequent queries. 
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services