I have just upgraded ElasticSearch 5.5.2 on a simple 2 node Windows cluster. Running Kibana in discover works only for a few seconds, after which it will crash with " Unable to get property 'data' of undefined or null reference (http://localhost:5601/bundles/kibana.bundle.js?v=15443:111) ". Browser IE11.
I did a search and found this discussion, where it states that this bug is present in 5.6.0 and was introduced in 5.5.2:
Last autumm ElasticSearch had a huge error in setting up Garbage collection on Windows 4.x , which resulted in a ton of crashes . Highly embarrasing. Lack of testing.
Which lead me to my question. Why are you releasing this kind of poor quality? I absolutely love this product and want to make it known and accepted in the Enterprise world, where you are competing with Splunk and Arcsight and others, but these kind of bugs are totally unacceptable. I find that upgrading an Elastic cluster to a new version is always a risky business, wondering what is broken this time.
Before you release any kind of new version of Kibana , you should be doing quality control and making sure , it works in all major browsers. An acceptance test would have caught this error in a heartbeat.
I wonder if you are sacrificing build quality in order to pump out new versions faster than you are able to keep up with.
Again , I love this product and it has saved me many times , but it is highly frustrating to have new errors to cope with every single time I upgrade.