Early this morning, users around the world reported hacks of their unsecured Elasticsearch clusters. A data ransoming group attacked vulnerable clusters they found on cloud providers. This follows the widely reported instances of tens of thousands of MongoDB databases being ransomed last week. Copycats virally spread the ransoming, and the copycatting has now apparently spread to Elasticsearch.Keep reading
Qbox clients have the advantage of Virtual Public Cloud peering. With this networking connection, password protection or IP whitelisting becomes fail-safe against the unlikely scenario where AWS has a glitch in the configuration of a network. VPC peering promises data "sovereignty," assuring any data in the Qbox cluster is only sent to the requesting VMs owned by the customer.
In this article, we give a brief overview of this connection, its basics, and the process to enable it.
A key question in the minds of most Elasticsearch users when they create an index is “How many shards should I use?" In this article, we explain the design tradeoffs and performance consequences of choosing different values for the number of shards. Continue reading if you want to learn how to demystify and optimize your sharding strategy.Keep reading
We recently wrote about how we're extending our global reach by offering many new SoftLayer data centers. We're glad to bring you more good news today: Qbox users can now run Elasticsearch clusters on any of our 10 new Microsoft Azure Data centers.
This expansion brings us to a total of 47 data centers worldwide. It is yet another in a series of recent achievements -- all part of our plan to greatly increase the flexibility of our infrastructure and widen the range of options for search-as-a-service.Keep reading
We always make time for our customers. That's a fact. And today we announce an even stronger commitment to our dedication to first-rate customer service. We're always thinking about the next best step to improve the support experience and weave our hosted Elasticsearch community more tightly together.
We've just taken another step in that direction by implementing a two-way intercom. Our support team is available round-the-clock. Anytime you need us, we're just a click away. Keep reading to learn about all of the goodness that we just put in place for you.Keep reading
If you're got a home-grown Elasticsearch environment, then you might not be thinking about backup automation. You might be relying on a very primitive backup solution, one that doesn't offer any of our advanced features. If you're like we were back in the day, you've got some rough measure of data security—at the cost of flexibility and periodic lapses in cluster responsiveness.
Although we've had backup and restore capability for quite sometime now, we're realizing that it's good to make a followup announcement. We have an automatic daily backup feature, which is built around the snapshot/restore API from Elasticsearch. Take a moment to read through this article and consider your options on backup and restore.Keep reading
Qbox has become the premier provider of hosted Elasticsearch services. The project began as a more economical solution to Amazon's Cloudsearch, but we quickly got caught up in the flexibility and power of Elasticsearch.
Now, several years later, we're enjoying steady growth as we help Elasticsearch developers and ops staff reduce their aches and pains — while lowering their overall operating costs. We invite you to read this article for an overview of the major considerations of launching and scaling Elasticsearch clusters.Keep reading
After a long wait, backup restoration functionality is now available in the Qbox dashboard. In addition, cluster "cloning" is now available, which allows for quick and easy Elasticsearch dataset copying onto new hardware.Keep reading
Disk I/O is a major component of any database system, and Elasticsearch is no exception. Elasticsearch, along with most modern databases, makes heavy use of filesystem cache (RAM) to optimize performance. However, when persistence is needed -- and it's needed often -- the disk is used. Heavy disk use under a high load can cause a bottleneck with I/O wait, which is a big factor in performance loss.
That being said, it can't hurt to have blazing fast hard drives as a foundation. With Elasticsearch, faster disk writes = faster indexing, faster disk reads = faster searching.Keep reading