This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 49
Plugin is always disabled #199
Comments
I have the same issue, any news on what prevent the plugin to start? |
Previous version made it start(
…On Mon, Nov 30, 2020, 21:47 Franckiboy15 ***@***.***> wrote:
I have the same issue, any news on what prevent the plugin to start?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#199 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJDZFVXBSON46FYGDSCXVCTSSPZG5ANCNFSM4Q6BY7PA>
.
|
I just update from 1.10.1 to 1.11.0 and I got the same issue |
During startup, cluster API to disable PA does not work. We are working on fixing this (#232) This is a problem only during startup. After re-enabling PA (cluster_state=3), the disable option for PA works fine.
From logs:
Intermittent solution:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am deploying opendistro elasticsearch as single node. And since last week i cannot make this plugin work(before it had worked and i did not change something). In logs i see:
[2020-09-07T11:21:24,156][INFO ][c.a.o.e.p.h.c.PerformanceAnalyzerConfigAction] [a7d349060c8c] PerformanceAnalyzer Enabled: false
I have tried different PCs with fresh docker, deploying by single run command and docker-compose files that are in official documentation.
I POSTed to localhost:9200/_opendistro/_performanceanalyzer/config and /_opendistro/_performanceanalyzer/cluster/config with
{"enabled": true}
or{"pa_enabled": true}
. Anyway it does not work.Every time i redeploy it, i clear everything from docker with
docker system prune -a --volumes
Es version: 1.9.0.
The text was updated successfully, but these errors were encountered: