Hi all,
The vote for Mesos 1.8.1 (rc1) has passed with the
following votes.
+1 (Binding)
--
Vinod Kone
Meng Zhu
Greg Mann
There were no 0 or -1 votes.
Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/1.8.1
It is recommended to use a
Hi all,
Please vote on releasing the following candidate as Apache Mesos 1.8.1.
We had a lot of good bugfixes that only very slightly missed the 1.8.0
release, some just by a few days. By now, the 1.8.x branch seems to have
calmed down a bit, so it seems to be a good opportunity to do an 1.8.1
e using OpenSSL calls.
>
> Please review.
>
> [1]
> https://docs.google.com/document/d/1O3q7UOXVGNw81xOkRNFPzrtbC__D-N_D_mwV6D--y0k/edit
>
--
Benno Evers
Software Engineer, Mesosphere
cking pending libprocess futures
> [2].
> >
> > Please review both of them.
> >
> > [1] Container debug endpoint:
> https://docs.google.com/document/d/1VtlKD6b8a22HzSdaJUeI7cPGuKd01vLwBJT4XfkeUDI
> > [2] Tracking libprocess futures:
> https://docs.google.com/document/d/1Unu2pe0dRq3Z6XQ5S8lWZm2cU2REjfkUj0xk2ePQ0MY
>
>
--
Benno Evers
Software Engineer, Mesosphere
Hi all,
The vote for Mesos 1.8.0 (rc3) has passed with the
following votes.
+1 (Binding)
--
Vinod Kone
Alex Rukletsov
Meng Zhu
+1 (Non-binding)
--
Jorge Machado
There were no 0 or -1 votes.
Please find the release at:
InvalidArgumentError'>, Default
> MaxPoolingOp only supports NHWC on device type CPU
>[[node tower_0/v/cg/mpool0/MaxPool (defined at
> /user/tf-benchmarks-113/scripts/tf_cnn_benchmarks/convnet_builder.py:261) ]
>
> running this on nvidia-docker2 works fine.
>
> image us
Addendum:
The vote is open until Thursday, May 2nd.
On Fri, Apr 26, 2019 at 6:28 PM Benno Evers wrote:
> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.8.0.
>
>
> 1.8.0 incl
Hi all,
Please vote on releasing the following candidate as Apache Mesos 1.8.0.
1.8.0 includes the following:
* Greatly reduced allocator cycle time.
* Operation feedback for v1 schedulers.
* Per-framework
;> [ FAILED ] VolumeGidManagerTest.ROOT_UNPRIVILEGED_USER_SlaveReboot
>> [ FAILED ] CniIsolatorTest.VETH_VerifyResourceStatistics
>> [ FAILED ]
>> DockerVolumeIsolatorTest.ROOT_EmptyCheckpointFileSlaveRecovery
>>
>>
>> On Thu, Apr 18, 2019 at 3:00
Hi all,
Please vote on releasing the following candidate as Apache Mesos 1.8.0.
1.8.0 includes the following:
* Greatly reduced allocator cycle time.
* Operation feedback for v1 schedulers.
* Per-framework
Hi all,
the vote for Mesos 1.8.0 (rc1) has *not* passed, with one +1 vote and one
-1 vote.
Since the issue that caused the -1 vote has already been fixed on master
and been backported to the release branch, a vote for rc2 will promptly
follow.
Best regards,
Benno
aster?
>
> On Mon, Apr 15, 2019 at 2:26 PM Benno Evers wrote:
>
> > Hi all,
> >
> > Please vote on releasing the following candidate as Apache Mesos 1.8.0.
> >
> >
> > 1.8.0 includes the following:
> >
> >
> --
Hi all,
Please vote on releasing the following candidate as Apache Mesos 1.8.0.
1.8.0 includes the following:
* Operation feedback for v1 schedulers.
* Per-framework minimum allocatable resources.
* New CLI
l,
> > > We are intending to update the bundled glog from 0.3.3 to 0.4.0.
> > >
> > > If you have any objections/concerns, or know about any issues
> introduced
> > > into glog between 0.3.3 and 0.4.0, please raise them.
> > >
> > > Corre
by the pending release, feel free to go wild now ;)
Best regards,
--
Benno Evers
Software Engineer, Mesosphere
st hangs. No logs nothing...
> I'm testing this on ubuntu 18.04.
>
> Any tipps ?
> thanks
> Jorge
>
>
> Jorge Machado
> www.jmachado.me
>
>
>
>
>
>
--
Benno Evers
Software Engineer, Mesosphere
ideas, etc.
Best regards,
--
Benno Evers
Software Engineer, Mesosphere
switching to LDAP logins.
Since reviewboard supports only exactly one sign-up backend, so when they
enabled LDAP, "classic" signup was disabled in the process. We're still
trying to get some background on this decision from the ASF Infra team.
Best regards,
--
Benno Evers
Softwar
peration status updates. This approach is the simplest in terms of the
> implementation,
> but the trade-off is that the framework needs to live with (1).
>
>
> So far we haven't discussed much about (2) for operation reconciliation, so
> let's also briefly talk
> about it. Potentially (2) can be addressed by making the agent *actively
> push *
> *operation statusupdates to the framework when an LRP is resubscribed*, so
> the framework won't need to do
> periodic operation reconciliation. If we do this in the future, it would
> also be more aligned with
> proposal II or III.
>
> So the question again: is it worth the complexity to keep
> `RECONCILE_OPERATIONS`
> synchronous? I'd like to hear the opinions from the community so we can
> drive towards a better
> API design!
>
> Best,
> Chun-Hung
>
--
Benno Evers
Software Engineer, Mesosphere
active in the project for almost a year and has been
>> very productive and collaborative. He is now one of the few people of
>> understands the allocator code well, as well as the roadmap for this area
>> of the project. He has also found and fixed bugs, and helped users in slac
etter than I expected, but I hope there's good
> tracking on getting these un-disabled again:
>
> $ grep -R DISABLED src/tests | grep -v DISABLED_ON_WINDOWS | grep -v
> NestedQuota | grep -v ChildRole | grep -v NestedRoles | grep -v
> environment.cpp | wc -l
> 22
>
> On Fri
then as we
might have hoped.
Hope this was interesting, and best regards,
--
Benno Evers
Software Engineer, Mesosphere
Ok then, let's not do it for now.
Best regards,
On Fri, Aug 10, 2018 at 6:10 PM, James Peach wrote:
>
>
> > On Aug 10, 2018, at 8:56 AM, Benno Evers wrote:
> >
> > Hi guys,
> >
> > it's quite late in the release cycle, but I've been thinking about
&
- The bundled jemalloc version (5.0.1) has been released as stable for
over a year and has not seen any severe bugs
- Our own Mesos builds with jemalloc don't show any issues so far
What do you think?
Best regards,
--
Benno Evers
Software Engineer, Mesosphere
out whether we should overwrite
> checkpointed data upon permitted changed.
>
>
> On Thu, Feb 22, 2018 at 9:44 AM, Benno Evers
> wrote:
>
> > Hi,
> >
> > I'm afraid these were mostly informal lunch-time discussions, but I just
> > opened https://issues.apa
at are the other reasons tests are DISABLED today?
>
> On Thu, Mar 29, 2018 at 10:35 AM, Meng Zhu <m...@mesosphere.com> wrote:
>
> > +1, the advantages are appealing.
> >
> > Though I am afraid that this will probably reduce the incentive to fix
> > flaky tests.
&g
hat do you think?
Best regards,
--
Benno Evers
Software Engineer, Mesosphere
capturing existing discussions?
>
> On Mon, Feb 19, 2018 at 9:59 AM, Benno Evers <bev...@mesosphere.com>
> wrote:
>
> > Hi Zhitao,
> >
> > great to see that there's interest in this.
> >
> > The most specific concern that we had at the time was that w
Just a quick follow-up, the version was bumped to 1.65 in 469363d.
On Tue, Jan 9, 2018 at 6:51 PM, Vinod Kone <vinodk...@gmail.com> wrote:
> If it’s backwards compatible then let’s go for it.
>
> @vinodkone
>
> > On Jan 9, 2018, at 9:21 AM, Benno Evers <bev...@mesosp
on't think this will effect the python
> bindings, at least initially. The tests that I aim to run with tox are
> mostly CLI-related. In the long term though, it may be worth
> considering
> using tox to perform all python-related build/test tasks.
>
> Eric
>
much easier, which we are facing
>>>> increasing pressure to address.
>>>>
>>>> The biggest concern here would probably the change in dependencies,
>>>> since
>>>> it may seem like we're adding an additional dependency to mesos. However
>>>> since virtualenv is a dependency of tox, we will not break any existing
>>>> dependencies, as requiring tox will automatically require virtualenv.
>>>> Otherwise I don't really see any downside in making the switch.
>>>>
>>>> Please let me know what you think!
>>>>
>>>> Eric
>>>>
>>>
>>>
>
>
> --
> Armand Grillet
> Software Engineer, Mesosphere
>
--
Benno Evers
Software Engineer, Mesosphere
the community about this?
Best regards,
--
Benno Evers
Software Engineer, Mesosphere
://reviews.apache.org/r/64384/ and share the feedback about any issues
it causes (or doesn't cause).
Best regards,
--
Benno Evers
Software Engineer, Mesosphere
style.py#L406).
> This is a not a common event as you can see from the history of the CLI
> pip-requirements.txt:
> https://github.com/apache/mesos/commits/master/src/python/cli_new/pip-
> requirements.txt
> and
> https://github.com/apache/mesos/commits/2d19111e4852aed25161e4549ff704
&g
sal would be to move most checks to
post-reviews.py, which is a slow operation anyways and which actually marks
the point in time where the commits should be cleaned up enough to pass all
checks.
What do you think?
Best regards,
--
Benno Evers
Software Engineer, Mesosphere
Whoops, sorry, done.
On Thu, Nov 9, 2017 at 6:41 AM, Zhitao Li <zhitaoli...@gmail.com> wrote:
> Can you allow viewers to comment on the doc? Thanks
>
> On Wed, Nov 8, 2017 at 5:06 PM, Benno Evers <bev...@mesosphere.com> wrote:
>
> > Thanks to everyone for the
n Sat, Nov 4, 2017 at 6:26 PM, Benno Evers <bev...@mesosphere.com> wrote:
>
> > Hi all,
> >
> > most people are probably familiar with the behaviour of the mesos-agent
> > that refuses to start when it detects incompatible slave information
> from a
> > p
e executors and exit.
Use this option when doing an incompatible agent
or executor upgrade!). (default: reconnect)
Best regards,
--
Benno Evers
Software Engineer, Mesosphere
are welcome and highly valued.
Best regards,
--
Benno Evers
Software Engineer, Mesosphere
that some framework you depend on would choke on this, now
would be a good time to update it before upgrading to Mesos 1.5.0 ;)
Best regards,
--
Benno Evers
Software Engineer, Mesosphere
On Wed, Aug 23, 2017 at 11:38 AM, Benno Evers <bev...@mesosphere.com> wrote:
> Hi all,
>
> when
is set to 4 it appears
> (without OMP) that libmesos or libprocess still spawn an additional 12
> threads. So what are those 12 threads used for?
>
> Oh - this is the (ancient) 0.28.3-2.0.1 release for Ubuntu 14.04 LTS, in
> case that matters.
>
> Cheers,
>
> Jim
>
> --
> S
build process for jemalloc
> against a specific branch. We already maintain local changes for some other
> 3rd party dependencies.
>
> /Jeff
>
> -Original Message-
> From: Benno Evers [mailto:bev...@mesosphere.com]
> Sent: Tuesday, September 5, 2017 4:02 AM
> To: dev@
I did not log the "reason" of the ERROR, so I do not know
> what occured, and cannot at this stage reproduce manually the use case.
>
> Can we have "non terminal" errors, from mesos point of view, where task
> should not be considered as over?
>
> Thanks
>
> Olivier
>
--
Benno Evers
Software Engineer, Mesosphere
s to the build step of those
> packages.
>
> Seems that without trying it, we won’t find out if jemalloc works as hoped
> on Windows for us - the Firefox project results however are encouraging. On
> the other hand, if it doesn’t work, we could simply decide to disable it on
> Windows
t;> >>> The second phase was refactoring the Mesos build itself (that is, not
>>> the
>>> >>> third party dependencies). With all our dependencies imported
>>> properly, I
>>> >>> was able to delete the files of extraneous information such as
>>> >>> `MasterConfigure.cmake`, `AgentConfigure.cmake`, etc. This
>>> information
>>> is
>>> >>> instead correctly stored in the aforementioned CMake dependency
>>> graph.
>>> >>>
>>> >>> With this all put together, the entirety of the required CMake code
>>> to
>>> >>> build the agent executable, on all platforms, is the following _two
>>> >>> lines_:
>>> >>>
>>> >>> add_executable(mesos-agent main.cpp)
>>> >>> target_link_libraries(mesos-agent PRIVATE mesos)
>>> >>>
>>> >>> All necessary link and compilation flags are parsed by CMake through
>>> the
>>> >>> dependency graph as it visits libmesos as the mesos-agent dependency.
>>> >>>
>>> >>> I keep an updated tree on GitHub here for easy testing:
>>> >>> https://github.com/andschwa/mesos/blob/cmake-refactor/src/sl
>>> >>> ave/CMakeLists.txt
>>> >>>
>>> >>> As we move closer to deprecating Autotools, I wanted to ensure that
>>> the
>>> >>> replacement build system was as correct and easy-to-use as possible.
>>> As
>>> >>> with any build system (and any software engineering effort), there is
>>> >>> always more to clean up and improve. However, I am satisfied with the
>>> >>> result of my efforts, and I hope this build system makes your work as
>>> >>> developers easier. If you have the time, please take a look at the
>>> the
>>> >>> patches and give it a test. Let me know know I can make it work
>>> better
>>> >>> for
>>> >>> you.
>>> >>>
>>> >>> Thank you,
>>> >>>
>>> >>> Andrew Schwartzmeyer
>>> >>>
>>> >>>
>>>
>>>
--
Benno Evers
Software Engineer, Mesosphere
Windows (from past work I've
> done). I'm unsure about either jemalloc and tcmalloc, however.
>
> Thanks,
>
> /Jeff
>
> -Original Message-
> From: Benno Evers [mailto:bev...@mesosphere.com]
> Sent: Tuesday, August 22, 2017 3:16 AM
> To: dev@mesos.apache.org
&g
the `docker inspect`
command for the started container.
On Wed, Aug 23, 2017 at 4:54 PM, James Peach <jor...@gmail.com> wrote:
>
> > On Aug 23, 2017, at 2:38 AM, Benno Evers <bev...@mesosphere.com> wrote:
> >
> > Hi all,
> >
> > when starting
-in mesos executors, and
2. it doesn't handle the possibility of receiving TASK_STARTING update, and
3. it reports an error whenever it encounters an unexpected task states in
an update.
If you are aware of any such framework, please speak up so we can consider
it.
Thanks,
--
Benno Evers
Software
advantages and disadvantages of both options.
>
> Alexander Rojas
> alexan...@mesosphere.io
>
>
>
>
> > On 18. Aug 2017, at 12:49, Benno Evers <bev...@mesosphere.com> wrote:
> >
> > Hi all,
> >
> > I would like to propose bundling
of this change.
Users who compile Mesos themselves would of course have the option
to disable jemalloc at configuration time or replace it with their
memory allocator of choice.
I'm looking forward to hear any thoughts and comments.
Thanks,
--
Benno Evers
Software Engineer, Mesosphere
50 matches
Mail list logo
