Latest news; We dp still have blocking issues. The release cut is being delayed
once again towards the end-of-day, today. That gives us the weekend to prepare
a release candidate.
Some blocking issues that did not show any progress or communication were now
re-targeted in silent consensus.
Alex
Hi,
we are interested in exposing user resource limits (rlimits) to Mesos so
executors can prepare environments for task with differing limit requirements.
The design doc can be found here,
https://docs.google.com/document/d/148og6TlknWIG2d-VmyCG01eliiOGhNEc12mG4TWsfHU/edit?usp=sharing
Fe
Thanks for the response.
May I know if there are any reasons for not continuing to develop and
support MPI framework? Are there any known issues with running MPI jobs on
Mesos?
Best Regards,
Mangirish
On Fri, Oct 14, 2016 at 2:20 AM, haosdent wrote:
> Refer to https://issues.apache.org/jira/bro
+1
Thanks MPark! I've dropped the ball several times recently and forgotten to
set up hangouts for these meetings, so I can also accept some of the
responsibility for the decline in consistency and attendance; my apologies.
I'm happy to help out going forward MPark, let me know if you need
anythin
Other than test frameworks or frameworks Mesos considers part of its CLI,
there shouldn't be any other Frameworks that are part of the Mesos
codebase. (Imagine shipping Spark or Marathon or a bunch of other
humongous frameworks along with Mesos.) Same thing goes for MPI, which may
or may not even
Hi Joseph,
Thanks for your response.
What I really want to know is, whether there are any particular reasons why
the community has not been supporting any work related to MPI on Mesos.
There has been some good demand for cloud based MPI support. Given the
known resource management capabilities of
Hi folks,
I'd like input from individuals who currently use frameworks but do
not enable checkpointing.
Background: "checkpointing" is a parameter that can be enabled in
FrameworkInfo; if enabled, the agent will write the framework pid,
executor PIDs, and status updates to disk for any tasks star
Thanks Alex for starting this!
In addition to comments below, I think it'll be helpful to keep the
existing versioning doc concise and user-friendly while having a dedicated
doc for the "implementation details" where precise requirements and
procedures go. Maybe some duplication/cross-referencing
On Fri, Oct 14, 2016 at 3:37 PM, Yan Xu wrote:
> Thanks Alex for starting this!
>
> In addition to comments below, I think it'll be helpful to keep the
> existing versioning doc concise and user-friendly while having a dedicated
> doc for the "implementation details" where precise requirements an
We will chat about this in the upcoming community sync (thursday 3 PM). So,
please make sure to attend if you are interested.
On Fri, Oct 14, 2016 at 3:44 PM, Yan Xu wrote:
>
> On Fri, Oct 14, 2016 at 3:37 PM, Yan Xu wrote:
>
>> Thanks Alex for starting this!
>>
>> In addition to comments below
Thanks @mpark and @greg. Another question is if we could set up a Google
calendar reminder in our slack via slackbot, refer to
https://slackhq.com/google-calendar-reminders-come-to-slack-8b8c515bfe87#.a6gqxvj5x
So that @grep don't need to send notification message in #general channel
everytime.
On
11 matches
Mail list logo