Suteng— such optimization makes sense in certain cases (e.g. sending a framework message), but it can be rather tricky in general, because the master has to maintain bookkeeping. Moreover, with the upcoming HTTP API it becomes harder for a framework to determine where to send messages to reach a specific agent.
Have you done any performance tests and seen master becoming a bottleneck? On Wed, Feb 17, 2016 at 5:14 AM, 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] > > > > >
