[GitHub] [skywalking] xsisno1 opened a new issue #3529: skywalking cannot write ElasticSearch trace data that is not current time

[GitBox <gi...@apache.org>]

xsisno1 opened a new issue #3529: skywalking cannot write ElasticSearch trace data that is not current time
URL: https://github.com/apache/skywalking/issues/3529
 
 
   Question
   
   When we use ElasticSearch as a store, we find that skywalking adds the current date to the index name when creating the index, but this will cause trace data that is not the current date to fail to write to the index. Here's an example: Set skywalking TTL time =2 days. When skywalking starts, create ElasticSearch index with the name of segment-20190924. Here, all data of 2019-09-24 will be written into this index, but when 2019-09-25, skywalking will fail to write. The reason is that the index name of skywalking when it writes trace data is segment-20190925, which actually does not exist in ElasticSearch. However, at 2019-09-26, after the previously created index named segment-20190924 was deleted by skywalking due to expiration, skywalking will create a new index named segment-20190926. Then 2019-09-26 trace data starts to be written into ElasticSearch. 
   
   How can we solve this problem?

----------------------------------------------------------------
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