Upgrading GROWI to v3.8.x
For those using Elasticsearch, the health check method has changed.
The health check method for Elasticsearch
- If you are not using Elasticsearch or you are not using X-Pack role-based access control, this change does not impact you.
- If you are not using Healthcheck API (opens new window) based service health monitoring, this change does not impact you.
Until GROWI v3.7, the Healthcheck API (opens new window)
used Elasticsearch's information acquisition Nodes info API (opens new window).
However, this API requires a very high level privilege called
Therefore, we have changed to use the Cluster health API (opens new window)
instead beginning with GROWI v3.8.
In accordance with this change, setting up X-Pack will require the
Setting required privileges
Please proceed with the following steps to set up your privileges
- Add the
cluster:monitor/healthprivilege to your Elasticsearch authenticated user role.
- If the
cluster:monitor/nodes/infoprivilege is no longer otherwise needed, remove it from your Elasticsearch authenticated user role.
Check before Upgrading
- Check if you are using Elasticsearch and/or X-Pack role-based access control.
- Check that your Elasticsearch authenticated user role has the
- Check if you are using Healthcheck API based service health monitoring