[jira] [Created] (MESOS-5390) v1 Executor Protos not included in maven jar

Ben Whitehead created MESOS-5390: Summary: v1 Executor Protos not included in maven jar Key: MESOS-5390 URL: https://issues.apache.org/jira/browse/MESOS-5390 Project: Mesos Issue Type: Bug

[jira] [Commented] (MESOS-3902) Mesos HTTP Scheduler API does not perform master redirection when it's not the leader

[ https://issues.apache.org/jira/browse/MESOS-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15168211#comment-15168211 ] Ben Whitehead commented on MESOS-3902: -- The master now sets a location header, but it's incomplete.

[jira] [Created] (MESOS-3923) Implement Authorization handling for HTTP Scheduler API

Ben Whitehead created MESOS-3923: Summary: Implement Authorization handling for HTTP Scheduler API Key: MESOS-3923 URL: https://issues.apache.org/jira/browse/MESOS-3923 Project: Mesos Issue

[jira] [Updated] (MESOS-3902) Mesos HTTP Scheduler API does not perform master redirection when it's not the leader

[ https://issues.apache.org/jira/browse/MESOS-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Whitehead updated MESOS-3902: - Description: When I attempt to send a {{SUBSCRIBE}} call to a non-leading master instead of

[jira] [Created] (MESOS-3747) HTTP Scheduler API no longer allows FrameworkInfo.user to be empty string

Ben Whitehead created MESOS-3747: Summary: HTTP Scheduler API no longer allows FrameworkInfo.user to be empty string Key: MESOS-3747 URL: https://issues.apache.org/jira/browse/MESOS-3747 Project:

[jira] [Updated] (MESOS-3562) Anomalous bytes in stream from HTTPI Api

[ https://issues.apache.org/jira/browse/MESOS-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Whitehead updated MESOS-3562: - Description: When connecting to the new HTTP Api and attempting to {{SUBSCRIBE}} there are some

[jira] [Commented] (MESOS-3747) HTTP Scheduler API no longer allows FrameworkInfo.user to be empty string

[ https://issues.apache.org/jira/browse/MESOS-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14959582#comment-14959582 ] Ben Whitehead commented on MESOS-3747: -- Requested logs of a framework using libmesos and tasks being

[jira] [Created] (MESOS-3739) Mesos does not set Content-Type for 400 Bad Request

Ben Whitehead created MESOS-3739: Summary: Mesos does not set Content-Type for 400 Bad Request Key: MESOS-3739 URL: https://issues.apache.org/jira/browse/MESOS-3739 Project: Mesos Issue

[jira] [Commented] (MESOS-3601) Formalize all headers and metadata for HTTP API Event Stream

[ https://issues.apache.org/jira/browse/MESOS-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14947516#comment-14947516 ] Ben Whitehead commented on MESOS-3601: -- As I understand it, part of the motivation for RecordIO was

[jira] [Commented] (MESOS-3566) Add a section to the Scheduler HTTP API docs around RecordIO specification

[ https://issues.apache.org/jira/browse/MESOS-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14947282#comment-14947282 ] Ben Whitehead commented on MESOS-3566: -- I would prefer there to be some documentation on RecordIO

[jira] [Commented] (MESOS-3566) Add a section to the Scheduler HTTP API docs around RecordIO specification

[ https://issues.apache.org/jira/browse/MESOS-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14947324#comment-14947324 ] Ben Whitehead commented on MESOS-3566: -- The documentation for the HTTP API should also explain why

[jira] [Created] (MESOS-3601) Formalize all headers and metadata for HTTP API Event Stream

Ben Whitehead created MESOS-3601: Summary: Formalize all headers and metadata for HTTP API Event Stream Key: MESOS-3601 URL: https://issues.apache.org/jira/browse/MESOS-3601 Project: Mesos

[jira] [Updated] (MESOS-3562) Anomalous bytes in stream from HTTPI Api

[ https://issues.apache.org/jira/browse/MESOS-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Whitehead updated MESOS-3562: - Attachment: tcpdump.log app.log > Anomalous bytes in stream from HTTPI Api >

[jira] [Created] (MESOS-3562) Anomalous bytes in stream from HTTPI Api

Ben Whitehead created MESOS-3562: Summary: Anomalous bytes in stream from HTTPI Api Key: MESOS-3562 URL: https://issues.apache.org/jira/browse/MESOS-3562 Project: Mesos Issue Type: Bug

[jira] [Commented] (MESOS-3562) Anomalous bytes in stream from HTTPI Api

[ https://issues.apache.org/jira/browse/MESOS-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14938932#comment-14938932 ] Ben Whitehead commented on MESOS-3562: -- [~vinodkone] [~anandmazumdar] [~ijimenez] Ping > Anomalous

[jira] [Updated] (MESOS-3562) Anomalous bytes in stream from HTTPI Api

[ https://issues.apache.org/jira/browse/MESOS-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Whitehead updated MESOS-3562: - Description: When connecting to the new HTTP Api and attempting to {{SUBSCRIBE}} there are some

[jira] [Commented] (MESOS-3562) Anomalous bytes in stream from HTTPI Api

[ https://issues.apache.org/jira/browse/MESOS-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939173#comment-14939173 ] Ben Whitehead commented on MESOS-3562: -- This isn't really standard chunks though, there are chunks

[jira] [Created] (MESOS-3524) HTTP API v1 Protobuf Jar in maven central

Ben Whitehead created MESOS-3524: Summary: HTTP API v1 Protobuf Jar in maven central Key: MESOS-3524 URL: https://issues.apache.org/jira/browse/MESOS-3524 Project: Mesos Issue Type: Story

[jira] [Commented] (MESOS-3013) Extend ContainerInfo to include "NetworkInfo" message

[ https://issues.apache.org/jira/browse/MESOS-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735822#comment-14735822 ] Ben Whitehead commented on MESOS-3013: -- Is mesos implementing the communication constraint based on

[jira] [Commented] (MESOS-2257) Set Mesos specific content type with version for HTTP endpoints

[ https://issues.apache.org/jira/browse/MESOS-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14621382#comment-14621382 ] Ben Whitehead commented on MESOS-2257: -- This is for things that aren't frameworks.

[jira] [Commented] (MESOS-2841) FrameworkInfo should include a Labels field to support arbitrary, lightweight metadata

[ https://issues.apache.org/jira/browse/MESOS-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14590162#comment-14590162 ] Ben Whitehead commented on MESOS-2841: -- Ah, missed the {{uri}} vs {{url}} subtlety.

[jira] [Commented] (MESOS-2841) FrameworkInfo should include a Labels field to support arbitrary, lightweight metadata

[ https://issues.apache.org/jira/browse/MESOS-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14590805#comment-14590805 ] Ben Whitehead commented on MESOS-2841: -- I think structured and unstructured can be

[jira] [Commented] (MESOS-2841) FrameworkInfo should include a Labels field to support arbitrary, lightweight metadata

[ https://issues.apache.org/jira/browse/MESOS-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14590801#comment-14590801 ] Ben Whitehead commented on MESOS-2841: -- Makes sense, I used the word Resource in an

[jira] [Commented] (MESOS-2841) FrameworkInfo should include a Labels field to support arbitrary, lightweight metadata

[ https://issues.apache.org/jira/browse/MESOS-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14589093#comment-14589093 ] Ben Whitehead commented on MESOS-2841: -- I think something like that would probably be

[jira] [Commented] (MESOS-2841) FrameworkInfo should include a Labels field to support arbitrary, lightweight metadata

[ https://issues.apache.org/jira/browse/MESOS-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14587291#comment-14587291 ] Ben Whitehead commented on MESOS-2841: -- I like the idea of a framework being able to

[jira] [Commented] (MESOS-2644) AS a framework developer I WANT to check and depend on a Mesos (master) version

[ https://issues.apache.org/jira/browse/MESOS-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14507953#comment-14507953 ] Ben Whitehead commented on MESOS-2644: -- Perhaps the concept that is applied to

[jira] [Commented] (MESOS-2644) AS a framework developer I WANT to check and depend on a Mesos (master) version

[ https://issues.apache.org/jira/browse/MESOS-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14507937#comment-14507937 ] Ben Whitehead commented on MESOS-2644: -- To extend it a bit further: As a framework

[jira] [Commented] (MESOS-313) report executor deaths to framework schedulers

[ https://issues.apache.org/jira/browse/MESOS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14299250#comment-14299250 ] Ben Whitehead commented on MESOS-313: - I recently ran into this issue when working on