Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

determine healthy disk size #30

Closed
spacejam opened this issue Aug 18, 2015 · 2 comments
Closed

determine healthy disk size #30

spacejam opened this issue Aug 18, 2015 · 2 comments

Comments

@spacejam
Copy link
Contributor

during load testing, some etcd nodes crashed during log compaction with the following error:

2015/08/17 17:24:41 etcdserver: raft save state and entries error: write etcd_data/member/wal/000000000000001f-00000000007582d2.wal: no space left on device

As can be seen at etcd-io/etcd#3300, etcd can use double the required disk space to complete a compaction. We need to determine a safe size for most workloads to safely exist in the mesos sandbox.

@jdef
Copy link
Contributor

jdef commented Aug 18, 2015

i've seen my mesos cluster crash in fun ways too (and, not surprisingly,
docker). the joys of storage.. it's a problem for everyone.

i'm not sure what the state of disk reservation is in core, but mesos-go
just upgraded to the 0.23 protos (warning: has probably not seen very much
testing).

On Mon, Aug 17, 2015 at 8:35 PM, Tyler Neely notifications@github.com
wrote:

during load testing, some etcd nodes crashed during log compaction with
the following error:

2015/08/17 17:24:41 etcdserver: raft save state and entries error: write etcd_data/member/wal/000000000000001f-00000000007582d2.wal: no space left on device

As can be seen at etcd-io/etcd#3300
etcd-io/etcd#3300, etcd can use double the
required disk space to complete a compaction. We need to determine a safe
size for most workloads to safely exist in the mesos sandbox.


Reply to this email directly or view it on GitHub
#30.

@spacejam
Copy link
Contributor Author

this is now fully configurable #33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants