>
> On Mon, Mar 6, 2017 at 7:51 PM, Zameer Manji <zma...@apache.org> wrote:
> > Hey,
> >
> > I noticed there is a TODO on the TimeInfo for adding Time Zone
> information.
> > ```
> > /**
> > * Represents time since the epoch, in nanos
understanding the TimeInfo much easier when it is received by the framework.
--
Zameer Manji
atibility,
> but they will always be empty.) We can also remove "orphan tasks" from
> the web UI.
>
> In addition to declaring that Mesos 1.3.0 masters will not support
> pre-1.0 Mesos agents in the CHANGELOG, it seems safer to me to
> disallow such agents from registering.
>
> Comments welcome.
>
> Thanks,
> Neil
>
> --
> Zameer Manji
>
;
> > Should we explore a more reliable way to track metrics independently from
> > libprocess's queue?
> >
> > --
> > Cheers,
> >
> > Zhitao Li
> >
>
>
>
> --
> Best Regards,
> Haosdent Huang
>
> --
> Zameer Manji
>
the Apple toolchain supports the c++11 standard.
> > >
> > > As I am not a common user of the Apple development experience I would
> > like
> > > to ask for some input from the community as to whether requiring this
> > > toolchain update is acceptable, and if we need a deprecation period or
> if
> > > we can just make this change now.
> > >
> > > I am leaning towards no deprecation period as I am not aware of
> > production
> > > environments running on systems that define `__APPLE__`.
> > > —
> > > *Joris Van Remoortere*
> > > Mesosphere
> > >
> >
>
> --
> Zameer Manji
>
uilt a new jar file. Is there any reason why these proto definitions
> > are not included in the original build apart from the reason that the
> APIs
> > are still evolving?
> >
> > Regards
> > Vijay
> >
>
> --
> Zameer Manji
>
>
> —
> *Joris Van Remoortere*
> Mesosphere
>
> On Wed, Nov 2, 2016 at 1:49 PM, Zameer Manji <zma...@apache.org> wrote:
>
> > Joris,
> >
> > You make a good point. However, I'm not convinced that `CommandInfo`
> should
> > be the well defined con
command information to them.
>
> The current model works well in a 1-1 mapping between framework and
> executor binaries. In a world where that is 1-N it means all N executors
> have to use the same method of passing the command.
>
> —
> *Joris Van Remoortere*
> Mesosphere
>
t; The signature of the tarball can be found at:
>> https://dist.apache.org/repos/dist/dev/mesos/1.1.0-rc1/mesos
>> -1.1.0.tar.gz.asc
>>
>> The PGP key used to sign the release is here:
>> https://dist.apache.org/repos/dist/release/mesos/KEYS
>>
>> The JAR is up in Maven in a staging repository here:
>> https://repository.apache.org/content/repositories/orgapachemesos-1158
>>
>> Please vote on releasing this package as Apache Mesos 1.1.0!
>>
>> The vote is open until Fri Oct 21 21:57:02 CEST 2016 and passes if a
>> majority of at least 3 +1 PMC votes are cast.
>>
>> [ ] +1 Release this package as Apache Mesos 1.1.0
>> [ ] -1 Do not release this package because ...
>>
>> Thanks,
>> Alex & Till
>>
>>
>
>
> --
> David Robinson
> SRE - Mesos
> @daverobinson
>
> --
> Zameer Manji
>
have to get this data via
> `TaskInfo.bytes`
> > which is not ideal.
> >
> > Are there any custom executors out there that crash if they get Tasks
> with
> > CommandInfo set?
> >
> > Thoughts?
> >
> > Vinod
> >
>
>
>
> --
> Best Regards,
> Haosdent Huang
>
> --
> Zameer Manji
>
ting on the slaves (I
> do not see an agent flag for that), I think checkpointing should be enabled
> in framework level rather than slave.
>
>
> Thanks,
> Qian Zhang
>
> On Sun, Oct 16, 2016 at 10:18 AM, Zameer Manji <zma...@apache.org> wrote:
>
>> +1 to
SOS-4049), we are
>> considering:
>>
>> (a) requiring that partition-aware frameworks must also enable
>> checkpointing, and/or
>> (b) enabling checkpointing by default
>>
>> If you have intentionally decided to disable checkpointing for your
>> Mesos framework, I'd be curious to hear more about your use-case and
>> why you haven't enabled it.
>>
>> Thanks!
>>
>> Neil
>>
>> --
>> Zameer Manji
>>
>
ie
>
> On Fri, Oct 7, 2016 at 5:28 PM, Zameer Manji <zma...@apache.org> wrote:
>
> > Jie,
> >
> > Without commenting on this deprecation, how is this going to work now
> that
> > Mesos is 1.0?
> >
> > What is the definition of "deprecate&
because it'll be really
> confusing to executor writers, and it'll be an error if they try to access
> $MESOS_DIRECTORY if their container has a root filesystem defined.
>
> - Jie
>
> --
> Zameer Manji
>
> T:$TASK_ID and as the context and lines with similar context can be
> more easily correlated visually.
>
> Is this feasible?
>
> Cheers,
>
> Frank
>
> --
> Zameer Manji
>
I might be in the minority here, but I think cutting an RC for 1.0 right
now is very aggressive. Does there exist even a single framework that uses
the Scheduler HTTP API or the Executor HTTP API? Does anyone even use these
APIs in production? Is there a single entity that uses the Operator API to
y but talk to a 0.27 (or earlier) master will
> not
> > be able to register because the message will be dropped.
> >
> > Ben
> >
>
>
>
> --
> Deshi Xiao
> Twitter: xds2000
> E-mail: xiaods(AT)gmail.com
>
> --
> Zameer Manji
>
> <http://gmail.com>
ant
> to
> > backport it to other releases as well.
> >
>
> It should be backported to whichever releases it applies to and you
> support,
> I don't see Mesos community has such a procedure.
>
> --
> Zameer Manji
>
>
t; Please let me know if you find further issues with 0.27.1.
>
> Thanks,
>
> MPark
>
> --
> Zameer Manji
>
>
re flags appropriate for
> > end-users (rather than Mesos developers): developers will be familiar
> > enough with Mesos to tune the configure flags according to their own
> > preferences.
> >
> > (3) The performance consequences of not enabling compiler
> > optimizations can be pretty severe: 5x in a benchmark I just ran, and
> > we've seen between 2x and 30x (!) performance differences for some
> > real-world workloads.
> >
> > Neil
>
> --
> Zameer Manji
>
>
; > this happen? I want my task to remain alive when the framework is
> > disconnected/dead.
> >
> > Here is how i create my framework
> > https://gist.github.com/anonymous/3357783ce938c4293947
> >
> > and here is how i create my task
> > https://gist.github.com/anonymous/d35f917ade791127f4c5
> >
> > Thanks
> > suppandi
> >
>
> --
> Zameer Manji
>
>
ving it. So functionality that has been
> >> deprecated in 0.26 can be safely removed in 0.32.
> >>
> >> Mixed Cluster Versions:
> >> ==
> >>
> >> We could adopt the same rule as above (if any two releases are made
> >> within six months of one another, they must be compatible), or else we
> >> could keep the same compatibility policy we have now (single release).
> >> I'm not sure the right answer here: keeping the current policy will
> >> make upgrading from, say, 0.26 to 0.32 somewhat painful, but (a) that
> >> can be ameliorated with deployment tooling (b) if we change to a 6-12
> >> month compatibility period, it will make testing the full
> >> compatibility matrix pretty difficult.
> >>
> >> Comments welcome!
> >>
> >> Neil
> >>
>
> --
> Zameer Manji
>
>
t;
> > On 28 September 2015 at 21:09, James DeFelice <james.defel...@gmail.com>
> > wrote:
> >
> >> +1 for time-based deprecation cycle of O(months)
> >>
> >>> On Mon, Sep 28, 2015 at 6:16 PM, Zameer Manji <zma...@apache.org>
> wrote
On March 10, 2015, 11:40 a.m., Zameer Manji wrote:
src/common/type_utils.cpp, line 56
https://reviews.apache.org/r/31905/diff/1/?file=890459#file890459line56
Would it be possible to add some sort of test or tooling to prevent
regressions?
Vinod Kone wrote:
Not sure, what
/#comment123254
Would it be possible to add some sort of test or tooling to prevent
regressions?
- Zameer Manji
On March 10, 2015, 11:27 a.m., Vinod Kone wrote:
---
This is an automatically generated e-mail. To reply, visit:
https
, Alexander Rukletsov, Joerg Schad, Till Toenshoff,
Vinod Kone, and Zameer Manji.
Bugs: mesos-2309
https://issues.apache.org/jira/browse/mesos-2309
Repository: mesos
Description
---
type_utils: Relaxened the equality check of CommandInfo to allow 'unset'
environment
in a generic
manner? For example the 'role' field of FrameworkInfo has the same problem:
https://github.com/apache/mesos/blob/1efdf1d69373cca7903bc06847f1c44a91383032/include/mesos/mesos.proto#L128
- Zameer Manji
On Feb. 17, 2015, 4:58 a.m., Joerg Schad wrote
this and a brief explanation on how it works can be
found in
this gist: https://gist.github.com/zmanji/f41df77510ef9d00265a. I hope it
serves
as a good example on how this problem can be mitigated.
--
Zameer Manji
Zameer Manji created MESOS-847:
--
Summary: Update Mesos webui favicon to use Mesos Logo
Key: MESOS-847
URL: https://issues.apache.org/jira/browse/MESOS-847
Project: Mesos
Issue Type: Improvement
29 matches
Mail list logo
