[jira] [Comment Edited] (MESOS-6644) Mesos master failed to devolve Scheduler HTTP v1 Call
[
https://issues.apache.org/jira/browse/MESOS-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15741036#comment-15741036
]
Zhongbo Tian edited comment on MESOS-6644 at 12/12/16 5:36 AM:
---
Hmm, seems our message is too large:
{code}
$ ls -al mesos_protobuf_exception.txt
-rw-r--r-- 1 tianzhongbo tianzhongbo 90893605 12月 12 13:06
mesos_protobuf_exception.txt
{code}
and when I tries to devolve this message manually, I gets:
{code}
[libprotobuf ERROR google/protobuf/io/coded_stream.cc:171] A protocol message
was rejected because it was too big (more than 67108864 bytes). To increase
the limit (or to disable these warnings), see
CodedInputStream::SetTotalBytesLimit() in google/protobuf/io/coded_stream.h.
{code}
was (Author: windreamer):
Hmm, seems our message is too large:
``$ ls -al mesos_protobuf_exception.txt
-rw-r--r-- 1 tianzhongbo tianzhongbo 90893605 12月 12 13:06
mesos_protobuf_exception.txt
``
and when I tries to devolve this message manually, I gets:
``[libprotobuf ERROR google/protobuf/io/coded_stream.cc:171] A protocol message
was rejected because it was too big (more than 67108864 bytes). To increase
the limit (or to disable these warnings), see
CodedInputStream::SetTotalBytesLimit() in google/protobuf/io/coded_stream.h.
``
> Mesos master failed to devolve Scheduler HTTP v1 Call
> -
>
> Key: MESOS-6644
> URL: https://issues.apache.org/jira/browse/MESOS-6644
> Project: Mesos
> Issue Type: Bug
> Components: HTTP API
>Affects Versions: 0.27.2
>Reporter: Zhongbo Tian
> Attachments: parsed_result_by_windreamer.txt
>
>
> Master failed with an assertion:
> {code:none}
> Check failed: t.ParsePartialFromString(data) Failed to parse
> mesos.scheduler.Call while devolving from mesos.v1.scheduler.Call
> {code}
> it is rare and hard to catch, so we patch the master to trying to dump the
> failed message:
> {code:none}
> diff --git a/src/internal/devolve.cpp b/src/internal/devolve.cpp
> index efcc5d6..0c457a9 100644
> --- a/src/internal/devolve.cpp
> +++ b/src/internal/devolve.cpp
> @@ -42,7 +42,8 @@ static T devolve(const google::protobuf::Message& message)
>// be set and we don't want an exception to get thrown.
>CHECK(t.ParsePartialFromString(data))
> << "Failed to parse " << t.GetTypeName()
> -<< " while devolving from " << message.GetTypeName();
> +<< " while devolving from " << message.GetTypeName()
> +<< " data: [" << data << "]";
>
>return t;
> }
> {code}
> and we get a partial dump of the message (seems glog only keep 32k logging
> maximum"), pls get the base64-ed dumped message here
> {code:none}
> curl -Ls
> https://gist.github.com/windreamer/48fb1b99ee3d4398f746766ee5879149/raw/8e5038c7d47c3db297bd12724ac1cca67ba93f53/dumped.base64|
> base64 -d
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MESOS-6644) Mesos master failed to devolve Scheduler HTTP v1 Call
[
https://issues.apache.org/jira/browse/MESOS-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15741036#comment-15741036
]
Zhongbo Tian edited comment on MESOS-6644 at 12/12/16 5:35 AM:
---
Hmm, seems our message is too large:
``$ ls -al mesos_protobuf_exception.txt
-rw-r--r-- 1 tianzhongbo tianzhongbo 90893605 12月 12 13:06
mesos_protobuf_exception.txt
``
and when I tries to devolve this message manually, I gets:
``[libprotobuf ERROR google/protobuf/io/coded_stream.cc:171] A protocol message
was rejected because it was too big (more than 67108864 bytes). To increase
the limit (or to disable these warnings), see
CodedInputStream::SetTotalBytesLimit() in google/protobuf/io/coded_stream.h.
``
was (Author: windreamer):
Hmm, seems our message is too large:
```
$ ls -al mesos_protobuf_exception.txt
-rw-r--r-- 1 tianzhongbo tianzhongbo 90893605 12月 12 13:06
mesos_protobuf_exception.txt
```
and when I tries to devolve this message manually, I gets:
```
[libprotobuf ERROR google/protobuf/io/coded_stream.cc:171] A protocol message
was rejected because it was too big (more than 67108864 bytes). To increase
the limit (or to disable these warnings), see
CodedInputStream::SetTotalBytesLimit() in google/protobuf/io/coded_stream.h.
```
> Mesos master failed to devolve Scheduler HTTP v1 Call
> -
>
> Key: MESOS-6644
> URL: https://issues.apache.org/jira/browse/MESOS-6644
> Project: Mesos
> Issue Type: Bug
> Components: HTTP API
>Affects Versions: 0.27.2
>Reporter: Zhongbo Tian
> Attachments: parsed_result_by_windreamer.txt
>
>
> Master failed with an assertion:
> {code:none}
> Check failed: t.ParsePartialFromString(data) Failed to parse
> mesos.scheduler.Call while devolving from mesos.v1.scheduler.Call
> {code}
> it is rare and hard to catch, so we patch the master to trying to dump the
> failed message:
> {code:none}
> diff --git a/src/internal/devolve.cpp b/src/internal/devolve.cpp
> index efcc5d6..0c457a9 100644
> --- a/src/internal/devolve.cpp
> +++ b/src/internal/devolve.cpp
> @@ -42,7 +42,8 @@ static T devolve(const google::protobuf::Message& message)
>// be set and we don't want an exception to get thrown.
>CHECK(t.ParsePartialFromString(data))
> << "Failed to parse " << t.GetTypeName()
> -<< " while devolving from " << message.GetTypeName();
> +<< " while devolving from " << message.GetTypeName()
> +<< " data: [" << data << "]";
>
>return t;
> }
> {code}
> and we get a partial dump of the message (seems glog only keep 32k logging
> maximum"), pls get the base64-ed dumped message here
> {code:none}
> curl -Ls
> https://gist.github.com/windreamer/48fb1b99ee3d4398f746766ee5879149/raw/8e5038c7d47c3db297bd12724ac1cca67ba93f53/dumped.base64|
> base64 -d
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-6644) Mesos master failed to devolve Scheduler HTTP v1 Call
[
https://issues.apache.org/jira/browse/MESOS-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15741036#comment-15741036
]
Zhongbo Tian commented on MESOS-6644:
-
Hmm, seems our message is too large:
```
$ ls -al mesos_protobuf_exception.txt
-rw-r--r-- 1 tianzhongbo tianzhongbo 90893605 12月 12 13:06
mesos_protobuf_exception.txt
```
and when I tries to devolve this message manually, I gets:
```
[libprotobuf ERROR google/protobuf/io/coded_stream.cc:171] A protocol message
was rejected because it was too big (more than 67108864 bytes). To increase
the limit (or to disable these warnings), see
CodedInputStream::SetTotalBytesLimit() in google/protobuf/io/coded_stream.h.
```
> Mesos master failed to devolve Scheduler HTTP v1 Call
> -
>
> Key: MESOS-6644
> URL: https://issues.apache.org/jira/browse/MESOS-6644
> Project: Mesos
> Issue Type: Bug
> Components: HTTP API
>Affects Versions: 0.27.2
>Reporter: Zhongbo Tian
> Attachments: parsed_result_by_windreamer.txt
>
>
> Master failed with an assertion:
> {code:none}
> Check failed: t.ParsePartialFromString(data) Failed to parse
> mesos.scheduler.Call while devolving from mesos.v1.scheduler.Call
> {code}
> it is rare and hard to catch, so we patch the master to trying to dump the
> failed message:
> {code:none}
> diff --git a/src/internal/devolve.cpp b/src/internal/devolve.cpp
> index efcc5d6..0c457a9 100644
> --- a/src/internal/devolve.cpp
> +++ b/src/internal/devolve.cpp
> @@ -42,7 +42,8 @@ static T devolve(const google::protobuf::Message& message)
>// be set and we don't want an exception to get thrown.
>CHECK(t.ParsePartialFromString(data))
> << "Failed to parse " << t.GetTypeName()
> -<< " while devolving from " << message.GetTypeName();
> +<< " while devolving from " << message.GetTypeName()
> +<< " data: [" << data << "]";
>
>return t;
> }
> {code}
> and we get a partial dump of the message (seems glog only keep 32k logging
> maximum"), pls get the base64-ed dumped message here
> {code:none}
> curl -Ls
> https://gist.github.com/windreamer/48fb1b99ee3d4398f746766ee5879149/raw/8e5038c7d47c3db297bd12724ac1cca67ba93f53/dumped.base64|
> base64 -d
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-907) Add Kerberos Authentication support
[ https://issues.apache.org/jira/browse/MESOS-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15740923#comment-15740923 ] haijiang.chen commented on MESOS-907: - OK, It seems resonable. > Add Kerberos Authentication support > --- > > Key: MESOS-907 > URL: https://issues.apache.org/jira/browse/MESOS-907 > Project: Mesos > Issue Type: Story > Components: general >Reporter: Adam B >Assignee: Tim Anderegg > Labels: security, twitter > > MESOS-704 added basic authentication support using CRAM-MD5 through SASL. Now > we should integrate Kerberos authentication using GSS-API, which is already > supported by SASL. Kerberos is a widely-used industry standard authentication > service, and integration with Mesos will make it easier for customers to > integrate their existing security process with Mesos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-6742) Adding support for s390x architecture
[ https://issues.apache.org/jira/browse/MESOS-6742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15740669#comment-15740669 ] Vinod Kone commented on MESOS-6742: --- Added you to contributors on JIRA so you can assign issues to yourself. Feel free to send a PR/review to add yourself to https://github.com/apache/mesos/blob/master/docs/contributors.yaml > Adding support for s390x architecture > -- > > Key: MESOS-6742 > URL: https://issues.apache.org/jira/browse/MESOS-6742 > Project: Mesos > Issue Type: Bug >Reporter: Ayanampudi Varsha > > There are 2 issues: > 1. LdcacheTest.Parse test case fails on s390x machines. > 2. From the value of flag docker_registry in slave/flags.cpp, amd64 images > get downloaded due to which test cases fail on s390x with "Exec format Error" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-6777) IOSwitchboardTest.RecoverThenKillSwitchboardContainerDestroyed hangs on FreeBSD
David Forsythe created MESOS-6777: - Summary: IOSwitchboardTest.RecoverThenKillSwitchboardContainerDestroyed hangs on FreeBSD Key: MESOS-6777 URL: https://issues.apache.org/jira/browse/MESOS-6777 Project: Mesos Issue Type: Bug Reporter: David Forsythe Assignee: David Forsythe -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MESOS-6726) IOSwitchboardServerFlags adds flags for non-optional fields w/o providing a default value
[
https://issues.apache.org/jira/browse/MESOS-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15739746#comment-15739746
]
Benjamin Bannier edited comment on MESOS-6726 at 12/11/16 1:33 PM:
---
Above RR was committed without updating the RR and ignoring raised issues.
was (Author: bbannier):
Above RR was committed without updating the RR and and ignoring raised issues.
> IOSwitchboardServerFlags adds flags for non-optional fields w/o providing a
> default value
> -
>
> Key: MESOS-6726
> URL: https://issues.apache.org/jira/browse/MESOS-6726
> Project: Mesos
> Issue Type: Bug
>Reporter: Benjamin Bannier
>Assignee: Kevin Klues
> Labels: tech-debt
> Fix For: 1.2.0
>
>
> The class {{IOSwitchboardFlags}} contains a number of members of
> non-{{Option}}, fundamental type (i.e., types which do not have
> constructors). As customary for a {{Flags}} class, these fields are not
> initialized since usually the initialization is done by the calling the
> correct overload of {{FlagsBase::add}} taking a default value.
> The class {{IOSwitchbardFlags}} calls an {{add}} overload acting on a
> non-{{Option}} member which does not take the default value. This can lead to
> the members containing garbage values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-6726) IOSwitchboardServerFlags adds flags for non-optional fields w/o providing a default value
[
https://issues.apache.org/jira/browse/MESOS-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15739746#comment-15739746
]
Benjamin Bannier commented on MESOS-6726:
-
Above RR was committed without updating the RR and and ignoring raised issues.
> IOSwitchboardServerFlags adds flags for non-optional fields w/o providing a
> default value
> -
>
> Key: MESOS-6726
> URL: https://issues.apache.org/jira/browse/MESOS-6726
> Project: Mesos
> Issue Type: Bug
>Reporter: Benjamin Bannier
>Assignee: Kevin Klues
> Labels: tech-debt
> Fix For: 1.2.0
>
>
> The class {{IOSwitchboardFlags}} contains a number of members of
> non-{{Option}}, fundamental type (i.e., types which do not have
> constructors). As customary for a {{Flags}} class, these fields are not
> initialized since usually the initialization is done by the calling the
> correct overload of {{FlagsBase::add}} taking a default value.
> The class {{IOSwitchbardFlags}} calls an {{add}} overload acting on a
> non-{{Option}} member which does not take the default value. This can lead to
> the members containing garbage values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
