No update, I'm afraid, still waiting for a review from the shepherd.
Implemented all suggested changes, but before investing more time on this,
I want to be sure I'm on the right track.
Been burned already a few times, having gone through several reviews cycle,
done all that was asked of me, and
Marco
Any progress on getting an update to this? It is a blocker on fixing the
perf issues.
Thanks
-- Paul
On Mon, Jul 13, 2015 at 3:24 PM, Paul Brett (JIRA) j...@apache.org wrote:
[
+1 (binding)
This vote has been silent for almost a week. I assume everybody's busy
testing. My testing results: basic integration tests passed for Mesos
0.23.0 on CoreOS with DCOS GUI/CLI, Marathon, Chronos, Spark, HDFS,
Cassandra, and Kafka.
`make check` passes on Ubuntu and CentOS, but `sudo
I wasn't referring to default configuration, but yeah we should improve
that!
Some operators already run production setups not using the default
configuration (e.g. --credentials and non-permissive --acls so that only
authenticated / authorized frameworks can connect and run workloads).
For
Found a bug in HTTP API related code: MESOS-3055
https://issues.apache.org/jira/browse/MESOS-3055
If we don't fix this in 0.23.0, we cannot expect the 0.24.0 scheduler
driver (that will send Calls) to properly subscribe with a 0.23.0 master. I
could add a work around in the driver to only send
Related: https://issues.apache.org/jira/browse/MESOS-3024 HTTP endpoint
authN is enabled merely by specifying --credentials
We cannot rely on --credentials as the only way to enable/disable HTTP
endpoints, as web auth should not be tied so closely to framework/slave
auth. There needs to be a
-1 so that we can cherry pick MESOS-3055.
The master crash bug is MESOS-3070
https://issues.apache.org/jira/browse/MESOS-3070 but the fix is
non-trivial and the bug has been in the code base prior to 23.0. So I won't
make it a blocker.
Can't update the spreadsheet. So here are the commits I
No, no - no frustration at all :)
It was just me going down the wrong path too fast, without waiting for
advice.
(as allegedly a Turkish proverb says: No matter how far down the wrong
path you're gone, it's never too late to turn back - I'm hoping someone
from Turkey on the list can confirm or
The 7 day voting period has ended with only 2 binding +1s (we needed 3) and
no explicit -1s.
However, Vinod says they've found a bug that crashes master when a
framework uses duplicate task ids.
Vinod, can you please share the new JIRA and officially vote -1 for rc3 if
you want to call for an rc4?
Thanks, Vinod. I've got those commits in the list already. We'll pull in
fixes for MESOS-3055 and others for rc4.
I'll give it another night for Bernd to commit the fetcher fix and for
Niklas to update the oversubscription doc.
Then I'll cut rc4 tomorrow and leave the new vote open until next
Adam - thanks.
Please let me know soon as you push an rc4, if I'm still home, I can test
it against Ubuntu 14.04 with/without SSL, with/without sudo (or I can
always VPN in :)
Very minor doc update: https://reviews.apache.org/r/36532/
(feel free to ignore).
Thanks, everyone!
*Marco Massenzio*
Hey sorry for the frustration, I wrote subprocess originally but it's
evolved over time through a number of folks. Is ben going to shepherd this?
Just a few higher level things to consider:
(1) Discard semantics: with subprocess the caller has the ability to kill
the process through s.pid.
As Adam mention I also think this is not a blocker, as it only affects
the way we test the cgroup on CentOS 7.x due to a CentOS bug and
doesn't actually impact Mesos normal operations.
My vote is +1 as well.
Tim
On Thu, Jul 16, 2015 at 12:10 PM, Vinod Kone vinodk...@gmail.com wrote:
Found a
Thanks for all your feedback!
We feel that we gained enough feedback and understanding to start creating
Jiras for the first part (i.e. HTTP endpoints, validation and persistence
of quota requests). If you any objections/additional feedback let us know!
For the open question above: For the MVP we
14 matches
Mail list logo
