# Moved to OSS...xpack settings left behind. How to remove?

**URL:** <https://discuss.elastic.co/t/moved-to-oss-xpack-settings-left-behind-how-to-remove/236063>\
**Category:** Elasticsearch\
**Created:** [June 7, 2020, 12:35am UTC](https://discuss.elastic.co/t/moved-to-oss-xpack-settings-left-behind-how-to-remove/236063 "2020-06-07T00:35:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![pszm](https://avatars.discourse-cdn.com/v4/letter/p/e36b37/32.png) [@pszm](https://discuss.elastic.co/u/pszm)\
**Post date:** [June 7, 2020, 12:35am UTC](https://discuss.elastic.co/t/moved-to-oss-xpack-settings-left-behind-how-to-remove/236063/1 "2020-06-07T00:35:57Z")

</div>

We upgraded from 6.8.1 default to 7.7.1 oss (unintentionally, but whats done is done).  
Now the issue is that there are xpack settings left behind. How to remove these?  
Specifically, in our cluster settings:

```auto
curl -X GET "localhost:9200/_cluster/settings?pretty"
{
  "persistent" : {
    "archived" : {
      "xpack" : {
        "monitoring" : {
          "collection" : {
            "enabled" : "true"
          }
        }
      }
    },
    "cluster" : {
      "routing" : {
        "allocation" : {
          "enable" : "primaries"
        }
      }
    }
  },
  "transient" : { }
}

```

No changes can be made to cluster settings because we always get this error:

```auto
{
  "error" : {
    "root_cause" : [
      {
        "type" : "illegal_argument_exception",
        "reason" : "unknown setting [archived.xpack.monitoring.collection.enabled] please check that any required plugins are installed, or check the breaking changes documentation for removed settings"
      }
    ],
    "type" : "illegal_argument_exception",
    "reason" : "unknown setting [archived.xpack.monitoring.collection.enabled] please check that any required plugins are installed, or check the breaking changes documentation for removed settings"
  },
  "status" : 400
}

```

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [June 7, 2020, 6:55am UTC](https://discuss.elastic.co/t/moved-to-oss-xpack-settings-left-behind-how-to-remove/236063/2 "2020-06-07T06:55:22Z")

</div>

You have to remove all the unrecognised "archived" settings at once:

```auto
PUT _cluster/settings
{"persistent":{"archived.*":null}}

```

Elasticsearch doesn't do this automatically in case archiving them was a mistake, so you need to remove them explicitly before you can do anything else.

---

<div class="post-metadata">

**Author:** ![pszm](https://avatars.discourse-cdn.com/v4/letter/p/e36b37/32.png) [@pszm](https://discuss.elastic.co/u/pszm)\
**Post date:** [June 7, 2020, 8:40am UTC](https://discuss.elastic.co/t/moved-to-oss-xpack-settings-left-behind-how-to-remove/236063/3 "2020-06-07T08:40:46Z")

</div>

You are the man!  
I could not find this info anywhere. This has also solved my cluster replication issues.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2020, 8:40am UTC](https://discuss.elastic.co/t/moved-to-oss-xpack-settings-left-behind-how-to-remove/236063/4 "2020-07-05T08:40:47Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.