Jepsen: MongoDB 3.6.4
In February 2017, we discussed data loss and fixes in MongoDB 3.4.0-rc3’s v0 and v1 replication protocols. In this Jepsen report, we will verify that MongoDB 3.6.4’s sharded clusters offer comparable safety to non-sharded deployments. We’ll also discuss MongoDB’s new support for causal consistency (CC) in version 3.6.4 and 4.0.0-rc1, and show that sessions prevent anomalies so long as user stick t
Chaos Engineering
Read it now on the O’Reilly learning platform with a 10-day free trial. O’Reilly members get unlimited access to books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers. With so many interacting components, the number of things that can go wrong in a distributed system is enormous. You’ll never be able to prevent all possible failure modes, but you can
Hexing the technical interview
Previously: Reversing the technical interview. Long ago, on Svalbard, when you were a young witch of forty-three, your mother took your unscarred wrists in her hands, and spoke: Vidrun, born of the sea-wind through the spruce Vidrun, green-tinged offshoot of my bough, joy and burden of my life Vidrun, fierce and clever, may our clan’s wisdom be yours: Never read Hacker News But Hacker News has rea
Jepsen: Dgraph 1.0.2
Dgraph is a distributed graph database which uses Raft for per-shard replication and a custom transactional protocol, based on Omid, Reloaded, for snapshot-isolated cross-shard transactions. Dgraph claimed to offer snapshot isolation, per-client monotonicity, and linearizability. However, in Dgraph 1.0.2 through 1.0.6, we found multiple deadlocks & crashes in the cluster join and node recovery pro
Consistency
We present a variety of consistency models and database phenomena with approachable explanations and links to the literature. These models are often defined in terms of dependencies between operations. We aim to make consistency properties accessible for industry practitioners, academics, and enthusiasts. Models A consistency model is a safety property which declares what a system can do. Formally
Asynchronous replication with failover
In response to my earlier post on Redis inconsistency, Antirez was kind enough to help clarify some points about Redis Sentinel’s design. First, I’d like to reiterate my respect for Redis. I’ve used Redis extensively in the past with good results. It’s delightfully fast, simple to operate, and offers some of the best documentation in the field. Redis is operationally predictable. Data structures a
Chaos Monkeyアップデート
NetflixはChaos Monkeyのアップグレードを発表した。Chaos MonkeyはSoftware as a Serviceの弾力性を改善するための汎用ツールであり、サービス提供時間中にランダムにサーバやコンテナを停止する。今回のアップグレードで、Chaos MonkeyはSpinnakerと統合された。SpinnakerはNetflixの継続的デリバリのプラットフォームであり、さまざまなクラウドプラットフォームで利用できる。同社のDockerコンテナのプラットフォームであるTitusも対応している。 Chaos MonkeyはSpinnakerを経由して構成情報を受信し、この情報を使うことでChaos Monkeyはリソースの停止をスケジューリングして実行する。これによって停止のスケジューリングのユーザ体験が向上できる。アプリやスタック、クラスタをグループ化できる。また、さま
Jepsen: Aerospike 3.99.0.3
Aerospike is a high-performance distributed document store. Following up on our 2015 analysis, we explored Aerospike’s new strong-consistency mode, which offers linearizable operations on single records. We confirmed two documented flaws in Aerospike’s homegrown replication algorithm. First, it can lose updates when more than k nodes crash (either concurrently or in sequence). Second, when either
Bloomberg - Are you a robot?
We've detected unusual activity from your computer network To continue, please click the box below to let us know you're not a robot. Why did this happen? Please make sure your browser supports JavaScript and cookies and that you are not blocking them from loading. For more information you can review our Terms of Service and Cookie Policy. Need Help? For inquiries related to this message please co
GitHub - simonmunro/ChaosMonkey: Chaos Monkey is a .NET based app that randomly selects a tagged AWS instance and terminates it
The Chaos Monkey originated with Netflix, who built a Chaos Monkey in order to test that they can consistently handle failure. Partly because of its name and partly because the idea of randomly terminating production servers is an absurd check of fault tolerate architectures, the Chaos Monkey concept took a life of its own and has become part of AWS legend. Werner Vogels even kicked off a t-shirt
米Netflix、AWSに対応するクラウドインフラ向け障害テストツール「Chaos Monkey」をリリース | OSDN Magazine
ネットを利用したビデオレンタルサービス大手の米Netflixは7月30日、Amazonクラウドインフラストラクチャ向けの障害テストツール「Chaos Monkey」をオープンソースソフトウェアとして公開した。クラウドインフラストラクチャ内での障害を意図的に発生させるツールで、アプリケーションの耐障害性をテストできるという。 Chaos MonkeyはAmazon Web Services（AWS）クラウドでホストされている環境の耐障害性をテストするシステム。インターネット経由でのDVDレンタルサービスやオンラインでの動画ストリーミングサービスを展開しているNetflixはクラウドを多用してシステムを構築しており、さまざまな障害シナリオに対応するために開発したという。 Chaos Monkeyはクラウドシステムで運用中のインスタンスをランダムに無効にし障害を引き起こす機能を持つ。これにより、
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
GitHub - adhorn/aws-chaos-scripts: DEPRECATED Collection of python scripts to run failure injection on AWS infrastructure
Chaos Engineering Bootcamp
障害ヲ抱擁セヨ──大規模クラウドサービスをマイクロサービスアーキテクチャで作るNetflixが実践する障害注入テスト（FIT）とは何か | さくらのナレッジ
カオスエンジニアリングによるAPIの回復力の向上
GitHub - powerfulseal/powerfulseal: A powerful testing tool for Kubernetes clusters.
IBM Developer
IBM Developer
GitHub - Netflix/SimianArmy: Tools for keeping your cloud operating in top form. Chaos Monkey is a resiliency tool that helps applications tolerate random instance failures.
NetflixがChaos Monkeyをオープンソースに
