[ 
https://issues.apache.org/jira/browse/IGNITE-11521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790295#comment-16790295
 ] 

Ignite TC Bot commented on IGNITE-11521:
----------------------------------------

{panel:title=--> Run :: All: Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET{color} [[tests 
6|https://ci.ignite.apache.org/viewLog.html?buildId=3288709]]
* exe: LifecycleTest.TestWithoutBeans - 0,0% fails in last 332 master runs.
* exe: LifecycleTest.TestWithBeans - 0,0% fails in last 332 master runs.

{color:#d04437}MVCC PDS 4{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3288737]]
* IgnitePdsPageEvictionDuringPartitionClearTest.testPageEvictionOnNodeStart 
(last started)

{color:#d04437}Platform C++ (Win x64 | Release){color} [[tests 1 
BuildFailureOnMessage 
|https://ci.ignite.apache.org/viewLog.html?buildId=3288664]]
* IgniteOdbcTest: SslQueriesTestSuite: TestConnectionSslSuccess - 0,9% fails in 
last 422 master runs.

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3288739&buildTypeId=IgniteTests24Java8_RunAll]

> Register listeners before joining the cluster
> ---------------------------------------------
>
>                 Key: IGNITE-11521
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11521
>             Project: Ignite
>          Issue Type: New Feature
>            Reporter: Lukas Polacek
>            Priority: Major
>
> The documentation says to register local listeners through 
> "ignite.events().localListen(...)", however that can only be done once e.g. 
> "ignite = Ignition.start(cfg)" has been called. At that point, the node has 
> already joined the cluster, so we might have missed events in the meantime.
> See also the discussion [in 
> apache-ignite-users|http://apache-ignite-users.70518.x6.nabble.com/Register-listeners-before-joining-the-cluster-td25944.html#none].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to