Failed to add match 'elasticsearch': Invalid argument

Hi,

I have the following issue after upgrading Elasticsearch from 6.8.22 to 7.14.2.

When trying to start the service:
Job for Elasticsearch.service failed because the control process exited with error code. See "systemctl status Elasticsearch.service" and "journalctl -xe" for details.

journalctl -xe Elasticsearch

Failed to add match 'Elasticsearch': Invalid argument
Failed to add filters: Invalid argument

journalctl -fu Elasticsearch

-- Logs begin at Tue 2021-11-16 16:44:59 EST. --
Jan 14 03:44:28 my-server systemd-entrypoint[4161]: Error: A fatal exception has occurred. Program will exit.
Jan 14 03:44:28 my-server systemd-entrypoint[4161]: at org.Elasticsearch.tools.launchers.JvmOption.flagsFinal(JvmOption.java:119)
Jan 14 03:44:28 my-server systemd-entrypoint[4161]: at org.Elasticsearch.tools.launchers.JvmOption.findFinalOptions(JvmOption.java:81)
Jan 14 03:44:28 my-server systemd-entrypoint[4161]: at org.Elasticsearch.tools.launchers.JvmErgonomics.choose(JvmErgonomics.java:38)
Jan 14 03:44:28 my-server systemd-entrypoint[4161]: at org.Elasticsearch.tools.launchers.JvmOptionsParser.jvmOptions(JvmOptionsParser.java:135)
Jan 14 03:44:28 my-server systemd-entrypoint[4161]: at org.Elasticsearch.tools.launchers.JvmOptionsParser.main(JvmOptionsParser.java:86)
Jan 14 03:44:28 my-server systemd[1]: Elasticsearch.service: main process exited, code=exited, status=1/FAILURE
Jan 14 03:44:28 my-server systemd[1]: Failed to start Elasticsearch.
Jan 14 03:44:28 my-server systemd[1]: Unit Elasticsearch.service entered failed state.
Jan 14 03:44:28 my-server systemd[1]: Elasticsearch.service failed.

I run my ELK Stack on RedHat Linux and used rpm package for the upgrade.

I added the following lines to my Elasticsearch.yml as I know this is required configuration for all versions after 7.0.
discovery.seed_hosts:

  • master_node_name_or_ip_address

cluster.initial_master_nodes:

  • master_node_name_or_ip_address

I checked my yml and it is a valid file.

Do you have any clues what might be the problem here?

Thank you!
PP

The issue were fixed by commeting these three lines in jvm.options:
#-XX:+UseConcMarkSweepGC
#-XX:CMSInitiatingOccupancyFraction=75
#-XX:+UseCMSInitiatingOccupancyOnly