You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Zhitao Li (JIRA)" <ji...@apache.org> on 2016/04/06 23:28:25 UTC
[jira] [Created] (MESOS-5131) DRF allocator crashes master with
CHECK when resource is incorrect
Zhitao Li created MESOS-5131:
--------------------------------
Summary: DRF allocator crashes master with CHECK when resource is incorrect
Key: MESOS-5131
URL: https://issues.apache.org/jira/browse/MESOS-5131
Project: Mesos
Issue Type: Bug
Components: allocation, oversubscription
Reporter: Zhitao Li
Priority: Critical
We were testing a custom resource estimator which broadcasts oversubscribed resources, but they are not marked as "revocable".
This unfortunately triggered the following check in hierarchical allocator:
{quote}
void HierarchicalAllocatorProcess::updateSlave(
// Check that all the oversubscribed resources are revocable.
CHECK_EQ(oversubscribed, oversubscribed.revocable());
{quote}
This definitely shouldn't happen in production cluster. IMO, we should do both of following:
1. Make sure incorrect resource is not sent from agent (even crash agent process is better);
2. Decline agent registration if it's resources is incorrect, or even tell it to shutdown, and possibly remove this check.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)