You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Tom Coupland (JIRA)" <ji...@apache.org> on 2016/08/24 16:19:20 UTC

[jira] [Commented] (MESOS-6081) Inconsistent state between master state and slave state

    [ https://issues.apache.org/jira/browse/MESOS-6081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15435197#comment-15435197 ] 

Tom Coupland commented on MESOS-6081:
-------------------------------------

Nevermind there appears to be some confusion over this. I'll try and work out exactly what is going on!

> Inconsistent state between master state and slave state
> -------------------------------------------------------
>
>                 Key: MESOS-6081
>                 URL: https://issues.apache.org/jira/browse/MESOS-6081
>             Project: Mesos
>          Issue Type: Bug
>          Components: statistics
>    Affects Versions: 0.28.1
>            Reporter: Tom Coupland
>         Attachments: master_state.json, slave_state.json
>
>
> We're seeing an inconsistent state in regard to a Kafka broker task between the master state json document and the slave state's document. This surfaces as an inconsistency between the dcos cli tool (which pulls the slave state doc) and the mesos webui (which i guess uses the master state document).
> The kafka framework was first installed via the DCOS package system, then removed, then installed via the DCOS cli. We then scaled it to zero in marathon, before ending up here.
> If you look at the attached files, in the master document you can see task: broker-0-9057535c-9455-4f7b-963f-1eb1f3e89241, which it claims is on 156, but when you look in the slave state file you'll find no sign of it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)