[GitHub] mesos issue #179: Added a new title to the existing list
Github user packtpartner commented on the issue: https://github.com/apache/mesos/pull/179 @jpeach can you help me in this? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Mesos V1 Operator HTTP API - Java Proto Classes
I believe the HTTP API will use the same underlying message format (proto def) and hence the request/response value objects (java) needs to be auto-generated from the proto files for it to be used in Jersey based java rest client? On Tuesday, November 15, 2016 12:37 PM, Tomek Janiszewskiwrote: I suspect jar is deprecated and includes only old API used by mesoslib. The goal is to create HTTP API and stop supporting native libs (jars, so, etc). I think you shouldn't use that jar in your project. wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan < vijikar...@yahoo.com> napisał: > Hello, > > I am writing a rest client for "operator APIs" and found that some of the > protobuf java classes (like "include/mesos/v1/quota/quota.proto", > "include/mesos/v1/master/master.proto") are not included in the mesos jar > file. While investigating, I have found that the "Make" file does not > include these proto definition files. > > I have updated the Make file and added the protos that I am interested in > and built 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 >
Re: Mesos V1 Operator HTTP API - Java Proto Classes
I suspect jar is deprecated and includes only old API used by mesoslib. The goal is to create HTTP API and stop supporting native libs (jars, so, etc). I think you shouldn't use that jar in your project. wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan < vijikar...@yahoo.com> napisał: > Hello, > > I am writing a rest client for "operator APIs" and found that some of the > protobuf java classes (like "include/mesos/v1/quota/quota.proto", > "include/mesos/v1/master/master.proto") are not included in the mesos jar > file. While investigating, I have found that the "Make" file does not > include these proto definition files. > > I have updated the Make file and added the protos that I am interested in > and built 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 >
Mesos V1 Operator HTTP API - Java Proto Classes
Hello, I am writing a rest client for "operator APIs" and found that some of the protobuf java classes (like "include/mesos/v1/quota/quota.proto", "include/mesos/v1/master/master.proto") are not included in the mesos jar file. While investigating, I have found that the "Make" file does not include these proto definition files. I have updated the Make file and added the protos that I am interested in and built 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? RegardsVijay
[RESULT][VOTE] Release Apache Mesos 1.0.2 (rc3)
Hi all, The vote for Mesos 1.0.2 (rc3) has passed with the following votes. +1 (Binding) -- Alex Rukletsov Till Toenshoff Yan Xu There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.0.2 It is recommended to use a mirror to download the release: http://www.apache.org/dyn/closer.cgi The CHANGELOG for the release is available at: https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.0.2 The mesos-1.0.2.jar has been released to: https://repository.apache.org The website (http://mesos.apache.org) will be updated shortly to reflect this release. Thanks,
MESOS-6233 Allow agents to re-register post a host reboot
Hi All, We have been working on the design for Restartable tasks ( MESOS-3545) and allowing agents to recover and re-register post reboot is a pre-requisite for that. Agent today doesn’t recover its state that includes its SlaveID post a host reboot, it short-circuits the recovery upon discovering the reboot and registers with the master as a new agent. With Partition Awareness, the mesos master even allows agents which have failed master’s health check pings (unreachable agents) to re-register with it and reconcile the tasks/executors. The executors on a rebooted host are anyway terminated so there is no harm in letting such an agent recover and re-register with the master using its old SlaveID. Would like to hear from the folks here if you see any operational concerns with letting the agents recover post a host reboot. MESOS JIRA: https://issues.apache.org/jira/browse/MESOS-6223 Many Thanks Megha Sharma