Enabling Elasticsearch on a Node

What is Elasticsearch?

Elasticsearch is a free search engine used for finding and indexing schema-free JSON documents. This makes viewing large data stores fast and simple. For our purposes, Elasticsearch is most useful for full nodes which host all account histories on the blockchain.
For more information, see the Elasticsearch Wikipedia page.

Enabling Elasticsearch on a Node

Elasticsearch is already installed along with the Witness node. There's no need to do any install for Elasticsearch. You just have to set up the config to enable its use.
Enabling Elasticsearch is as simple as editing the node config file. First you'll add the Elasticsearch plugins to the list of active plugins. Then you'll add the Elasticsearch URL to a couple of options within the config.

Editing the configuration for Elasticsearch

Inside ./witness_node_data_dir/config.ini edit the following:
Uncomment plugins = and add the elasticsearch and es_object plugins.
# Space-separated list of plugins to activate
plugins = elasticsearch es_objects
Uncomment elasticsearch-node-url = and add the Endpoint URL for your Elasticsearch instance.
Make sure to keep the trailing slash at the end of the URL.
# Elastic Search database node url(http://localhost:9200/)
elasticsearch-node-url = <ES-ENDPOINT>
Unless you makes some custom changes to the Elasticsearch configuration, the endpoint url is going to be http://localhost:9200/. So your config in this case will be:elasticsearch-node-url = http://localhost:9200/
Uncomment es-objects-elasticsearch-url = and add the Endpoint URL for your Elasticsearch instance.
Make sure to keep the trailing slash at the end of the URL.
# Elasticsearch node url(http://localhost:9200/)
es-objects-elasticsearch-url = <ES-ENDPOINT>
Like the last one, unless you make some changes to your Elasticsearch config, the endpoint url is going to be http://localhost:9200/. So your config in this case will be:es-objects-elasticsearch-url = http://localhost:9200/

Start the witness node

Start the witness node to being pushing indexes to Elasticsearch. The beginning few logs should show the Elasticsearch plugins started:
572387ms th_a elasticsearch_plugin.cpp:516 plugin_startup ] elasticsearch ACCOUNT HISTORY: plugin_startup() begin
572387ms th_a application.cpp:1235 startup_plugins ] Plugin elasticsearch started
572395ms th_a es_objects.cpp:405 plugin_startup ] elasticsearch OBJECTS: plugin_startup() begin
572395ms th_a application.cpp:1235 startup_plugins ] Plugin es_objects started ...
575659ms th_a es_objects.cpp:82 genesis

Basic Checks

You can check the indexes created after the witness start with the next call:
$ curl -X GET '<ES-ENDPOINT>/_cat/indices'
yellow open ppobjects-asset vnF2F0BMSKKNxQfu013OCQ 1 1 2 0 12.4kb 12.4kb
yellow open ppobjects-balance 3psSvHIeRC-fKHyqP2Legg 1 1 1 0 5.9kb 5.9kb
yellow open ppobjects-account zQ7uv01ESEeqCED3WHmmxg 1 1 21 0 42.4kb 42.4kb
You can also get index search data with:
curl -X GET '<ES-ENDPOINT>/peerplays-*/data/_search?pretty=true' -H 'Content-Type: application/json'
Export as PDF
Copy link
On this page
What is Elasticsearch?
Enabling Elasticsearch on a Node
Editing the configuration for Elasticsearch
Start the witness node
Basic Checks