I think MESOS-8169 is a candidate, but I don't be able to get to it until next
week
> On Nov 3, 2017, at 1:48 AM, Qian Zhang wrote:
>
> And I will backport MESOS-8051 to 1.2.x, 1.3.x and 1.4.x.
>
>
> Regards,
> Qian Zhang
>
> On Fri, Nov 3, 2017 at 9:01 AM, Qian Zhang
It isn't clear to me how DC/OS would benefit from (ongoing) work to
create/push Mesos packages. DC/OS downloads and builds all of its
component parts from source.
Also, we (Mesos devs) are hoping to get more frameworks to move away from
using libmesos (including the API shims), in favor of using
This is great to see! Thanks for driving this Kapil.
Once the official packages are vetted, we should update our website to
point users to it. For new users, getting started with binary packages is
infinitely better than having to build from source.
Folks, please help us by testing this packages
I've filed a JIRA for it here:
https://issues.apache.org/jira/browse/MESOS-8169
The change I'm proposing would change validation (for slave reregistration)
to only enforce ExecutorID uniqueness in the context of (FrameworkID,
SlaveID) as opposed to simply SlaveID as currently implemented.
This
Github user abudnik commented on the issue:
https://github.com/apache/mesos/pull/248
If some framework relies on the assumption that there shouldn't be multiple
executors running with the same executor_id on the same agent, then this change
might lead to bugs.
It would be great
Github user jdef commented on the issue:
https://github.com/apache/mesos/pull/248
@abudnik the master.hpp code you cited is already scoped to Framework. I
don't think we need to change anything there.
---
Github user abudnik commented on the issue:
https://github.com/apache/mesos/pull/248
Should we also update comment
https://github.com/apache/mesos/blob/master/include/mesos/mesos.proto#L78-L82 ?
---
Github user abudnik commented on the issue:
https://github.com/apache/mesos/pull/248
We should also update here
https://github.com/apache/mesos/blob/master/src/master/master.hpp#L2665-L2667
and maybe in other places, where master/agent checks for duplicate executor
ids.
---
Hi All,
We have some updates regarding the binary RPM build/release process for
Mesos.
Here are some important bullet points:
* Jira: https://issues.apache.org/jira/browse/MESOS-7981
* The RPM packages are now built using a jenkins job [1] on the Apache CI.
* The build scripts are part of the
Github user jpeach commented on a diff in the pull request:
https://github.com/apache/mesos/pull/248#discussion_r148843748
--- Diff: src/master/validation.cpp ---
@@ -298,7 +299,9 @@ Option reregisterSlave(
const vector& frameworkInfos)
{
hashset frameworkIDs;
Github user jpeach commented on a diff in the pull request:
https://github.com/apache/mesos/pull/248#discussion_r148844153
--- Diff: src/master/validation.cpp ---
@@ -350,12 +353,13 @@ Option reregisterSlave(
}
if (executor.has_executor_id()) {
- if
+ dev list for visibility and history.
Okay, let's dig into this a little bit : ).
First, it is true that Marathon and Mesos HTTP health checks are not
equivalent. It's not just 1xx status codes, you can't have multiple Mesos
health checks for example. I don't understand why you say that the
Please reply to this email if you have pending patches to backport to 1.2.x.
I'm aiming to cut a 1.2.3 next week. This will be the last 1.2.x release.
I see 3 JIRAs targeted for 1.2.3, but none of them look quite ready to land:
Hi,
I'd like to contribute to DC/OS with a Debian/Suse/... support.
Surprisingly on Debian most of the compatibility issues could be solved by
a sequence of symlinks.
Why Mesos dev list? :)
Currently the biggest issue is connected to distributing libmesos-bundle
tar archive, which contain the
Github user jdef commented on the issue:
https://github.com/apache/mesos/pull/248
https://issues.apache.org/jira/browse/MESOS-8169
---
Github user jpeach commented on the issue:
https://github.com/apache/mesos/pull/248
@jdef Good find! Can you please make a JIRA for this?
---
Github user jdef commented on the issue:
https://github.com/apache/mesos/pull/248
@jpeach it looks like you were in here recently, what are your thoughts on
this?
---
Github user jdef commented on a diff in the pull request:
https://github.com/apache/mesos/pull/248#discussion_r148790566
--- Diff: src/master/validation.cpp ---
@@ -350,12 +353,13 @@ Option reregisterSlave(
}
if (executor.has_executor_id()) {
- if
Hi Benjamin,
Apologies for the delay. GC seem be working fine. Folders older than 2 hours
are being deleted. After change of config and restart, Mesos agent took some
time to delete the old folder that are around before the restart. I may have
jumped the gun.
Thanks,
Venkat
> On Oct 30,
GitHub user jdef opened a pull request:
https://github.com/apache/mesos/pull/248
Fix master validation, incorrect detection of dup ExecutorID.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jdef/mesos
And I will backport MESOS-8051 to 1.2.x, 1.3.x and 1.4.x.
Regards,
Qian Zhang
On Fri, Nov 3, 2017 at 9:01 AM, Qian Zhang wrote:
> We want to backport https://reviews.apache.org/r/62518/ to 1.2.x, 1.3.x
> and 1.4.x, James will work on it.
>
>
> Regards,
> Qian Zhang
>
> On
21 matches
Mail list logo