Article Content
| Issue | VxRail Manager shows 0% storage IOPS even if the cluster is subject to workload and I/O is flowing. There is no impact on production but the dashboard still reports incorrect I/O information: |
| Cause | The cause of failing to run the script is determined by vCenter which takes too long to respond to VxRail Manager's query: May 01 13:30:39,947 GMT 2017 ERROR [myScheduler-3] ScriptServiceImpl.runLocalScript:408 - Killing script after timeout - taken maximum 10000 ms. May 01 13:30:39,950 GMT 2017 WARN [myScheduler-3] ScriptServiceImpl.runLocalScript:443 - [/usr/lib/vmware-marvin/marvind/webapps/ROOT/WEB-INF/classes/scripts/query-vsan-stats.py]: Timed out, null return code. You would typically find VSAN query failures in the Web.log as well: Line 17663: 2016-09-12T17:57:51Z ERROR c.v.m.c.s.s.VsanIopStatsService:96 - Failed running vsan stats query script. Line 17665: 2016-09-12T18:03:52Z ERROR c.v.m.c.s.s.VsanIopStatsService:96 - Failed running vsan stats query script. |
| Resolution | Enhancement has been made to bump up the default timeout from 10 to 30 seconds. Above change is tentatively expected in a future VxRail release version. |
