For your concern of large scale cluster, there is indeed a JIRA tracking this https://issues.apache.org/jira/browse/MESOS-3548
Thanks, Guangya On Wed, Feb 17, 2016 at 12:14 PM, Suteng <[email protected]> wrote: > Hi, > > > > Currently, Mesos framework’s task related operations lauchTask, > updateStatus and executorSendMessage etc., and resource related operations > resourceOffer etc., all operations are pass through Mesos Master. > > When the cluster and task number become huge, or with optimistic resource > offer, multi-framework concurrently launchTask, maybe Mesos Master will be > a bottleneck. > > Is possible for framework scheduler directly access Mesos agent, > launchTask, updateStatus and SendMessage2Executore to Mesos Agent directly, > bypass the Master? > > Will invoke big conflict with current mechanism? > > > > Looking forward to your comments and opinions. > > > > Best Regards, > > Teng > > > > > > > > Su Teng 00241668 > > > > Distributed and Parallel Software Lab > > Huawei Technologies Co., Ltd. > > Email:[email protected] > > > > > -- Guangya Liu (刘光亚) Senior Software Engineer DCOS and OpenStack Development IBM Platform Computing Systems and Technology Group
