from:"Alex Evonosky"

Re: fyi: mesos-dns is not registering all ip addresses

2020-07-27 Thread Alex Evonosky

Thank you Marc for the clarification.



On Mon, Jul 27, 2020 at 8:50 AM Marc Roos  wrote:

>
> Hi Alex,
>
> My config.json is quite similar, but having "IPSources": ["netinfo",
> "mesos", "host"]
>
> You will only run into this issue when you have multihomed tasks, having
> two or more network adapters, eth0, eth1 etc
>
>
>
>
> -Original Message-
> From: Alex Evonosky [mailto:alex.evono...@gmail.com]
> Sent: maandag 27 juli 2020 14:36
> To: user@mesos.apache.org
> Subject: Re: fyi: mesos-dns is not registering all ip addresses
>
> thank you.
>
> We have been running mesos-dns for years now without any issues.  The
> docker apps spin up on marathon and automatically gets picked up by
> mesos-dns...
>
> This is our config.json:
>
>
> {
>   "zk": "zk://10.10.10.51:2181,10.10.10.52:2181,10.10.10.53:2181/mesos",
>   "masters": ["10.10.10.51:5050", "10.10.10.52:5050",
> "10.10.10.53:5050"],
>   "refreshSeconds": 3,
>   "ttl": 3,
>   "domain": "mesos",
>   "port": 53,
>   "resolvers": ["10.10.10.88", "10.10.10.86"],
>   "timeout": 3,
>   "httpon": true,
>   "dnson": true,
>   "httpport": 8123,
>   "externalon": true,
>   "listener": "0.0.0.0",
>   "SOAMname": "ns1.mesos",
>   "SOARname": "root.ns1.mesos",
>   "SOARefresh": 5,
>   "SOARetry":   600,
>   "SOAExpire":  86400,
>   "SOAMinttl": 5,
>   "IPSources":["mesos", "host"]
> }
>
>
>
>
> we just have our main DNS resolvers have a zone  "mesos.marathon" and
> forwards the request to this cluster...
>
>
>
> On Mon, Jul 27, 2020 at 3:56 AM Marc Roos 
> wrote:
>
>
>
>
> I am not sure if mesos-dns is discontinued. But for the ones still
> using
> it, in some cases it does not register all tasks ip addresses.
>
> The default[2] works, but if you have this setup[1] it will only
> register one ip address 192.168.122.140 and not the 2nd. I filed
> issue a
> year ago or so[3]
>
>
>
> [3]
> https://github.com/mesosphere/mesos-dns/issues/54145
> https://issues.apache.org/jira/browse/MESOS-10164
>
> [1]
> "network_infos": [
>   {
> "ip_addresses": [
>   {
> "protocol": "IPv4",
> "ip_address": "192.168.122.140"
>   }
> ]
>   },
>   {
> "ip_addresses": [
>   {
> "protocol": "IPv4",
> "ip_address": "192.168.10.17"
>   }
> ],
>   }
> ]
>
>
> [2]
> "network_infos": [
>   {
> "ip_addresses": [
>   {
> "protocol": "IPv4",
> "ip_address": "12.0.1.2"
>   },
>   {
> "protocol": "IPv6",
> "ip_address": "fd01:b::1:8000:2"
>   }
> ],
>   }
> ]
>
>
>
>
>
>

Re: fyi: mesos-dns is not registering all ip addresses

2020-07-27 Thread Alex Evonosky

thank you.

We have been running mesos-dns for years now without any issues.  The
docker apps spin up on marathon and automatically gets picked up by
mesos-dns...

This is our config.json:


{
  "zk": "zk://10.10.10.51:2181,10.10.10.52:2181,10.10.10.53:2181/mesos",
  "masters": ["10.10.10.51:5050", "10.10.10.52:5050", "10.10.10.53:5050"],
  "refreshSeconds": 3,
  "ttl": 3,
  "domain": "mesos",
  "port": 53,
  "resolvers": ["10.10.10.88", "10.10.10.86"],
  "timeout": 3,
  "httpon": true,
  "dnson": true,
  "httpport": 8123,
  "externalon": true,
  "listener": "0.0.0.0",
  "SOAMname": "ns1.mesos",
  "SOARname": "root.ns1.mesos",
  "SOARefresh": 5,
  "SOARetry":   600,
  "SOAExpire":  86400,
  "SOAMinttl": 5,
  "IPSources":["mesos", "host"]
}



we just have our main DNS resolvers have a zone  "mesos.marathon" and
forwards the request to this cluster...



On Mon, Jul 27, 2020 at 3:56 AM Marc Roos  wrote:

>
>
> I am not sure if mesos-dns is discontinued. But for the ones still using
> it, in some cases it does not register all tasks ip addresses.
>
> The default[2] works, but if you have this setup[1] it will only
> register one ip address 192.168.122.140 and not the 2nd. I filed issue a
> year ago or so[3]
>
>
>
> [3]
> https://github.com/mesosphere/mesos-dns/issues/54145
> https://issues.apache.org/jira/browse/MESOS-10164
>
> [1]
> "network_infos": [
>   {
> "ip_addresses": [
>   {
> "protocol": "IPv4",
> "ip_address": "192.168.122.140"
>   }
> ]
>   },
>   {
> "ip_addresses": [
>   {
> "protocol": "IPv4",
> "ip_address": "192.168.10.17"
>   }
> ],
>   }
> ]
>
>
> [2]
> "network_infos": [
>   {
> "ip_addresses": [
>   {
> "protocol": "IPv4",
> "ip_address": "12.0.1.2"
>   },
>   {
> "protocol": "IPv6",
> "ip_address": "fd01:b::1:8000:2"
>   }
> ],
>   }
> ]
>
>
>

Re: Welcome Chun-Hung Hsiao as Mesos Committer and PMC Member

2018-03-12 Thread Alex Evonosky

congratulations!

On Mon, Mar 12, 2018 at 1:16 PM, Meng Zhu  wrote:

> Congrats Chun! Well deserved!
>
> On Mon, Mar 12, 2018 at 10:09 AM, Zhitao Li  wrote:
>
>> Congrats, Chun!
>>
>> On Sun, Mar 11, 2018 at 11:47 PM, Gilbert Song 
>> wrote:
>>
>> > Congrats, Chun!
>> >
>> > It is great to have you in the community!
>> >
>> > - Gilbert
>> >
>> > On Sun, Mar 11, 2018 at 4:40 PM, Andrew Schwartzmeyer <
>> > and...@schwartzmeyer.com> wrote:
>> >
>> > > Congratulations Chun!
>> > >
>> > > I apologize for not also giving you a +1, as I certainly would have,
>> but
>> > > just discovered my mailing list isn't working. Just a heads up, don't
>> let
>> > > that happen to you too!
>> > >
>> > > I look forward to continuing to work with you.
>> > >
>> > > Cheers,
>> > >
>> > > Andy
>> > >
>> > >
>> > > On 03/10/2018 9:14 pm, Jie Yu wrote:
>> > >
>> > >> Hi,
>> > >>
>> > >> I am happy to announce that the PMC has voted Chun-Hung Hsiao as a
>> new
>> > >> committer and member of PMC for the Apache Mesos project. Please
>> join me
>> > >> to
>> > >> congratulate him!
>> > >>
>> > >> Chun has been an active contributor for the past year. His main
>> > >> contributions to the project include:
>> > >> * Designed and implemented gRPC client support to libprocess
>> > (MESOS-7749)
>> > >> * Designed and implemented Storage Local Resource Provider
>> (MESOS-7235,
>> > >> MESOS-8374)
>> > >> * Implemented part of the CSI support (MESOS-7235, MESOS-8374)
>> > >>
>> > >> Chun is friendly and humble, but also intelligent, insightful, and
>> > >> opinionated. I am confident that he will be a great addition to our
>> > >> committer pool. Thanks Chun for all your contributions to the
>> project so
>> > >> far!
>> > >>
>> > >> His committer checklist can be found here:
>> > >> https://docs.google.com/document/d/1FjroAvjGa5NdP29zM7-2eg6t
>> > >> LPAzQRMUmCorytdEI_U/edit?usp=sharing
>> > >>
>> > >> - Jie
>> > >>
>> > >
>> > >
>> >
>>
>>
>>
>> --
>> Cheers,
>>
>> Zhitao Li
>>
>
>

Re: Zookeeper or Marathon issue?

2017-11-22 Thread Alex Evonosky

Ivan-

I ran the following:

 zookeepercli -servers=10.10.10.51:2181 -c rm
/marathon/state/migration-in-progress
2017-11-22 11:00:47 FATAL zk: node does not exist


and tried to restart Marathon and same issue.  Does this appear to be a
Zookeeper issue?

Thanks!

Alex




On Wed, Nov 22, 2017 at 10:21 AM, Ivan Chernetsky <
ichernet...@mesosphere.com> wrote:

> Hi Alex,
>
> If you are sure that the Marathon state in ZK is consistent, you can
> remove the flag using zkCli.sh
>
> For instance, if the ZK connection string for Marathon, you use is
> zk://localhost:2181/marathon, then once connected to ZK using zkCli.sh,
> just execute "rm /marathon/state/migration-in-progress"
>
> This should revolve it.
>
> Please refer to https://github.com/mesosphere/marathon/blob/
> master/docs/docs/data-migration.md for further details.
>
> Regards,
> Ivan.
>
> On Wed, Nov 22, 2017 at 5:18 PM, Alex Evonosky <alex.evono...@gmail.com>
> wrote:
>
>> Tomas-
>>
>> thank you for the reply!  I am running marathon 1.5.2, zookeeper: 3.4.8-1
>>
>> I looked on the referenced gitlab [age, but I really did find the syntax
>> to remove the flag as suggested.  Do you happen to know the syntax via the
>> zookeeper cli?
>>
>> Thank you again!
>>
>>
>> On Wed, Nov 22, 2017 at 8:50 AM, Tomas Barton <barton.to...@gmail.com>
>> wrote:
>>
>>> Hi Alex,
>>>
>>> looks like you've restarted Marathon during election. Try to backup
>>> ZooKeeper data and then go to exhibitor / ZooKeeper CLI and remove flag
>>> from Marathon namespace:
>>>
>>> /state/migration-in-progress
>>>
>>> According to https://github.com/mesosphere/marathon/pull/5662 the flag
>>> should be removed upon unsuccessful migration. Which version of Marathon do
>>> you run?
>>>
>>> Tomas
>>>
>>> On 22 November 2017 at 08:21, Alex Evonosky <alex.evono...@gmail.com>
>>> wrote:
>>>
>>>> Hello group-
>>>>
>>>> Long time Mesos user and first time post about an issue.  I have been
>>>> running mesos 1.4.0 for a while without any issues.  The other day, Ubuntu
>>>> upgraded mesos to 1.4.1, which seemed to go ok, however, I reloaded one
>>>> master node to verify it can come back up after the upgrade and now mesos
>>>> and zookeeper appear fine, however, marathon did not recover.  Starting
>>>> marathon shows many errors now (attached file).
>>>>
>>>> Could someone let me know what the issue could be from just rebooting a
>>>> server?
>>>>
>>>>
>>>> Thank you!
>>>>
>>>> Alex
>>>>
>>>
>>>
>>
>

Re: Zookeeper or Marathon issue?

2017-11-22 Thread Alex Evonosky

Tomas-

thank you for the reply!  I am running marathon 1.5.2, zookeeper: 3.4.8-1

I looked on the referenced gitlab [age, but I really did find the syntax to
remove the flag as suggested.  Do you happen to know the syntax via the
zookeeper cli?

Thank you again!


On Wed, Nov 22, 2017 at 8:50 AM, Tomas Barton <barton.to...@gmail.com>
wrote:

> Hi Alex,
>
> looks like you've restarted Marathon during election. Try to backup
> ZooKeeper data and then go to exhibitor / ZooKeeper CLI and remove flag
> from Marathon namespace:
>
> /state/migration-in-progress
>
> According to https://github.com/mesosphere/marathon/pull/5662 the flag
> should be removed upon unsuccessful migration. Which version of Marathon do
> you run?
>
> Tomas
>
> On 22 November 2017 at 08:21, Alex Evonosky <alex.evono...@gmail.com>
> wrote:
>
>> Hello group-
>>
>> Long time Mesos user and first time post about an issue.  I have been
>> running mesos 1.4.0 for a while without any issues.  The other day, Ubuntu
>> upgraded mesos to 1.4.1, which seemed to go ok, however, I reloaded one
>> master node to verify it can come back up after the upgrade and now mesos
>> and zookeeper appear fine, however, marathon did not recover.  Starting
>> marathon shows many errors now (attached file).
>>
>> Could someone let me know what the issue could be from just rebooting a
>> server?
>>
>>
>> Thank you!
>>
>> Alex
>>
>
>

Zookeeper or Marathon issue?

2017-11-21 Thread Alex Evonosky

Hello group-

Long time Mesos user and first time post about an issue.  I have been
running mesos 1.4.0 for a while without any issues.  The other day, Ubuntu
upgraded mesos to 1.4.1, which seemed to go ok, however, I reloaded one
master node to verify it can come back up after the upgrade and now mesos
and zookeeper appear fine, however, marathon did not recover.  Starting
marathon shows many errors now (attached file).

Could someone let me know what the issue could be from just rebooting a
server?


Thank you!

Alex
[INFO] [11/22/2017 02:09:50.438] [main] [SystemMetricsExtension(akka://kamon)] 
Starting the Kamon(SystemMetrics) extension
[2017-11-22 02:09:50,455] INFO  Sigar library provisioned: 
/root/native/libsigar-amd64-linux.so (kamon.sigar.SigarProvisioner:main)
[INFO] [11/22/2017 02:09:50.541] [main] [JMXExtension(akka://kamon)] Starting 
the Kamon(JMX) extension
[INFO] [11/22/2017 02:09:50.560] [main] [JMXMetricsExtension(akka://kamon)] 
Starting the Kamon(JMXMetrics) extension
registering jmx exporter
[2017-11-22 02:09:50,654] INFO  Slf4jLogger started 
(akka.event.slf4j.Slf4jLogger:marathon-akka.actor.default-dispatcher-3)
[2017-11-22 02:09:50,705] INFO  Starting Marathon 
1.5.2/c55acb9a135a8b4b30f8cb1fafa529cfaefc3f8a with --master 
zk://10.10.10.51:2181/mesos --zk zk://10.10.10.51:2181/marathon 
(mesosphere.marathon.MarathonApp:JMX exporting thread)
[2017-11-22 02:09:50,796] INFO  Successfully loaded libmesos: version 1.4.1 
(mesosphere.marathon.MarathonApp:JMX exporting thread)
[2017-11-22 02:09:51,835] INFO  Starting 
(org.apache.curator.framework.imps.CuratorFrameworkImpl:JMX exporting thread)
[2017-11-22 02:09:51,846] INFO  Client environment:zookeeper.version=3.4.8--1, 
built on 02/06/2016 03:18 GMT (org.apache.zookeeper.ZooKeeper:JMX exporting 
thread)
[2017-11-22 02:09:51,847] INFO  Client environment:host.name=mesos-master1 
(org.apache.zookeeper.ZooKeeper:JMX exporting thread)
[2017-11-22 02:09:51,847] INFO  Client environment:java.version=1.8.0_151 
(org.apache.zookeeper.ZooKeeper:JMX exporting thread)
[2017-11-22 02:09:51,847] INFO  Client environment:java.vendor=Oracle 
Corporation (org.apache.zookeeper.ZooKeeper:JMX exporting thread)
[2017-11-22 02:09:51,847] INFO  Client 
environment:java.home=/usr/lib/jvm/java-8-openjdk-amd64/jre 
(org.apache.zookeeper.ZooKeeper:JMX exporting thread)
[2017-11-22 02:09:51,847] INFO  Client

Re: fyi: mesos-dns is not registering all ip addresses

Re: fyi: mesos-dns is not registering all ip addresses

Re: Welcome Chun-Hung Hsiao as Mesos Committer and PMC Member

Re: Zookeeper or Marathon issue?

Re: Zookeeper or Marathon issue?

Zookeeper or Marathon issue?

6 matches

Site Navigation

Mail list logo

Footer information