[jira] [Assigned] (MESOS-5496) Implement UPDATE_WEIGHTS Call in v1 master API.
[ https://issues.apache.org/jira/browse/MESOS-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhou xing reassigned MESOS-5496: Assignee: zhou xing > Implement UPDATE_WEIGHTS Call in v1 master API. > --- > > Key: MESOS-5496 > URL: https://issues.apache.org/jira/browse/MESOS-5496 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: zhou xing > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5492) Implement GET_FRAMEWORKS Call in v1 master API.
[ https://issues.apache.org/jira/browse/MESOS-5492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhou xing reassigned MESOS-5492: Assignee: zhou xing > Implement GET_FRAMEWORKS Call in v1 master API. > --- > > Key: MESOS-5492 > URL: https://issues.apache.org/jira/browse/MESOS-5492 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: zhou xing > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5495) Implement GET_WEIGHTS Call in v1 master API.
[ https://issues.apache.org/jira/browse/MESOS-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhou xing reassigned MESOS-5495: Assignee: zhou xing > Implement GET_WEIGHTS Call in v1 master API. > > > Key: MESOS-5495 > URL: https://issues.apache.org/jira/browse/MESOS-5495 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: zhou xing > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5491) Implement GET_AGENTS Call in v1 master API.
[ https://issues.apache.org/jira/browse/MESOS-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhou xing reassigned MESOS-5491: Assignee: zhou xing > Implement GET_AGENTS Call in v1 master API. > --- > > Key: MESOS-5491 > URL: https://issues.apache.org/jira/browse/MESOS-5491 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: zhou xing > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5518) Implement GET_CONTAINERS Call in v1 agent API.
[ https://issues.apache.org/jira/browse/MESOS-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Guo reassigned MESOS-5518: -- Assignee: Jay Guo > Implement GET_CONTAINERS Call in v1 agent API. > -- > > Key: MESOS-5518 > URL: https://issues.apache.org/jira/browse/MESOS-5518 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: Jay Guo > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5519) Refresh Mesos project website homepage
[ https://issues.apache.org/jira/browse/MESOS-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent updated MESOS-5519: Summary: Refresh Mesos project website homepage (was: Refresh Mesos project website) > Refresh Mesos project website homepage > -- > > Key: MESOS-5519 > URL: https://issues.apache.org/jira/browse/MESOS-5519 > Project: Mesos > Issue Type: Improvement >Reporter: haosdent >Assignee: haosdent > Attachments: website_ipad.gif, website_mobile.gif, website_pc.gif > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5519) Refresh Mesos project website
[ https://issues.apache.org/jira/browse/MESOS-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent updated MESOS-5519: Attachment: website_pc.gif website_mobile.gif website_ipad.gif > Refresh Mesos project website > - > > Key: MESOS-5519 > URL: https://issues.apache.org/jira/browse/MESOS-5519 > Project: Mesos > Issue Type: Improvement >Reporter: haosdent >Assignee: haosdent > Attachments: website_ipad.gif, website_mobile.gif, website_pc.gif > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5519) Refresh Mesos project website
haosdent created MESOS-5519: --- Summary: Refresh Mesos project website Key: MESOS-5519 URL: https://issues.apache.org/jira/browse/MESOS-5519 Project: Mesos Issue Type: Improvement Reporter: haosdent Assignee: haosdent Attachments: website_ipad.gif, website_mobile.gif, website_pc.gif -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5488) Implement READ_FILE Call in v1 master API.
[ https://issues.apache.org/jira/browse/MESOS-5488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent reassigned MESOS-5488: --- Assignee: haosdent > Implement READ_FILE Call in v1 master API. > -- > > Key: MESOS-5488 > URL: https://issues.apache.org/jira/browse/MESOS-5488 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: haosdent > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5485) Implement GET_LOGGING_LEVEL Call in v1 master API.
[ https://issues.apache.org/jira/browse/MESOS-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent reassigned MESOS-5485: --- Assignee: haosdent > Implement GET_LOGGING_LEVEL Call in v1 master API. > -- > > Key: MESOS-5485 > URL: https://issues.apache.org/jira/browse/MESOS-5485 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: haosdent > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5486) Implement SET_LOGGING_LEVEL Call in v1 master API.
[ https://issues.apache.org/jira/browse/MESOS-5486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent reassigned MESOS-5486: --- Assignee: haosdent > Implement SET_LOGGING_LEVEL Call in v1 master API. > -- > > Key: MESOS-5486 > URL: https://issues.apache.org/jira/browse/MESOS-5486 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: haosdent > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5487) Implement LIST_FILES Call in v1 master API.
[ https://issues.apache.org/jira/browse/MESOS-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent reassigned MESOS-5487: --- Assignee: haosdent > Implement LIST_FILES Call in v1 master API. > --- > > Key: MESOS-5487 > URL: https://issues.apache.org/jira/browse/MESOS-5487 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: haosdent > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5484) Implement GET_METRICS Call in v1 master API.
[ https://issues.apache.org/jira/browse/MESOS-5484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent reassigned MESOS-5484: --- Assignee: haosdent > Implement GET_METRICS Call in v1 master API. > > > Key: MESOS-5484 > URL: https://issues.apache.org/jira/browse/MESOS-5484 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: haosdent > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5490) Implement GET_STATE_SUMMARY Call in v1 master API.
[ https://issues.apache.org/jira/browse/MESOS-5490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone reassigned MESOS-5490: - Assignee: Vinod Kone > Implement GET_STATE_SUMMARY Call in v1 master API. > -- > > Key: MESOS-5490 > URL: https://issues.apache.org/jira/browse/MESOS-5490 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: Vinod Kone > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5498) Implement SUBSCRIBE Call in v1 master API.
[ https://issues.apache.org/jira/browse/MESOS-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone reassigned MESOS-5498: - Assignee: Vinod Kone > Implement SUBSCRIBE Call in v1 master API. > -- > > Key: MESOS-5498 > URL: https://issues.apache.org/jira/browse/MESOS-5498 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: Vinod Kone > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5516) Implement GET_STATE Call in v1 agent API.
[ https://issues.apache.org/jira/browse/MESOS-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone reassigned MESOS-5516: - Assignee: Vinod Kone > Implement GET_STATE Call in v1 agent API. > - > > Key: MESOS-5516 > URL: https://issues.apache.org/jira/browse/MESOS-5516 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: Vinod Kone > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5489) Implement GET_STATE Call in v1 master API.
[ https://issues.apache.org/jira/browse/MESOS-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone reassigned MESOS-5489: - Assignee: Vinod Kone > Implement GET_STATE Call in v1 master API. > -- > > Key: MESOS-5489 > URL: https://issues.apache.org/jira/browse/MESOS-5489 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: Vinod Kone > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5478) Implement GET_HEALTH Call in v1 agent API.
[ https://issues.apache.org/jira/browse/MESOS-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-5478: -- Summary: Implement GET_HEALTH Call in v1 agent API. (was: Implement CHECK_HEALTH Call in v1 agent API.) > Implement GET_HEALTH Call in v1 agent API. > -- > > Key: MESOS-5478 > URL: https://issues.apache.org/jira/browse/MESOS-5478 > Project: Mesos > Issue Type: Bug >Reporter: Vinod Kone >Assignee: Vinod Kone > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5477) Implement GET_HEALTH Call in v1 master API.
[ https://issues.apache.org/jira/browse/MESOS-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-5477: -- Summary: Implement GET_HEALTH Call in v1 master API. (was: Implement CHECK_HEALTH Call in v1 master API.) > Implement GET_HEALTH Call in v1 master API. > --- > > Key: MESOS-5477 > URL: https://issues.apache.org/jira/browse/MESOS-5477 > Project: Mesos > Issue Type: Bug >Reporter: Vinod Kone >Assignee: Vinod Kone > > https://reviews.apache.org/r/48017/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5517) Implement GET_RESOURCE_STATISTICS Call in v1 agent API.
Vinod Kone created MESOS-5517: - Summary: Implement GET_RESOURCE_STATISTICS Call in v1 agent API. Key: MESOS-5517 URL: https://issues.apache.org/jira/browse/MESOS-5517 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5518) Implement GET_CONTAINERS Call in v1 agent API.
Vinod Kone created MESOS-5518: - Summary: Implement GET_CONTAINERS Call in v1 agent API. Key: MESOS-5518 URL: https://issues.apache.org/jira/browse/MESOS-5518 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5516) Implement GET_STATE Call in v1 agent API.
Vinod Kone created MESOS-5516: - Summary: Implement GET_STATE Call in v1 agent API. Key: MESOS-5516 URL: https://issues.apache.org/jira/browse/MESOS-5516 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5514) Implement LIST_FILES Call in v1 agent API.
Vinod Kone created MESOS-5514: - Summary: Implement LIST_FILES Call in v1 agent API. Key: MESOS-5514 URL: https://issues.apache.org/jira/browse/MESOS-5514 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5515) Implement READ_FILE Call in v1 agent API.
Vinod Kone created MESOS-5515: - Summary: Implement READ_FILE Call in v1 agent API. Key: MESOS-5515 URL: https://issues.apache.org/jira/browse/MESOS-5515 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5513) Implement SET_LOGGING_LEVEL Call in v1 agent API.
Vinod Kone created MESOS-5513: - Summary: Implement SET_LOGGING_LEVEL Call in v1 agent API. Key: MESOS-5513 URL: https://issues.apache.org/jira/browse/MESOS-5513 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5511) Implement GET_METRICS Call in v1 agent API.
Vinod Kone created MESOS-5511: - Summary: Implement GET_METRICS Call in v1 agent API. Key: MESOS-5511 URL: https://issues.apache.org/jira/browse/MESOS-5511 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5510) Implement REMOVE_QUOTA Call in v1 master API.
Vinod Kone created MESOS-5510: - Summary: Implement REMOVE_QUOTA Call in v1 master API. Key: MESOS-5510 URL: https://issues.apache.org/jira/browse/MESOS-5510 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5512) Implement GET_LOGGING_LEVEL Call in v1 agent API.
Vinod Kone created MESOS-5512: - Summary: Implement GET_LOGGING_LEVEL Call in v1 agent API. Key: MESOS-5512 URL: https://issues.apache.org/jira/browse/MESOS-5512 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5508) Implement GET_QUOTA Call in v1 master API.
Vinod Kone created MESOS-5508: - Summary: Implement GET_QUOTA Call in v1 master API. Key: MESOS-5508 URL: https://issues.apache.org/jira/browse/MESOS-5508 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5509) Implement SET_QUOTA Call in v1 master API.
Vinod Kone created MESOS-5509: - Summary: Implement SET_QUOTA Call in v1 master API. Key: MESOS-5509 URL: https://issues.apache.org/jira/browse/MESOS-5509 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5506) Implement START_MAINTENANCE Call in v1 master API.
Vinod Kone created MESOS-5506: - Summary: Implement START_MAINTENANCE Call in v1 master API. Key: MESOS-5506 URL: https://issues.apache.org/jira/browse/MESOS-5506 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5505) Implement UPDATE_MAINTENANCE_SCHEDULE Call in v1 master API.
Vinod Kone created MESOS-5505: - Summary: Implement UPDATE_MAINTENANCE_SCHEDULE Call in v1 master API. Key: MESOS-5505 URL: https://issues.apache.org/jira/browse/MESOS-5505 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5507) Implement STOP_MAINTENANCE Call in v1 master API.
Vinod Kone created MESOS-5507: - Summary: Implement STOP_MAINTENANCE Call in v1 master API. Key: MESOS-5507 URL: https://issues.apache.org/jira/browse/MESOS-5507 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5501) Implement CREATE_VOLUMES Call in v1 master API.
Vinod Kone created MESOS-5501: - Summary: Implement CREATE_VOLUMES Call in v1 master API. Key: MESOS-5501 URL: https://issues.apache.org/jira/browse/MESOS-5501 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5503) Implement GET_MAINTENANCE_STATUS Call in v1 master API.
Vinod Kone created MESOS-5503: - Summary: Implement GET_MAINTENANCE_STATUS Call in v1 master API. Key: MESOS-5503 URL: https://issues.apache.org/jira/browse/MESOS-5503 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5504) Implement GET_MAINTENANCE_SCHEDULE Call in v1 master API.
Vinod Kone created MESOS-5504: - Summary: Implement GET_MAINTENANCE_SCHEDULE Call in v1 master API. Key: MESOS-5504 URL: https://issues.apache.org/jira/browse/MESOS-5504 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5500) Implement UNRESERVE_RESOURCES Call in v1 master API.
Vinod Kone created MESOS-5500: - Summary: Implement UNRESERVE_RESOURCES Call in v1 master API. Key: MESOS-5500 URL: https://issues.apache.org/jira/browse/MESOS-5500 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5502) Implement DESTROY_VOLUMES Call in v1 master API.
Vinod Kone created MESOS-5502: - Summary: Implement DESTROY_VOLUMES Call in v1 master API. Key: MESOS-5502 URL: https://issues.apache.org/jira/browse/MESOS-5502 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5497) Implement GET_LEADING_MASTER Call in v1 master API.
Vinod Kone created MESOS-5497: - Summary: Implement GET_LEADING_MASTER Call in v1 master API. Key: MESOS-5497 URL: https://issues.apache.org/jira/browse/MESOS-5497 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5496) Implement UPDATE_WEIGHTS Call in v1 master API.
Vinod Kone created MESOS-5496: - Summary: Implement UPDATE_WEIGHTS Call in v1 master API. Key: MESOS-5496 URL: https://issues.apache.org/jira/browse/MESOS-5496 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5498) Implement SUBSCRIBE Call in v1 master API.
Vinod Kone created MESOS-5498: - Summary: Implement SUBSCRIBE Call in v1 master API. Key: MESOS-5498 URL: https://issues.apache.org/jira/browse/MESOS-5498 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5495) Implement GET_WEIGHTS Call in v1 master API.
Vinod Kone created MESOS-5495: - Summary: Implement GET_WEIGHTS Call in v1 master API. Key: MESOS-5495 URL: https://issues.apache.org/jira/browse/MESOS-5495 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5492) Implement GET_FRAMEWORKS Call in v1 master API.
Vinod Kone created MESOS-5492: - Summary: Implement GET_FRAMEWORKS Call in v1 master API. Key: MESOS-5492 URL: https://issues.apache.org/jira/browse/MESOS-5492 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5494) Implement GET_ROLES Call in v1 master API.
Vinod Kone created MESOS-5494: - Summary: Implement GET_ROLES Call in v1 master API. Key: MESOS-5494 URL: https://issues.apache.org/jira/browse/MESOS-5494 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5491) Implement GET_AGENTS Call in v1 master API.
Vinod Kone created MESOS-5491: - Summary: Implement GET_AGENTS Call in v1 master API. Key: MESOS-5491 URL: https://issues.apache.org/jira/browse/MESOS-5491 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5489) Implement GET_STATE Call in v1 master API.
Vinod Kone created MESOS-5489: - Summary: Implement GET_STATE Call in v1 master API. Key: MESOS-5489 URL: https://issues.apache.org/jira/browse/MESOS-5489 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5490) Implement GET_STATE_SUMMARY Call in v1 master API.
Vinod Kone created MESOS-5490: - Summary: Implement GET_STATE_SUMMARY Call in v1 master API. Key: MESOS-5490 URL: https://issues.apache.org/jira/browse/MESOS-5490 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5488) Implement READ_FILE Call in v1 master API.
Vinod Kone created MESOS-5488: - Summary: Implement READ_FILE Call in v1 master API. Key: MESOS-5488 URL: https://issues.apache.org/jira/browse/MESOS-5488 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5487) Implement LIST_FILES Call in v1 master API.
Vinod Kone created MESOS-5487: - Summary: Implement LIST_FILES Call in v1 master API. Key: MESOS-5487 URL: https://issues.apache.org/jira/browse/MESOS-5487 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5486) Implement SET_LOGGING_LEVEL Call in v1 master API.
Vinod Kone created MESOS-5486: - Summary: Implement SET_LOGGING_LEVEL Call in v1 master API. Key: MESOS-5486 URL: https://issues.apache.org/jira/browse/MESOS-5486 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5485) Implement GET_LOGGING_LEVEL Call in v1 master API.
Vinod Kone created MESOS-5485: - Summary: Implement GET_LOGGING_LEVEL Call in v1 master API. Key: MESOS-5485 URL: https://issues.apache.org/jira/browse/MESOS-5485 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5484) Implement GET_METRICS Call in v1 master API.
Vinod Kone created MESOS-5484: - Summary: Implement GET_METRICS Call in v1 master API. Key: MESOS-5484 URL: https://issues.apache.org/jira/browse/MESOS-5484 Project: Mesos Issue Type: Task Reporter: Vinod Kone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3067) Implement a streaming response decoder for events stream
[
https://issues.apache.org/jira/browse/MESOS-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15306123#comment-15306123
]
David Rauschenbach commented on MESOS-3067:
---
Have you considered application/jsonstream encoding (line-separated JSON) for
the chunked response? That's easy to integrate with present Java and Node libs.
These lengths and JSON blocks aren't consistent with the Content-Type:
application/json header being returned by the interface.
> Implement a streaming response decoder for events stream
>
>
> Key: MESOS-3067
> URL: https://issues.apache.org/jira/browse/MESOS-3067
> Project: Mesos
> Issue Type: Task
>Reporter: Anand Mazumdar
>Assignee: Benjamin Mahler
> Fix For: 0.24.0
>
>
> We need a streaming response decoder to de-serialize chunks sent from the
> master on the events stream.
> From the HTTP API design doc:
> Master encodes each Event in RecordIO format, i.e. a string representation of
> length of the event in bytes followed by JSON or binary Protobuf (possibly
> compressed) encoded event.
> As of now for getting the basic features right , this is being done in the
> test-cases:
> {code}
> auto reader = response.get().reader;
> ASSERT_SOME(reader);
> Future eventFuture = reader.get().read();
> AWAIT_READY(eventFuture);
> Event event;
> event.ParseFromString(eventFuture.get());
> {code}
> Two things need to happen:
> - We need master to emit events in RecordIO format i.e. event size followed
> by the serialized event instead of just the serialized events as is the case
> now.
> - The decoder class should then abstract away the logic of reading the
> response and de-serializing events from the stream.
> Ideally, the decoder should work with both "json" and "protobuf" responses.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5465) Container image as a volume source should also include image manifest.
[ https://issues.apache.org/jira/browse/MESOS-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-5465: -- Shepherd: Jie Yu > Container image as a volume source should also include image manifest. > -- > > Key: MESOS-5465 > URL: https://issues.apache.org/jira/browse/MESOS-5465 > Project: Mesos > Issue Type: Bug >Reporter: Jie Yu >Assignee: Guangya Liu > > Currently, if a user specifies the source of a volume to be an image (e.g., > Docker image), we only prepare the rootfs and mount it at 'container_path' in > the container. > However, the rootfs itself is not sufficient to allow the executor to launch > the docker container. We need the docker manifest as well to get the env, > entry point, cmd information. > One solutions is to make container_path a directory containing two things: 1) > rootfs, 2) manifest. But this is a breaking change, we might need to > introduce a deprecation cycle for that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4512) Render quota status consistently with other endpoints.
[
https://issues.apache.org/jira/browse/MESOS-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15306083#comment-15306083
]
Vinod Kone commented on MESOS-4512:
---
Why is `role` here misleading? In the v1 master API we are modeling the output
as QuotaInfo as well. Let me know how you want it to look instead. Note that
the output needs to be a protobuf not a model() in v1.
> Render quota status consistently with other endpoints.
> --
>
> Key: MESOS-4512
> URL: https://issues.apache.org/jira/browse/MESOS-4512
> Project: Mesos
> Issue Type: Bug
> Components: master
>Reporter: Alexander Rukletsov
>Assignee: Alexander Rukletsov
> Labels: http, mesosphere
>
> Currently quota status endpoint returns a collection of {{QuotaInfo}} protos
> converted to JSON. An example response looks like this:
> {code:xml}
> {
> "infos": [
> {
> "role": "role1",
> "guarantee": [
> {
> "name": "cpus",
> "role": "*",
> "type": "SCALAR",
> "scalar": { "value": 12 }
> },
> {
> "name": "mem",
> "role": "*",
> "type": "SCALAR",
> "scalar": { "value": 6144 }
> }
> ]
> }
> ]
> }
> {code}
> Presence of some fields, e.g. "role", is misleading. To address this issue
> and make the output more informative, we should probably introduce a
> {{model()}} function for {{QuotaStatus}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5392) Design doc for adding resource limits support for Mesos containerizer
[ https://issues.apache.org/jira/browse/MESOS-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5392: - Sprint: Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 35) > Design doc for adding resource limits support for Mesos containerizer > - > > Key: MESOS-5392 > URL: https://issues.apache.org/jira/browse/MESOS-5392 > Project: Mesos > Issue Type: Task > Components: containerization >Reporter: Jojy Varghese >Assignee: Jojy Varghese > Labels: mesosphere > > This will be the design doc for MESOS-5391. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5275) Add capabilities support for unified containerizer.
[ https://issues.apache.org/jira/browse/MESOS-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5275: - Sprint: Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 34, Mesosphere Sprint 35) > Add capabilities support for unified containerizer. > --- > > Key: MESOS-5275 > URL: https://issues.apache.org/jira/browse/MESOS-5275 > Project: Mesos > Issue Type: Task > Components: containerization >Reporter: Jojy Varghese >Assignee: Jojy Varghese > Labels: mesosphere > > Add capabilities support for unified containerizer. > Requirements: > 1. Use the mesos capabilities API. > 2. Frameworks be able to add capability requests for containers. > 3. Agents be able to add maximum allowed capabilities for all containers > launched. > Design document: > https://docs.google.com/document/d/1YiTift8TQla2vq3upQr7K-riQ_pQ-FKOCOsysQJROGc/edit#heading=h.rgfwelqrskmd -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5303) Add capabilities support for mesos execute cli.
[ https://issues.apache.org/jira/browse/MESOS-5303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5303: - Sprint: Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 34, Mesosphere Sprint 35) > Add capabilities support for mesos execute cli. > --- > > Key: MESOS-5303 > URL: https://issues.apache.org/jira/browse/MESOS-5303 > Project: Mesos > Issue Type: Bug > Components: containerization >Reporter: Jojy Varghese >Assignee: Jojy Varghese > Labels: mesosphere > > Add support for `user` and `capabilities` to execute cli. This will help in > testing the `capabilities` feature for unified containerizer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5345) Design doc for TASK_LOST_IN_PROGRESS
[ https://issues.apache.org/jira/browse/MESOS-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5345: - Sprint: Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 35) > Design doc for TASK_LOST_IN_PROGRESS > > > Key: MESOS-5345 > URL: https://issues.apache.org/jira/browse/MESOS-5345 > Project: Mesos > Issue Type: Task > Components: master >Reporter: Neil Conway > Labels: mesosphere > > The TASK_LOST task status describes two different situations: (a) the task > was not launched because of an error (e.g., insufficient available > resources), or (b) the master lost contact with a running task (e.g., due to > a network partition); the master will kill the task when it can (e.g., when > the network partition heals), but in the meantime the task may still be > running. > This has two problems: > 1. Using the same task status for two fairly different situations is > confusing. > 2. In the partitioned-but-still-running case, frameworks have no easy way to > determine when a task has truly terminated. > To address these problems, we propose introducing a new task status, > TASK_LOST_IN_PROGRESS. If a framework opts into this behavior using a new > capability, TASK_LOST would mean "the task is definitely not running", > whereas TASK_LOST_IN_PROGRESS would mean "the task may or may not be running > (we've lost contact with the agent), but the master will try to shut it down > when possible." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5401) Add ability to inject a Volume of Nvidia GPU-related libraries into a docker container.
[ https://issues.apache.org/jira/browse/MESOS-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5401: - Sprint: Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 35) > Add ability to inject a Volume of Nvidia GPU-related libraries into a docker > container. > --- > > Key: MESOS-5401 > URL: https://issues.apache.org/jira/browse/MESOS-5401 > Project: Mesos > Issue Type: Improvement >Reporter: Kevin Klues >Assignee: Kevin Klues > > In order to support Nvidia GPUs with docker containers in Mesos, we need to > be able to consolidate all Nvidia libraries into a common volume and inject > that volume into the container. > More info on why this is necessary here: > https://github.com/NVIDIA/nvidia-docker/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4626) Support Nvidia GPUs with filesystem isolation enabled.
[ https://issues.apache.org/jira/browse/MESOS-4626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-4626: - Sprint: Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 35) > Support Nvidia GPUs with filesystem isolation enabled. > -- > > Key: MESOS-4626 > URL: https://issues.apache.org/jira/browse/MESOS-4626 > Project: Mesos > Issue Type: Task > Components: isolation >Reporter: Benjamin Mahler >Assignee: Kevin Klues > > When filesystem isolation is enabled, containers that use Nvidia GPU > resources need access to GPU libraries residing on the host. > We'll need to provide a means for operators to inject the necessary volumes > into *all* containers that use "gpus" resources. > See the nvidia-docker project for more details: > [nvidia-docker/tools/src/nvidia/volumes.go|https://github.com/NVIDIA/nvidia-docker/blob/fda10b2d27bf5578cc5337c23877f827e4d1ed77/tools/src/nvidia/volumes.go#L50-L103] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5064) Remove default value for the agent `work_dir`
[
https://issues.apache.org/jira/browse/MESOS-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Harutyunyan updated MESOS-5064:
-
Sprint: Mesosphere Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34,
Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 32,
Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35)
> Remove default value for the agent `work_dir`
> -
>
> Key: MESOS-5064
> URL: https://issues.apache.org/jira/browse/MESOS-5064
> Project: Mesos
> Issue Type: Bug
>Reporter: Artem Harutyunyan
>Assignee: Greg Mann
>Priority: Blocker
> Fix For: 0.29.0
>
>
> Following a crash report from the user we need to be more explicit about the
> dangers of using {{/tmp}} as agent {{work_dir}}. In addition, we can remove
> the default value for the {{\-\-work_dir}} flag, forcing users to explicitly
> set the work directory for the agent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5232) Add capability information to ContainerInfo protobuf message.
[ https://issues.apache.org/jira/browse/MESOS-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5232: - Sprint: Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35) > Add capability information to ContainerInfo protobuf message. > - > > Key: MESOS-5232 > URL: https://issues.apache.org/jira/browse/MESOS-5232 > Project: Mesos > Issue Type: Task > Components: containerization >Reporter: Jojy Varghese >Assignee: Jojy Varghese > Labels: mesosphere > > To enable support for capability as first class framework entity, we need to > add capabilities related information to the ContainerInfo protobuf. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5296) Split Resource and Inverse offer protobufs for V1 API
[ https://issues.apache.org/jira/browse/MESOS-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5296: - Sprint: Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 34, Mesosphere Sprint 35) > Split Resource and Inverse offer protobufs for V1 API > - > > Key: MESOS-5296 > URL: https://issues.apache.org/jira/browse/MESOS-5296 > Project: Mesos > Issue Type: Improvement >Reporter: Joris Van Remoortere >Assignee: Joris Van Remoortere >Priority: Blocker > Fix For: 0.29.0 > > > The protobufs for the V1 api regarding inverse offers initially re-used the > existing offer / rescind / accept / decline messages for regular offers. > We should split these out the be more explicit, and provide the ability to > augment the messages with particulars to either resource or inverse offers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5216) Document docker volume driver isolator.
[ https://issues.apache.org/jira/browse/MESOS-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5216: - Sprint: Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 35) > Document docker volume driver isolator. > --- > > Key: MESOS-5216 > URL: https://issues.apache.org/jira/browse/MESOS-5216 > Project: Mesos > Issue Type: Bug > Components: containerization >Reporter: Gilbert Song >Assignee: Guangya Liu > Labels: documentaion, mesosphere > Fix For: 0.29.0 > > > Should include the followings: > 1. What features (driver options) are supported in docker volume driver > isolator. > 2. How to use docker volume driver isolator. > *related agent flags introduction and usage. > *isolator dependency clarification (e.g., filesystem/linux). > *related driver daemon preprocess. > *volumes pre-specified by users and volume cleanup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5256) Add support for per-containerizer resource enumeration
[ https://issues.apache.org/jira/browse/MESOS-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5256: - Sprint: Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 35) > Add support for per-containerizer resource enumeration > -- > > Key: MESOS-5256 > URL: https://issues.apache.org/jira/browse/MESOS-5256 > Project: Mesos > Issue Type: Task > Components: isolation >Reporter: Kevin Klues >Assignee: Kevin Klues > Labels: containerizer > > Currently the top level containerizer includes a static function for > enumerating the resources available on a given agent. Ideally, this > functionality should be the responsibility of individual containerizers (and > specifically the responsibility of each isolator used to control access to > those resources). > Adding support for this will involve making the `Containerizer::resources()` > function virtual instead of static and then implementing it on a > per-containerizer basis. We should consider providing a default to make this > easier in cases where there is only really one good way of enumerating a > given set of resources. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4781) Executor env variables should not be leaked to the command task.
[ https://issues.apache.org/jira/browse/MESOS-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-4781: - Sprint: Mesosphere Sprint 30, Mesosphere Sprint 31, Mesosphere Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 30, Mesosphere Sprint 31, Mesosphere Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35) > Executor env variables should not be leaked to the command task. > > > Key: MESOS-4781 > URL: https://issues.apache.org/jira/browse/MESOS-4781 > Project: Mesos > Issue Type: Bug > Components: containerization >Reporter: Gilbert Song >Assignee: Gilbert Song > Labels: mesosphere > > Currently, command task inherits the env variables of the command executor. > This is less ideal because the command executor environment variables include > some Mesos internal env variables like MESOS_XXX and LIBPROCESS_XXX. Also, > this behavior does not match what Docker containerizer does. We should > construct the env variables from scratch for the command task, rather than > relying on inheriting the env variables from the command executor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5222) Create a benchmark for scale testing HTTP frameworks
[ https://issues.apache.org/jira/browse/MESOS-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5222: - Sprint: Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 35) > Create a benchmark for scale testing HTTP frameworks > > > Key: MESOS-5222 > URL: https://issues.apache.org/jira/browse/MESOS-5222 > Project: Mesos > Issue Type: Task >Reporter: Anand Mazumdar >Assignee: Anand Mazumdar > Labels: mesosphere > > It would be good to add a benchmark for scale testing the HTTP frameworks wrt > driver based frameworks. The benchmark can be as simple as trying to launch N > tasks (parameterized) with the old/new API. We can then focus on fixing > performance issues that we find as a result of this exercise. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5348) Enhance the log message when launching docker containerizer.
[ https://issues.apache.org/jira/browse/MESOS-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5348: - Sprint: Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 35) > Enhance the log message when launching docker containerizer. > > > Key: MESOS-5348 > URL: https://issues.apache.org/jira/browse/MESOS-5348 > Project: Mesos > Issue Type: Improvement > Components: containerization >Reporter: Gilbert Song >Assignee: Guangya Liu > Labels: mesosphere > Fix For: 0.29.0 > > > Log the launch flag which includes the executor command and other information > when launching the docker containerizer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5173) Allow master/agent to take multiple modules manifest files
[ https://issues.apache.org/jira/browse/MESOS-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5173: - Sprint: Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35) > Allow master/agent to take multiple modules manifest files > -- > > Key: MESOS-5173 > URL: https://issues.apache.org/jira/browse/MESOS-5173 > Project: Mesos > Issue Type: Task >Reporter: Kapil Arya >Assignee: Kapil Arya >Priority: Blocker > Labels: mesosphere > Fix For: 0.29.0 > > > When loading multiple modules into master/agent, one has to merge all module > metadata (library name, module name, parameters, etc.) into a single json > file which is then passed on to the --modules flag. This quickly becomes > cumbersome especially if the modules are coming from different > vendors/developers. > An alternate would be to allow multiple invocations of --modules flag that > can then be passed on to the module manager. That way, each flag corresponds > to just one module library and modules from that library. > Another approach is to create a new flag (e.g., --modules-dir) that contains > a path to a directory that would contain multiple json files. One can think > of it as an analogous to systemd units. The operator that drops a new file > into this directory and the file would automatically be picked up by the > master/agent module manager. Further, the naming scheme can also be inherited > to prefix the filename with an "NN_" to signify oad order. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2043) framework auth fail with timeout error and never get authenticated
[
https://issues.apache.org/jira/browse/MESOS-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Harutyunyan updated MESOS-2043:
-
Sprint: Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint
35)
> framework auth fail with timeout error and never get authenticated
> --
>
> Key: MESOS-2043
> URL: https://issues.apache.org/jira/browse/MESOS-2043
> Project: Mesos
> Issue Type: Bug
> Components: master, scheduler driver, security, slave
>Affects Versions: 0.21.0
>Reporter: Bhuvan Arumugam
>Priority: Critical
> Labels: mesosphere, security
> Attachments: aurora-scheduler.20141104-1606-1706.log, master.log,
> mesos-master.20141104-1606-1706.log, slave.log
>
>
> I'm facing this issue in master as of
> https://github.com/apache/mesos/commit/74ea59e144d131814c66972fb0cc14784d3503d4
> As [~adam-mesos] mentioned in IRC, this sounds similar to MESOS-1866. I'm
> running 1 master and 1 scheduler (aurora). The framework authentication fail
> due to time out:
> error on mesos master:
> {code}
> I1104 19:37:17.741449 8329 master.cpp:3874] Authenticating
> scheduler-d2d4437b-d375-4467-a583-362152fe065a@SCHEDULER_IP:8083
> I1104 19:37:17.741585 8329 master.cpp:3885] Using default CRAM-MD5
> authenticator
> I1104 19:37:17.742106 8336 authenticator.hpp:169] Creating new server SASL
> connection
> W1104 19:37:22.742959 8329 master.cpp:3953] Authentication timed out
> W1104 19:37:22.743548 8329 master.cpp:3930] Failed to authenticate
> scheduler-d2d4437b-d375-4467-a583-362152fe065a@SCHEDULER_IP:8083:
> Authentication discarded
> {code}
> scheduler error:
> {code}
> I1104 19:38:57.885486 49012 sched.cpp:283] Authenticating with master
> master@MASTER_IP:PORT
> I1104 19:38:57.885928 49002 authenticatee.hpp:133] Creating new client SASL
> connection
> I1104 19:38:57.890581 49007 authenticatee.hpp:224] Received SASL
> authentication mechanisms: CRAM-MD5
> I1104 19:38:57.890656 49007 authenticatee.hpp:250] Attempting to authenticate
> with mechanism 'CRAM-MD5'
> W1104 19:39:02.891196 49005 sched.cpp:378] Authentication timed out
> I1104 19:39:02.891850 49018 sched.cpp:338] Failed to authenticate with master
> master@MASTER_IP:PORT: Authentication discarded
> {code}
> Looks like 2 instances {{scheduler-20f88a53-5945-4977-b5af-28f6c52d3c94}} &
> {{scheduler-d2d4437b-d375-4467-a583-362152fe065a}} of same framework is
> trying to authenticate and fail.
> {code}
> W1104 19:36:30.769420 8319 master.cpp:3930] Failed to authenticate
> scheduler-20f88a53-5945-4977-b5af-28f6c52d3c94@SCHEDULER_IP:8083: Failed to
> communicate with authenticatee
> I1104 19:36:42.701441 8328 master.cpp:3860] Queuing up authentication
> request from scheduler-d2d4437b-d375-4467-a583-362152fe065a@SCHEDULER_IP:8083
> because authentication is still in progress
> {code}
> Restarting master and scheduler didn't fix it.
> This particular issue happen with 1 master and 1 scheduler after MESOS-1866
> is fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5221) Add Documentation for Nvidia GPU support
[ https://issues.apache.org/jira/browse/MESOS-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5221: - Sprint: Mesosphere Sprint 33, Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 33, Mesosphere Sprint 35) > Add Documentation for Nvidia GPU support > > > Key: MESOS-5221 > URL: https://issues.apache.org/jira/browse/MESOS-5221 > Project: Mesos > Issue Type: Documentation >Reporter: Kevin Klues >Assignee: Kevin Klues >Priority: Minor > > https://reviews.apache.org/r/46220/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4279) Docker executor truncates task's output when the task is killed.
[
https://issues.apache.org/jira/browse/MESOS-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Harutyunyan updated MESOS-4279:
-
Sprint: Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint
35)
> Docker executor truncates task's output when the task is killed.
>
>
> Key: MESOS-4279
> URL: https://issues.apache.org/jira/browse/MESOS-4279
> Project: Mesos
> Issue Type: Bug
> Components: containerization, docker
>Affects Versions: 0.25.0, 0.26.0, 0.27.2, 0.28.1
>Reporter: Martin Bydzovsky
>Assignee: Martin Bydzovsky
>Priority: Blocker
> Labels: docker, mesosphere
> Fix For: 0.29.0
>
>
> I'm implementing a graceful restarts of our mesos-marathon-docker setup and I
> came to a following issue:
> (it was already discussed on
> https://github.com/mesosphere/marathon/issues/2876 and guys form mesosphere
> got to a point that its probably a docker containerizer problem...)
> To sum it up:
> When i deploy simple python script to all mesos-slaves:
> {code}
> #!/usr/bin/python
> from time import sleep
> import signal
> import sys
> import datetime
> def sigterm_handler(_signo, _stack_frame):
> print "got %i" % _signo
> print datetime.datetime.now().time()
> sys.stdout.flush()
> sleep(2)
> print datetime.datetime.now().time()
> print "ending"
> sys.stdout.flush()
> sys.exit(0)
> signal.signal(signal.SIGTERM, sigterm_handler)
> signal.signal(signal.SIGINT, sigterm_handler)
> try:
> print "Hello"
> i = 0
> while True:
> i += 1
> print datetime.datetime.now().time()
> print "Iteration #%i" % i
> sys.stdout.flush()
> sleep(1)
> finally:
> print "Goodbye"
> {code}
> and I run it through Marathon like
> {code:javascript}
> data = {
> args: ["/tmp/script.py"],
> instances: 1,
> cpus: 0.1,
> mem: 256,
> id: "marathon-test-api"
> }
> {code}
> During the app restart I get expected result - the task receives sigterm and
> dies peacefully (during my script-specified 2 seconds period)
> But when i wrap this python script in a docker:
> {code}
> FROM node:4.2
> RUN mkdir /app
> ADD . /app
> WORKDIR /app
> ENTRYPOINT []
> {code}
> and run appropriate application by Marathon:
> {code:javascript}
> data = {
> args: ["./script.py"],
> container: {
> type: "DOCKER",
> docker: {
> image: "bydga/marathon-test-api"
> },
> forcePullImage: yes
> },
> cpus: 0.1,
> mem: 256,
> instances: 1,
> id: "marathon-test-api"
> }
> {code}
> The task during restart (issued from marathon) dies immediately without
> having a chance to do any cleanup.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5228) Add tests for Capability API.
[ https://issues.apache.org/jira/browse/MESOS-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5228: - Sprint: Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35) > Add tests for Capability API. > - > > Key: MESOS-5228 > URL: https://issues.apache.org/jira/browse/MESOS-5228 > Project: Mesos > Issue Type: Task > Components: containerization >Reporter: Jojy Varghese >Assignee: Jojy Varghese > Labels: mesosphere, unified-containerizer-mvp > > Add basic tests for the capability API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5051) Create helpers for manipulating Linux capabilities.
[ https://issues.apache.org/jira/browse/MESOS-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5051: - Sprint: Mesosphere Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35) > Create helpers for manipulating Linux capabilities. > --- > > Key: MESOS-5051 > URL: https://issues.apache.org/jira/browse/MESOS-5051 > Project: Mesos > Issue Type: Task >Reporter: Jie Yu >Assignee: Jojy Varghese > Labels: mesosphere > > These helpers can either based on some existing library (e.g. libcap), or use > system calls directly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4099) parallel make tests does not build all test targets
[
https://issues.apache.org/jira/browse/MESOS-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Harutyunyan updated MESOS-4099:
-
Sprint: Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint
35)
> parallel make tests does not build all test targets
> ---
>
> Key: MESOS-4099
> URL: https://issues.apache.org/jira/browse/MESOS-4099
> Project: Mesos
> Issue Type: Bug
> Components: build, libprocess
>Affects Versions: 0.26.0
> Environment: Ubuntu 15.04
> clang-3.6 as well as gcc-4.9
>Reporter: Joris Van Remoortere
>Assignee: Kapil Arya
> Labels: mesosphere
> Fix For: 0.29.0
>
>
> When inside 3rdparty/libprocess:
> Running {{make -j8 tests}} from a clean build does not yield the
> {{libprocess-tests}} binary.
> Running it a subsequent time triggers more compilation and ends up yielding
> the {{libprocess-tests}} binary.
> This suggests the {{test}} target is not being built correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4690) Reorganize 3rdparty directory
[ https://issues.apache.org/jira/browse/MESOS-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-4690: - Sprint: Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35) > Reorganize 3rdparty directory > - > > Key: MESOS-4690 > URL: https://issues.apache.org/jira/browse/MESOS-4690 > Project: Mesos > Issue Type: Epic > Components: build, libprocess, stout >Reporter: Kapil Arya >Assignee: Kapil Arya > Labels: mesosphere > > This issues is currently being discussed in the dev mailing list: > http://www.mail-archive.com/dev@mesos.apache.org/msg34349.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4766) Improve allocator performance.
[ https://issues.apache.org/jira/browse/MESOS-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-4766: - Sprint: Mesosphere Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35) > Improve allocator performance. > -- > > Key: MESOS-4766 > URL: https://issues.apache.org/jira/browse/MESOS-4766 > Project: Mesos > Issue Type: Epic > Components: allocation >Reporter: Benjamin Mahler >Assignee: Michael Park >Priority: Critical > > This is an epic to track the various tickets around improving the performance > of the allocator, including the following: > * Preventing un-necessary backup of the allocator. > * Reducing the cost of allocations and allocator state updates. > * Improving performance of the DRF sorter. > * More benchmarking to simulate scenarios with performance issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4938) Support docker registry authentication
[ https://issues.apache.org/jira/browse/MESOS-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-4938: - Sprint: Mesosphere Sprint 31, Mesosphere Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 31, Mesosphere Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35) > Support docker registry authentication > -- > > Key: MESOS-4938 > URL: https://issues.apache.org/jira/browse/MESOS-4938 > Project: Mesos > Issue Type: Task >Reporter: Jie Yu >Assignee: Gilbert Song > Labels: mesosphere > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5258) Turn the Nvidia GPU isolator into a module
[ https://issues.apache.org/jira/browse/MESOS-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5258: - Sprint: Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 35) > Turn the Nvidia GPU isolator into a module > -- > > Key: MESOS-5258 > URL: https://issues.apache.org/jira/browse/MESOS-5258 > Project: Mesos > Issue Type: Task >Reporter: Kevin Klues >Assignee: Kevin Klues > > The Nvidia GPU isolator has an external dependence on `libnvidia-ml.so`. As > it currently stands, this forces *all* binaries that link with `libmesos.so` > to also link with `libnvidia-ml.so` (including master, agents on machines > without GPUs, scheduler, exectors, etc.). > By turning the Nvidia GPU isolator into a module, it will be loaded at > runtime only when an agent has explicitly including the the Nvidia GPU > isolator in its `--isolation` flag. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5153) Sandboxes contents should be protected from unauthorized users
[ https://issues.apache.org/jira/browse/MESOS-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5153: - Sprint: Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35) > Sandboxes contents should be protected from unauthorized users > -- > > Key: MESOS-5153 > URL: https://issues.apache.org/jira/browse/MESOS-5153 > Project: Mesos > Issue Type: Bug > Components: security, slave >Reporter: Alexander Rojas >Assignee: Alexander Rojas > Labels: mesosphere, security > Fix For: 0.29.0 > > > MESOS-4956 introduced authentication support for the sandboxes. However, > authentication can only go as far as to tell whether an user is known to > mesos or not. An extra additional step is necessary to verify whether the > known user is allowed to executed the requested operation on the sandbox > (browse, read, download, debug). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5445) Allow libprocess/stout to build without first doing `make` in 3rdparty.
[ https://issues.apache.org/jira/browse/MESOS-5445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5445: - Sprint: Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 35) > Allow libprocess/stout to build without first doing `make` in 3rdparty. > --- > > Key: MESOS-5445 > URL: https://issues.apache.org/jira/browse/MESOS-5445 > Project: Mesos > Issue Type: Bug > Components: build >Reporter: Kapil Arya >Assignee: Kapil Arya > Labels: mesosphere > Fix For: 0.29.0 > > > After the 3rdparty reorg, libprocess/stout are enable to build their > dependencies and so one has to do `make` in 3rdpart/ before building > libprocess/stout. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5257) Add autodiscovery for GPU resources
[ https://issues.apache.org/jira/browse/MESOS-5257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5257: - Sprint: Mesosphere Sprint 35, Mesosphere Sprint 36 (was: Mesosphere Sprint 35) > Add autodiscovery for GPU resources > --- > > Key: MESOS-5257 > URL: https://issues.apache.org/jira/browse/MESOS-5257 > Project: Mesos > Issue Type: Task >Reporter: Kevin Klues >Assignee: Kevin Klues > Labels: isolator > > Right now, the only way to enumerate the available GPUs on an agent is to use > the `--nvidia_gpu_devices` flag and explicitly list them out. Instead, we > should leverage NVML to autodiscover the GPUs that are available and only use > this flag as a way to explicitly list out the GPUs you want to make available > in order to restrict access to some of them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4233) Logging is too verbose for sysadmins / syslog
[
https://issues.apache.org/jira/browse/MESOS-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Harutyunyan updated MESOS-4233:
-
Sprint: Mesosphere Sprint 26, Mesosphere Sprint 27, Mesosphere Sprint 28,
Mesosphere Sprint 29, Mesosphere Sprint 30, Mesosphere Sprint 31, Mesosphere
Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35,
Mesosphere Sprint 36 (was: Mesosphere Sprint 26, Mesosphere Sprint 27,
Mesosphere Sprint 28, Mesosphere Sprint 29, Mesosphere Sprint 30, Mesosphere
Sprint 31, Mesosphere Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34,
Mesosphere Sprint 35)
> Logging is too verbose for sysadmins / syslog
> -
>
> Key: MESOS-4233
> URL: https://issues.apache.org/jira/browse/MESOS-4233
> Project: Mesos
> Issue Type: Epic
>Reporter: Cody Maloney
>Assignee: Kapil Arya
> Labels: mesosphere
> Attachments: giant_port_range_logging
>
>
> Currently mesos logs a lot. When launching a thousand tasks in the space of
> 10 seconds it will print tens of thousands of log lines, overwhelming syslog
> (there is a max rate at which a process can send stuff over a unix socket)
> and not giving useful information to a sysadmin who cares about just the
> high-level activity and when something goes wrong.
> Note mesos also blocks writing to its log locations, so when writing a lot of
> log messages, it can fill up the write buffer in the kernel, and be suspended
> until the syslog agent catches up reading from the socket (GLOG does a
> blocking fwrite to stderr). GLOG also has a big mutex around logging so only
> one thing logs at a time.
> While for "internal debugging" it is useful to see things like "message went
> from internal compoent x to internal component y", from a sysadmin
> perspective I only care about the high level actions taken (launched task for
> framework x), sent offer to framework y, got task failed from host z. Note
> those are what I'd expect at the "INFO" level. At the "WARNING" level I'd
> expect very little to be logged / almost nothing in normal operation. Just
> things like "WARN: Repliacted log write took longer than expected". WARN
> would also get things like backtraces on crashes and abnormal exits / abort.
> When trying to launch 3k+ tasks inside a second, mesos logging currently
> overwhelms syslog with 100k+ messages, many of which are thousands of bytes.
> Sysadmins expect to be able to use syslog to monitor basic events in their
> system. This is too much.
> We can keep logging the messages to files, but the logging to stderr needs to
> be reduced significantly (stderr gets picked up and forwarded to syslog /
> central aggregation).
> What I would like is if I can set the stderr logging level to be different /
> independent from the file logging level (Syslog giving the "sysadmin"
> aggregated overview, files useful for debugging in depth what happened in a
> cluster). A lot of what mesos currently logs at info is really debugging info
> / should show up as debug log level.
> Some samples of mesos logging a lot more than a sysadmin would want / expect
> are attached, and some are below:
> - Every task gets printed multiple times for a basic launch:
> {noformat}
> Dec 15 22:58:30 ip-10-0-7-60.us-west-2.compute.internal mesos-master[1311]:
> I1215 22:58:29.382644 1315 master.cpp:3248] Launching task
> envy.5b19a713-a37f-11e5-8b3e-0251692d6109 of framework
> 5178f46d-71d6-422f-922c-5bbe82dff9cc- (marathon)
> Dec 15 22:58:30 ip-10-0-7-60.us-west-2.compute.internal mesos-master[1311]:
> I1215 22:58:29.382925 1315 master.hpp:176] Adding task
> envy.5b1958f2-a37f-11e5-8b3e-0251692d6109 with resources cpus(*):0.0001;
> mem(*):16; ports(*):[14047-14047]
> {noformat}
> - Every task status update prints many log lines, successful ones are part
> of normal operation and maybe should be logged at info / debug levels, but
> not to a sysadmin (Just show when things fail, and maybe aggregate counters
> to tell of the volume of working)
> - No log messagse should be really big / more than 1k characters (Would
> prevent the giant port list attached, make that easily discoverable / bug
> filable / fixable)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (MESOS-3216) virtual memory exhausted:: Cannot allocate memory
[ https://issues.apache.org/jira/browse/MESOS-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Cwienczek updated MESOS-3216: Comment: was deleted (was: ibtool: compile: g++ -DPACKAGE_NAME=\"libprocess\" -DPACKAGE_TARNAME=\"libprocess\" -DPACKAGE_VERSION=\"0.0.1\" "-DPACKAGE_STRING=\"libprocess 0.0.1\"" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"libprocess\" -DVERSION=\"0.0.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_APR_POOLS_H=1 -DHAVE_LIBAPR_1=1 -DHAVE_SVN_VERSION_H=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_SVN_DELTA_H=1 -DHAVE_LIBSVN_DELTA_1=1 -DHAVE_LIBCURL=1 -DHAVE_PTHREAD_PRIO_INHERIT=1 -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBDL=1 -I. -I../../../3rdparty/libprocess -DBUILD_DIR=\"/home/vagrant/mesos-0.28.1/build/3rdparty/libprocess\" -I../../../3rdparty/libprocess/include -I../../../3rdparty/libprocess/3rdparty/stout/include -isystem 3rdparty/boost-1.53.0 -I3rdparty/libev-4.15 -I3rdparty/picojson-1.3.0 -DPICOJSON_USE_INT64 -D__STDC_FORMAT_MACROS -I3rdparty/glog-0.3.3/src -I3rdparty/ry-http-parser-1c3624a -I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0 -g1 -O0 -Wno-unused-local-typedefs -std=c++11 -MT libprocess_la-poll_socket.lo -MD -MP -MF .deps/libprocess_la-poll_socket.Tpo -c ../../../3rdparty/libprocess/src/poll_socket.cpp -fPIC -DPIC -o libprocess_la-poll_socket.o ./libtool: line 1762: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8) mv -f .deps/libprocess_la-poll_socket.Tpo .deps/libprocess_la-poll_socket.Plo /bin/bash ./libtool --tag=CXX --mode=compile g++ -DPACKAGE_NAME=\"libprocess\" -DPACKAGE_TARNAME=\"libprocess\" -DPACKAGE_VERSION=\"0.0.1\" -DPACKAGE_STRING=\"libprocess\ 0.0.1\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"libprocess\" -DVERSION=\"0.0.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_APR_POOLS_H=1 -DHAVE_LIBAPR_1=1 -DHAVE_SVN_VERSION_H=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_SVN_DELTA_H=1 -DHAVE_LIBSVN_DELTA_1=1 -DHAVE_LIBCURL=1 -DHAVE_PTHREAD_PRIO_INHERIT=1 -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBDL=1 -I. -I../../../3rdparty/libprocess -DBUILD_DIR=\"/home/vagrant/mesos-0.28.1/build/3rdparty/libprocess\" -I../../../3rdparty/libprocess/include -I../../../3rdparty/libprocess/3rdparty/stout/include -isystem 3rdparty/boost-1.53.0 -I3rdparty/libev-4.15 -I3rdparty/picojson-1.3.0 -DPICOJSON_USE_INT64 -D__STDC_FORMAT_MACROS -I3rdparty/glog-0.3.3/src -I3rdparty/ry-http-parser-1c3624a -I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0 -g1 -O0 -Wno-unused-local-typedefs -std=c++11 -MT libprocess_la-profiler.lo -MD -MP -MF .deps/libprocess_la-profiler.Tpo -c -o libprocess_la-profiler.lo `test -f 'src/profiler.cpp' || echo '../../../3rdparty/libprocess/'`src/profiler.cpp libtool: compile: g++ -DPACKAGE_NAME=\"libprocess\" -DPACKAGE_TARNAME=\"libprocess\" -DPACKAGE_VERSION=\"0.0.1\" "-DPACKAGE_STRING=\"libprocess 0.0.1\"" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"libprocess\" -DVERSION=\"0.0.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_APR_POOLS_H=1 -DHAVE_LIBAPR_1=1 -DHAVE_SVN_VERSION_H=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_SVN_DELTA_H=1 -DHAVE_LIBSVN_DELTA_1=1 -DHAVE_LIBCURL=1 -DHAVE_PTHREAD_PRIO_INHERIT=1 -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBDL=1 -I. -I../../../3rdparty/libprocess -DBUILD_DIR=\"/home/vagrant/mesos-0.28.1/build/3rdparty/libprocess\" -I../../../3rdparty/libprocess/include -I../../../3rdparty/libprocess/3rdparty/stout/include -isystem 3rdparty/boost-1.53.0 -I3rdparty/libev-4.15 -I3rdparty/picojson-1.3.0 -DPICOJSON_USE_INT64 -D__STDC_FORMAT_MACROS -I3rdparty/glog-0.3.3/src -I3rdparty/ry-http-parser-1c3624a -I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0 -g1 -O0 -Wno-unused-local-typedefs -std=c++11 -MT libprocess_la-profiler.lo -MD -MP -MF .deps/libprocess_la-profiler.Tpo -c ../../../3rdparty/libprocess/src/profiler.cpp -fPIC -DPIC -o libprocess_la-profiler.o ./libtool: line 1762: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8) mv -f .deps/libprocess_la-profiler.Tpo .deps/libprocess_la-profiler.Plo /bin/bash ./libtool --tag=CXX --mode=compile g++ -DPACKAGE_NAME=\"libprocess\" -DPACKAGE_TARNAME=\"libprocess\" -DPACKAGE_VERSION=\"0.0.1\" -DPACKAGE_STRING=\"libprocess\ 0.0.1\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\"
[jira] [Commented] (MESOS-3216) virtual memory exhausted:: Cannot allocate memory
[ https://issues.apache.org/jira/browse/MESOS-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15306027#comment-15306027 ] Michal Cwienczek commented on MESOS-3216: - libtool: compile: g++ -DPACKAGE_NAME=\"libprocess\" -DPACKAGE_TARNAME=\"libprocess\" -DPACKAGE_VERSION=\"0.0.1\" "-DPACKAGE_STRING=\"libprocess 0.0.1\"" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"libprocess\" -DVERSION=\"0.0.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_APR_POOLS_H=1 -DHAVE_LIBAPR_1=1 -DHAVE_SVN_VERSION_H=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_SVN_DELTA_H=1 -DHAVE_LIBSVN_DELTA_1=1 -DHAVE_LIBCURL=1 -DHAVE_PTHREAD_PRIO_INHERIT=1 -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBDL=1 -I. -I../../../3rdparty/libprocess -DBUILD_DIR=\"/home/vagrant/mesos-0.28.1/build/3rdparty/libprocess\" -I../../../3rdparty/libprocess/include -I../../../3rdparty/libprocess/3rdparty/stout/include -isystem 3rdparty/boost-1.53.0 -I3rdparty/libev-4.15 -I3rdparty/picojson-1.3.0 -DPICOJSON_USE_INT64 -D__STDC_FORMAT_MACROS -I3rdparty/glog-0.3.3/src -I3rdparty/ry-http-parser-1c3624a -I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0 -g1 -O0 -Wno-unused-local-typedefs -std=c++11 -MT libprocess_la-profiler.lo -MD -MP -MF .deps/libprocess_la-profiler.Tpo -c ../../../3rdparty/libprocess/src/profiler.cpp -fPIC -DPIC -o libprocess_la-profiler.o ./libtool: line 1762: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8) mv -f .deps/libprocess_la-profiler.Tpo .deps/libprocess_la-profiler.Plo /bin/bash ./libtool --tag=CXX --mode=compile g++ -DPACKAGE_NAME=\"libprocess\" -DPACKAGE_TARNAME=\"libprocess\" -DPACKAGE_VERSION=\"0.0.1\" -DPACKAGE_STRING=\"libprocess\ 0.0.1\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"libprocess\" -DVERSION=\"0.0.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_APR_POOLS_H=1 -DHAVE_LIBAPR_1=1 -DHAVE_SVN_VERSION_H=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_SVN_DELTA_H=1 -DHAVE_LIBSVN_DELTA_1=1 -DHAVE_LIBCURL=1 -DHAVE_PTHREAD_PRIO_INHERIT=1 -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBDL=1 -I. -I../../../3rdparty/libprocess -DBUILD_DIR=\"/home/vagrant/mesos-0.28.1/build/3rdparty/libprocess\" -I../../../3rdparty/libprocess/include -I../../../3rdparty/libprocess/3rdparty/stout/include -isystem 3rdparty/boost-1.53.0 -I3rdparty/libev-4.15 -I3rdparty/picojson-1.3.0 -DPICOJSON_USE_INT64 -D__STDC_FORMAT_MACROS -I3rdparty/glog-0.3.3/src -I3rdparty/ry-http-parser-1c3624a -I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0 -g1 -O0 -Wno-unused-local-typedefs -std=c++11 -MT libprocess_la-process.lo -MD -MP -MF .deps/libprocess_la-process.Tpo -c -o libprocess_la-process.lo `test -f 'src/process.cpp' || echo '../../../3rdparty/libprocess/'`src/process.cpp libtool: compile: g++ -DPACKAGE_NAME=\"libprocess\" -DPACKAGE_TARNAME=\"libprocess\" -DPACKAGE_VERSION=\"0.0.1\" "-DPACKAGE_STRING=\"libprocess 0.0.1\"" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"libprocess\" -DVERSION=\"0.0.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_APR_POOLS_H=1 -DHAVE_LIBAPR_1=1 -DHAVE_SVN_VERSION_H=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_SVN_DELTA_H=1 -DHAVE_LIBSVN_DELTA_1=1 -DHAVE_LIBCURL=1 -DHAVE_PTHREAD_PRIO_INHERIT=1 -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBDL=1 -I. -I../../../3rdparty/libprocess -DBUILD_DIR=\"/home/vagrant/mesos-0.28.1/build/3rdparty/libprocess\" -I../../../3rdparty/libprocess/include -I../../../3rdparty/libprocess/3rdparty/stout/include -isystem 3rdparty/boost-1.53.0 -I3rdparty/libev-4.15 -I3rdparty/picojson-1.3.0 -DPICOJSON_USE_INT64 -D__STDC_FORMAT_MACROS -I3rdparty/glog-0.3.3/src -I3rdparty/ry-http-parser-1c3624a -I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0 -g1 -O0 -Wno-unused-local-typedefs -std=c++11 -MT libprocess_la-process.lo -MD -MP -MF .deps/libprocess_la-process.Tpo -c ../../../3rdparty/libprocess/src/process.cpp -fPIC -DPIC -o libprocess_la-process.o ./libtool: line 1762: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8) virtual memory exhausted: Cannot allocate memory make[4]: *** [libprocess_la-process.lo] Error 1 make[4]: Leaving directory `/home/vagrant/mesos-0.28.1/build/3rdparty/libprocess' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/vagrant/mesos-0.28.1/build/3rdparty/libprocess' make[2]: *** [all-recursive] Error 1
[jira] [Commented] (MESOS-3216) virtual memory exhausted:: Cannot allocate memory
[ https://issues.apache.org/jira/browse/MESOS-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15306026#comment-15306026 ] Michal Cwienczek commented on MESOS-3216: - ibtool: compile: g++ -DPACKAGE_NAME=\"libprocess\" -DPACKAGE_TARNAME=\"libprocess\" -DPACKAGE_VERSION=\"0.0.1\" "-DPACKAGE_STRING=\"libprocess 0.0.1\"" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"libprocess\" -DVERSION=\"0.0.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_APR_POOLS_H=1 -DHAVE_LIBAPR_1=1 -DHAVE_SVN_VERSION_H=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_SVN_DELTA_H=1 -DHAVE_LIBSVN_DELTA_1=1 -DHAVE_LIBCURL=1 -DHAVE_PTHREAD_PRIO_INHERIT=1 -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBDL=1 -I. -I../../../3rdparty/libprocess -DBUILD_DIR=\"/home/vagrant/mesos-0.28.1/build/3rdparty/libprocess\" -I../../../3rdparty/libprocess/include -I../../../3rdparty/libprocess/3rdparty/stout/include -isystem 3rdparty/boost-1.53.0 -I3rdparty/libev-4.15 -I3rdparty/picojson-1.3.0 -DPICOJSON_USE_INT64 -D__STDC_FORMAT_MACROS -I3rdparty/glog-0.3.3/src -I3rdparty/ry-http-parser-1c3624a -I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0 -g1 -O0 -Wno-unused-local-typedefs -std=c++11 -MT libprocess_la-poll_socket.lo -MD -MP -MF .deps/libprocess_la-poll_socket.Tpo -c ../../../3rdparty/libprocess/src/poll_socket.cpp -fPIC -DPIC -o libprocess_la-poll_socket.o ./libtool: line 1762: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8) mv -f .deps/libprocess_la-poll_socket.Tpo .deps/libprocess_la-poll_socket.Plo /bin/bash ./libtool --tag=CXX --mode=compile g++ -DPACKAGE_NAME=\"libprocess\" -DPACKAGE_TARNAME=\"libprocess\" -DPACKAGE_VERSION=\"0.0.1\" -DPACKAGE_STRING=\"libprocess\ 0.0.1\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"libprocess\" -DVERSION=\"0.0.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_APR_POOLS_H=1 -DHAVE_LIBAPR_1=1 -DHAVE_SVN_VERSION_H=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_SVN_DELTA_H=1 -DHAVE_LIBSVN_DELTA_1=1 -DHAVE_LIBCURL=1 -DHAVE_PTHREAD_PRIO_INHERIT=1 -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBDL=1 -I. -I../../../3rdparty/libprocess -DBUILD_DIR=\"/home/vagrant/mesos-0.28.1/build/3rdparty/libprocess\" -I../../../3rdparty/libprocess/include -I../../../3rdparty/libprocess/3rdparty/stout/include -isystem 3rdparty/boost-1.53.0 -I3rdparty/libev-4.15 -I3rdparty/picojson-1.3.0 -DPICOJSON_USE_INT64 -D__STDC_FORMAT_MACROS -I3rdparty/glog-0.3.3/src -I3rdparty/ry-http-parser-1c3624a -I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0 -g1 -O0 -Wno-unused-local-typedefs -std=c++11 -MT libprocess_la-profiler.lo -MD -MP -MF .deps/libprocess_la-profiler.Tpo -c -o libprocess_la-profiler.lo `test -f 'src/profiler.cpp' || echo '../../../3rdparty/libprocess/'`src/profiler.cpp libtool: compile: g++ -DPACKAGE_NAME=\"libprocess\" -DPACKAGE_TARNAME=\"libprocess\" -DPACKAGE_VERSION=\"0.0.1\" "-DPACKAGE_STRING=\"libprocess 0.0.1\"" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"libprocess\" -DVERSION=\"0.0.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_APR_POOLS_H=1 -DHAVE_LIBAPR_1=1 -DHAVE_SVN_VERSION_H=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_SVN_DELTA_H=1 -DHAVE_LIBSVN_DELTA_1=1 -DHAVE_LIBCURL=1 -DHAVE_PTHREAD_PRIO_INHERIT=1 -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBDL=1 -I. -I../../../3rdparty/libprocess -DBUILD_DIR=\"/home/vagrant/mesos-0.28.1/build/3rdparty/libprocess\" -I../../../3rdparty/libprocess/include -I../../../3rdparty/libprocess/3rdparty/stout/include -isystem 3rdparty/boost-1.53.0 -I3rdparty/libev-4.15 -I3rdparty/picojson-1.3.0 -DPICOJSON_USE_INT64 -D__STDC_FORMAT_MACROS -I3rdparty/glog-0.3.3/src -I3rdparty/ry-http-parser-1c3624a -I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0 -g1 -O0 -Wno-unused-local-typedefs -std=c++11 -MT libprocess_la-profiler.lo -MD -MP -MF .deps/libprocess_la-profiler.Tpo -c ../../../3rdparty/libprocess/src/profiler.cpp -fPIC -DPIC -o libprocess_la-profiler.o ./libtool: line 1762: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8) mv -f .deps/libprocess_la-profiler.Tpo .deps/libprocess_la-profiler.Plo /bin/bash ./libtool --tag=CXX --mode=compile g++ -DPACKAGE_NAME=\"libprocess\" -DPACKAGE_TARNAME=\"libprocess\" -DPACKAGE_VERSION=\"0.0.1\" -DPACKAGE_STRING=\"libprocess\ 0.0.1\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\"
[jira] [Commented] (MESOS-5439) registerExecutor problem
[
https://issues.apache.org/jira/browse/MESOS-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305929#comment-15305929
]
kimjoohwan commented on MESOS-5439:
---
Hello Joseph, Thank you for your comments
1. How many tasks are you launching at once? (i.e. from a single offer) And how
many over a given time?
I using this framework
#!/usr/bin/env python
import os
import sys
import time
import datetime
import mesos.interface
from mesos.interface import mesos_pb2
import mesos.native
TOTAL_TASKS = 32
TASK_CPUS = 1
TASK_MEM = 350
class TestScheduler(mesos.interface.Scheduler):
def __init__(self, implicitAcknowledgements, executor):
self.implicitAcknowledgements = implicitAcknowledgements
self.executor = executor
self.taskData = {}
self.tasksLaunched = 0
self.tasksFinished = 0
self.messagesSent = 0
self.messagesReceived = 0
self.result = " "
self.data = " "
self.tasks = []
self.start = " "
self.end = " "
self.finish = " "
self.time1 = {}
self.time2 = {}
self.time3 = {}
self.time4 = {}
self.time5 = {}
self.time6 = {}
self.time7 = {}
self.time8 = {}
self.time0 = {}
self.count = 0
self.count2 = 0
def work1(self, offer):
tid = self.tasksLaunched
self.tasksLaunched += 1
tasks = []
print "Launching egrep_task %d using offer %s " \
% (tid, offer.hostname)
task = mesos_pb2.TaskInfo()
task.task_id.value = str(tid)
task.slave_id.value = offer.slave_id.value
task.name = "task %d" % tid
executor.executor_id.value = str(tid)
executor.command.value = os.path.abspath("./work1-executor")
task.executor.MergeFrom(self.executor)
cpus = task.resources.add()
cpus.name = "cpus"
cpus.type = mesos_pb2.Value.SCALAR
cpus.scalar.value = TASK_CPUS
mem = task.resources.add()
mem.name = "mem"
mem.type = mesos_pb2.Value.SCALAR
mem.scalar.value = TASK_MEM
return task
def work2(self, offer):
tasks = []
tid = self.tasksLaunched
self.tasksLaunched += 1
print "Launching wc_task %d using offer %s" \
% (tid, offer.hostname)
task = mesos_pb2.TaskInfo()
task.task_id.value = str(tid)
task.slave_id.value = offer.slave_id.value
task.name = "task %d" % tid
executor.executor_id.value = str(tid)
executor.command.value = os.path.abspath("./work2-executor")
task.executor.MergeFrom(self.executor)
cpus = task.resources.add()
cpus.name = "cpus"
cpus.type = mesos_pb2.Value.SCALAR
cpus.scalar.value = TASK_CPUS
mem = task.resources.add()
mem.name = "mem"
mem.type = mesos_pb2.Value.SCALAR
mem.scalar.value = TASK_MEM
print "work2"
return task
def work3(self, offer):
tid = self.tasksLaunched
self.tasksLaunched += 1
tasks = []
print "Launching egrep_task %d using offer %s" \
% (tid, offer.hostname)
task = mesos_pb2.TaskInfo()
task.task_id.value = str(tid)
task.slave_id.value = offer.slave_id.value
task.name = "task %d" % tid
executor.executor_id.value = str(tid)
executor.command.value = os.path.abspath("./work3-executor")
task.executor.MergeFrom(self.executor)
cpus = task.resources.add()
cpus.name = "cpus"
cpus.type = mesos_pb2.Value.SCALAR
cpus.scalar.value = TASK_CPUS
mem = task.resources.add()
mem.name = "mem"
mem.type = mesos_pb2.Value.SCALAR
mem.scalar.value = TASK_MEM
return task
def work4(self, offer):
tasks = []
tid = self.tasksLaunched
self.tasksLaunched += 1
print "Launching wc_task %d using offer %s" \
% (tid, offer.hostname)
task = mesos_pb2.TaskInfo()
task.task_id.value = str(tid)
task.slave_id.value = offer.slave_id.value
task.name = "task %d" % tid
executor.executor_id.value = str(tid)
executor.command.value = os.path.abspath("./work4-executor")
task.executor.MergeFrom(self.executor)
cpus = task.resources.add()
cpus.name = "cpus"
cpus.type = mesos_pb2.Value.SCALAR
cpus.scalar.value = TASK_CPUS
mem = task.resources.add()
mem.name = "mem"
mem.type = mesos_pb2.Value.SCALAR
mem.scalar.value = TASK_MEM
print "work2"
return task
def registered(self, driver, frameworkId, masterInfo):
print "Registered with framework ID %s" % frameworkId.value
self.start = datetime.datetime.now()
def
[jira] [Commented] (MESOS-4642) Mesos Agent Json API can dump binary data from log files out as invalid JSON
[
https://issues.apache.org/jira/browse/MESOS-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305894#comment-15305894
]
Klaus Ma commented on MESOS-4642:
-
[~kaysoky], do you mean all content of JSON or only task related data? I think
in v1.0, only user's data need to be Base64 encoded.
> Mesos Agent Json API can dump binary data from log files out as invalid JSON
>
>
> Key: MESOS-4642
> URL: https://issues.apache.org/jira/browse/MESOS-4642
> Project: Mesos
> Issue Type: Bug
> Components: json api, slave
>Affects Versions: 0.27.0
>Reporter: Steven Schlansker
>Priority: Critical
> Fix For: 1.0.0
>
>
> One of our tasks accidentally started logging binary data to stderr. This
> was not intentional and generally should not happen -- however, it causes
> severe problems with the Mesos Agent "files/read.json" API, since it gladly
> dumps this binary data out as invalid JSON.
> {code}
> # hexdump -C /path/to/task/stderr | tail
> 0003d1f0 6f 6e 6e 65 63 74 69 6f 6e 0a 4e 45 54 3a 20 31 |onnection.NET: 1|
> 0003d200 20 6f 6e 72 65 61 64 20 45 4e 4f 45 4e 54 20 32 | onread ENOENT 2|
> 0003d210 39 35 34 35 36 20 32 35 31 20 32 39 35 37 30 37 |95456 251 295707|
> 0003d220 0a 01 00 00 00 00 00 00 ac 57 65 64 2c 20 31 30 |.Wed, 10|
> 0003d230 20 55 6e 72 65 63 6f 67 6e 69 7a 65 64 20 69 6e | Unrecognized in|
> 0003d240 70 75 74 20 68 65 61 64 65 72 0a |put header.|
> {code}
> {code}
> # curl
> 'http://agent-host:5051/files/read.json?path=/path/to/task/stderr=220443=9='
> | hexdump -C
> 7970 6e 65 63 74 69 6f 6e 5c 6e 4e 45 54 3a 20 31 20 |nection\nNET: 1 |
> 7980 6f 6e 72 65 61 64 20 45 4e 4f 45 4e 54 20 32 39 |onread ENOENT 29|
> 7990 35 34 35 36 20 32 35 31 20 32 39 35 37 30 37 5c |5456 251 295707\|
> 79a0 6e 5c 75 30 30 30 31 5c 75 30 30 30 30 5c 75 30 |n\u0001\u\u0|
> 79b0 30 30 30 5c 75 30 30 30 30 5c 75 30 30 30 30 5c |000\u\u\|
> 79c0 75 30 30 30 30 5c 75 30 30 30 30 ac 57 65 64 2c |u\u.Wed,|
> 79d0 20 31 30 20 55 6e 72 65 63 6f 67 6e 69 7a 65 64 | 10 Unrecognized|
> 79e0 20 69 6e 70 75 74 20 68 65 61 64 65 72 5c 6e 22 | input header\n"|
> 79f0 2c 22 6f 66 66 73 65 74 22 3a 32 32 30 34 34 33 |,"offset":220443|
> 7a00 7d|}|
> {code}
> This causes downstream sadness:
> {code}
> ERROR [2016-02-10 18:55:12,303]
> io.dropwizard.jersey.errors.LoggingExceptionMapper: Error handling a request:
> 0ee749630f8b26f1
> ! com.fasterxml.jackson.core.JsonParseException: Invalid UTF-8 start byte 0xac
> ! at [Source: org.jboss.netty.buffer.ChannelBufferInputStream@6d69ee8; line:
> 1, column: 31181]
> ! at
> com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1487)
> ~[singularity-0.4.9.jar:0.4.9]
> ! at
> com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:518)
> ~[singularity-0.4.9.jar:0.4.9]
> ! at
> com.fasterxml.jackson.core.json.UTF8StreamJsonParser._reportInvalidInitial(UTF8StreamJsonParser.java:3339)
> ~[singularity-0.4.9.jar:0.4.9]
> ! at
> com.fasterxml.jackson.core.json.UTF8StreamJsonParser._reportInvalidChar(UTF8StreamJsonParser.java:)
> ~[singularity-0.4.9.jar:0.4.9]
> ! at
> com.fasterxml.jackson.core.json.UTF8StreamJsonParser._finishString2(UTF8StreamJsonParser.java:2360)
> ~[singularity-0.4.9.jar:0.4.9]
> ! at
> com.fasterxml.jackson.core.json.UTF8StreamJsonParser._finishString(UTF8StreamJsonParser.java:2287)
> ~[singularity-0.4.9.jar:0.4.9]
> ! at
> com.fasterxml.jackson.core.json.UTF8StreamJsonParser.getText(UTF8StreamJsonParser.java:286)
> ~[singularity-0.4.9.jar:0.4.9]
> ! at
> com.fasterxml.jackson.databind.deser.std.StringDeserializer.deserialize(StringDeserializer.java:29)
> ~[singularity-0.4.9.jar:0.4.9]
> ! at
> com.fasterxml.jackson.databind.deser.std.StringDeserializer.deserialize(StringDeserializer.java:12)
> ~[singularity-0.4.9.jar:0.4.9]
> ! at
> com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:523)
> ~[singularity-0.4.9.jar:0.4.9]
> ! at
> com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeUsingPropertyBased(BeanDeserializer.java:381)
> ~[singularity-0.4.9.jar:0.4.9]
> ! at
> com.fasterxml.jackson.databind.deser.BeanDeserializerBase.deserializeFromObjectUsingNonDefault(BeanDeserializerBase.java:1073)
> ~[singularity-0.4.9.jar:0.4.9]
> ! at
> com.fasterxml.jackson.module.afterburner.deser.SuperSonicBeanDeserializer.deserializeFromObject(SuperSonicBeanDeserializer.java:196)
> ~[singularity-0.4.9.jar:0.4.9]
> ! at
> com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:142)
>
[jira] [Commented] (MESOS-5482) mesos task stuck in staging after slave reboot
[ https://issues.apache.org/jira/browse/MESOS-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305887#comment-15305887 ] Klaus Ma commented on MESOS-5482: - OK, thanks :). > mesos task stuck in staging after slave reboot > -- > > Key: MESOS-5482 > URL: https://issues.apache.org/jira/browse/MESOS-5482 > Project: Mesos > Issue Type: Bug >Reporter: lutful karim > > The main idea of mesos/marathon is to sleep well, but after node reboot mesos > task gets stuck in staging for about 4 hours. > To reproduce the issue: > - setup a mesos cluster in HA mode with systemd enabled mesos-master and > mesos-slave service. > - run docker registry (https://hub.docker.com/_/registry/ ) with mesos > constraint (hostname:LIKE:mesos-slave-1) in one node. Reboot the node and > notice that task getting stuck in staging. > Possible workaround: service mesos-slave restart fixes the issue. > OS: centos 7.2 > mesos version: 0.28.1 > marathon: 1.1.1 > zookeeper: 3.4.8 > docker: 1.9.1 dockerAPIversion: 1.21 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2744) MasterAuthorizationTest.SlaveRemoved is flaky
[ https://issues.apache.org/jira/browse/MESOS-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305878#comment-15305878 ] Klaus Ma commented on MESOS-2744: - Re-run this case in MacOS, it passed. It seems OS related, I'll try it later in Ubuntu 15.x. > MasterAuthorizationTest.SlaveRemoved is flaky > - > > Key: MESOS-2744 > URL: https://issues.apache.org/jira/browse/MESOS-2744 > Project: Mesos > Issue Type: Bug >Reporter: haosdent > Labels: flaky, flaky-test > > See (1) and (2), just executed in that order. > Results make for me - from a blackbox point of view - no sense at all. My two > cents/theory - tests themselfs(t.i. the framework's they use) seem to affect > each other. > Will file an issue in your JIRA. Pls provide info for access/handling your > JIRA e.g. is this email as description enough information for your > investigation? > (1) > joma@kopernikus-u:~/dev/programme/mesos/build/mesos/build$ make check > GTEST_FILTER="MasterAuthorizationTest.SlaveRemoved" GTEST_REPEAT=1000 > GTEST_BREAK_ON_FAILURE=1 > ... > Repeating all tests (iteration 1000) . . . > Note: Google Test filter = > MasterAuthorizationTest.SlaveRemoved-DockerContainerizerTest.ROOT_DOCKER_Launch_Executor:DockerContainerizerTest.ROOT_DOCKER_Launch_Executor_Bridged:DockerContainerizerTest.ROOT_DOCKER_Launch:DockerContainerizerTest.ROOT_DOCKER_Kill:DockerContainerizerTest.ROOT_DOCKER_Usage:DockerContainerizerTest.ROOT_DOCKER_Update:DockerContainerizerTest.DISABLED_ROOT_DOCKER_Recover:DockerContainerizerTest.ROOT_DOCKER_SkipRecoverNonDocker:DockerContainerizerTest.ROOT_DOCKER_Logs:DockerContainerizerTest.ROOT_DOCKER_Default_CMD:DockerContainerizerTest.ROOT_DOCKER_Default_CMD_Override:DockerContainerizerTest.ROOT_DOCKER_Default_CMD_Args:DockerContainerizerTest.ROOT_DOCKER_SlaveRecoveryTaskContainer:DockerContainerizerTest.DISABLED_ROOT_DOCKER_SlaveRecoveryExecutorContainer:DockerContainerizerTest.ROOT_DOCKER_PortMapping:DockerContainerizerTest.ROOT_DOCKER_LaunchSandboxWithColon:DockerContainerizerTest.ROOT_DOCKER_DestroyWhileFetching:DockerContainerizerTest.ROOT_DOCKER_Destr > o > yWhilePulling:DockerTest.ROOT_DOCKER_interface:DockerTest.ROOT_DOCKER_CheckCommandWithShell:DockerTest.ROOT_DOCKER_CheckPortResource:DockerTest.ROOT_DOCKER_CancelPull:CpuIsolatorTest/1.UserCpuUsage:CpuIsolatorTest/1.SystemCpuUsage:LimitedCpuIsolatorTest.ROOT_CGROUPS_Cfs:LimitedCpuIsolatorTest.ROOT_CGROUPS_Cfs_Big_Quota:MemIsolatorTest/0.MemUsage:MemIsolatorTest/1.MemUsage:MemIsolatorTest/2.MemUsage:PerfEventIsolatorTest.ROOT_CGROUPS_Sample:SharedFilesystemIsolatorTest.ROOT_RelativeVolume:SharedFilesystemIsolatorTest.ROOT_AbsoluteVolume:NamespacesPidIsolatorTest.ROOT_PidNamespace:UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup:UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup:UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup:MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PerfRollForward:MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PidNamespaceForward:MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PidNamespaceBackward:SlaveTest.ROOT_RunTaskWithCommandInfoWithoutUser:SlaveTest.DI > S > ABLED_ROOT_RunTaskWithCommandInfoWithUser:ContainerizerTest.ROOT_CGROUPS_BalloonFramework:CgroupsAnyHierarchyTest.ROOT_CGROUPS_Enabled:CgroupsAnyHierarchyTest.ROOT_CGROUPS_Subsystems:CgroupsAnyHierarchyTest.ROOT_CGROUPS_Mounted:CgroupsAnyHierarchyTest.ROOT_CGROUPS_Get:CgroupsAnyHierarchyTest.ROOT_CGROUPS_NestedCgroups:CgroupsAnyHierarchyTest.ROOT_CGROUPS_Tasks:CgroupsAnyHierarchyTest.ROOT_CGROUPS_Read:CgroupsAnyHierarchyTest.ROOT_CGROUPS_Write:CgroupsAnyHierarchyTest.ROOT_CGROUPS_Cfs_Big_Quota:CgroupsAnyHierarchyWithCpuMemoryTest.ROOT_CGROUPS_Busy:CgroupsAnyHierarchyWithCpuMemoryTest.ROOT_CGROUPS_SubsystemsHierarchy:CgroupsAnyHierarchyWithCpuMemoryTest.ROOT_CGROUPS_FindCgroupSubsystems:CgroupsAnyHierarchyWithCpuMemoryTest.ROOT_CGROUPS_MountedSubsystems:CgroupsAnyHierarchyWithCpuMemoryTest.ROOT_CGROUPS_CreateRemove:CgroupsAnyHierarchyWithCpuMemoryTest.ROOT_CGROUPS_Listen:CgroupsAnyHierarchyWithCpuMemoryTest.ROOT_CGROUPS_FreezeNonFreezer:CgroupsNoHierarchyTest.ROOT_CGROUPS_NOHIERARCHY_ > M >
[jira] [Commented] (MESOS-5482) mesos task stuck in staging after slave reboot
[ https://issues.apache.org/jira/browse/MESOS-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305859#comment-15305859 ] lutful karim commented on MESOS-5482: - I need to clean up system, setup a new cluster and provide the logs. I will provide soon again. > mesos task stuck in staging after slave reboot > -- > > Key: MESOS-5482 > URL: https://issues.apache.org/jira/browse/MESOS-5482 > Project: Mesos > Issue Type: Bug >Reporter: lutful karim > > The main idea of mesos/marathon is to sleep well, but after node reboot mesos > task gets stuck in staging for about 4 hours. > To reproduce the issue: > - setup a mesos cluster in HA mode with systemd enabled mesos-master and > mesos-slave service. > - run docker registry (https://hub.docker.com/_/registry/ ) with mesos > constraint (hostname:LIKE:mesos-slave-1) in one node. Reboot the node and > notice that task getting stuck in staging. > Possible workaround: service mesos-slave restart fixes the issue. > OS: centos 7.2 > mesos version: 0.28.1 > marathon: 1.1.1 > zookeeper: 3.4.8 > docker: 1.9.1 dockerAPIversion: 1.21 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5482) mesos task stuck in staging after slave reboot
[ https://issues.apache.org/jira/browse/MESOS-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent updated MESOS-5482: Priority: Major (was: Blocker) > mesos task stuck in staging after slave reboot > -- > > Key: MESOS-5482 > URL: https://issues.apache.org/jira/browse/MESOS-5482 > Project: Mesos > Issue Type: Bug >Reporter: lutful karim > > The main idea of mesos/marathon is to sleep well, but after node reboot mesos > task gets stuck in staging for about 4 hours. > To reproduce the issue: > - setup a mesos cluster in HA mode with systemd enabled mesos-master and > mesos-slave service. > - run docker registry (https://hub.docker.com/_/registry/ ) with mesos > constraint (hostname:LIKE:mesos-slave-1) in one node. Reboot the node and > notice that task getting stuck in staging. > Possible workaround: service mesos-slave restart fixes the issue. > OS: centos 7.2 > mesos version: 0.28.1 > marathon: 1.1.1 > zookeeper: 3.4.8 > docker: 1.9.1 dockerAPIversion: 1.21 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5482) mesos task stuck in staging after slave reboot
[ https://issues.apache.org/jira/browse/MESOS-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305858#comment-15305858 ] lutful karim commented on MESOS-5482: - Sure...gimme a minute. > mesos task stuck in staging after slave reboot > -- > > Key: MESOS-5482 > URL: https://issues.apache.org/jira/browse/MESOS-5482 > Project: Mesos > Issue Type: Bug >Reporter: lutful karim > > The main idea of mesos/marathon is to sleep well, but after node reboot mesos > task gets stuck in staging for about 4 hours. > To reproduce the issue: > - setup a mesos cluster in HA mode with systemd enabled mesos-master and > mesos-slave service. > - run docker registry (https://hub.docker.com/_/registry/ ) with mesos > constraint (hostname:LIKE:mesos-slave-1) in one node. Reboot the node and > notice that task getting stuck in staging. > Possible workaround: service mesos-slave restart fixes the issue. > OS: centos 7.2 > mesos version: 0.28.1 > marathon: 1.1.1 > zookeeper: 3.4.8 > docker: 1.9.1 dockerAPIversion: 1.21 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5482) mesos task stuck in staging after slave reboot
[ https://issues.apache.org/jira/browse/MESOS-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lutful karim updated MESOS-5482: Description: The main idea of mesos/marathon is to sleep well, but after node reboot mesos task gets stuck in staging for about 4 hours. To reproduce the issue: - setup a mesos cluster in HA mode with systemd enabled mesos-master and mesos-slave service. - run docker registry (https://hub.docker.com/_/registry/ ) with mesos constraint (hostname:LIKE:mesos-slave-1) in one node. Reboot the node and notice that task getting stuck in staging. Possible workaround: service mesos-slave restart fixes the issue. OS: centos 7.2 mesos version: 0.28.1 marathon: 1.1.1 zookeeper: 3.4.8 docker: 1.9.1 dockerAPIversion: 1.21 was: The main idea of mesos/marathon is to sleep well, but after node reboot mesos task gets stuck in staging for about 4 hours. To reproduce the issue: - setup a mesos cluster in HA mode with systemd enabled mesos-master and mesos-slave service. - run docker registry with mesos constraint (hostname:LIKE:mesos-slave-1) in one node. Reboot the node and notice that task getting stuck in staging. Possible workaround: service mesos-slave restart fixes the issue. OS: centos 7.2 mesos version: 0.28.1 marathon: 1.1.1 zookeeper: 3.4.8 docker: 1.9.1 dockerAPIversion: 1.21 > mesos task stuck in staging after slave reboot > -- > > Key: MESOS-5482 > URL: https://issues.apache.org/jira/browse/MESOS-5482 > Project: Mesos > Issue Type: Bug >Reporter: lutful karim >Priority: Blocker > > The main idea of mesos/marathon is to sleep well, but after node reboot mesos > task gets stuck in staging for about 4 hours. > To reproduce the issue: > - setup a mesos cluster in HA mode with systemd enabled mesos-master and > mesos-slave service. > - run docker registry (https://hub.docker.com/_/registry/ ) with mesos > constraint (hostname:LIKE:mesos-slave-1) in one node. Reboot the node and > notice that task getting stuck in staging. > Possible workaround: service mesos-slave restart fixes the issue. > OS: centos 7.2 > mesos version: 0.28.1 > marathon: 1.1.1 > zookeeper: 3.4.8 > docker: 1.9.1 dockerAPIversion: 1.21 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5482) mesos task stuck in staging after slave reboot
[ https://issues.apache.org/jira/browse/MESOS-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305857#comment-15305857 ] Klaus Ma commented on MESOS-5482: - [~gufran...@yahoo.com], would you share mesos-master, mesos-slave and marathon's log? Is there any other service can run in the rebooted node? > mesos task stuck in staging after slave reboot > -- > > Key: MESOS-5482 > URL: https://issues.apache.org/jira/browse/MESOS-5482 > Project: Mesos > Issue Type: Bug >Reporter: lutful karim >Priority: Blocker > > The main idea of mesos/marathon is to sleep well, but after node reboot mesos > task gets stuck in staging for about 4 hours. > To reproduce the issue: > - setup a mesos cluster in HA mode with systemd enabled mesos-master and > mesos-slave service. > - run docker registry with mesos constraint (hostname:LIKE:mesos-slave-1) in > one node. Reboot the node and notice that task getting stuck in staging. > Possible workaround: service mesos-slave restart fixes the issue. > OS: centos 7.2 > mesos version: 0.28.1 > marathon: 1.1.1 > zookeeper: 3.4.8 > docker: 1.9.1 dockerAPIversion: 1.21 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5482) mesos task stuck in staging after slave reboot
[ https://issues.apache.org/jira/browse/MESOS-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lutful karim updated MESOS-5482: Summary: mesos task stuck in staging after slave reboot (was: mesos task stuck in stagin after slave reboot) > mesos task stuck in staging after slave reboot > -- > > Key: MESOS-5482 > URL: https://issues.apache.org/jira/browse/MESOS-5482 > Project: Mesos > Issue Type: Bug >Reporter: lutful karim >Priority: Blocker > > The main idea of mesos/marathon is to sleep well, but after node reboot mesos > task gets stuck in staging for about 4 hours. > To reproduce the issue: > - setup a mesos cluster in HA mode with systemd enabled mesos-master and > mesos-slave service. > - run docker registry with mesos constraint (hostname:LIKE:mesos-slave-1) in > one node. Reboot the node and notice that task getting stuck in staging. > Possible workaround: service mesos-slave restart fixes the issue. > OS: centos 7.2 > mesos version: 0.28.1 > marathon: 1.1.1 > zookeeper: 3.4.8 > docker: 1.9.1 dockerAPIversion: 1.21 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5482) mesos task stuck in stagin after slave reboot
[ https://issues.apache.org/jira/browse/MESOS-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lutful karim updated MESOS-5482: Description: The main idea of mesos/marathon is to sleep well, but after node reboot mesos task gets stuck in staging for about 4 hours. To reproduce the issue: - setup a mesos cluster in HA mode with systemd enabled mesos-master and mesos-slave service. - run docker registry with mesos constraint (hostname:LIKE:mesos-slave-1) in one node. Reboot the node and notice that task getting stuck in staging. Possible workaround: service mesos-slave restart fixes the issue. OS: centos 7.2 mesos version: 0.28.1 marathon: 1.1.1 zookeeper: 3.4.8 docker: 1.9.1 dockerAPIversion: 1.21 was: The main idea of mesos/marathon is to sleep well, but after node reboot mesos task gets stuck in staging for about 4 hours. To reproduce the issue: - setup a mesos cluster with systemd enabled mesos-master and mesos-slave service. - run docker registry with mesos constraint in one node. Reboot the node and notice that task getting stuck in staging. Possible workaround: service mesos-slave restart fixes the issue. mesos version: 0.28.1 marathon: 1.1.1 zookeeper: 3.4.8 docker: 1.9.1 dockerAPIversion: 1.21 > mesos task stuck in stagin after slave reboot > - > > Key: MESOS-5482 > URL: https://issues.apache.org/jira/browse/MESOS-5482 > Project: Mesos > Issue Type: Bug >Reporter: lutful karim >Priority: Blocker > > The main idea of mesos/marathon is to sleep well, but after node reboot mesos > task gets stuck in staging for about 4 hours. > To reproduce the issue: > - setup a mesos cluster in HA mode with systemd enabled mesos-master and > mesos-slave service. > - run docker registry with mesos constraint (hostname:LIKE:mesos-slave-1) in > one node. Reboot the node and notice that task getting stuck in staging. > Possible workaround: service mesos-slave restart fixes the issue. > OS: centos 7.2 > mesos version: 0.28.1 > marathon: 1.1.1 > zookeeper: 3.4.8 > docker: 1.9.1 dockerAPIversion: 1.21 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5483) SlaveCount/Registrar_BENCHMARK_Test.Performance/3 failed
haosdent created MESOS-5483:
---
Summary: SlaveCount/Registrar_BENCHMARK_Test.Performance/3 failed
Key: MESOS-5483
URL: https://issues.apache.org/jira/browse/MESOS-5483
Project: Mesos
Issue Type: Bug
Reporter: haosdent
Assignee: haosdent
Priority: Minor
When we simulate 5 agents in Registrar_BENCHMARK_Test test cases, it failed
when
{code}
[ RUN ] SlaveCount/Registrar_BENCHMARK_Test.Performance/3
../../src/tests/registrar_tests.cpp:1225: Failure
Failed to wait 15secs for registry
[ FAILED ] SlaveCount/Registrar_BENCHMARK_Test.Performance/3, where
GetParam() = 5 (60264 ms)
{code}
In my machine, it elapse
{code}
I0529 17:49:50.078006 59434 registrar_tests.cpp:1227] Recovered 5 agents
(8238915B) in 23.141143715secs
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-5482) mesos task stuck in stagin after slave reboot
lutful karim created MESOS-5482: --- Summary: mesos task stuck in stagin after slave reboot Key: MESOS-5482 URL: https://issues.apache.org/jira/browse/MESOS-5482 Project: Mesos Issue Type: Bug Reporter: lutful karim Priority: Blocker The main idea of mesos/marathon is to sleep well, but after node reboot mesos task gets stuck in staging for about 4 hours. To reproduce the issue: - setup a mesos cluster with systemd enabled mesos-master and mesos-slave service. - run docker registry with mesos constraint in one node. Reboot the node and notice that task getting stuck in staging. Possible workaround: service mesos-slave restart fixes the issue. mesos version: 0.28.1 marathon: 1.1.1 zookeeper: 3.4.8 docker: 1.9.1 dockerAPIversion: 1.21 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
