最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

Upgrading OpenSearch cluster on aws from Elasticsearch 6.8 OSS to OpenSearch 1.3 and 2.17 - Stack Overflow

programmeradmin3浏览0评论

I’m managing AWS OpenSearch cluster with indexes created in Elasticsearch 6.8 OSS which I successfully manage to reindex to OpenSearch 1.3 and 2.17 compatible versions. When I run eligibility check for the update to 2.17, I’m getting:

Check eligibility - Failed

The following indices are not compatible with the target Elasticsearch version OS_2.17 - .opendistro-ism-config. Please refer to our documentation .html for tips to address this issue

I’ve tried to reindex .opendistro-ism-config but it didn’t help, nether to I’m able to delete the index, because I’m getting

{
    "error": {
        "root_cause": [
            {
                "type": "security_exception",
                "reason": "no permissions for [] and User [name=administrator, backend_roles=[], requestedTenant=null]"
            }
        ],
        "type": "security_exception",
        "reason": "no permissions for [] and User [name=administrator, backend_roles=[], requestedTenant=null]"
    },
    "status": 403
}

How can mitigate the issue and upgrade the cluster to the latest openserach version?

I’m managing AWS OpenSearch cluster with indexes created in Elasticsearch 6.8 OSS which I successfully manage to reindex to OpenSearch 1.3 and 2.17 compatible versions. When I run eligibility check for the update to 2.17, I’m getting:

Check eligibility - Failed

The following indices are not compatible with the target Elasticsearch version OS_2.17 - .opendistro-ism-config. Please refer to our documentation https://docs.aws.amazon/elasticsearch-service/latest/developerguide/es-version-migration.html for tips to address this issue

I’ve tried to reindex .opendistro-ism-config but it didn’t help, nether to I’m able to delete the index, because I’m getting

{
    "error": {
        "root_cause": [
            {
                "type": "security_exception",
                "reason": "no permissions for [] and User [name=administrator, backend_roles=[], requestedTenant=null]"
            }
        ],
        "type": "security_exception",
        "reason": "no permissions for [] and User [name=administrator, backend_roles=[], requestedTenant=null]"
    },
    "status": 403
}

How can mitigate the issue and upgrade the cluster to the latest openserach version?

Share Improve this question asked Mar 17 at 10:00 ROZZROZZ 1,4543 gold badges21 silver badges38 bronze badges
Add a comment  | 

1 Answer 1

Reset to default 0

I contacted the AWS support team, and it turned out that someone with super admin rights needs to reindex it.

发布评论

评论列表(0)

  1. 暂无评论