[jira] [Updated] (IGNITE-12204) In binary distribution, essential dependencies for ignite-spark missing
[
https://issues.apache.org/jira/browse/IGNITE-12204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-12204:
-
Affects Version/s: (was: 2.9)
2.7.6
> In binary distribution, essential dependencies for ignite-spark missing
> ---
>
> Key: IGNITE-12204
> URL: https://issues.apache.org/jira/browse/IGNITE-12204
> Project: Ignite
> Issue Type: Bug
> Components: spark
>Affects Versions: 2.7.6
>Reporter: Ilya Kasnacheev
>Assignee: Alexey Zinoviev
>Priority: Major
> Fix For: 3.0
>
>
> It seems that we only put direct dependencies of other JARs in our binary
> distribution, and not transient ones.
> For example, libs/optional/ignite-spark lacks the essential commons-lang3
> jar, which will lead to the following error immediately:
> {code}
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org.apache.commons.lang3.SystemUtils
> at org.apache.spark.util.Utils$.(Utils.scala:1915)
> at org.apache.spark.util.Utils$.(Utils.scala)
> at
> org.apache.spark.SparkConf.loadFromSystemProperties(SparkConf.scala:75)
> {code}
> It's almost impossible to fix without resorting to Maven source build.
> I understand that adding Spark module to Ignite server is something not
> widely used, but if we ship this module at all, we should make sure that it
> is usable in some form.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13169) Remove Ignite bean name requirement for Spring Data Repository
[ https://issues.apache.org/jira/browse/IGNITE-13169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-13169: - Fix Version/s: 2.9 > Remove Ignite bean name requirement for Spring Data Repository > -- > > Key: IGNITE-13169 > URL: https://issues.apache.org/jira/browse/IGNITE-13169 > Project: Ignite > Issue Type: Improvement > Components: springdata >Affects Versions: 2.8.1 >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > At the moment IgniteRepositoryFactoryBean requires Ignite instance bean (or > IgniteConfiguration instance bean) with specific name. > There are couple of problems with that behavior: > 1) We have a SpringBoot autoconfiguration module which creates bean with > different name, so Ignite Spring Data won't work out of the box > 2) That is, actually, not a Spring-way to do things: Spring prefers > injecting by class, qualifiers like name and order should be used only when > necessay > I propose changing behavior to "getting bean by class and not by name" > > This won't require any user code changes, because we only remove restrictions > on Ignite instance bean name -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12054) [Umbrella][Spark] Upgrade Spark module to 2.4
[ https://issues.apache.org/jira/browse/IGNITE-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144055#comment-17144055 ] Shenson Joseph commented on IGNITE-12054: - Hello All, I have created a backlog to have support for spark-3.0.0 https://issues.apache.org/jira/browse/IGNITE-13181 > [Umbrella][Spark] Upgrade Spark module to 2.4 > - > > Key: IGNITE-12054 > URL: https://issues.apache.org/jira/browse/IGNITE-12054 > Project: Ignite > Issue Type: New Feature > Components: spark >Reporter: Denis A. Magda >Assignee: Alexey Zinoviev >Priority: Blocker > Labels: important > Fix For: 3.0 > > Attachments: ignite-spark-patch-new.diff > > Time Spent: 0.5h > Remaining Estimate: 0h > > Users can't use APIs that are already available in Spark 2.4: > https://stackoverflow.com/questions/57392143/persisting-spark-dataframe-to-ignite > Let's upgrade Spark from 2.3 to 2.4 until we extract the Spark Integration as > a separate module that can support multiple Spark versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12716) Ignite support for spark-3.0.0
[ https://issues.apache.org/jira/browse/IGNITE-12716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144054#comment-17144054 ] Shenson Joseph commented on IGNITE-12716: - Hello All, I have created a backlog to have support for spark-3.0.0 https://issues.apache.org/jira/browse/IGNITE-13181 > Ignite support for spark-3.0.0 > -- > > Key: IGNITE-12716 > URL: https://issues.apache.org/jira/browse/IGNITE-12716 > Project: Ignite > Issue Type: Bug > Components: spark >Affects Versions: 2.7, 2.8, 2.7.5, 2.7.6 >Reporter: Shenson Joseph >Priority: Blocker > > Ignite support for spark-3.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13181) Ignite support for spark-3.0.0
Shenson Joseph created IGNITE-13181: --- Summary: Ignite support for spark-3.0.0 Key: IGNITE-13181 URL: https://issues.apache.org/jira/browse/IGNITE-13181 Project: Ignite Issue Type: New Feature Components: spark Affects Versions: 2.8.1 Reporter: Shenson Joseph feature to support apache spark-3.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13180) AuthenticationContext does not contain subject address when subject is IgniteClient
[
https://issues.apache.org/jira/browse/IGNITE-13180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143930#comment-17143930
]
Ignite TC Bot commented on IGNITE-13180:
{panel:title=Branch: [pull/7960/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/7960/head] Base: [master] : New Tests
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid{color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=6b539f4c-5e7a-45c0-a050-0267a5931078, topVer=0,
nodeId8=17c11653, msg=, type=NODE_JOINED, tstamp=1592951410804],
val2=AffinityTopologyVersion [topVer=4397444367561355914, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=6b539f4c-5e7a-45c0-a050-0267a5931078, topVer=0,
nodeId8=17c11653, msg=, type=NODE_JOINED, tstamp=1592951410804],
val2=AffinityTopologyVersion [topVer=4397444367561355914, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=8709d43e271-e7864063-5005-457a-af6f-f33f543c0474, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=39498587-7ecc-42f2-813f-633cc20cdb33, topVer=0, nodeId8=39498587,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1592951410804]],
val2=AffinityTopologyVersion [topVer=-2891332264240459759, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=8709d43e271-e7864063-5005-457a-af6f-f33f543c0474, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=39498587-7ecc-42f2-813f-633cc20cdb33, topVer=0, nodeId8=39498587,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1592951410804]],
val2=AffinityTopologyVersion [topVer=-2891332264240459759, minorTopVer=0]]] -
PASSED{color}
{color:#8b}Service Grid (legacy mode){color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=032dbba6-c46d-471b-8340-e7445d2e475c, topVer=0,
nodeId8=158b2030, msg=, type=NODE_JOINED, tstamp=1592951505481],
val2=AffinityTopologyVersion [topVer=-314010942147711395, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=032dbba6-c46d-471b-8340-e7445d2e475c, topVer=0,
nodeId8=158b2030, msg=, type=NODE_JOINED, tstamp=1592951505481],
val2=AffinityTopologyVersion [topVer=-314010942147711395, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=f4bf853e271-4bd1fe83-6fa3-49a8-a1c2-88bac1aaf6f7, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=5183675c-9584-4cbe-974c-b30837a64211, topVer=0, nodeId8=5183675c,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1592951505481]],
val2=AffinityTopologyVersion [topVer=3384916733215357033, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=f4bf853e271-4bd1fe83-6fa3-49a8-a1c2-88bac1aaf6f7, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=5183675c-9584-4cbe-974c-b30837a64211, topVer=0, nodeId8=5183675c,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1592951505481]],
val2=AffinityTopologyVersion [topVer=3384916733215357033, minorTopVer=0]]] -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5413208&buildTypeId=IgniteTests24Java8_RunAll]
> AuthenticationContext does not contain subject address when subject is
> IgniteClient
> ---
>
> Key: IGNITE-13180
> URL: https://issues.apache.org/jira/browse/IGNITE-13180
> Project: Ignite
> Issue Type: Task
> Components: thin client
>Reporter: Sergei Ryzhov
>Assignee: Sergei Ryzhov
>Priority: Minor
>
> AuthenticationContext does not contain subject address when s
[jira] [Commented] (IGNITE-12716) Ignite support for spark-3.0.0
[ https://issues.apache.org/jira/browse/IGNITE-12716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143850#comment-17143850 ] Alexey Zinoviev commented on IGNITE-12716: -- Dear [~shensonj] I'm not going to release something for spark support, hope another contributor could help > Ignite support for spark-3.0.0 > -- > > Key: IGNITE-12716 > URL: https://issues.apache.org/jira/browse/IGNITE-12716 > Project: Ignite > Issue Type: Bug > Components: spark >Affects Versions: 2.7, 2.8, 2.7.5, 2.7.6 >Reporter: Shenson Joseph >Priority: Blocker > > Ignite support for spark-3.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12716) Ignite support for spark-3.0.0
[ https://issues.apache.org/jira/browse/IGNITE-12716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143798#comment-17143798 ] Shenson Joseph commented on IGNITE-12716: - [~zaleslaw] [~mmuzaf] [~ alexlumpov] Since apache spark-3.0 is officially released, can we geta support for spark-3.0 for next ignite release? > Ignite support for spark-3.0.0 > -- > > Key: IGNITE-12716 > URL: https://issues.apache.org/jira/browse/IGNITE-12716 > Project: Ignite > Issue Type: Bug > Components: spark >Affects Versions: 2.7, 2.7.5, 2.7.6 >Reporter: Shenson Joseph >Priority: Blocker > > Ignite support for spark-3.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12716) Ignite support for spark-3.0.0
[ https://issues.apache.org/jira/browse/IGNITE-12716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shenson Joseph updated IGNITE-12716: Affects Version/s: 2.8 > Ignite support for spark-3.0.0 > -- > > Key: IGNITE-12716 > URL: https://issues.apache.org/jira/browse/IGNITE-12716 > Project: Ignite > Issue Type: Bug > Components: spark >Affects Versions: 2.7, 2.8, 2.7.5, 2.7.6 >Reporter: Shenson Joseph >Priority: Blocker > > Ignite support for spark-3.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13180) AuthenticationContext does not contain subject address when subject is IgniteClient
[
https://issues.apache.org/jira/browse/IGNITE-13180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143792#comment-17143792
]
Ignite TC Bot commented on IGNITE-13180:
{panel:title=Branch: [pull/7960/head] Base: [master] : Possible Blockers
(508)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform C++ CMake (Linux Clang){color} [[tests 506 JVM CRASH ,
Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=5413827]]
* IgniteOdbcTest: SqlNumericFunctionTestSuite: TestNumericFunctionFloor - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteOdbcTest: TransactionTestSuite: TransactionVersionMismatchError - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteOdbcTest: SqlNumericFunctionTestSuite: TestNumericFunctionLog - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteOdbcTest: SqlDateTimeFunctionTestSuite: TestCurrentDate - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: CacheQueryTestSuite: TestFieldsQueryByteArrayInsertSelect -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestBasic - Test has low fail rate
in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQueryScan - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteOdbcTest: ApiRobustnessTestSuite: TestSQLGetStmtAttr - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteOdbcTest: StreamingTestSuite: TestStreamingManyObjects - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQuerySql - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteThinClientTest: AuthTestSuite: AuthSuccess - Test has low fail rate in
base branch 0,0% and is not flaky
... and 495 tests blockers
{color:#d04437}Platform C++ CMake (Linux){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5413784]]
{panel}
{panel:title=Branch: [pull/7960/head] Base: [master] : New Tests
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid{color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=6b539f4c-5e7a-45c0-a050-0267a5931078, topVer=0,
nodeId8=17c11653, msg=, type=NODE_JOINED, tstamp=1592951410804],
val2=AffinityTopologyVersion [topVer=4397444367561355914, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=6b539f4c-5e7a-45c0-a050-0267a5931078, topVer=0,
nodeId8=17c11653, msg=, type=NODE_JOINED, tstamp=1592951410804],
val2=AffinityTopologyVersion [topVer=4397444367561355914, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=8709d43e271-e7864063-5005-457a-af6f-f33f543c0474, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=39498587-7ecc-42f2-813f-633cc20cdb33, topVer=0, nodeId8=39498587,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1592951410804]],
val2=AffinityTopologyVersion [topVer=-2891332264240459759, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=8709d43e271-e7864063-5005-457a-af6f-f33f543c0474, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=39498587-7ecc-42f2-813f-633cc20cdb33, topVer=0, nodeId8=39498587,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1592951410804]],
val2=AffinityTopologyVersion [topVer=-2891332264240459759, minorTopVer=0]]] -
PASSED{color}
{color:#8b}Service Grid (legacy mode){color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=032dbba6-c46d-471b-8340-e7445d2e475c, topVer=0,
nodeId8=158b2030, msg=, type=NODE_JOINED, tstamp=1592951505481],
val2=AffinityTopologyVersion [topVer=-314010942147711395, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=032dbba6-c46d-471b-8340-e7445d2e475c, topVer=0,
nodeId8=158b2030, msg=, type=NODE_JOINED, tstamp=1592951505481],
val2=AffinityTopologyVersion [topVer=-314010942147711395, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVe
[jira] [Updated] (IGNITE-13042) Update SSL certificates in C++ test suites to more secure signature
[
https://issues.apache.org/jira/browse/IGNITE-13042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-13042:
-
Affects Version/s: 2.8.1
> Update SSL certificates in C++ test suites to more secure signature
> ---
>
> Key: IGNITE-13042
> URL: https://issues.apache.org/jira/browse/IGNITE-13042
> Project: Ignite
> Issue Type: Test
> Components: platforms
>Affects Versions: 2.8.1
>Reporter: Ivan Daschinskiy
>Assignee: Igor Sapego
>Priority: Minor
> Fix For: 2.9
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When modern openssl is used (i.e OpenSSL 1.1.1f, which is default for ubuntu
> 20.04, for example), provided certificates are not accepted, because
> Sha1WithRSAEncryption signature is used, that is widely considered flaw. So
> certificates needs to be renewed (i.e. with sha256WithRSAEncryption signature)
> Example error:
> {code}
> Connecting to 127.0.0.1:0
> 140246535644992:error:140AB18E:SSL routines:SSL_CTX_use_certificate:ca md too
> weak:../ssl/ssl_rsa.c:310:
> Failed to connect :Can not set client certificate file for secure connection:
> path
> /home/ivandasch/ignite/modules/platforms/cpp/thin-client-test/config/ssl/client_full.pem
> {code}
> Affected ignite-odbc-tests and ignite-thin-client-tests
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13042) Update SSL certificates in C++ test suites to more secure signature
[
https://issues.apache.org/jira/browse/IGNITE-13042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-13042:
-
Fix Version/s: 2.9
> Update SSL certificates in C++ test suites to more secure signature
> ---
>
> Key: IGNITE-13042
> URL: https://issues.apache.org/jira/browse/IGNITE-13042
> Project: Ignite
> Issue Type: Test
> Components: platforms
>Reporter: Ivan Daschinskiy
>Assignee: Igor Sapego
>Priority: Minor
> Fix For: 2.9
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When modern openssl is used (i.e OpenSSL 1.1.1f, which is default for ubuntu
> 20.04, for example), provided certificates are not accepted, because
> Sha1WithRSAEncryption signature is used, that is widely considered flaw. So
> certificates needs to be renewed (i.e. with sha256WithRSAEncryption signature)
> Example error:
> {code}
> Connecting to 127.0.0.1:0
> 140246535644992:error:140AB18E:SSL routines:SSL_CTX_use_certificate:ca md too
> weak:../ssl/ssl_rsa.c:310:
> Failed to connect :Can not set client certificate file for secure connection:
> path
> /home/ivandasch/ignite/modules/platforms/cpp/thin-client-test/config/ssl/client_full.pem
> {code}
> Affected ignite-odbc-tests and ignite-thin-client-tests
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13012) Fix failure detection timeout. Simplify node ping routine.
[
https://issues.apache.org/jira/browse/IGNITE-13012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143656#comment-17143656
]
Anton Vinogradov commented on IGNITE-13012:
---
Merged to master.
Thanks for your contribution!
> Fix failure detection timeout. Simplify node ping routine.
> --
>
> Key: IGNITE-13012
> URL: https://issues.apache.org/jira/browse/IGNITE-13012
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.8.1
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Labels: iep-45
> Attachments: IGNITE-13012-patch.patch
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> Connection failure may not be detected within
> IgniteConfiguration.failureDetectionTimeout. Actual worst delay is:
> ServerImpl.CON_CHECK_INTERVAL + IgniteConfiguration.failureDetectionTimeout.
> Node ping routine is duplicated.
> We should fix:
> 1. Failure detection timeout should take in account last sent message.
> Current ping is bound to own time:
> {code:java}ServerImpl. RingMessageWorker.lastTimeConnCheckMsgSent{code}
> This is weird because any discovery message check connection.
> 2. Make connection check interval depend on failure detection timeout (FTD).
> Current value is a constant:
> {code:java}static int ServerImpls.CON_CHECK_INTERVAL = 500{code}
> 3. Remove additional, quickened connection checking. Once we do fix 1, this
> will become even more useless.
> Despite TCP discovery has a period of connection checking, it may send ping
> before this period exhausts. This premature ping relies also on the time of
> any received message for some reason.
> 4. Do not worry user with “Node seems disconnected” when everything is OK.
> Once we do fix 1 and 3, this will become even more useless.
> Node may log on INFO: “Local node seems to be disconnected from topology …”
> whereas it is not actually disconnected at all.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
