- Plugins and Integrations: other versions:
- Introduction to plugins
- Plugin management
- API extension plugins
- Analysis plugins
- ICU analysis plugin
- Japanese (kuromoji) analysis plugin
kuromojianalyzerkuromoji_iteration_markcharacter filterkuromoji_tokenizerkuromoji_baseformtoken filterkuromoji_part_of_speechtoken filterkuromoji_readingformtoken filterkuromoji_stemmertoken filterja_stoptoken filterkuromoji_numbertoken filterhiragana_uppercasetoken filterkatakana_uppercasetoken filterkuromoji_completiontoken filter
- Korean (nori) analysis plugin
- Phonetic analysis plugin
- Smart Chinese analysis plugin
- Stempel Polish analysis plugin
- Ukrainian analysis plugin
- Discovery plugins
- Mapper plugins
- Snapshot/restore repository plugins
- Store plugins
- Integrations
- Creating an Elasticsearch plugin
Changing default transport port
editChanging default transport port
editBy default, Elasticsearch GCE plugin assumes that you run Elasticsearch on 9300 default port.
But you can specify the port value Elasticsearch is meant to use using google compute engine metadata es_port:
When creating instance
editAdd --metadata es_port=9301 option:
# when creating first instance gcloud compute instances create myesnode1 \ --scopes=compute-rw,storage-full \ --metadata es_port=9301 # when creating an instance from an image gcloud compute instances create myesnode2 --image=elasticsearch-1-0-0-RC1 \ --zone europe-west1-a --machine-type f1-micro --scopes=compute-rw \ --metadata es_port=9301
On a running instance
editgcloud compute instances add-metadata myesnode1 \ --zone europe-west1-a \ --metadata es_port=9301
On this page
Was this helpful?
Thank you for your feedback.