Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Warning on ES service status - An illegal reflective access operation has occurred #214

Open
sarthi2395 opened this issue Oct 7, 2020 · 2 comments
Assignees

Comments

@sarthi2395
Copy link

Describe the bug
I installed a RPM based OpenDistro on my Centos7 server and added it as a system service as specified in the installation documents. When I check the status of the service, I get a couple of warnings that asks me to report it to the developers.

To Reproduce
Steps to reproduce the behavior:

  1. Run
systemctl status elasticsearch.service -l
  1. See error
systemd[1]: Starting Elasticsearch...
systemd[1]: Started Elasticsearch.
systemd-entrypoint[9149]: WARNING: An illegal reflective access operation has occurred
systemd-entrypoint[9149]: WARNING: Illegal reflective access by com.amazon.opendistro.elasticsearch.performanceanalyzer.collectors.MasterServiceEventMetrics (file:/usr/share/elasticsearch/plugins/opendistro_performance_analyzer/opendistro_performance_analyzer-1.10.1.0.jar) to field java.util.concurrent.ThreadPoolExecutor.workers
systemd-entrypoint[9149]: WARNING: Please consider reporting this to the maintainers of com.amazon.opendistro.elasticsearch.performanceanalyzer.collectors.MasterServiceEventMetrics
systemd-entrypoint[9149]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
systemd-entrypoint[9149]: WARNING: All illegal access operations will be denied in a future release

Configuration:

  • ODFE/Kibana version - 1.8.0
  • Distribution - RPM
  • Host Machine - Centos7
@peterzhuamazon peterzhuamazon transferred this issue from opendistro-for-elasticsearch/opendistro-build Oct 7, 2020
@peterzhuamazon
Copy link
Contributor

peterzhuamazon commented Oct 7, 2020

According to the logs, this is an issue related to performance analyzer plugin.
I have transferred this issue to the corresponding repo issues section.
Thanks for reporting the issues here @sarthi2395

@ktkrg ktkrg self-assigned this Nov 20, 2020
@ktkrg
Copy link
Contributor

ktkrg commented Jan 15, 2021

@sarthi2395 Thanks for reporting this issue. You can ignore this warning for now. We will work on removing this benign message.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants