[GitHub] ignite pull request #1836: Ignite 4799

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #1836: Ignite 4799

andrey-kuznetsov
GitHub user abeliak opened a pull request:

    https://github.com/apache/ignite/pull/1836

    Ignite 4799

    Do not merge

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-4799

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/1836.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1836
   
----
commit 3129807585a1a968396d51bd63ff927c0d5c26b5
Author: Yakov Zhdanov <[hidden email]>
Date:   2017-04-10T11:08:24Z

    ignite-4799 - removed TCP Discovery heartbeat frequency property, fixed compilation and logic, fixed xml configs

commit 1a684e9e9856113d4577dd3a655902f80705a455
Author: Denis Magda <[hidden email]>
Date:   2017-04-10T18:35:30Z

    IGNITE-4799: altered IgniteConfiguration.metricsUpdateFrequency documentation.

commit a4ba8a9a18ab5d7f5ad0910b761ef8f46c83e884
Author: Pavel Tupitsyn <[hidden email]>
Date:   2017-04-11T07:14:51Z

    .NET: Remove TcpDiscoverySpi.HeartbeatFrequency

commit d2910dc5ac942433535dec5689532f2cbc87c277
Author: Alexander Belyak <[hidden email]>
Date:   2017-04-17T16:11:39Z

    Remove maxMissed*Heartbeats, rename TcpDiscoveryClientHeartbeatMessage to TDCMetrics message, add clientFailureDetectionTimeout

commit c72040a6ccb58dcbd1df8a0693c800dfa5c372b3
Author: Alexander Belyak <[hidden email]>
Date:   2017-04-18T11:47:38Z

    Remove -1 and 0 special values from IgniteConfiguration.metricsUpdateFrequency

commit 2fcb7b840816a86de9881795f0c5d22e7f8a68d9
Author: Alexander Belyak <[hidden email]>
Date:   2017-04-18T12:52:12Z

    Use clientFailureDetectionTimeout in ServerImpl, fix comment

commit cd593c19be65abaa1a1df5fc031f02a07d272799
Author: Alexander Belyak <[hidden email]>
Date:   2017-04-18T13:30:19Z

    Merge remote-tracking branch 'apache/master' into ignite-4799

commit dc13866824e7dedfc5f9e3b038068b03ec3bc2cf
Author: Yakov Zhdanov <[hidden email]>
Date:   2017-04-18T14:19:03Z

    ignite-4799 review

commit 3be940080a2564d8995981fb75d6f867b9b4c6a0
Author: Alexander Belyak <[hidden email]>
Date:   2017-04-18T15:50:07Z

    Rename MetricsMessage to MetricsUpdateMessage, muFreq to metricsUpdateFreq, fix metricsUpdateInterval

commit f6d5974fb95f7fc0bc40d0dc4df2457dda4bc697
Author: Alexander Belyak <[hidden email]>
Date:   2017-04-19T10:02:14Z

    Add clientFailureDetectionTimeout test

commit 4d3a60dea820e4df87365e706f37ef2d55e67ce4
Author: Alexander Belyak <[hidden email]>
Date:   2017-04-19T16:06:24Z

    Use clientFailureDetectionTimeout in ServerImpl, add test

commit 9d0ede1741f9a93acc3aa5947521838afc69cf5d
Author: Alexander Belyak <[hidden email]>
Date:   2017-04-20T07:24:51Z

    Merge branch 'master' into ignite-4799

commit c7ffa178182c80f9b86d5a76fb53a714284b491b
Author: Alexander Belyak <[hidden email]>
Date:   2017-04-20T08:22:23Z

    Add test for Server to Server failure detection timeout

commit fab170cabdb25f1a84129256f6fbc824f933fee1
Author: Yakov Zhdanov <[hidden email]>
Date:   2017-04-20T08:32:53Z

    ignite-4799 review

commit 37d9f2c89f62689204c68d8795c1d4a47be98231
Author: Alexander Belyak <[hidden email]>
Date:   2017-04-20T10:17:19Z

    Simplify tests for failure detect timeouts

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #1836: Ignite 4799

andrey-kuznetsov
Github user abeliak closed the pull request at:

    https://github.com/apache/ignite/pull/1836


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---