GCS repository plugin - restart node (docker)


I'm used following Install Elasticsearch with Docker | Elasticsearch Reference [5.6] | Elastic to span up elasticsearch cluster and now trying to integrate Google Cloud Storage Repository Plugin | Elasticsearch Plugins and Integrations [5.6] | Elastic as well...

I'll quote part of "Google Cloud Storage Repository Plugin" document:

The plugin must be installed on every node in the cluster, and each node must be restarted after installation.

I was able to install plugin without any issue, however restarting node/service is another issue:

root@elk11:~# docker exec -it elasticsearch11 bash
[elasticsearch@1231f1e0307c ~]$ bin/elasticsearch-plugin install repository-gcs
-> Downloading repository-gcs from elastic
[=================================================] 100%?? 
@     WARNING: plugin requires additional permissions     @
* java.lang.RuntimePermission accessDeclaredMembers
* java.lang.RuntimePermission setFactory
* java.lang.reflect.ReflectPermission suppressAccessChecks
* java.net.URLPermission http://www.googleapis.com/* *:
* java.net.URLPermission https://www.googleapis.com/* *:
See http://docs.oracle.com/javase/8/docs/technotes/guides/security/permissions.html
for descriptions of what these permissions allow and the associated risks.

Continue with installation? [y/N]y
-> Installed repository-gcs
[elasticsearch@1231f1e0307c ~]$ systemctl status elasticsearch
Failed to get D-Bus connection: Operation not permitted
[elasticsearch@1231f1e0307c ~]$ sudo systemctl status elasticsearch
bash: sudo: command not found
[elasticsearch@1231f1e0307c ~]$ service
bash: service: command not found
[elasticsearch@1231f1e0307c ~]$ exit
root@elk11:~/elastic/elasticsearch# docker-compose ps
     Name                 Command           State                Ports              
elasticsearch11   /bin/bash bin/es-docker   Up>9200/tcp, 9300/tcp
root@elk11:~/elastic/elasticsearch# docker-compose restart
Restarting elasticsearch11 ... done

I'm not sure how to restart node (service) other then restarting the whole docker container itself, If this isn't right way to go about it, what's the better way?

Please advise.

(system) #2

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