Qbox to join forces with Instaclustr. Read about it on our blog post here.

Qbox is excited to announce that Phase 1 of integrating Elasticsearch 6.2.1 into cluster provisioning is now complete! 

Extensive development work went into implementing this version of Elasticsearch with Qbox, and we are excited to offer this to the Qbox community.

As always, major version changes contain several breaking changes, which we have summarized below. We highly recommend testing in a staging environment before upgrading your Qbox hosted production environment to Elasticsearch 6.2.1. Feel free to contact our 24/7 support team to assist in your migration.

All credit for this major upgrade is due to the Elasticsearch contributor community under the leadership of Elastic, the company. Much of the documentation cited below links to them.

Release Highlights:

ElasticHQ has been chosen as the built-in monitoring solution because it provides monitoring in real-time, is viewable across multiple devices, and has a friendly, user-centric interface. Kibana has also been updated for your visualization needs.

We currently have the Ingest Attachment Processor plugin available as an option in 6.2.1 and plan to have more plugins available on completion of Phase 2. We look to have Phase 2 completed in a few weeks.

Improvements found in Elasticsearch 6.x:

  1. Cross-Cluster Search
  2. Quicker Restarts and Recovery
  3. Sparsely Populated Fields Enhancement
  4. Improved Query Times
  5. Searching Upgrade
  6. Searching and Indexing NEW Features

Please refer to Elastic’s official Elasicsearch 6.x release page for a complete listing of all improvements.

Many changes have been implemented in Elasticsearch 6.x, so please read over all of Elastic’s official breaking changes documentation to further familiarize yourself with what you may need to change in your code.

Summary of Breaking Changes:

  1. Migrating from Elasticsearch 2.x or before: You will need to reindex with Elasticsearch 5.x so that your indices can be usable in Elasticsearch 6.x. 
    Article:  “Setup Guide”
  2. Mapping types are no longer used: Indices created in 6.x are now restricted to a single type. We feel this may be the largest obstacle for users to overcome. 
    Article: “Removal of Types”
  3. Aggregation revisions: Some changes were made to aggregations. For example, the deprecated ‘pattern’ element has been eliminated. 
    Article: “Breaking 6.0 Aggregations Changes”
  4. Analysis modifications: The Synonym token filter will neglect ‘ignore_case’ and ‘tokenizer’ options on indices created in 6.x. 
    Article: “Breaking 6.0 Analysis Changes”
  5. Adjustments to the Document API: The ’found’ field can no longer be used in the delete API as with the ‘created’ field in the Index API. 
    Article: “Breaking 6.0 Docs Changes”
  6. Examples to modifications in mappings: You are no longer able to use the mapping parameter ‘include_in_all,’ and the ‘_all’ meta field is now disabled.
    Article: “Breaking 6.0 Mappings Changes”
  7. Changes to plugins: Many changes were made to the s3 Repository plugin. We recommend that you read and understand these changes if you use a personal s3 bucket. 
    Article: “Breaking 6.0 Plugins Changes”
  8. Changes to the REST API: Backwards compatibility when using unquoted JSON has been removed. Other changes were made to the REST API, so please examine Elastic’s documentation and study these changes.  
    Article: “Breaking 6.0 Rest Changes”
  9. Streamlining in scripting: Python, JavaScript, and Groovy have been removed, and Painless is now available for your scripting needs. 
    Article: “Breaking 6.0 Scripting Changes”

For further details on all breaking changes implemented in Elasticsearch 6.x and how they can affect you, please consult Elastic’s official documentation. 

When you are ready to migrate your current Qbox Elasticsearch cluster to 6.2.1, please contact the 24/7 support team so that our Support Engineers can assist.

Production issues 1hr

 1 (512) 772-2535

Product questions 4hr Open a ticket
Upgrades, maintenance, migrations 8hr Open a ticket
General Questions 24hr
Open a ticket

Creating a new Elasticsearch 6.2.1 cluster on Qbox:

To create a new Elasticsearch 6.2.1 cluster in your hosted Qbox environment, please follow the below steps:

Qbox: new Elasticsearch cluster

  1. Log into your Qbox account
  2. Click ‘New Cluster’
  3. Choose ‘AWS’
  4. Name your cluster
  5. Select 6.2.1 in the ‘Version’ drop-down
  6. Determine how much ‘RAM’ you would like
  7. Decide on how many ‘Processors’ you need
  8. Assign the number of needed ‘Replicas’
  9. Click ‘Create’

You can also consult our interactive video tutorial on Spinning Up your Qbox Cluster.

To signup for a Qbox account, please click here or contact our Sales Manager, Will, at will@qbox.io.