ah, ok - sorry, I do use Ngnix, but a bit like a caveman :)
we (as in, Mesosphere) recommend that Mesos (master/agents) are run under
supervision (either systemd or upstart or supervisord or your favorite
supervisor) so that when the process gets killed (by accident / bug /
planned restart) the su
On Tue, Nov 24, 2015 at 3:15 PM, Marco Massenzio
wrote:
> On Tue, Nov 24, 2015 at 10:45 AM, Adam Avilla wrote:
>
> > Is there any way to support HUP reloading of config with this design
> > paradigm?
>
>
> Can you please elaborate what do you mean by "support HUP reloading"?
> I don't suppose an
We are still hoping to land things by the end of the year, but it will
depend on the bandwidth the committers have to actually devote time to
this work. They, understandably, are busy with other important
initiatives. :)
On Tue, Nov 24, 2015 at 7:43 AM, tommy xiao wrote:
> when can we use the sla
not bad! I like it
> 在 2015年11月25日，00:48，Marco Massenzio 写道：
>
> Thank you for asking :)
>
> The idea is pretty simple (and not even original, it's the "Facade
> pattern"): essentially we would define a YAML syntax for the various
> configuration flags that Mesos ({Master, Agent}) define, possi
On Tue, Nov 24, 2015 at 10:45 AM, Adam Avilla wrote:
> Is there any way to support HUP reloading of config with this design
> paradigm?
Can you please elaborate what do you mean by "support HUP reloading"?
I don't suppose anyone really runs Mesos in production inside a terminal?
At any rate, b
Is there any way to support HUP reloading of config with this design
paradigm? Is HUPing mesos even possible / helpful? From an end user
perspective it sounds useful, but I am not sure if even possible for mesos
to accomplish safely.
On Nov 24, 2015 10:04 AM, "haosdent" wrote:
> Use YAML sounds g
HTTP API would be the recommended way for frameworks to interact with
Mesos. The plan is to deprecate the driver based framework communication
once we release 1.0 and remove the driver support in 2.0.
Current status: Scheduler HTTP API is in beta. We are still fixing bugs and
adding features (e.g.
Use YAML sounds great. Suppose I am a framework developer, use a widely
used format would be helpful. Because framework maybe written by different
programming languages, if use some rare formats, I have to write some code
to parse the configuration file when I want to get some fields from it.
On W
Hi all
It looks simple for the first sight. Marco, I can work on it.
-
Tomek
wt., 24 lis 2015, 17:49 Marco Massenzio użytkownik
napisał:
> Thank you for asking :)
>
> The idea is pretty simple (and not even original, it's the "Facade
> pattern"): essentially we would define a YAML syntax for t
Thank you for asking :)
The idea is pretty simple (and not even original, it's the "Facade
pattern"): essentially we would define a YAML syntax for the various
configuration flags that Mesos ({Master, Agent}) define, possibly grouping
them by "topic" and then write a few python classes, that read
when can we use the slave on windows?
2015-11-24 16:49 GMT+08:00 Alex Clemmer :
> The short answer is that the Windows integration work we have planned
> currently is aimed specifically at getting the agent/slave working and
> production-worthy on Windows. This plan does not specifically aim to
>
how to do that? Marco
2015-11-24 3:54 GMT+08:00 Marco Massenzio :
> I was thinking along the same lines, with a slightly more "modern" approach
> :)
>
> My idea was to write a thin Python layer that reads a configuration YAML
> file (possibly with "override" flags) and then invokes mesos-{master,
Hi team,
My understanding to v1 HTTP API is that, it's used for API compatibility
between different mesos version. But what's scope of v1 HTTP API? Before
Mesos 1.0? And how/when should we upgrade API version?
Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer
Platform Symphony/DCOS Dev
I'd suggest to open a JIRA to trace issue; I think you can append
master.log & slave.log for owner reference.
Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer
Platform Symphony/DCOS Development & Support, STG, IBM GCG
+86-10-8245 4084 | klaus1982...@gmail.com | http://k82.me
On Tue, N
Hi,
I'm having a problem while trying to create the initial cluster, no leader
is elected.
For a start, let me explain my setup:
3 nodes
3 zookeepers
3 mesos-master services, configured as initctl services and controlled by
puppet, RPM's installed are from the RHEL repository at mesosphere
(instal
The short answer is that the Windows integration work we have planned
currently is aimed specifically at getting the agent/slave working and
production-worthy on Windows. This plan does not specifically aim to
add Windows support to the master.
That said, there are _provisional_ plans to add Windo
16 matches
Mail list logo
