# Just tried out ELK stack v7.13 but found two issues **URL:** \ **Category:** Elasticsearch\ **Created:** [June 16, 2021, 1:25am UTC](https://discuss.elastic.co/t/just-tried-out-elk-stack-v7-13-but-found-two-issues/276068 "2021-06-16T01:25:47Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![vincetai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vincetai/32/90372_2.png) [@vincetai](https://discuss.elastic.co/u/vincetai)\ **Post date:** [June 16, 2021, 1:25am UTC](https://discuss.elastic.co/t/just-tried-out-elk-stack-v7-13-but-found-two-issues/276068/1 "2021-06-16T01:25:47Z")
I moved from ELK v6.8.16 to ELK v7.13.2 and found the following issues: - 1. In v6.8.16, when I removed a namespace, Kibana could show such event but it is not happening in v7.13.2 2. The navigation on Kibana web is faster in v7.13.2 compared w/ v6.8.16 but it takes longer time to do a search in v7.13.2 I'm a newbie to ELK stack. Please advise. Thanks a lot. VT ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 16, 2021, 1:26am UTC](https://discuss.elastic.co/t/just-tried-out-elk-stack-v7-13-but-found-two-issues/276068/2 "2021-06-16T01:26:40Z")
Welcome to our community! 😃 It's not clear to me what you mean in your first point. Can you elaborate a little more? As for your second point, how are you measuring this? ---
**Author:** ![vincetai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vincetai/32/90372_2.png) [@vincetai](https://discuss.elastic.co/u/vincetai)\ **Post date:** [June 16, 2021, 1:38am UTC](https://discuss.elastic.co/t/just-tried-out-elk-stack-v7-13-but-found-two-issues/276068/3 "2021-06-16T01:38:54Z")
Thanks for your reply, warkolm. Point 1: i issued "kubectl delete -f ns ibsl" command and such event will be recorded, sent to, and displayed on elasticsearch/kibana v6.8.16. ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/6/b643dd60769d1787042ec436e033f855d749e98c.png) But I couldn't see the event in v7.13.2. For point 2, both ELK stacks were cloned from the same VM instance, and hence, they are of the same hardware spec. 8core cpu + 24g RAM, ubuntu 16.04. when I clicked "Discover" and "Refresh" on Kibana, ELK stack v6.8.16 takes 1 second to show the results of last 15 mins while ELK stack v7.13.2 takes 3 seconds to do the same thing. Thanks. VT ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 16, 2021, 1:42am UTC](https://discuss.elastic.co/t/just-tried-out-elk-stack-v7-13-but-found-two-issues/276068/4 "2021-06-16T01:42:12Z")
> [@vincetai](#): > > But I couldn't see the event in v7.13.2. Just to be clear, you saw it in 6.8, but after upgrading to 7.13 it's not showing? Does the index it was in still exist? ---
**Author:** ![vincetai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vincetai/32/90372_2.png) [@vincetai](https://discuss.elastic.co/u/vincetai)\ **Post date:** [June 16, 2021, 1:43am UTC](https://discuss.elastic.co/t/just-tried-out-elk-stack-v7-13-but-found-two-issues/276068/5 "2021-06-16T01:43:45Z")
no. i have both stacks up and running. both are new installations. no migration. when i compared two i found it. thanks. vt ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 16, 2021, 1:47am UTC](https://discuss.elastic.co/t/just-tried-out-elk-stack-v7-13-but-found-two-issues/276068/6 "2021-06-16T01:47:41Z")
Ok, well if you didn't copy the indices over, or send the existing data to the new cluster, then that's not surprising. ---
**Author:** ![vincetai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vincetai/32/90372_2.png) [@vincetai](https://discuss.elastic.co/u/vincetai)\ **Post date:** [June 16, 2021, 1:51am UTC](https://discuss.elastic.co/t/just-tried-out-elk-stack-v7-13-but-found-two-issues/276068/7 "2021-06-16T01:51:09Z")
but i tested it separately. k8s cluster 1 is sending logs to v6.8 k8s cluster 2 is sending logs to v7.13 that is a new kubectl command i issued. event was logged on v6.8 but not on v7.13 i'm wondering if such event was filtered on logstash or filebeat or any component? any way I can enable to accept all logs from k8s? thanks. VT ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 16, 2021, 1:57am UTC](https://discuss.elastic.co/t/just-tried-out-elk-stack-v7-13-but-found-two-issues/276068/8 "2021-06-16T01:57:13Z")
And you issued that command on both kubernetes clusters? Did you confirm that the second cluster actually created that in it's logging output? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 14, 2021, 1:57am UTC](https://discuss.elastic.co/t/just-tried-out-elk-stack-v7-13-but-found-two-issues/276068/9 "2021-07-14T01:57:19Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.