A needed help About Es expection "without one being designated as a write index" when creating a new profile task

[sunrongxin7666]

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• Question or discussion

---

Question

• What do you want to know?
  Similarly with When i click new task，backend log output reason=no write index is defined for alias [skywalkinges_profile_task] #4729 ，I find an errors "The write index may be explicitly disabled using is_write_index=false or the alias points to multiple indices without one being designated as a write index" when creating a new profile task. However I am sure that I have pulled the lastest code in master branch.
  

There are multiple indices with alias "profile_task" in my Es and the latest "Write Index" also exists

If "profile_task-20200516" is set as "is_write_index" = true, it will work without this error. But other metrics indexes with the same alias can work well without doing this.

It is also a TTL Bug? Would you mind to share some suggestions to deal with it?

[wu-sheng]

All indexes should be created based on the template. This seems very strange.

[wu-sheng]

Seems I could reproduce this issue locally, but don't know why for now.