You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by dp...@gmail.com on 2020/10/15 03:11:22 UTC

[MTCGA]: new failures in builds [5665538] needs to be handled

Hi Igniters,

 I've detected some new issue on TeamCity to be handled. You are more than welcomed to help.

 If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution.
 Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. 

 *    New Critical Failure in master Platform .NET (Long Running) https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetLongRunning?branch=%3Cdefault%3E
 Changes may lead to failure were done by 
	 - bojidar marinov <bo...@gmail.com> https://ci.ignite.apache.org/viewModification.html?modId=908629
	 - igor sapego <is...@apache.org> https://ci.ignite.apache.org/viewModification.html?modId=908581
	 - ivan daschinskiy <iv...@gmail.com> https://ci.ignite.apache.org/viewModification.html?modId=908625
	 - ivan daschinskiy <iv...@gmail.com> https://ci.ignite.apache.org/viewModification.html?modId=908576
	 - maxim muzafarov <mm...@apache.org> https://ci.ignite.apache.org/viewModification.html?modId=908579

	 - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute 
	 - Should you have any questions please contact dev@ignite.apache.org 

Best Regards,
Apache Ignite TeamCity Bot 
https://github.com/apache/ignite-teamcity-bot
Notification generated at 06:11:16 15-10-2020 

Re: [MTCGA]: new failures in builds [5665538] needs to be handled

Posted by Ivan Daschinsky <iv...@gmail.com>.
I'd suggest to completely deny all UDP outer traffic on TC agents.

чт, 15 окт. 2020 г. в 11:13, Pavel Tupitsyn <pt...@apache.org>:

> Ivan, thanks for pointing that out, I should have read the exception fully.
>
> The test checks whether Ignite.NET can be started with default settings.
> This is an important use case to verify, and I'd like to keep the test as
> is,
> if possible.
>
> Petr, can you please check the firewall settings?
> Seems like GridGain lab machines interfere with Ignite TC agents.
>
> On Thu, Oct 15, 2020 at 10:43 AM Ivan Daschinsky <iv...@gmail.com>
> wrote:
>
> > >> Do you think this can be caused by the recent changes in GridNioServer
> > Of course no. Discovery has nothing common with GridNioServer at all.
> > >> but it was fine for 5 years, and now got broken.
> > It seems that this is an infrastructure issue. Do you
> > see lab11.gridgain.local in log? I suppose that this host should not be a
> > part of test topology.
> > So, if we want to have a stable test, we should not use MulticastIpFinder
> > except in some specific cases. At least, default multicast group should
> be
> > changed.
> >
> >
> > чт, 15 окт. 2020 г. в 10:14, Pavel Tupitsyn <pt...@apache.org>:
> >
> > > Ivan, yes, it does use MulticastIpFinder, which can be problematic in
> > > tests,
> > > but it was fine for 5 years, and now got broken.
> > >
> > > Do you think this can be caused by the recent changes in GridNioServer?
> > >
> > > Pavel
> > >
> > > On Thu, Oct 15, 2020 at 9:41 AM Ivan Daschinsky <iv...@gmail.com>
> > > wrote:
> > >
> > > > It seems, that in this test we use MulticastIpFinder. I suppose, that
> > it
> > > > should be fixed.
> > > > Excerpts from a failed test's log:
> > > >
> > > > [15-Oct-2020 02:47:10][WARN ][main][TcpDiscoveryMulticastIpFinder]
> > > > TcpDiscoveryMulticastIpFinder has no pre-configured addresses (it is
> > > > recommended in production to specify at least one address in
> > > > TcpDiscoveryMulticastIpFinder.getAddresses() configuration property)
> > > > [15-Oct-2020 02:47:26][ERROR][main][IgniteKernal] Failed to start
> > > manager:
> > > > GridManagerAdapter [enabled=true,
> > > > name=o.a.i.i.managers.discovery.GridDiscoveryManager]
> > > > class org.apache.ignite.IgniteCheckedException: Failed to start SPI:
> > > > TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
> > > > marsh=JdkMarshaller
> > > > [clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@18fc665b],
> > > > reconCnt=10, reconDelay=2000, maxAckTimeout=600000, soLinger=5,
> > > > forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null,
> > > > skipAddrsRandomization=false]
> > > >   at
> > > >
> > > >
> > >
> >
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:281)
> > > >   at
> > > >
> > > >
> > >
> >
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:974)
> > > >   at
> > > >
> > > >
> > >
> >
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1933)
> > > >   at
> > > org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1289)
> > > >   at
> > > >
> > > >
> > >
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2096)
> > > >   at
> > > >
> > > >
> > >
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1748)
> > > >   at
> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1143)
> > > >   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:641)
> > > >   at
> > > >
> > > >
> > >
> >
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:43)
> > > >   at
> > > >
> > > >
> > >
> >
> org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:74)
> > > > Caused by: class org.apache.ignite.spi.IgniteSpiException: Impossible
> > to
> > > > continue join, check if local discovery and communication ports are
> not
> > > > blocked with firewall [addr=lab11.gridgain.local/172.25.1.11:47500,
> > > > req=TcpDiscoveryJoinRequestMessage [node=TcpDiscoveryNode
> > > > [id=8d1076b1-b131-4c80-abd7-90fda1daba64,
> > > > consistentId=0:0:0:0:0:0:0:1,127.0.0.1,172.25.1.162,
> 172.31.176.1:47500
> > ,
> > > > addrs=ArrayList [0:0:0:0:0:0:0:1, 127.0.0.1, 172.25.1.162,
> > 172.31.176.1],
> > > > sockAddrs=HashSet [/0:0:0:0:0:0:0:1:47500,
> > > > publicagent01_02.mshome.net/172.31.176.1:47500, /127.0.0.1:47500, /
> > > > 172.25.1.162:47500], discPort=47500, order=0, intOrder=0,
> > > > lastExchangeTime=1602730030490, loc=true,
> > > > ver=2.10.0#20201015-sha1:00000000, isClient=false],
> > > >
> > > >
> > >
> >
> dataPacket=org.apache.ignite.spi.discovery.tcp.internal.DiscoveryDataPacket@4ee43b4f
> > > > ,
> > > > super=TcpDiscoveryAbstractMessage [sndNodeId=null,
> > > > id=370afaa2571-8d1076b1-b131-4c80-abd7-90fda1daba64,
> > verifierNodeId=null,
> > > > topVer=0, pendingIdx=0, failedNodes=null, isClient=false]],
> > > > discoLocalPort=47500, discoLocalPortRange=100]
> > > >
> > > > чт, 15 окт. 2020 г. в 06:11, <dp...@gmail.com>:
> > > >
> > > > > Hi Igniters,
> > > > >
> > > > >  I've detected some new issue on TeamCity to be handled. You are
> more
> > > > than
> > > > > welcomed to help.
> > > > >
> > > > >  If your changes can lead to this failure(s): We're grateful that
> you
> > > > were
> > > > > a volunteer to make the contribution to this project, but things
> > change
> > > > and
> > > > > you may no longer be able to finalize your contribution.
> > > > >  Could you respond to this email and indicate if you wish to
> continue
> > > and
> > > > > fix test failures or step down and some committer may revert you
> > > commit.
> > > > >
> > > > >  *    New Critical Failure in master Platform .NET (Long Running)
> > > > >
> > > >
> > >
> >
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetLongRunning?branch=%3Cdefault%3E
> > > > >  Changes may lead to failure were done by
> > > > >          - bojidar marinov <bo...@gmail.com>
> > > > > https://ci.ignite.apache.org/viewModification.html?modId=908629
> > > > >          - igor sapego <is...@apache.org>
> > > > > https://ci.ignite.apache.org/viewModification.html?modId=908581
> > > > >          - ivan daschinskiy <iv...@gmail.com>
> > > > > https://ci.ignite.apache.org/viewModification.html?modId=908625
> > > > >          - ivan daschinskiy <iv...@gmail.com>
> > > > > https://ci.ignite.apache.org/viewModification.html?modId=908576
> > > > >          - maxim muzafarov <mm...@apache.org>
> > > > > https://ci.ignite.apache.org/viewModification.html?modId=908579
> > > > >
> > > > >          - Here's a reminder of what contributors were agreed to do
> > > > >
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > > > >          - Should you have any questions please contact
> > > > > dev@ignite.apache.org
> > > > >
> > > > > Best Regards,
> > > > > Apache Ignite TeamCity Bot
> > > > > https://github.com/apache/ignite-teamcity-bot
> > > > > Notification generated at 06:11:16 15-10-2020
> > > > >
> > > >
> > > >
> > > > --
> > > > Sincerely yours, Ivan Daschinskiy
> > > >
> > >
> >
> >
> > --
> > Sincerely yours, Ivan Daschinskiy
> >
>


-- 
Sincerely yours, Ivan Daschinskiy

Re: [MTCGA]: new failures in builds [5665538] needs to be handled

Posted by Pavel Tupitsyn <pt...@apache.org>.
Ivan, thanks for pointing that out, I should have read the exception fully.

The test checks whether Ignite.NET can be started with default settings.
This is an important use case to verify, and I'd like to keep the test as
is,
if possible.

Petr, can you please check the firewall settings?
Seems like GridGain lab machines interfere with Ignite TC agents.

On Thu, Oct 15, 2020 at 10:43 AM Ivan Daschinsky <iv...@gmail.com>
wrote:

> >> Do you think this can be caused by the recent changes in GridNioServer
> Of course no. Discovery has nothing common with GridNioServer at all.
> >> but it was fine for 5 years, and now got broken.
> It seems that this is an infrastructure issue. Do you
> see lab11.gridgain.local in log? I suppose that this host should not be a
> part of test topology.
> So, if we want to have a stable test, we should not use MulticastIpFinder
> except in some specific cases. At least, default multicast group should be
> changed.
>
>
> чт, 15 окт. 2020 г. в 10:14, Pavel Tupitsyn <pt...@apache.org>:
>
> > Ivan, yes, it does use MulticastIpFinder, which can be problematic in
> > tests,
> > but it was fine for 5 years, and now got broken.
> >
> > Do you think this can be caused by the recent changes in GridNioServer?
> >
> > Pavel
> >
> > On Thu, Oct 15, 2020 at 9:41 AM Ivan Daschinsky <iv...@gmail.com>
> > wrote:
> >
> > > It seems, that in this test we use MulticastIpFinder. I suppose, that
> it
> > > should be fixed.
> > > Excerpts from a failed test's log:
> > >
> > > [15-Oct-2020 02:47:10][WARN ][main][TcpDiscoveryMulticastIpFinder]
> > > TcpDiscoveryMulticastIpFinder has no pre-configured addresses (it is
> > > recommended in production to specify at least one address in
> > > TcpDiscoveryMulticastIpFinder.getAddresses() configuration property)
> > > [15-Oct-2020 02:47:26][ERROR][main][IgniteKernal] Failed to start
> > manager:
> > > GridManagerAdapter [enabled=true,
> > > name=o.a.i.i.managers.discovery.GridDiscoveryManager]
> > > class org.apache.ignite.IgniteCheckedException: Failed to start SPI:
> > > TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
> > > marsh=JdkMarshaller
> > > [clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@18fc665b],
> > > reconCnt=10, reconDelay=2000, maxAckTimeout=600000, soLinger=5,
> > > forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null,
> > > skipAddrsRandomization=false]
> > >   at
> > >
> > >
> >
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:281)
> > >   at
> > >
> > >
> >
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:974)
> > >   at
> > >
> > >
> >
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1933)
> > >   at
> > org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1289)
> > >   at
> > >
> > >
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2096)
> > >   at
> > >
> > >
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1748)
> > >   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1143)
> > >   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:641)
> > >   at
> > >
> > >
> >
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:43)
> > >   at
> > >
> > >
> >
> org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:74)
> > > Caused by: class org.apache.ignite.spi.IgniteSpiException: Impossible
> to
> > > continue join, check if local discovery and communication ports are not
> > > blocked with firewall [addr=lab11.gridgain.local/172.25.1.11:47500,
> > > req=TcpDiscoveryJoinRequestMessage [node=TcpDiscoveryNode
> > > [id=8d1076b1-b131-4c80-abd7-90fda1daba64,
> > > consistentId=0:0:0:0:0:0:0:1,127.0.0.1,172.25.1.162,172.31.176.1:47500
> ,
> > > addrs=ArrayList [0:0:0:0:0:0:0:1, 127.0.0.1, 172.25.1.162,
> 172.31.176.1],
> > > sockAddrs=HashSet [/0:0:0:0:0:0:0:1:47500,
> > > publicagent01_02.mshome.net/172.31.176.1:47500, /127.0.0.1:47500, /
> > > 172.25.1.162:47500], discPort=47500, order=0, intOrder=0,
> > > lastExchangeTime=1602730030490, loc=true,
> > > ver=2.10.0#20201015-sha1:00000000, isClient=false],
> > >
> > >
> >
> dataPacket=org.apache.ignite.spi.discovery.tcp.internal.DiscoveryDataPacket@4ee43b4f
> > > ,
> > > super=TcpDiscoveryAbstractMessage [sndNodeId=null,
> > > id=370afaa2571-8d1076b1-b131-4c80-abd7-90fda1daba64,
> verifierNodeId=null,
> > > topVer=0, pendingIdx=0, failedNodes=null, isClient=false]],
> > > discoLocalPort=47500, discoLocalPortRange=100]
> > >
> > > чт, 15 окт. 2020 г. в 06:11, <dp...@gmail.com>:
> > >
> > > > Hi Igniters,
> > > >
> > > >  I've detected some new issue on TeamCity to be handled. You are more
> > > than
> > > > welcomed to help.
> > > >
> > > >  If your changes can lead to this failure(s): We're grateful that you
> > > were
> > > > a volunteer to make the contribution to this project, but things
> change
> > > and
> > > > you may no longer be able to finalize your contribution.
> > > >  Could you respond to this email and indicate if you wish to continue
> > and
> > > > fix test failures or step down and some committer may revert you
> > commit.
> > > >
> > > >  *    New Critical Failure in master Platform .NET (Long Running)
> > > >
> > >
> >
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetLongRunning?branch=%3Cdefault%3E
> > > >  Changes may lead to failure were done by
> > > >          - bojidar marinov <bo...@gmail.com>
> > > > https://ci.ignite.apache.org/viewModification.html?modId=908629
> > > >          - igor sapego <is...@apache.org>
> > > > https://ci.ignite.apache.org/viewModification.html?modId=908581
> > > >          - ivan daschinskiy <iv...@gmail.com>
> > > > https://ci.ignite.apache.org/viewModification.html?modId=908625
> > > >          - ivan daschinskiy <iv...@gmail.com>
> > > > https://ci.ignite.apache.org/viewModification.html?modId=908576
> > > >          - maxim muzafarov <mm...@apache.org>
> > > > https://ci.ignite.apache.org/viewModification.html?modId=908579
> > > >
> > > >          - Here's a reminder of what contributors were agreed to do
> > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > > >          - Should you have any questions please contact
> > > > dev@ignite.apache.org
> > > >
> > > > Best Regards,
> > > > Apache Ignite TeamCity Bot
> > > > https://github.com/apache/ignite-teamcity-bot
> > > > Notification generated at 06:11:16 15-10-2020
> > > >
> > >
> > >
> > > --
> > > Sincerely yours, Ivan Daschinskiy
> > >
> >
>
>
> --
> Sincerely yours, Ivan Daschinskiy
>

Re: [MTCGA]: new failures in builds [5665538] needs to be handled

Posted by Ivan Daschinsky <iv...@gmail.com>.
>> Do you think this can be caused by the recent changes in GridNioServer
Of course no. Discovery has nothing common with GridNioServer at all.
>> but it was fine for 5 years, and now got broken.
It seems that this is an infrastructure issue. Do you
see lab11.gridgain.local in log? I suppose that this host should not be a
part of test topology.
So, if we want to have a stable test, we should not use MulticastIpFinder
except in some specific cases. At least, default multicast group should be
changed.


чт, 15 окт. 2020 г. в 10:14, Pavel Tupitsyn <pt...@apache.org>:

> Ivan, yes, it does use MulticastIpFinder, which can be problematic in
> tests,
> but it was fine for 5 years, and now got broken.
>
> Do you think this can be caused by the recent changes in GridNioServer?
>
> Pavel
>
> On Thu, Oct 15, 2020 at 9:41 AM Ivan Daschinsky <iv...@gmail.com>
> wrote:
>
> > It seems, that in this test we use MulticastIpFinder. I suppose, that it
> > should be fixed.
> > Excerpts from a failed test's log:
> >
> > [15-Oct-2020 02:47:10][WARN ][main][TcpDiscoveryMulticastIpFinder]
> > TcpDiscoveryMulticastIpFinder has no pre-configured addresses (it is
> > recommended in production to specify at least one address in
> > TcpDiscoveryMulticastIpFinder.getAddresses() configuration property)
> > [15-Oct-2020 02:47:26][ERROR][main][IgniteKernal] Failed to start
> manager:
> > GridManagerAdapter [enabled=true,
> > name=o.a.i.i.managers.discovery.GridDiscoveryManager]
> > class org.apache.ignite.IgniteCheckedException: Failed to start SPI:
> > TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
> > marsh=JdkMarshaller
> > [clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@18fc665b],
> > reconCnt=10, reconDelay=2000, maxAckTimeout=600000, soLinger=5,
> > forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null,
> > skipAddrsRandomization=false]
> >   at
> >
> >
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:281)
> >   at
> >
> >
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:974)
> >   at
> >
> >
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1933)
> >   at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1289)
> >   at
> >
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2096)
> >   at
> >
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1748)
> >   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1143)
> >   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:641)
> >   at
> >
> >
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:43)
> >   at
> >
> >
> org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:74)
> > Caused by: class org.apache.ignite.spi.IgniteSpiException: Impossible to
> > continue join, check if local discovery and communication ports are not
> > blocked with firewall [addr=lab11.gridgain.local/172.25.1.11:47500,
> > req=TcpDiscoveryJoinRequestMessage [node=TcpDiscoveryNode
> > [id=8d1076b1-b131-4c80-abd7-90fda1daba64,
> > consistentId=0:0:0:0:0:0:0:1,127.0.0.1,172.25.1.162,172.31.176.1:47500,
> > addrs=ArrayList [0:0:0:0:0:0:0:1, 127.0.0.1, 172.25.1.162, 172.31.176.1],
> > sockAddrs=HashSet [/0:0:0:0:0:0:0:1:47500,
> > publicagent01_02.mshome.net/172.31.176.1:47500, /127.0.0.1:47500, /
> > 172.25.1.162:47500], discPort=47500, order=0, intOrder=0,
> > lastExchangeTime=1602730030490, loc=true,
> > ver=2.10.0#20201015-sha1:00000000, isClient=false],
> >
> >
> dataPacket=org.apache.ignite.spi.discovery.tcp.internal.DiscoveryDataPacket@4ee43b4f
> > ,
> > super=TcpDiscoveryAbstractMessage [sndNodeId=null,
> > id=370afaa2571-8d1076b1-b131-4c80-abd7-90fda1daba64, verifierNodeId=null,
> > topVer=0, pendingIdx=0, failedNodes=null, isClient=false]],
> > discoLocalPort=47500, discoLocalPortRange=100]
> >
> > чт, 15 окт. 2020 г. в 06:11, <dp...@gmail.com>:
> >
> > > Hi Igniters,
> > >
> > >  I've detected some new issue on TeamCity to be handled. You are more
> > than
> > > welcomed to help.
> > >
> > >  If your changes can lead to this failure(s): We're grateful that you
> > were
> > > a volunteer to make the contribution to this project, but things change
> > and
> > > you may no longer be able to finalize your contribution.
> > >  Could you respond to this email and indicate if you wish to continue
> and
> > > fix test failures or step down and some committer may revert you
> commit.
> > >
> > >  *    New Critical Failure in master Platform .NET (Long Running)
> > >
> >
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetLongRunning?branch=%3Cdefault%3E
> > >  Changes may lead to failure were done by
> > >          - bojidar marinov <bo...@gmail.com>
> > > https://ci.ignite.apache.org/viewModification.html?modId=908629
> > >          - igor sapego <is...@apache.org>
> > > https://ci.ignite.apache.org/viewModification.html?modId=908581
> > >          - ivan daschinskiy <iv...@gmail.com>
> > > https://ci.ignite.apache.org/viewModification.html?modId=908625
> > >          - ivan daschinskiy <iv...@gmail.com>
> > > https://ci.ignite.apache.org/viewModification.html?modId=908576
> > >          - maxim muzafarov <mm...@apache.org>
> > > https://ci.ignite.apache.org/viewModification.html?modId=908579
> > >
> > >          - Here's a reminder of what contributors were agreed to do
> > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > >          - Should you have any questions please contact
> > > dev@ignite.apache.org
> > >
> > > Best Regards,
> > > Apache Ignite TeamCity Bot
> > > https://github.com/apache/ignite-teamcity-bot
> > > Notification generated at 06:11:16 15-10-2020
> > >
> >
> >
> > --
> > Sincerely yours, Ivan Daschinskiy
> >
>


-- 
Sincerely yours, Ivan Daschinskiy

Re: [MTCGA]: new failures in builds [5665538] needs to be handled

Posted by Pavel Tupitsyn <pt...@apache.org>.
Ivan, yes, it does use MulticastIpFinder, which can be problematic in tests,
but it was fine for 5 years, and now got broken.

Do you think this can be caused by the recent changes in GridNioServer?

Pavel

On Thu, Oct 15, 2020 at 9:41 AM Ivan Daschinsky <iv...@gmail.com> wrote:

> It seems, that in this test we use MulticastIpFinder. I suppose, that it
> should be fixed.
> Excerpts from a failed test's log:
>
> [15-Oct-2020 02:47:10][WARN ][main][TcpDiscoveryMulticastIpFinder]
> TcpDiscoveryMulticastIpFinder has no pre-configured addresses (it is
> recommended in production to specify at least one address in
> TcpDiscoveryMulticastIpFinder.getAddresses() configuration property)
> [15-Oct-2020 02:47:26][ERROR][main][IgniteKernal] Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=o.a.i.i.managers.discovery.GridDiscoveryManager]
> class org.apache.ignite.IgniteCheckedException: Failed to start SPI:
> TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
> marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@18fc665b],
> reconCnt=10, reconDelay=2000, maxAckTimeout=600000, soLinger=5,
> forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null,
> skipAddrsRandomization=false]
>   at
>
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:281)
>   at
>
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:974)
>   at
>
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1933)
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1289)
>   at
>
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2096)
>   at
>
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1748)
>   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1143)
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:641)
>   at
>
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:43)
>   at
>
> org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:74)
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Impossible to
> continue join, check if local discovery and communication ports are not
> blocked with firewall [addr=lab11.gridgain.local/172.25.1.11:47500,
> req=TcpDiscoveryJoinRequestMessage [node=TcpDiscoveryNode
> [id=8d1076b1-b131-4c80-abd7-90fda1daba64,
> consistentId=0:0:0:0:0:0:0:1,127.0.0.1,172.25.1.162,172.31.176.1:47500,
> addrs=ArrayList [0:0:0:0:0:0:0:1, 127.0.0.1, 172.25.1.162, 172.31.176.1],
> sockAddrs=HashSet [/0:0:0:0:0:0:0:1:47500,
> publicagent01_02.mshome.net/172.31.176.1:47500, /127.0.0.1:47500, /
> 172.25.1.162:47500], discPort=47500, order=0, intOrder=0,
> lastExchangeTime=1602730030490, loc=true,
> ver=2.10.0#20201015-sha1:00000000, isClient=false],
>
> dataPacket=org.apache.ignite.spi.discovery.tcp.internal.DiscoveryDataPacket@4ee43b4f
> ,
> super=TcpDiscoveryAbstractMessage [sndNodeId=null,
> id=370afaa2571-8d1076b1-b131-4c80-abd7-90fda1daba64, verifierNodeId=null,
> topVer=0, pendingIdx=0, failedNodes=null, isClient=false]],
> discoLocalPort=47500, discoLocalPortRange=100]
>
> чт, 15 окт. 2020 г. в 06:11, <dp...@gmail.com>:
>
> > Hi Igniters,
> >
> >  I've detected some new issue on TeamCity to be handled. You are more
> than
> > welcomed to help.
> >
> >  If your changes can lead to this failure(s): We're grateful that you
> were
> > a volunteer to make the contribution to this project, but things change
> and
> > you may no longer be able to finalize your contribution.
> >  Could you respond to this email and indicate if you wish to continue and
> > fix test failures or step down and some committer may revert you commit.
> >
> >  *    New Critical Failure in master Platform .NET (Long Running)
> >
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetLongRunning?branch=%3Cdefault%3E
> >  Changes may lead to failure were done by
> >          - bojidar marinov <bo...@gmail.com>
> > https://ci.ignite.apache.org/viewModification.html?modId=908629
> >          - igor sapego <is...@apache.org>
> > https://ci.ignite.apache.org/viewModification.html?modId=908581
> >          - ivan daschinskiy <iv...@gmail.com>
> > https://ci.ignite.apache.org/viewModification.html?modId=908625
> >          - ivan daschinskiy <iv...@gmail.com>
> > https://ci.ignite.apache.org/viewModification.html?modId=908576
> >          - maxim muzafarov <mm...@apache.org>
> > https://ci.ignite.apache.org/viewModification.html?modId=908579
> >
> >          - Here's a reminder of what contributors were agreed to do
> > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> >          - Should you have any questions please contact
> > dev@ignite.apache.org
> >
> > Best Regards,
> > Apache Ignite TeamCity Bot
> > https://github.com/apache/ignite-teamcity-bot
> > Notification generated at 06:11:16 15-10-2020
> >
>
>
> --
> Sincerely yours, Ivan Daschinskiy
>

Re: [MTCGA]: new failures in builds [5665538] needs to be handled

Posted by Ivan Daschinsky <iv...@gmail.com>.
It seems, that in this test we use MulticastIpFinder. I suppose, that it
should be fixed.
Excerpts from a failed test's log:

[15-Oct-2020 02:47:10][WARN ][main][TcpDiscoveryMulticastIpFinder]
TcpDiscoveryMulticastIpFinder has no pre-configured addresses (it is
recommended in production to specify at least one address in
TcpDiscoveryMulticastIpFinder.getAddresses() configuration property)
[15-Oct-2020 02:47:26][ERROR][main][IgniteKernal] Failed to start manager:
GridManagerAdapter [enabled=true,
name=o.a.i.i.managers.discovery.GridDiscoveryManager]
class org.apache.ignite.IgniteCheckedException: Failed to start SPI:
TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
marsh=JdkMarshaller
[clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@18fc665b],
reconCnt=10, reconDelay=2000, maxAckTimeout=600000, soLinger=5,
forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null,
skipAddrsRandomization=false]
  at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:281)
  at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:974)
  at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1933)
  at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1289)
  at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2096)
  at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1748)
  at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1143)
  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:641)
  at
org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:43)
  at
org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:74)
Caused by: class org.apache.ignite.spi.IgniteSpiException: Impossible to
continue join, check if local discovery and communication ports are not
blocked with firewall [addr=lab11.gridgain.local/172.25.1.11:47500,
req=TcpDiscoveryJoinRequestMessage [node=TcpDiscoveryNode
[id=8d1076b1-b131-4c80-abd7-90fda1daba64,
consistentId=0:0:0:0:0:0:0:1,127.0.0.1,172.25.1.162,172.31.176.1:47500,
addrs=ArrayList [0:0:0:0:0:0:0:1, 127.0.0.1, 172.25.1.162, 172.31.176.1],
sockAddrs=HashSet [/0:0:0:0:0:0:0:1:47500,
publicagent01_02.mshome.net/172.31.176.1:47500, /127.0.0.1:47500, /
172.25.1.162:47500], discPort=47500, order=0, intOrder=0,
lastExchangeTime=1602730030490, loc=true,
ver=2.10.0#20201015-sha1:00000000, isClient=false],
dataPacket=org.apache.ignite.spi.discovery.tcp.internal.DiscoveryDataPacket@4ee43b4f,
super=TcpDiscoveryAbstractMessage [sndNodeId=null,
id=370afaa2571-8d1076b1-b131-4c80-abd7-90fda1daba64, verifierNodeId=null,
topVer=0, pendingIdx=0, failedNodes=null, isClient=false]],
discoLocalPort=47500, discoLocalPortRange=100]

чт, 15 окт. 2020 г. в 06:11, <dp...@gmail.com>:

> Hi Igniters,
>
>  I've detected some new issue on TeamCity to be handled. You are more than
> welcomed to help.
>
>  If your changes can lead to this failure(s): We're grateful that you were
> a volunteer to make the contribution to this project, but things change and
> you may no longer be able to finalize your contribution.
>  Could you respond to this email and indicate if you wish to continue and
> fix test failures or step down and some committer may revert you commit.
>
>  *    New Critical Failure in master Platform .NET (Long Running)
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetLongRunning?branch=%3Cdefault%3E
>  Changes may lead to failure were done by
>          - bojidar marinov <bo...@gmail.com>
> https://ci.ignite.apache.org/viewModification.html?modId=908629
>          - igor sapego <is...@apache.org>
> https://ci.ignite.apache.org/viewModification.html?modId=908581
>          - ivan daschinskiy <iv...@gmail.com>
> https://ci.ignite.apache.org/viewModification.html?modId=908625
>          - ivan daschinskiy <iv...@gmail.com>
> https://ci.ignite.apache.org/viewModification.html?modId=908576
>          - maxim muzafarov <mm...@apache.org>
> https://ci.ignite.apache.org/viewModification.html?modId=908579
>
>          - Here's a reminder of what contributors were agreed to do
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>          - Should you have any questions please contact
> dev@ignite.apache.org
>
> Best Regards,
> Apache Ignite TeamCity Bot
> https://github.com/apache/ignite-teamcity-bot
> Notification generated at 06:11:16 15-10-2020
>


-- 
Sincerely yours, Ivan Daschinskiy