Bonsai Blog Posts

[...] would have returned with a 404 error. Bringing in the big guns With one node offline, and index creation still failing intermittently, we enlisted the help of Elasticsearch creator Shay Banon to [...]

[...] found and fixed a small regression in our routing layer, which caused some complications with index creation over the past 24 hours. We felt the issue deserved a post-mortem writeup with more details. [...]

[...] requests would fail with a 502 error, only to apparently succeed a few minutes later, while index creation requests failed entirely. Based on the logs, we saw that servers within the Elasticsearch [...]

[...] release of 0.90: Probably the biggest improvement that our users will notice is much better memory usage when loading fielddata for faceting or sorting on a field. Fielddata uses less memory and [...]

[...] the 25th, when an Elasticsearch node was restarted abruptly to recover from unusual load and memory usage, without having been removed from our load balancers. During that time, a fraction of requests [...]

[...] returned to normal operation, reporting a green state, with normal load levels, CPU and memory usage across all nodes. Total duration of this outage was approximately 20 minutes of hard downtime [...]

[...] Summary On Tuesday, October 29, we experienced an outage on our primary Elasticsearch cluster in our US East region. Up to 20% of our customers in this cluster experienced a total [...]

[...] On Monday, March 5, 2013 we experienced a substantial outage of our production Elasticsearch cluster. We are profoundly sorry for the outage and its affect on our customers and the users and [...]

[...] of degraded performance, and four full cluster restarts, contributing nearly 20 minutes of hard downtime each. Our March uptime, as reported by Pingdom health checks, was 99.73%. That’s the [...]

[...] , Inc. While this upgrade did require a full cluster restart, we were able to limit our hard downtime to about three minutes. All index primary shards were back online in less than ten minutes, [...]

[...] usage across all nodes. Total duration of this outage was approximately 20 minutes of hard downtime for an average index, due to cluster restarts. In addition to that, approximately six [...]

[...] we did experience a small blip: about five seconds of partial 503 responses during a minor system maintenance deploy. However, the issue was automatically corrected, and otherwise our service ran [...]

[...] we did experience a small blip: about five seconds of partial 503 responses during a minor system maintenance deploy. However, the issue was automatically corrected, and otherwise our service ran [...]

[...] for November 2013 was 100%. During November, we performed some notable upgrades to our routing proxy layer, as well as minor release upgrades to Elasticsearch in all our clusters and regions. [...]

[...] for November 2013 was 100%. During November, we performed some notable upgrades to our routing proxy layer, as well as minor release upgrades to Elasticsearch in all our clusters and regions. [...]

[...] not accounted for in our uptime reports. On the 21st, we had a few hours during which index creation requests were failing due to a regression deployed with our multi-index syntax support. Another [...]

[...] would fail with a 502 error, only to apparently succeed a few minutes later, while index creation requests failed entirely. Based on the logs, we saw that servers within the Elasticsearch cluster [...]

[...] recording of last week's webinar by Elasticsearch, Inc. While this upgrade did require a full cluster restart, we were able to limit our hard downtime to about three minutes. All index primary shards [...]

[...] binary itself to affect the cluster settings you need. Expect some failovers to require a full cluster restart. For example, we were unable to set index.recovery.initial_shards via the api, so we were [...]

[...] deployed with our multi-index syntax support. Another was on Monday the 25th, when an Elasticsearch node was restarted abruptly to recover from unusual load and memory usage, without having been [...]