You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Dylan, I tried to reproduce this with an analogous setup: agents offering 36GB of ROOT disk space, 40GB of MOUNT disk space, and with the Cassandra scheduler set up to expect 38GB of ROOT disk space (running scheduler version 1.0.25-3.0.10). I saw the expected behavior, which is that all incoming offers were rejected and no task launch or volume creation was attempted. Can you give some more details about your setup? DC/OS version, Cassandra version, scheduler configuration on launch?
Seems to be two separate issues here. Mesos agent is configured with ~15Gb ROOT disk resource, cassandra is looking for 20Gb. See offer here:
Cassandra decides to accept this insufficient offer:
But after launching receives failed notification from master
And finally on attempting to relaunch is unable to as it cannot find the non existent peristence id
From the master logs:
The text was updated successfully, but these errors were encountered: