[jira] [Commented] (MESOS-3809) Expose advertise_ip and advertise_port as command line options in mesos slave
[ https://issues.apache.org/jira/browse/MESOS-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15080903#comment-15080903 ] Harry Metske commented on MESOS-3809: - Thanks for the quick response. kind regards, Harry > Expose advertise_ip and advertise_port as command line options in mesos slave > - > > Key: MESOS-3809 > URL: https://issues.apache.org/jira/browse/MESOS-3809 > Project: Mesos > Issue Type: Bug > Components: slave >Affects Versions: 0.25.0 >Reporter: Anindya Sinha >Assignee: Anindya Sinha >Priority: Minor > Labels: mesosphere > > advertise_ip and advertise_port are exposed as mesos master command line args > (MESOS-809). But the following use case makes it a candidate for adding as > command line args in mesos slave as well. > On Tue, Oct 27, 2015 at 7:43 PM, Xiaodong Zhang wrote: > It works! Thanks a lot. > 发件人: haosdent > 答复: "u...@mesos.apache.org" > 日期: 2015年10月28日 星期三 上午10:23 > 至: user > 主题: Re: How to tell master which ip to connect. > Do you try `export LIBPROCESS_ADVERTISE_IP=xxx` and > `LIBPROCESS_ADVERTISE_PORT` when start slave? > On Wed, Oct 28, 2015 at 10:16 AM, Xiaodong Zhang wrote: > Hi teams: > My scenarios is like this: > My master nodes were deployed in AWS. My slaves were in AZURE.So they > communicate via public ip. > I got trouble when slaves try to register to master. > Now slaves can get master’s public ip address,and can send register > request.But they can only send there private ip to master.(Because they don’t > know there public ip,thus they can’t not bind a public ip via —ip flag), > thus masters can’t connect slaves.How can the slave to tell master which ip > master should connect(I can’t find any flags like —advertise_ip in master). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3809) Expose advertise_ip and advertise_port as command line options in mesos slave
[ https://issues.apache.org/jira/browse/MESOS-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076525#comment-15076525 ] Harry Metske commented on MESOS-3809: - The documentation (#1) says that advertise_ip and advertise_port are available for both master and slave. However, when running the mesos-slave (version 0.26) , it does not accept these 2 parameters (Failed to load unknown flag 'advertise_ip'). Also the help text (mesos-slave --help) does not mention these 2 options. (1) http://mesos.apache.org/documentation/latest/configuration/ > Expose advertise_ip and advertise_port as command line options in mesos slave > - > > Key: MESOS-3809 > URL: https://issues.apache.org/jira/browse/MESOS-3809 > Project: Mesos > Issue Type: Bug > Components: slave >Affects Versions: 0.25.0 >Reporter: Anindya Sinha >Assignee: Anindya Sinha >Priority: Minor > Labels: mesosphere > Fix For: 0.26.0 > > > advertise_ip and advertise_port are exposed as mesos master command line args > (MESOS-809). But the following use case makes it a candidate for adding as > command line args in mesos slave as well. > On Tue, Oct 27, 2015 at 7:43 PM, Xiaodong Zhang wrote: > It works! Thanks a lot. > 发件人: haosdent > 答复: "u...@mesos.apache.org" > 日期: 2015年10月28日 星期三 上午10:23 > 至: user > 主题: Re: How to tell master which ip to connect. > Do you try `export LIBPROCESS_ADVERTISE_IP=xxx` and > `LIBPROCESS_ADVERTISE_PORT` when start slave? > On Wed, Oct 28, 2015 at 10:16 AM, Xiaodong Zhang wrote: > Hi teams: > My scenarios is like this: > My master nodes were deployed in AWS. My slaves were in AZURE.So they > communicate via public ip. > I got trouble when slaves try to register to master. > Now slaves can get master’s public ip address,and can send register > request.But they can only send there private ip to master.(Because they don’t > know there public ip,thus they can’t not bind a public ip via —ip flag), > thus masters can’t connect slaves.How can the slave to tell master which ip > master should connect(I can’t find any flags like —advertise_ip in master). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2254) Posix CPU isolator usage call introduce high cpu load
[
https://issues.apache.org/jira/browse/MESOS-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511373#comment-14511373
]
Harry Metske commented on MESOS-2254:
-
I noticed the same issue. Running with only about 10 tasks on a slave (version
0.21.0) the mesos-slave eats about 25% of an i5 core.
> Posix CPU isolator usage call introduce high cpu load
> -
>
> Key: MESOS-2254
> URL: https://issues.apache.org/jira/browse/MESOS-2254
> Project: Mesos
> Issue Type: Bug
>Reporter: Niklas Quarfot Nielsen
>
> With more than 20 executors running on a slave with the posix isolator, we
> have seen an very high cpu load (over 200%).
> From profiling one thread (there were two, taking up all the cpu time. The
> total CPU time was over 200%):
> {code}
> Running Time SelfSymbol Name
> 27133.0ms 47.8% 0.0 _pthread_body 0x1adb50
> 27133.0ms 47.8% 0.0 thread_start
> 27133.0ms 47.8% 0.0 _pthread_start
> 27133.0ms 47.8% 0.0_pthread_body
> 27133.0ms 47.8% 0.0 process::schedule(void*)
> 27133.0ms 47.8% 2.0
> process::ProcessManager::resume(process::ProcessBase*)
> 27126.0ms 47.8% 1.0
> process::ProcessBase::serve(process::Event const&)
> 27125.0ms 47.8% 0.0
> process::DispatchEvent::visit(process::EventVisitor*) const
> 27125.0ms 47.8% 0.0
> process::ProcessBase::visit(process::DispatchEvent const&)
> 27125.0ms 47.8% 0.0 std::__1::function (process::ProcessBase*)>::operator()(process::ProcessBase*) const
> 27124.0ms 47.8% 0.0
> std::__1::__function::__func
> process::dispatch mesos::internal::slave::IsolatorProcess, mesos::ContainerID const&,
> mesos::ContainerID>(process::PID
> const&, process::Future
> (mesos::internal::slave::IsolatorProcess::*)(mesos::ContainerID const&),
> mesos::ContainerID)::'lambda'(process::ProcessBase*),
> std::__1::allocator
> process::dispatch mesos::internal::slave::IsolatorProcess, mesos::ContainerID const&,
> mesos::ContainerID>(process::PID
> const&, process::Future
> (mesos::internal::slave::IsolatorProcess::*)(mesos::ContainerID const&),
> mesos::ContainerID)::'lambda'(process::ProcessBase*)>, void
> (process::ProcessBase*)>::operator()(process::ProcessBase*&&)
> 27124.0ms 47.8% 1.0
> process::Future
> process::dispatch mesos::internal::slave::IsolatorProcess, mesos::ContainerID const&,
> mesos::ContainerID>(process::PID
> const&, process::Future
> (mesos::internal::slave::IsolatorProcess::*)(mesos::ContainerID const&),
> mesos::ContainerID)::'lambda'(process::ProcessBase*)::operator()(process::ProcessBase*)
> const
> 27060.0ms 47.7% 1.0
> mesos::internal::slave::PosixCpuIsolatorProcess::usage(mesos::ContainerID
> const&)
> 27046.0ms 47.7% 2.0
> mesos::internal::usage(int, bool, bool)
> 27023.0ms 47.6% 2.0 os::pstree(Option)
> 26748.0ms 47.1% 23.0 os::processes()
> 24809.0ms 43.7% 349.0 os::process(int)
> 8199.0ms 14.4% 47.0 os::sysctl::string()
> const
> 7562.0ms 13.3% 7562.0__sysctl
> {code}
> We could see that usage() in usage/usage.cpp is causing this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
