[jira] [Commented] (IGNITE-13258) Improve control.sh --cache list command to show cache sizes
[
https://issues.apache.org/jira/browse/IGNITE-13258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157893#comment-17157893
]
Ignite TC Bot commented on IGNITE-13258:
{panel:title=Branch: [pull/8040/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5463846]]
{panel}
{panel:title=Branch: [pull/8040/head] Base: [master] : New Tests
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5463495]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=94385412-a0fa-468b-a9d0-0f6761f8cf54, topVer=0,
nodeId8=3d0493a4, msg=, type=NODE_JOINED, tstamp=1594763678402],
val2=AffinityTopologyVersion [topVer=2243776564316919527, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=94385412-a0fa-468b-a9d0-0f6761f8cf54, topVer=0,
nodeId8=3d0493a4, msg=, type=NODE_JOINED, tstamp=1594763678402],
val2=AffinityTopologyVersion [topVer=2243776564316919527, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=6c2925f4371-03cb8d3d-8a71-4e93-8bb0-18ff9f7066a8, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=0066be58-7c3e-4c30-897e-0ee828e345be, topVer=0, nodeId8=0066be58,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594763678402]],
val2=AffinityTopologyVersion [topVer=-34429067466773871, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=6c2925f4371-03cb8d3d-8a71-4e93-8bb0-18ff9f7066a8, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=0066be58-7c3e-4c30-897e-0ee828e345be, topVer=0, nodeId8=0066be58,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594763678402]],
val2=AffinityTopologyVersion [topVer=-34429067466773871, minorTopVer=0]]] -
PASSED{color}
{color:#8b}Service Grid (legacy mode){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5463700]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=ed9c6a8f-c807-4287-9e2b-28c94245dc02, topVer=0,
nodeId8=81e0063b, msg=, type=NODE_JOINED, tstamp=1594773832917],
val2=AffinityTopologyVersion [topVer=9219164705887131927, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=ed9c6a8f-c807-4287-9e2b-28c94245dc02, topVer=0,
nodeId8=81e0063b, msg=, type=NODE_JOINED, tstamp=1594773832917],
val2=AffinityTopologyVersion [topVer=9219164705887131927, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=46817ff4371-16d78d8c-2dc4-44c9-9e61-27ad67369d02, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=1b913dcc-094a-4af9-a1da-d6fe37ea0f49, topVer=0, nodeId8=1b913dcc,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594773832917]],
val2=AffinityTopologyVersion [topVer=7346781935103230527, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=46817ff4371-16d78d8c-2dc4-44c9-9e61-27ad67369d02, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=1b913dcc-094a-4af9-a1da-d6fe37ea0f49, topVer=0, nodeId8=1b913dcc,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594773832917]],
val2=AffinityTopologyVersion [topVer=7346781935103230527, minorTopVer=0]]] -
PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5463516buildTypeId=IgniteTests24Java8_RunAll]
> Improve control.sh --cache list command to show cache sizes
> ---
>
> Key: IGNITE-13258
> URL: https://issues.apache.org/jira/browse/IGNITE-13258
> Project: Ignite
> Issue Type: Improvement
> Components:
[jira] [Created] (IGNITE-13259) "default" cache usage should be removed from REST API
Evgeniy Rudenko created IGNITE-13259: Summary: "default" cache usage should be removed from REST API Key: IGNITE-13259 URL: https://issues.apache.org/jira/browse/IGNITE-13259 Project: Ignite Issue Type: Improvement Reporter: Evgeniy Rudenko Assignee: Evgeniy Rudenko Right now lots of REST APIs will try to use "default" cache if cacheName is not provided. This is pointless because such cache doesn't exist by default. It will be better to change current behavior and return correct error instead of "Failed to find cache for given cache name: default". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13257) Kubernetes example is not working
[ https://issues.apache.org/jira/browse/IGNITE-13257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157701#comment-17157701 ] Denis A. Magda commented on IGNITE-13257: - Hello Maksim, thanks for sending the changes. I'll have a look in the next few days. > Kubernetes example is not working > - > > Key: IGNITE-13257 > URL: https://issues.apache.org/jira/browse/IGNITE-13257 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > kubernetes module contains config directory that: > # contains misleading DEVNOTES.txt that contains non-actual description how > to assemble Apache Ignite; > # default example isn't worked out-of-the box: > ## latest kubernetes complains about deployment API version; > ## leads to 403 error while nodes try find each other. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13257) Kubernetes example is not working
[ https://issues.apache.org/jira/browse/IGNITE-13257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157581#comment-17157581 ] Maksim Timonin edited comment on IGNITE-13257 at 7/14/20, 7:05 PM: --- [~dmagda] hi! Could you please review my PR? was (Author: timonin.maksim): [~dma...@apache.org] hi! Could you please review my PR? > Kubernetes example is not working > - > > Key: IGNITE-13257 > URL: https://issues.apache.org/jira/browse/IGNITE-13257 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > kubernetes module contains config directory that: > # contains misleading DEVNOTES.txt that contains non-actual description how > to assemble Apache Ignite; > # default example isn't worked out-of-the box: > ## latest kubernetes complains about deployment API version; > ## leads to 403 error while nodes try find each other. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13257) Kubernetes example is not working
[ https://issues.apache.org/jira/browse/IGNITE-13257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157581#comment-17157581 ] Maksim Timonin commented on IGNITE-13257: - [~dma...@apache.org] hi! Could you please review my PR? > Kubernetes example is not working > - > > Key: IGNITE-13257 > URL: https://issues.apache.org/jira/browse/IGNITE-13257 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > kubernetes module contains config directory that: > # contains misleading DEVNOTES.txt that contains non-actual description how > to assemble Apache Ignite; > # default example isn't worked out-of-the box: > ## latest kubernetes complains about deployment API version; > ## leads to 403 error while nodes try find each other. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13258) Improve control.sh --cache list command to show cache sizes
Vladimir Goncharov created IGNITE-13258: --- Summary: Improve control.sh --cache list command to show cache sizes Key: IGNITE-13258 URL: https://issues.apache.org/jira/browse/IGNITE-13258 Project: Ignite Issue Type: Improvement Components: general Affects Versions: 2.8.1 Reporter: Vladimir Goncharov For now --list command doesn't show cache size. CacheInfo and ViewCacheClosure is extended with cache size parameter and according code to show caches size. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13229) GridClient instance leakage.
[ https://issues.apache.org/jira/browse/IGNITE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanilovsky Evgeny updated IGNITE-13229: Release Note: Correctly clears GridClient instances after various errors, for leakage preventing. > GridClient instance leakage. > > > Key: IGNITE-13229 > URL: https://issues.apache.org/jira/browse/IGNITE-13229 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 2.8.1 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Fix For: 2.10 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Instances of GridClient - deprecated realization of thin client, still used > for example, in _control.sh_ can be leaked in some circumstances. Can bring > to OOM in some tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13257) Kubernetes example is not working
Maksim Timonin created IGNITE-13257: --- Summary: Kubernetes example is not working Key: IGNITE-13257 URL: https://issues.apache.org/jira/browse/IGNITE-13257 Project: Ignite Issue Type: Bug Reporter: Maksim Timonin Assignee: Maksim Timonin kubernetes module contains config directory that: # contains misleading DEVNOTES.txt that contains non-actual description how to assemble Apache Ignite; # default example isn't worked out-of-the box: ## latest kubernetes complains about deployment API version; ## leads to 403 error while nodes try find each other. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13255) ODBC/JDBC is very slow
[ https://issues.apache.org/jira/browse/IGNITE-13255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157415#comment-17157415 ] Ilya Kasnacheev commented on IGNITE-13255: -- Creating or destroying a table is a blocking operation across cluster - it would trigger a Partition Map Exchange. This is why the scenario is slow. I doubt that anything can be done about that right now. > ODBC/JDBC is very slow > -- > > Key: IGNITE-13255 > URL: https://issues.apache.org/jira/browse/IGNITE-13255 > Project: Ignite > Issue Type: Bug > Components: jdbc, odbc >Affects Versions: 2.8.1 >Reporter: Christian Ehrlicher >Priority: Major > Attachments: create_table.sql, drop_table.sql > > > The ODBC/JDBC interface seems to be very slow compared to other databases. > I'm not sure if it is a configuration problem on my side but since I more or > less used the default configuration I don't think so. > Attached a small testcase which simply creates 100 tables and another one > which deletes them afterwards. Executing both in a sql browser (I'm using > DBeaver for this test, but should not matter) takes 17 and 20 seconds and > java.exe takes ~2 full cpus. Executing this on a postgreSQL or informix > database the runtime is ~200 / 60 msec. > Even considering that it's no sql database I find the execution times far > from useable. Is this maybe a regression? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13060) Tracing: initial implementation
[
https://issues.apache.org/jira/browse/IGNITE-13060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157395#comment-17157395
]
Ignite TC Bot commented on IGNITE-13060:
{panel:title=Branch: [pull/7973/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/7973/head] Base: [master] : New Tests
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5459353]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=26e0a0c8-4f63-412d-8018-d4a973204c4f, topVer=0,
msgTemplate=null, span=null, nodeId8=07844b0b, msg=, type=NODE_JOINED,
tstamp=1594664079423], val2=AffinityTopologyVersion
[topVer=4229260287584335734, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=340d2694371-f7fad4bb-03ad-454e-a05c-2be1fbd313f0, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=de437e01-0ebf-44a2-8f47-6564d224c43c, topVer=0, msgTemplate=null,
span=null, nodeId8=de437e01, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1594664079423]], val2=AffinityTopologyVersion
[topVer=-8113870052135566906, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=340d2694371-f7fad4bb-03ad-454e-a05c-2be1fbd313f0, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=de437e01-0ebf-44a2-8f47-6564d224c43c, topVer=0, msgTemplate=null,
span=null, nodeId8=de437e01, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1594664079423]], val2=AffinityTopologyVersion
[topVer=-8113870052135566906, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=26e0a0c8-4f63-412d-8018-d4a973204c4f, topVer=0,
msgTemplate=null, span=null, nodeId8=07844b0b, msg=, type=NODE_JOINED,
tstamp=1594664079423], val2=AffinityTopologyVersion
[topVer=4229260287584335734, minorTopVer=0]]] - PASSED{color}
{color:#8b}Service Grid (legacy mode){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5459354]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=be27102e-4d5e-4456-b4fa-d84d1405ae59, topVer=0,
msgTemplate=null, span=null, nodeId8=90615428, msg=, type=NODE_JOINED,
tstamp=1594664002576], val2=AffinityTopologyVersion
[topVer=-4042860089241502699, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=be27102e-4d5e-4456-b4fa-d84d1405ae59, topVer=0,
msgTemplate=null, span=null, nodeId8=90615428, msg=, type=NODE_JOINED,
tstamp=1594664002576], val2=AffinityTopologyVersion
[topVer=-4042860089241502699, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=414a1694371-e6a02854-c90e-4e4e-9f54-d50a21b6bc1e, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=349e439e-0e9b-4e1c-92f9-b88c51f79c84, topVer=0, msgTemplate=null,
span=null, nodeId8=349e439e, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1594664002576]], val2=AffinityTopologyVersion
[topVer=8350738768049997222, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=414a1694371-e6a02854-c90e-4e4e-9f54-d50a21b6bc1e, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=349e439e-0e9b-4e1c-92f9-b88c51f79c84, topVer=0, msgTemplate=null,
span=null, nodeId8=349e439e, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1594664002576]], val2=AffinityTopologyVersion
[topVer=8350738768049997222, minorTopVer=0]]] - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5459374buildTypeId=IgniteTests24Java8_RunAll]
> Tracing: initial implementation
> ---
>
> Key: IGNITE-13060
> URL: https://issues.apache.org/jira/browse/IGNITE-13060
> Project: Ignite
[jira] [Commented] (IGNITE-13229) GridClient instance leakage.
[ https://issues.apache.org/jira/browse/IGNITE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157382#comment-17157382 ] Stanilovsky Evgeny commented on IGNITE-13229: - [~ilyak] looks like basic suite rerun already completed, can u check it ones more plz ? > GridClient instance leakage. > > > Key: IGNITE-13229 > URL: https://issues.apache.org/jira/browse/IGNITE-13229 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 2.8.1 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Instances of GridClient - deprecated realization of thin client, still used > for example, in _control.sh_ can be leaked in some circumstances. Can bring > to OOM in some tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13229) GridClient instance leakage.
[
https://issues.apache.org/jira/browse/IGNITE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157381#comment-17157381
]
Ignite TC Bot commented on IGNITE-13229:
{panel:title=Branch: [pull/8006/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5450704]]
{panel}
{panel:title=Branch: [pull/8006/head] Base: [master] : New Tests
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5449476]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=1d3deeb7-c13d-4740-bc54-9ba5c8c1a4ee, topVer=0,
nodeId8=6ef28d05, msg=, type=NODE_JOINED, tstamp=1594220236209],
val2=AffinityTopologyVersion [topVer=7215358582909498952, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=1d3deeb7-c13d-4740-bc54-9ba5c8c1a4ee, topVer=0,
nodeId8=6ef28d05, msg=, type=NODE_JOINED, tstamp=1594220236209],
val2=AffinityTopologyVersion [topVer=7215358582909498952, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=5bd4eee2371-9569be51-7b3f-4180-9dd2-57341d8cd813, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=0a4002e9-1db2-4e32-9f20-c61157ef731c, topVer=0, nodeId8=0a4002e9,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594220236209]],
val2=AffinityTopologyVersion [topVer=440979196143354, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=5bd4eee2371-9569be51-7b3f-4180-9dd2-57341d8cd813, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=0a4002e9-1db2-4e32-9f20-c61157ef731c, topVer=0, nodeId8=0a4002e9,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594220236209]],
val2=AffinityTopologyVersion [topVer=440979196143354, minorTopVer=0]]] -
PASSED{color}
{color:#8b}Service Grid (legacy mode){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5449477]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=0d0512d1-bed1-4a2f-b239-f76e31739329, topVer=0,
nodeId8=2a4e0452, msg=, type=NODE_JOINED, tstamp=1594220520431],
val2=AffinityTopologyVersion [topVer=-3810796796632234237, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=0d0512d1-bed1-4a2f-b239-f76e31739329, topVer=0,
nodeId8=2a4e0452, msg=, type=NODE_JOINED, tstamp=1594220520431],
val2=AffinityTopologyVersion [topVer=-3810796796632234237, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=3f3a2fe2371-aac23888-8aee-4812-a212-5e9c11adf721, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=543d7ad7-7861-4a68-9dbd-98a9c7a05b0b, topVer=0, nodeId8=543d7ad7,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594220520431]],
val2=AffinityTopologyVersion [topVer=997360565232791116, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=3f3a2fe2371-aac23888-8aee-4812-a212-5e9c11adf721, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=543d7ad7-7861-4a68-9dbd-98a9c7a05b0b, topVer=0, nodeId8=543d7ad7,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594220520431]],
val2=AffinityTopologyVersion [topVer=997360565232791116, minorTopVer=0]]] -
PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5449497buildTypeId=IgniteTests24Java8_RunAll]
> GridClient instance leakage.
>
>
> Key: IGNITE-13229
> URL: https://issues.apache.org/jira/browse/IGNITE-13229
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 2.8.1
>
[jira] [Commented] (IGNITE-13256) IgniteCacheNearRestartRollbackSelfTest.testRestarts (Cache restarts) (Regression) became flaky
[ https://issues.apache.org/jira/browse/IGNITE-13256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157361#comment-17157361 ] Sergey Uttsel commented on IGNITE-13256: [https://github.com/apache/ignite/pull/8037] > IgniteCacheNearRestartRollbackSelfTest.testRestarts (Cache restarts) > (Regression) became flaky > -- > > Key: IGNITE-13256 > URL: https://issues.apache.org/jira/browse/IGNITE-13256 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13256) IgniteCacheNearRestartRollbackSelfTest.testRestarts (Cache restarts) (Regression) became flaky
[ https://issues.apache.org/jira/browse/IGNITE-13256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel reassigned IGNITE-13256: -- Assignee: Sergey Uttsel > IgniteCacheNearRestartRollbackSelfTest.testRestarts (Cache restarts) > (Regression) became flaky > -- > > Key: IGNITE-13256 > URL: https://issues.apache.org/jira/browse/IGNITE-13256 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13255) ODBC/JDBC is very slow
[ https://issues.apache.org/jira/browse/IGNITE-13255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157348#comment-17157348 ] Christian Ehrlicher commented on IGNITE-13255: -- I added the config options but no change. > ODBC/JDBC is very slow > -- > > Key: IGNITE-13255 > URL: https://issues.apache.org/jira/browse/IGNITE-13255 > Project: Ignite > Issue Type: Bug > Components: jdbc, odbc >Affects Versions: 2.8.1 >Reporter: Christian Ehrlicher >Priority: Major > Attachments: create_table.sql, drop_table.sql > > > The ODBC/JDBC interface seems to be very slow compared to other databases. > I'm not sure if it is a configuration problem on my side but since I more or > less used the default configuration I don't think so. > Attached a small testcase which simply creates 100 tables and another one > which deletes them afterwards. Executing both in a sql browser (I'm using > DBeaver for this test, but should not matter) takes 17 and 20 seconds and > java.exe takes ~2 full cpus. Executing this on a postgreSQL or informix > database the runtime is ~200 / 60 msec. > Even considering that it's no sql database I find the execution times far > from useable. Is this maybe a regression? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13256) IgniteCacheNearRestartRollbackSelfTest.testRestarts (Cache restarts) (Regression) became flaky
Sergey Uttsel created IGNITE-13256: -- Summary: IgniteCacheNearRestartRollbackSelfTest.testRestarts (Cache restarts) (Regression) became flaky Key: IGNITE-13256 URL: https://issues.apache.org/jira/browse/IGNITE-13256 Project: Ignite Issue Type: Bug Reporter: Sergey Uttsel -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13254) Historical rebalance iterator may skip checkpoint if it not contains updates
[ https://issues.apache.org/jira/browse/IGNITE-13254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-13254: --- Description: Historical iterator can move forward, bypassing a WAL interval, if one or more checkpoints do not contain update for interest partitions of cache. This can be done through checkpoint records, because it stores all partition counters. > Historical rebalance iterator may skip checkpoint if it not contains updates > > > Key: IGNITE-13254 > URL: https://issues.apache.org/jira/browse/IGNITE-13254 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Priority: Major > > Historical iterator can move forward, bypassing a WAL interval, if one or > more checkpoints do not contain update for interest partitions of cache. > This can be done through checkpoint records, because it stores all partition > counters. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13255) ODBC/JDBC is very slow
[ https://issues.apache.org/jira/browse/IGNITE-13255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157335#comment-17157335 ] Stanilovsky Evgeny commented on IGNITE-13255: - may be it would be helpful somehow, we compare odbc\jdbc performance here [1] [1]https://issues.apache.org/jira/browse/IGNITE-12374 > ODBC/JDBC is very slow > -- > > Key: IGNITE-13255 > URL: https://issues.apache.org/jira/browse/IGNITE-13255 > Project: Ignite > Issue Type: Bug > Components: jdbc, odbc >Affects Versions: 2.8.1 >Reporter: Christian Ehrlicher >Priority: Major > Attachments: create_table.sql, drop_table.sql > > > The ODBC/JDBC interface seems to be very slow compared to other databases. > I'm not sure if it is a configuration problem on my side but since I more or > less used the default configuration I don't think so. > Attached a small testcase which simply creates 100 tables and another one > which deletes them afterwards. Executing both in a sql browser (I'm using > DBeaver for this test, but should not matter) takes 17 and 20 seconds and > java.exe takes ~2 full cpus. Executing this on a postgreSQL or informix > database the runtime is ~200 / 60 msec. > Even considering that it's no sql database I find the execution times far > from useable. Is this maybe a regression? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13255) ODBC/JDBC is very slow
[ https://issues.apache.org/jira/browse/IGNITE-13255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157335#comment-17157335 ] Stanilovsky Evgeny edited comment on IGNITE-13255 at 7/14/20, 12:37 PM: may be it would be helpful somehow, we compare odbc\jdbc performance here [1] [1] https://issues.apache.org/jira/browse/IGNITE-12374 was (Author: zstan): may be it would be helpful somehow, we compare odbc\jdbc performance here [1] [1]https://issues.apache.org/jira/browse/IGNITE-12374 > ODBC/JDBC is very slow > -- > > Key: IGNITE-13255 > URL: https://issues.apache.org/jira/browse/IGNITE-13255 > Project: Ignite > Issue Type: Bug > Components: jdbc, odbc >Affects Versions: 2.8.1 >Reporter: Christian Ehrlicher >Priority: Major > Attachments: create_table.sql, drop_table.sql > > > The ODBC/JDBC interface seems to be very slow compared to other databases. > I'm not sure if it is a configuration problem on my side but since I more or > less used the default configuration I don't think so. > Attached a small testcase which simply creates 100 tables and another one > which deletes them afterwards. Executing both in a sql browser (I'm using > DBeaver for this test, but should not matter) takes 17 and 20 seconds and > java.exe takes ~2 full cpus. Executing this on a postgreSQL or informix > database the runtime is ~200 / 60 msec. > Even considering that it's no sql database I find the execution times far > from useable. Is this maybe a regression? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13254) Historical rebalance iterator may skip checkpoint if it not contains updates
Vladislav Pyatkov created IGNITE-13254: -- Summary: Historical rebalance iterator may skip checkpoint if it not contains updates Key: IGNITE-13254 URL: https://issues.apache.org/jira/browse/IGNITE-13254 Project: Ignite Issue Type: Improvement Reporter: Vladislav Pyatkov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13255) ODBC/JDBC is very slow
Christian Ehrlicher created IGNITE-13255: Summary: ODBC/JDBC is very slow Key: IGNITE-13255 URL: https://issues.apache.org/jira/browse/IGNITE-13255 Project: Ignite Issue Type: Bug Components: jdbc, odbc Affects Versions: 2.8.1 Reporter: Christian Ehrlicher Attachments: create_table.sql, drop_table.sql The ODBC/JDBC interface seems to be very slow compared to other databases. I'm not sure if it is a configuration problem on my side but since I more or less used the default configuration I don't think so. Attached a small testcase which simply creates 100 tables and another one which deletes them afterwards. Executing both in a sql browser (I'm using DBeaver for this test, but should not matter) takes 17 and 20 seconds and java.exe takes ~2 full cpus. Executing this on a postgreSQL or informix database the runtime is ~200 / 60 msec. Even considering that it's no sql database I find the execution times far from useable. Is this maybe a regression? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13086) Improve current page replacement mechanism.
[ https://issues.apache.org/jira/browse/IGNITE-13086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157301#comment-17157301 ] Aleksey Plekhanov commented on IGNITE-13086: [~zstan] thanks for the review and benchmarks! I've merged my fix to master and cherry-picked to 2.9. > Improve current page replacement mechanism. > --- > > Key: IGNITE-13086 > URL: https://issues.apache.org/jira/browse/IGNITE-13086 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.8.1 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Fix For: 2.9 > > Attachments: 8.7-fix-replacement400_rand_512val_5touch_oldts.log, > 8.7-replacement400_rand_512val_5touch_oldts.log, > IgnitePdsPageReplacementTestToYard.java, replacement_64_new.jfr.zip, > replacement_64_old.jfr.zip, screenshot-1.png, screenshot-2.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Experimentally proven that current page replacement functionality has > problems with replace candidate computation. Current implementation obtain 5 > random pages and make further decisions basing this pages last touch > timestamp and some inner flags, however still possible cases when this pages > set can be simply nullified due to inner logic. All improvements need to be > proven, for example, by simple scenario: > 1. put some data until event EVT_PAGE_REPLACEMENT_STARTED is triggered > 2. put 2 times more data than been loaded in p1. > 3. execute fullscan (through ScanQuery) for old\cold data processing > emulation. > 4. start processing only pages which can fit into current mem region. > 5. measure "replacedPages" metric. > (i attach code mention above) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13253) Advanced heuristics for historical rebalance
Vladislav Pyatkov created IGNITE-13253: -- Summary: Advanced heuristics for historical rebalance Key: IGNITE-13253 URL: https://issues.apache.org/jira/browse/IGNITE-13253 Project: Ignite Issue Type: Improvement Reporter: Vladislav Pyatkov Before, cluster detects partitions that have not to rebalance by history, by them size. This threshold might be set through a system property IGNITE_PDS_WAL_REBALANCE_THRESHOLD. But it is not fair deciding which partitions will be rebalanced by WAL only by them size. WAL can have much more records than size of a partition (many update by one key) and that rebalance required more data than full transferring by network. Need to implement a heuristic, that might to estimate data size. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13086) Improve current page replacement mechanism.
[
https://issues.apache.org/jira/browse/IGNITE-13086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157286#comment-17157286
]
Ignite TC Bot commented on IGNITE-13086:
{panel:title=Branch: [pull/7919/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/7919/head] Base: [master] : New Tests
(20)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5395410]]
* {color:#013220}exe:
CallPlatformServiceTest.TestCallPlatformServiceCollections(False) -
PASSED{color}
* {color:#013220}exe:
CallPlatformServiceTest.TestCallPlatformServiceCollections(True) - PASSED{color}
* {color:#013220}exe: CallPlatformServiceTest.TestCallPlatformService(False) -
PASSED{color}
* {color:#013220}exe: CallPlatformServiceTest.TestCallPlatformService(True) -
PASSED{color}
{color:#8b}Platform .NET (Core Linux){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5394312]]
* {color:#013220}dll:
CallPlatformServiceTest.TestCallPlatformServiceCollections(False) -
PASSED{color}
* {color:#013220}dll:
CallPlatformServiceTest.TestCallPlatformServiceCollections(True) - PASSED{color}
* {color:#013220}dll: CallPlatformServiceTest.TestCallPlatformService(False) -
PASSED{color}
* {color:#013220}dll: CallPlatformServiceTest.TestCallPlatformService(True) -
PASSED{color}
{color:#8b}Java Client{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5394245]]
* {color:#013220}IgniteClientTestSuite:
JettyRestProcessorAuthenticationWithTokenSelfTest.testDeactivateActivate -
PASSED{color}
* {color:#013220}IgniteClientTestSuite:
JettyRestProcessorAuthenticationWithCredsSelfTest.testDeactivateActivate -
PASSED{color}
* {color:#013220}IgniteClientTestSuite:
JettyRestProcessorUnsignedSelfTest.testDeactivateActivate - PASSED{color}
* {color:#013220}IgniteClientTestSuite:
JettyRestProcessorSignedSelfTest.testDeactivateActivate - PASSED{color}
{color:#8b}Service Grid{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5394323]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=333f9aa1-2da9-43d4-a790-014918a86c01, topVer=0,
nodeId8=2cf7b4bf, msg=, type=NODE_JOINED, tstamp=1592317005087],
val2=AffinityTopologyVersion [topVer=-2020623706474349563, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=333f9aa1-2da9-43d4-a790-014918a86c01, topVer=0,
nodeId8=2cf7b4bf, msg=, type=NODE_JOINED, tstamp=1592317005087],
val2=AffinityTopologyVersion [topVer=-2020623706474349563, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=defa78db271-9c99baa4-02d0-4b27-afa8-aec29ef6d463, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=51da83fc-196f-442c-a7f9-12ecb08091a0, topVer=0, nodeId8=51da83fc,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1592317005087]],
val2=AffinityTopologyVersion [topVer=-6371275225840810150, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=defa78db271-9c99baa4-02d0-4b27-afa8-aec29ef6d463, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=51da83fc-196f-442c-a7f9-12ecb08091a0, topVer=0, nodeId8=51da83fc,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1592317005087]],
val2=AffinityTopologyVersion [topVer=-6371275225840810150, minorTopVer=0]]] -
PASSED{color}
{color:#8b}Service Grid (legacy mode){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5394324]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=b604fed5-1857-435b-af50-9b1cd9f2e585, topVer=0,
nodeId8=08bd3bf9, msg=, type=NODE_JOINED, tstamp=1592316978448],
val2=AffinityTopologyVersion [topVer=60973813218742, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=b604fed5-1857-435b-af50-9b1cd9f2e585, topVer=0,
nodeId8=08bd3bf9, msg=, type=NODE_JOINED, tstamp=1592316978448],
val2=AffinityTopologyVersion [topVer=60973813218742, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
[jira] [Commented] (IGNITE-9764) Node may hang on start if cluster state is in transition
[
https://issues.apache.org/jira/browse/IGNITE-9764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157282#comment-17157282
]
Aleksey Plekhanov commented on IGNITE-9764:
---
[~agoncharuk], is it still actual? I found that IGNITE-10484 with almost the
same description is already fixed.
Also, I've tried to reproduce the problem, but with no luck
([^JoinNodeToTransitionStateClusterTest.java])
Can we close the ticket?
> Node may hang on start if cluster state is in transition
>
>
> Key: IGNITE-9764
> URL: https://issues.apache.org/jira/browse/IGNITE-9764
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.9
>
> Attachments: JoinNodeToTransitionStateClusterTest.java
>
>
> The following sequence of events may cause node hang on start
> Node starts, detects cluster state transition and waits for it to complete
> {code}
> "start-node-1" #11804 prio=5 os_prio=0 tid=0x7f9cc4022000 nid=0x1094
> waiting on condition [0x7f9ffc4c2000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1084)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2033)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1728)
> - locked <0x9467c890> (a
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1156)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:654)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:917)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:855)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:843)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:809)
> at
> org.apache.ignite.internal.processors.cache.IgniteClusterActivateDeactivateTest.lambda$testConcurrentJoinAndActivate$4(IgniteClusterActivateDeactivateTest.java:539)
> at
> org.apache.ignite.internal.processors.cache.IgniteClusterActivateDeactivateTest$$Lambda$99/295822519.call(Unknown
> Source)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {code}
> Nio thread that is to process a message that would complete the exchange is
> attempting to create a session and get a local node ID
> {code}
> "grid-nio-worker-tcp-comm-3-#9833%cache.IgniteClusterActivateDeactivateTest3%"
> #11875 prio=5 os_prio=0 tid=0x7f9c8009e800 nid=0x10dc waiting on
> condition [0x7f9ff4d76000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for (a
> java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
> at
> org.apache.ignite.internal.util.IgniteUtils.await(IgniteUtils.java:7577)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.getSpiContext(TcpCommunicationSpi.java:2266)
> at
> org.apache.ignite.spi.IgniteSpiAdapter.getLocalNode(IgniteSpiAdapter.java:156)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeLocalNodeId(TcpCommunicationSpi.java:4006)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.nodeIdMessage(TcpCommunicationSpi.java:3999)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.access$300(TcpCommunicationSpi.java:271)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$2.onConnected(TcpCommunicationSpi.java:412)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onSessionOpened(GridNioFilterChain.java:251)
> at
>
[jira] [Updated] (IGNITE-9764) Node may hang on start if cluster state is in transition
[
https://issues.apache.org/jira/browse/IGNITE-9764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-9764:
--
Attachment: JoinNodeToTransitionStateClusterTest.java
> Node may hang on start if cluster state is in transition
>
>
> Key: IGNITE-9764
> URL: https://issues.apache.org/jira/browse/IGNITE-9764
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.9
>
> Attachments: JoinNodeToTransitionStateClusterTest.java
>
>
> The following sequence of events may cause node hang on start
> Node starts, detects cluster state transition and waits for it to complete
> {code}
> "start-node-1" #11804 prio=5 os_prio=0 tid=0x7f9cc4022000 nid=0x1094
> waiting on condition [0x7f9ffc4c2000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1084)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2033)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1728)
> - locked <0x9467c890> (a
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1156)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:654)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:917)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:855)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:843)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:809)
> at
> org.apache.ignite.internal.processors.cache.IgniteClusterActivateDeactivateTest.lambda$testConcurrentJoinAndActivate$4(IgniteClusterActivateDeactivateTest.java:539)
> at
> org.apache.ignite.internal.processors.cache.IgniteClusterActivateDeactivateTest$$Lambda$99/295822519.call(Unknown
> Source)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {code}
> Nio thread that is to process a message that would complete the exchange is
> attempting to create a session and get a local node ID
> {code}
> "grid-nio-worker-tcp-comm-3-#9833%cache.IgniteClusterActivateDeactivateTest3%"
> #11875 prio=5 os_prio=0 tid=0x7f9c8009e800 nid=0x10dc waiting on
> condition [0x7f9ff4d76000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for (a
> java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
> at
> org.apache.ignite.internal.util.IgniteUtils.await(IgniteUtils.java:7577)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.getSpiContext(TcpCommunicationSpi.java:2266)
> at
> org.apache.ignite.spi.IgniteSpiAdapter.getLocalNode(IgniteSpiAdapter.java:156)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeLocalNodeId(TcpCommunicationSpi.java:4006)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.nodeIdMessage(TcpCommunicationSpi.java:3999)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.access$300(TcpCommunicationSpi.java:271)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$2.onConnected(TcpCommunicationSpi.java:412)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onSessionOpened(GridNioFilterChain.java:251)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedSessionOpened(GridNioFilterAdapter.java:88)
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onSessionOpened(GridNioCodecFilter.java:67)
> at
>
[jira] [Updated] (IGNITE-12346) .NET: Platform error:System.NullReferenceException
[
https://issues.apache.org/jira/browse/IGNITE-12346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-12346:
Release Note: .NET: Fix query cursor thread safety (was: Fix query cursor
thread safety)
> .NET: Platform error:System.NullReferenceException
> --
>
> Key: IGNITE-12346
> URL: https://issues.apache.org/jira/browse/IGNITE-12346
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: Denis A. Magda
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.9
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Came across [this StackOverflow
> issue|https://stackoverflow.com/questions/58624177/blocked-system-critical-thread-has-been-detected]
> and the found an NPE that might cause the rest of instabilities:
> {code:java}
> class org.apache.ignite.IgniteException: Platform
> error:System.NullReferenceException: Ññûëêà íà îáúåêò íå óêàçûâàåò íà
> ýêçåìïëÿð îáúåêòà.
>â
> Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.CacheEntryFilterApply(Int64
> memPtr)
>â Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.InLongOutLong(Int32
> type, Int64 val)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.loggerLog(PlatformProcessorImpl.java:404)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:460)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:512)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
> at
> org.apache.ignite.internal.processors.platform.callback.PlatformCallbackUtils.inLongOutLong(Native
> Method)
> at
> org.apache.ignite.internal.processors.platform.callback.PlatformCallbackGateway.cacheEntryFilterApply(PlatformCallbackGateway.java:143)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCacheEntryFilterImpl.apply(PlatformCacheEntryFilterImpl.java:70)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$InternalScanFilter.apply(GridCacheQueryManager.java:3139)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12307) Data types coverage for basic cache operations.
[ https://issues.apache.org/jira/browse/IGNITE-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Rakov updated IGNITE-12307: Fix Version/s: (was: 2.9) 2.10 > Data types coverage for basic cache operations. > --- > > Key: IGNITE-12307 > URL: https://issues.apache.org/jira/browse/IGNITE-12307 > Project: Ignite > Issue Type: Task > Components: cache >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Fix For: 2.10 > > Time Spent: 1h > Remaining Estimate: 0h > > The data types used for testing are not collected at single test/suite and > it's not clear which types are covered and which not. We should redesign the > coverage and cover following > Operations: > * put > * putAll > * remove > * removeAll > * get > * getAll > Data Types both for value and key (if applicable): > * byte/Byte > * short/Short > * int/Integer > * long/Long > * float/Float > * double/Double > * boolean/Boolean > * char/String > * Arrays of primitives (single type) > * Arrays of Objects (different types) > * Collections > * > ** List > * > ** Queue > * > ** Set > * Objects based on: > * > ** primitives only > * > ** primitives + collections > * > ** primitives + collections + nested objects > Persistance mode: > * in-memory > * PDS > Cache configurations: > * atomic/tx/mvcc > * replication/partitioned > * TTL/no TTL > * QueryEntnty > * Backups=1,2 > * EvictionPolicy > * writeSynchronizationMode(FULL_SYNC, PRIMARY_SYNC, FULL_ASYNC) > * onheapCacheEnabled > > We should check basic cache operation, basic sql operations as well as cache > to jdbc and jdbc to cache operations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13245) Rebalance future might hangs in no final state though all partitions are owned
[ https://issues.apache.org/jira/browse/IGNITE-13245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Rakov updated IGNITE-13245: Fix Version/s: (was: 2.9) 2.10 > Rebalance future might hangs in no final state though all partitions are owned > -- > > Key: IGNITE-13245 > URL: https://issues.apache.org/jira/browse/IGNITE-13245 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Fix For: 2.10 > > Time Spent: 20m > Remaining Estimate: 0h > > It is very specific case, when supplier go out of cluster and in the same > time, its partitions have not needed rebalance in new topology. > Loot at my PR for to understand it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12320) Partial index rebuild fails in case indexed cache contains different datatypes
[
https://issues.apache.org/jira/browse/IGNITE-12320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Rakov updated IGNITE-12320:
Fix Version/s: (was: 2.9)
2.10
> Partial index rebuild fails in case indexed cache contains different datatypes
> --
>
> Key: IGNITE-12320
> URL: https://issues.apache.org/jira/browse/IGNITE-12320
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The problem is that in case cache contains different datatypes, all of them
> will be passed to IndexRebuildPartialClosure during iteration over partition.
> Perhaps, TableCacheFilter is supposed to filter out entries of unwanted
> types, but it doesn't work properly.
> Steps to reprocude:
> 1. Add entries of different types (both indexed and not) to cache
> 2. Trigger partial index rebuild
> Index rebuild will fail with the following error:
> {code:java}
> [2019-08-20
> 00:33:55,640][ERROR][pub-#302%h2.GridIndexFullRebuildTest3%][IgniteTestResources]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=98629247,
> val2=844420635165670]], msg=Runtime failure on row: %s string representation>]]]
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=98629247,
> val2=844420635165670]], msg=Runtime failure on row: %s string representation>]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:5126)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2236)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2183)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:285)
> at
> org.apache.ignite.internal.processors.query.h2.IndexRebuildPartialClosure.apply(IndexRebuildPartialClosure.java:49)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.updateIndex(GridCacheMapEntry.java:3867)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processKey(SchemaIndexCacheVisitorImpl.java:254)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processPartition(SchemaIndexCacheVisitorImpl.java:217)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processPartitions(SchemaIndexCacheVisitorImpl.java:176)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.visit(SchemaIndexCacheVisitorImpl.java:135)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.rebuildIndexesFromHash0(IgniteH2Indexing.java:2191)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$7.body(IgniteH2Indexing.java:2154)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed to
> get field because type ID of passed object differs from type ID this
> BinaryField belongs to [expected=-635374417, actual=1778229603]
> at
> org.apache.ignite.internal.binary.BinaryFieldImpl.fieldOrder(BinaryFieldImpl.java:287)
> at
> org.apache.ignite.internal.binary.BinaryFieldImpl.value(BinaryFieldImpl.java:109)
> at
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.fieldValue(QueryBinaryProperty.java:220)
> at
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.value(QueryBinaryProperty.java:116)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2RowDescriptor.columnValue(GridH2RowDescriptor.java:331)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOnheap.getValue0(GridH2KeyValueRowOnheap.java:122)
> at
>
[jira] [Updated] (IGNITE-13191) Public-facing API for "waiting for backups on shutdown"
[ https://issues.apache.org/jira/browse/IGNITE-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Rakov updated IGNITE-13191: Fix Version/s: (was: 2.9) 2.10 > Public-facing API for "waiting for backups on shutdown" > --- > > Key: IGNITE-13191 > URL: https://issues.apache.org/jira/browse/IGNITE-13191 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Fix For: 2.10 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > We should introduce "should wait for backups on shutdown" flag in Ignition > and/or IgniteConfiguration. > Maybe we should do the same to "cancel compute tasks" flag. > Also make sure that we can shut down node explicitly, overriding this flag > but without JVM termination. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-2890) .NET: Add CacheConfiguration.NodeFilter
[ https://issues.apache.org/jira/browse/IGNITE-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Shapkin reassigned IGNITE-2890: Assignee: Alexandr Shapkin > .NET: Add CacheConfiguration.NodeFilter > --- > > Key: IGNITE-2890 > URL: https://issues.apache.org/jira/browse/IGNITE-2890 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 1.6 >Reporter: Pavel Tupitsyn >Assignee: Alexandr Shapkin >Priority: Major > Labels: .net > > See ServiceConfiguration.NodeFilter > * Caches start earlier than platform => need to pass pointer for static > CacheConfigurations > * For dynamic cache start, no need for pointers -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13251) Deadlock between grid-timeout-worker and a thread opening a communication connection.
[
https://issues.apache.org/jira/browse/IGNITE-13251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-13251:
-
Description:
grid-timeout-worker is known to go into a deadlock state with other threads in
a few scenarios.
The general scheme is:
1. A thread `T` is holding lock `L` and is trying to establish a communication
connection, hanging in `safeTcpHandshake` method. Due to the logic of
`safeTcpHandshake`, `grid-timeout-worker` needs to send a signal to `T` in
order for it to proceed.
2. `grid-timeout-worker` is trying to acquire `L`. Hence, the deadlock.
It may include more threads. The lock `L` can be different: checkpoint lock,
GridCacheMapEntry lock, etc.
#
## Example
The below example shows a lock between
* `grid-timeout-worker` trying to acquire a cp read lock in a
`dumpLongRunningTransactions`
* `tcp-comm-worker` trying to establish a connection but hanging on socket
read due to unstable network
* checkpointer trying to start a checkpoint and acquire cp write lock
* `utility` worker waiting for the connection to be established by
`tcp-comm-worker` while holding cp read lock
{code:java}
Thread [name="grid-timeout-worker-#23", id=42, state=WAITING, blockCnt=6991,
waitCnt=1746467]
Lock
[object=java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync@4545a8b9,
ownerName=null, ownerId=-1]
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283)
at
java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(ReentrantReadWriteLock.java:727)
at
o.a.i.i.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1707)
at
o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:715)
at
o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.localGet(GridPartitionedSingleGetFuture.java:511)
at
o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.tryLocalGet(GridPartitionedSingleGetFuture.java:399)
at
o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.mapKeyToNode(GridPartitionedSingleGetFuture.java:366)
at
o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.map(GridPartitionedSingleGetFuture.java:243)
at
o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.init(GridPartitionedSingleGetFuture.java:232)
at
o.a.i.i.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:246)
at
o.a.i.i.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4190)
at
o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4171)
at
o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1362)
at
o.a.i.i.processors.task.GridTaskProcessor.saveTaskMetadata(GridTaskProcessor.java:908)
at
o.a.i.i.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:746)
at
o.a.i.i.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:477)
at
o.a.i.i.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:674)
at
o.a.i.i.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:479)
at o.a.i.i.IgniteComputeImpl.callAsync0(IgniteComputeImpl.java:809)
at o.a.i.i.IgniteComputeImpl.callAsync(IgniteComputeImpl.java:794)
at
o.a.i.i.processors.cache.GridCachePartitionExchangeManager.dumpLongRunningTransaction(GridCachePartitionExchangeManager.java:2115)
at
o.a.i.i.processors.cache.GridCachePartitionExchangeManager.dumpLongRunningOperations0(GridCachePartitionExchangeManager.java:2012)
- locked
o.a.i.i.processors.cache.GridCachePartitionExchangeManager$ActionLimiter@47b86e8f
at
o.a.i.i.processors.cache.GridCachePartitionExchangeManager.dumpLongRunningOperations(GridCachePartitionExchangeManager.java:2180)
at o.a.i.i.IgniteKernal$4.run(IgniteKernal.java:1478)
at
o.a.i.i.processors.timeout.GridTimeoutProcessor$CancelableTask.onTimeout(GridTimeoutProcessor.java:410)
- locked
o.a.i.i.processors.timeout.GridTimeoutProcessor$CancelableTask@67c951c7
at
o.a.i.i.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:279)
at o.a.i.i.util.worker.GridWorker.run(GridWorker.java:120)
[jira] [Updated] (IGNITE-7552) .NET: AtomicConfiguration.DefaultBackups should be 1
[
https://issues.apache.org/jira/browse/IGNITE-7552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-7552:
---
Fix Version/s: (was: 2.10)
> .NET: AtomicConfiguration.DefaultBackups should be 1
>
>
> Key: IGNITE-7552
> URL: https://issues.apache.org/jira/browse/IGNITE-7552
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET, newbie
>
> Defaults have changed in Java (see {{AtomicConfiguration.DFLT_BACKUPS}}),
> update .NET part, add test (we usually check that .NET and Java defaults
> match in {{IgniteConfigurationTest.TestSpringXml}}).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12090) .NET logging exception when creating cache with nullable 'sbyte?' field
[
https://issues.apache.org/jira/browse/IGNITE-12090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-12090:
Priority: Major (was: Critical)
> .NET logging exception when creating cache with nullable 'sbyte?' field
> ---
>
> Key: IGNITE-12090
> URL: https://issues.apache.org/jira/browse/IGNITE-12090
> Project: Ignite
> Issue Type: Bug
> Components: binary, platforms
>Affects Versions: 2.7.5
>Reporter: Denis Zakharov
>Assignee: Alexandr Shapkin
>Priority: Major
> Labels: .NET
> Attachments: a.cs
>
>
>
> Logger throws KeyNotFound exception if NetToJava[type] doesn't have a _type_
> key.
> Looks like we need to replace it with NetToJava[directType].
> {code:java}
> public static void LogIndirectMappingWarning(Type type, ILogger log, string
> logInfo)
> {
> if (type == null)
> return;
> var directType = GetDirectlyMappedType(type);
> if (directType == type)
> return;
> log.Warn("{0}: Type '{1}' maps to Java type '{2}' using unchecked conversion.
> " +
> "This may cause issues in SQL queries. " +
> "You can use '{3}' instead to achieve direct mapping.",
> logInfo, type, NetToJava[type], directType);
> }
> {code}
>
> Steps to reproduce:
> Define a QueryEntity with a sbyte? nullable field, try to create a cache. The
> reproducer is attached.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-7552) .NET: AtomicConfiguration.DefaultBackups should be 1
[
https://issues.apache.org/jira/browse/IGNITE-7552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-7552:
---
Priority: Minor (was: Major)
> .NET: AtomicConfiguration.DefaultBackups should be 1
>
>
> Key: IGNITE-7552
> URL: https://issues.apache.org/jira/browse/IGNITE-7552
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET, newbie
> Fix For: 2.10
>
>
> Defaults have changed in Java (see {{AtomicConfiguration.DFLT_BACKUPS}}),
> update .NET part, add test (we usually check that .NET and Java defaults
> match in {{IgniteConfigurationTest.TestSpringXml}}).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13129) .NET: Thin Client auto retry idempotent operations on node failure
[ https://issues.apache.org/jira/browse/IGNITE-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-13129: Issue Type: Improvement (was: Bug) > .NET: Thin Client auto retry idempotent operations on node failure > -- > > Key: IGNITE-13129 > URL: https://issues.apache.org/jira/browse/IGNITE-13129 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Fix For: 2.9 > > Original Estimate: 12h > Remaining Estimate: 12h > > .NET Thin Client supports failover, but user code is still responsible for > catching exceptions and retrying operations. > 1. IgniteClientException does not provide a reliable way for the user code to > understand whether this is a node failure or something else > 2. We can introduce RetryPolicy configuration parameter with values like > `Reads`, `IdempotentWrites`, `All` and retry corresponding operations > automatically and transparently for the user -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13251) Deadlock between grid-timeout-worker and a thread opening a communication connection.
[
https://issues.apache.org/jira/browse/IGNITE-13251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157200#comment-17157200
]
Alexander Lapin commented on IGNITE-13251:
--
[~ivan.glukos] Could you please take a look?
> Deadlock between grid-timeout-worker and a thread opening a communication
> connection.
> -
>
> Key: IGNITE-13251
> URL: https://issues.apache.org/jira/browse/IGNITE-13251
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> rid-timeout-worker is known to go into a deadlock state with other threads in
> a few scenarios.
> The general scheme is:
> 1. A thread `T` is holding lock `L` and is trying to establish a
> communication connection, hanging in `safeTcpHandshake` method. Due to the
> logic of `safeTcpHandshake`, `grid-timeout-worker` needs to send a signal to
> `T` in order for it to proceed.
> 2. `grid-timeout-worker` is trying to acquire `L`. Hence, the deadlock.
> It may include more threads. The lock `L` can be different: checkpoint lock,
> GridCacheMapEntry lock, etc.
> #
> ## Example
> The below example shows a lock between
> * `grid-timeout-worker` trying to acquire a cp read lock in a
> `dumpLongRunningTransactions`
> * `tcp-comm-worker` trying to establish a connection but hanging on socket
> read due to unstable network
> * checkpointer trying to start a checkpoint and acquire cp write lock
> * `utility` worker waiting for the connection to be established by
> `tcp-comm-worker` while holding cp read lock
> {code:java}
> Thread [name="grid-timeout-worker-#23", id=42, state=WAITING, blockCnt=6991,
> waitCnt=1746467]
> Lock
> [object=java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync@4545a8b9,
> ownerName=null, ownerId=-1]
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283)
> at
> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(ReentrantReadWriteLock.java:727)
> at
> o.a.i.i.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1707)
> at
> o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:715)
> at
> o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.localGet(GridPartitionedSingleGetFuture.java:511)
> at
> o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.tryLocalGet(GridPartitionedSingleGetFuture.java:399)
> at
> o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.mapKeyToNode(GridPartitionedSingleGetFuture.java:366)
> at
> o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.map(GridPartitionedSingleGetFuture.java:243)
> at
> o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.init(GridPartitionedSingleGetFuture.java:232)
> at
> o.a.i.i.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:246)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4190)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4171)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1362)
> at
> o.a.i.i.processors.task.GridTaskProcessor.saveTaskMetadata(GridTaskProcessor.java:908)
> at
> o.a.i.i.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:746)
> at
> o.a.i.i.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:477)
> at
> o.a.i.i.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:674)
> at
> o.a.i.i.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:479)
> at o.a.i.i.IgniteComputeImpl.callAsync0(IgniteComputeImpl.java:809)
> at o.a.i.i.IgniteComputeImpl.callAsync(IgniteComputeImpl.java:794)
> at
> o.a.i.i.processors.cache.GridCachePartitionExchangeManager.dumpLongRunningTransaction(GridCachePartitionExchangeManager.java:2115)
> at
>
[jira] [Assigned] (IGNITE-13251) Deadlock between grid-timeout-worker and a thread opening a communication connection.
[
https://issues.apache.org/jira/browse/IGNITE-13251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin reassigned IGNITE-13251:
Assignee: Alexander Lapin
> Deadlock between grid-timeout-worker and a thread opening a communication
> connection.
> -
>
> Key: IGNITE-13251
> URL: https://issues.apache.org/jira/browse/IGNITE-13251
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> rid-timeout-worker is known to go into a deadlock state with other threads in
> a few scenarios.
> The general scheme is:
> 1. A thread `T` is holding lock `L` and is trying to establish a
> communication connection, hanging in `safeTcpHandshake` method. Due to the
> logic of `safeTcpHandshake`, `grid-timeout-worker` needs to send a signal to
> `T` in order for it to proceed.
> 2. `grid-timeout-worker` is trying to acquire `L`. Hence, the deadlock.
> It may include more threads. The lock `L` can be different: checkpoint lock,
> GridCacheMapEntry lock, etc.
> #
> ## Example
> The below example shows a lock between
> * `grid-timeout-worker` trying to acquire a cp read lock in a
> `dumpLongRunningTransactions`
> * `tcp-comm-worker` trying to establish a connection but hanging on socket
> read due to unstable network
> * checkpointer trying to start a checkpoint and acquire cp write lock
> * `utility` worker waiting for the connection to be established by
> `tcp-comm-worker` while holding cp read lock
> {code:java}
> Thread [name="grid-timeout-worker-#23", id=42, state=WAITING, blockCnt=6991,
> waitCnt=1746467]
> Lock
> [object=java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync@4545a8b9,
> ownerName=null, ownerId=-1]
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283)
> at
> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(ReentrantReadWriteLock.java:727)
> at
> o.a.i.i.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1707)
> at
> o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:715)
> at
> o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.localGet(GridPartitionedSingleGetFuture.java:511)
> at
> o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.tryLocalGet(GridPartitionedSingleGetFuture.java:399)
> at
> o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.mapKeyToNode(GridPartitionedSingleGetFuture.java:366)
> at
> o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.map(GridPartitionedSingleGetFuture.java:243)
> at
> o.a.i.i.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.init(GridPartitionedSingleGetFuture.java:232)
> at
> o.a.i.i.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:246)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4190)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4171)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1362)
> at
> o.a.i.i.processors.task.GridTaskProcessor.saveTaskMetadata(GridTaskProcessor.java:908)
> at
> o.a.i.i.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:746)
> at
> o.a.i.i.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:477)
> at
> o.a.i.i.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:674)
> at
> o.a.i.i.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:479)
> at o.a.i.i.IgniteComputeImpl.callAsync0(IgniteComputeImpl.java:809)
> at o.a.i.i.IgniteComputeImpl.callAsync(IgniteComputeImpl.java:794)
> at
> o.a.i.i.processors.cache.GridCachePartitionExchangeManager.dumpLongRunningTransaction(GridCachePartitionExchangeManager.java:2115)
> at
> o.a.i.i.processors.cache.GridCachePartitionExchangeManager.dumpLongRunningOperations0(GridCachePartitionExchangeManager.java:2012)
> - locked
>
[jira] [Commented] (IGNITE-13251) Deadlock between grid-timeout-worker and a thread opening a communication connection.
[
https://issues.apache.org/jira/browse/IGNITE-13251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157198#comment-17157198
]
Ignite TC Bot commented on IGNITE-13251:
{panel:title=Branch: [pull/8033/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8033/head] Base: [master] : New Tests
(10)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Basic 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5459183]]
* {color:#013220}IgniteBasicTestSuite:
IgniteDiagnosticMessagesMultipleConnectionsTest.testDumpLongRunningOperationDoesntBlockTimeoutWorker
- PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteDiagnosticMessagesTest.testDumpLongRunningOperationDoesntBlockTimeoutWorker
- PASSED{color}
{color:#8b}Service Grid{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5459236]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=fc642316-9ab3-42ad-a21d-fc4330d6a5cc, topVer=0,
nodeId8=a87136fe, msg=, type=NODE_JOINED, tstamp=1594661934844],
val2=AffinityTopologyVersion [topVer=-8225423157668001557, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=fc642316-9ab3-42ad-a21d-fc4330d6a5cc, topVer=0,
nodeId8=a87136fe, msg=, type=NODE_JOINED, tstamp=1594661934844],
val2=AffinityTopologyVersion [topVer=-8225423157668001557, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=00712494371-c5bcc173-35e2-49ea-b9d8-e455df8dcddd, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=378a8773-6711-47ae-a206-b0f0a2beca7c, topVer=0, nodeId8=378a8773,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594661934844]],
val2=AffinityTopologyVersion [topVer=-4831703738820019562, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=00712494371-c5bcc173-35e2-49ea-b9d8-e455df8dcddd, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=378a8773-6711-47ae-a206-b0f0a2beca7c, topVer=0, nodeId8=378a8773,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594661934844]],
val2=AffinityTopologyVersion [topVer=-4831703738820019562, minorTopVer=0]]] -
PASSED{color}
{color:#8b}Service Grid (legacy mode){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5459237]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=6d1f2b57-6e1b-4b96-99cb-dba12e1af46c, topVer=0,
nodeId8=3b6f62a5, msg=, type=NODE_JOINED, tstamp=1594661941700],
val2=AffinityTopologyVersion [topVer=3348899625857375747, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=6d1f2b57-6e1b-4b96-99cb-dba12e1af46c, topVer=0,
nodeId8=3b6f62a5, msg=, type=NODE_JOINED, tstamp=1594661941700],
val2=AffinityTopologyVersion [topVer=3348899625857375747, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=8c132494371-e2f15599-5f63-4cd1-9402-eeb28e0d3208, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=ca71b1ef-c62d-4a54-aae2-eba3927c5251, topVer=0, nodeId8=ca71b1ef,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594661941700]],
val2=AffinityTopologyVersion [topVer=7251829635398505639, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=8c132494371-e2f15599-5f63-4cd1-9402-eeb28e0d3208, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=ca71b1ef-c62d-4a54-aae2-eba3927c5251, topVer=0, nodeId8=ca71b1ef,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594661941700]],
val2=AffinityTopologyVersion [topVer=7251829635398505639, minorTopVer=0]]] -
PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5459257buildTypeId=IgniteTests24Java8_RunAll]
> Deadlock between grid-timeout-worker and
[jira] [Commented] (IGNITE-13248) FileWriteAheadLogManager creates 0-length WAL segments and cannot start later
[
https://issues.apache.org/jira/browse/IGNITE-13248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157185#comment-17157185
]
Ignite TC Bot commented on IGNITE-13248:
{panel:title=Branch: [pull/8030/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8030/head] Base: [master] : New Tests
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5458140]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=0ec035d6-edcd-4c9b-bf08-8c4e126fe324, topVer=0,
nodeId8=7fff2ffe, msg=, type=NODE_JOINED, tstamp=1594644789295],
val2=AffinityTopologyVersion [topVer=8207001182005912424, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=0ec035d6-edcd-4c9b-bf08-8c4e126fe324, topVer=0,
nodeId8=7fff2ffe, msg=, type=NODE_JOINED, tstamp=1594644789295],
val2=AffinityTopologyVersion [topVer=8207001182005912424, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=7fb86484371-4287f42f-9dd0-49c4-aa68-61f4510eb183, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=c2b635b2-d38a-459b-9f49-de1757c7e5fb, topVer=0, nodeId8=c2b635b2,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594644789295]],
val2=AffinityTopologyVersion [topVer=1607146359425875070, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=7fb86484371-4287f42f-9dd0-49c4-aa68-61f4510eb183, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=c2b635b2-d38a-459b-9f49-de1757c7e5fb, topVer=0, nodeId8=c2b635b2,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594644789295]],
val2=AffinityTopologyVersion [topVer=1607146359425875070, minorTopVer=0]]] -
PASSED{color}
{color:#8b}Service Grid (legacy mode){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5458141]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=ebf5f5a8-1751-45b5-b6ec-5d22a9e9c5aa, topVer=0,
nodeId8=10417f34, msg=, type=NODE_JOINED, tstamp=1594644912719],
val2=AffinityTopologyVersion [topVer=1810886295893757325, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=ebf5f5a8-1751-45b5-b6ec-5d22a9e9c5aa, topVer=0,
nodeId8=10417f34, msg=, type=NODE_JOINED, tstamp=1594644912719],
val2=AffinityTopologyVersion [topVer=1810886295893757325, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=e6778484371-93638f39-f9be-4d5b-9dc6-4ff3027aca21, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=7c0e2741-38fd-4678-8279-5b962b40436a, topVer=0, nodeId8=7c0e2741,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594644912719]],
val2=AffinityTopologyVersion [topVer=-8574602747287792466, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=e6778484371-93638f39-f9be-4d5b-9dc6-4ff3027aca21, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=7c0e2741-38fd-4678-8279-5b962b40436a, topVer=0, nodeId8=7c0e2741,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594644912719]],
val2=AffinityTopologyVersion [topVer=-8574602747287792466, minorTopVer=0]]] -
PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5458161buildTypeId=IgniteTests24Java8_RunAll]
> FileWriteAheadLogManager creates 0-length WAL segments and cannot start later
> -
>
> Key: IGNITE-13248
> URL: https://issues.apache.org/jira/browse/IGNITE-13248
> Project: Ignite
> Issue Type: Bug
>Reporter: Nikita Tolstunov
>Assignee: Nikita Tolstunov
>Priority: Major
>
[jira] [Assigned] (IGNITE-13204) Java Thin client Kubernetes discovery
[ https://issues.apache.org/jira/browse/IGNITE-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin reassigned IGNITE-13204: --- Assignee: Maksim Timonin > Java Thin client Kubernetes discovery > - > > Key: IGNITE-13204 > URL: https://issues.apache.org/jira/browse/IGNITE-13204 > Project: Ignite > Issue Type: New Feature > Components: platforms >Reporter: Alexandr >Assignee: Maksim Timonin >Priority: Major > Labels: java > > Thin clients should be able to discover servers from within Kubernetes pod > through k8s API, without specifying any IP addresses. -- This message was sent by Atlassian Jira (v8.3.4#803005)
