[jira] [Updated] (IGNITE-13158) Get rid of Externalizable interface at IgniteTxAdapter
[
https://issues.apache.org/jira/browse/IGNITE-13158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-13158:
-
Fix Version/s: 2.10
> Get rid of Externalizable interface at IgniteTxAdapter
> --
>
> Key: IGNITE-13158
> URL: https://issues.apache.org/jira/browse/IGNITE-13158
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8.1
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It seems that {{IgniteTxAdapter}} implements {{Externalizable}} without any
> reason. Transaction instances are not transferred via network, and so I see
> no reason for implementing {{Externalizable}} interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13069) Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression
[
https://issues.apache.org/jira/browse/IGNITE-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167355#comment-17167355
]
Ignite TC Bot commented on IGNITE-13069:
{panel:title=Branch: [pull/8090/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8090/head] Base: [master] : New Tests
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid (legacy mode){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5497406]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=d05c8658-6f66-416c-a5a8-3e222eaafcb0, topVer=0,
msgTemplate=null, span=null, nodeId8=5f1c8d65, msg=, type=NODE_JOINED,
tstamp=1596016731254], val2=AffinityTopologyVersion
[topVer=6797525586752196905, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=d05c8658-6f66-416c-a5a8-3e222eaafcb0, topVer=0,
msgTemplate=null, span=null, nodeId8=5f1c8d65, msg=, type=NODE_JOINED,
tstamp=1596016731254], val2=AffinityTopologyVersion
[topVer=6797525586752196905, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=98cec0a9371-8a1a16b7-e7a7-44fe-9cac-9117a5f1b480, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=9da1cdfb-545c-4e9f-bfde-ed4ad6ab644e, topVer=0, msgTemplate=null,
span=null, nodeId8=9da1cdfb, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1596016731254]], val2=AffinityTopologyVersion
[topVer=2402949203257572053, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=98cec0a9371-8a1a16b7-e7a7-44fe-9cac-9117a5f1b480, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=9da1cdfb-545c-4e9f-bfde-ed4ad6ab644e, topVer=0, msgTemplate=null,
span=null, nodeId8=9da1cdfb, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1596016731254]], val2=AffinityTopologyVersion
[topVer=2402949203257572053, minorTopVer=0]]] - PASSED{color}
{color:#8b}Service Grid{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5498244]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=7a515290-e161-4fb1-ae7d-4d22500359ee, topVer=0,
msgTemplate=null, span=null, nodeId8=d7f7e8d3, msg=, type=NODE_JOINED,
tstamp=1596026175240], val2=AffinityTopologyVersion
[topVer=3254158474756786088, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=23c1c9a9371-edb6db8c-a356-47ef-9642-d43f64a7084b, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=4750aa84-dbaf-4651-bd66-613f2a530d1f, topVer=0, msgTemplate=null,
span=null, nodeId8=4750aa84, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1596026175240]], val2=AffinityTopologyVersion
[topVer=-4755534584482214321, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=23c1c9a9371-edb6db8c-a356-47ef-9642-d43f64a7084b, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=4750aa84-dbaf-4651-bd66-613f2a530d1f, topVer=0, msgTemplate=null,
span=null, nodeId8=4750aa84, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1596026175240]], val2=AffinityTopologyVersion
[topVer=-4755534584482214321, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=7a515290-e161-4fb1-ae7d-4d22500359ee, topVer=0,
msgTemplate=null, span=null, nodeId8=d7f7e8d3, msg=, type=NODE_JOINED,
tstamp=1596026175240], val2=AffinityTopologyVersion
[topVer=3254158474756786088, minorTopVer=0]]] - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5498267buildTypeId=IgniteTests24Java8_RunAll]
> Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression
> -
>
> Key: IGNITE-13069
>
[jira] [Commented] (IGNITE-13299) Flacky GridServiceDeployClusterReadOnlyModeTest and all including tests.
[ https://issues.apache.org/jira/browse/IGNITE-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167338#comment-17167338 ] Aleksey Plekhanov commented on IGNITE-13299: [~zstan], looks good to me. Merged to master. Thanks for the contribution! > Flacky GridServiceDeployClusterReadOnlyModeTest and all including tests. > > > Key: IGNITE-13299 > URL: https://issues.apache.org/jira/browse/IGNITE-13299 > Project: Ignite > Issue Type: Bug > Components: managed services >Affects Versions: 2.8.1 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > > Starting > GridServiceDeployClusterReadOnlyModeTest#testDeployClusterSingletonAllowed > until failure and catch assertion on 200 iteration. This failure is due > incorrect assumption that if service already deployed > org.apache.ignite.services.Service#execute would be called before returning > from deployment would be happened. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13069) Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression
[
https://issues.apache.org/jira/browse/IGNITE-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167256#comment-17167256
]
Ignite TC Bot commented on IGNITE-13069:
{panel:title=Branch: [pull/8090/head] Base: [master] : Possible Blockers
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5498212]]
{color:#d04437}Control Utility (Zookeeper){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5498266]]
* ZookeeperIgniteControlUtilityTestSuite:
GridCommandHandlerTest.testCacheIdleVerifyPrintLostPartitions - Test has low
fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/8090/head] Base: [master] : New Tests
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid (legacy mode){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5497406]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=d05c8658-6f66-416c-a5a8-3e222eaafcb0, topVer=0,
msgTemplate=null, span=null, nodeId8=5f1c8d65, msg=, type=NODE_JOINED,
tstamp=1596016731254], val2=AffinityTopologyVersion
[topVer=6797525586752196905, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=d05c8658-6f66-416c-a5a8-3e222eaafcb0, topVer=0,
msgTemplate=null, span=null, nodeId8=5f1c8d65, msg=, type=NODE_JOINED,
tstamp=1596016731254], val2=AffinityTopologyVersion
[topVer=6797525586752196905, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=98cec0a9371-8a1a16b7-e7a7-44fe-9cac-9117a5f1b480, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=9da1cdfb-545c-4e9f-bfde-ed4ad6ab644e, topVer=0, msgTemplate=null,
span=null, nodeId8=9da1cdfb, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1596016731254]], val2=AffinityTopologyVersion
[topVer=2402949203257572053, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=98cec0a9371-8a1a16b7-e7a7-44fe-9cac-9117a5f1b480, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=9da1cdfb-545c-4e9f-bfde-ed4ad6ab644e, topVer=0, msgTemplate=null,
span=null, nodeId8=9da1cdfb, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1596016731254]], val2=AffinityTopologyVersion
[topVer=2402949203257572053, minorTopVer=0]]] - PASSED{color}
{color:#8b}Service Grid{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5498244]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=7a515290-e161-4fb1-ae7d-4d22500359ee, topVer=0,
msgTemplate=null, span=null, nodeId8=d7f7e8d3, msg=, type=NODE_JOINED,
tstamp=1596026175240], val2=AffinityTopologyVersion
[topVer=3254158474756786088, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=23c1c9a9371-edb6db8c-a356-47ef-9642-d43f64a7084b, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=4750aa84-dbaf-4651-bd66-613f2a530d1f, topVer=0, msgTemplate=null,
span=null, nodeId8=4750aa84, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1596026175240]], val2=AffinityTopologyVersion
[topVer=-4755534584482214321, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=23c1c9a9371-edb6db8c-a356-47ef-9642-d43f64a7084b, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=4750aa84-dbaf-4651-bd66-613f2a530d1f, topVer=0, msgTemplate=null,
span=null, nodeId8=4750aa84, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1596026175240]], val2=AffinityTopologyVersion
[topVer=-4755534584482214321, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=7a515290-e161-4fb1-ae7d-4d22500359ee, topVer=0,
msgTemplate=null, span=null, nodeId8=d7f7e8d3, msg=, type=NODE_JOINED,
tstamp=1596026175240], val2=AffinityTopologyVersion
[jira] [Commented] (IGNITE-13302) Java thin client connect/disconnect during topology update may lead to partition divergence in ignite-sys-cache
[
https://issues.apache.org/jira/browse/IGNITE-13302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167230#comment-17167230
]
Stepachev Maksim commented on IGNITE-13302:
---
[https://github.com/apache/ignite/pull/8096]
> Java thin client connect/disconnect during topology update may lead to
> partition divergence in ignite-sys-cache
> ---
>
> Key: IGNITE-13302
> URL: https://issues.apache.org/jira/browse/IGNITE-13302
> Project: Ignite
> Issue Type: Bug
>Reporter: Stepachev Maksim
>Assignee: Stepachev Maksim
>Priority: Major
>
> And you can see partition inconsistency in ignite-sys-cache
> {noformat}
> [2020-04-23 15:26:31,816][WARN ][sys-#45%gridgain.Sdsb11784Ver20%][root]
> Partition states validation has failed for group: ignite-sys-cache, msg:
> Partitions cache sizes are inconsistent for Part 31: [127.0.0.1:47500=1
> 127.0.0.1:47501=2 ] Part 43: [127.0.0.1:47500=3 127.0.0.1:47501=4 ] Part 44:
> [127.0.0.1:47500=1 127.0.0.1:47501=2 ] Part 46: [127.0.0.1:47500=0
> 127.0.0.1:47501=1 ] Part 91: [127.0.0.1:47500=1 127.0.0.1:47501=2 ]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13288) Include few system events by default
[ https://issues.apache.org/jira/browse/IGNITE-13288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167177#comment-17167177 ] Denis Mekhanikov commented on IGNITE-13288: --- The fix looks good to me. I left a minor comment in the PR. > Include few system events by default > > > Key: IGNITE-13288 > URL: https://issues.apache.org/jira/browse/IGNITE-13288 > Project: Ignite > Issue Type: Wish >Reporter: Aleksandr Kozhenkov >Assignee: Aleksandr Kozhenkov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > There are discovery events that are listened to by all nodes. > It will be useful to include these events to listen on all nodes by default > too: > - EVT_CLUSTER_ACTIVATED > - EVT_CLUSTER_DEACTIVATED > - EVT_BASELINE_CHANGED > - EVT_CLUSTER_STATE_CHANGED > > They all are rare, system and cluster-wide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13306) CpuLoad metric return -1 under Java 11
[
https://issues.apache.org/jira/browse/IGNITE-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167164#comment-17167164
]
Denis Mekhanikov commented on IGNITE-13306:
---
[~ibessonov] there are different possible ways to solve this issue.
One of them is to cast the {{java.lang.management.OperatingSystemMXBean}} to
{{com.sun.management.OperatingSystemMXBean}} and call {{getProcessCpuTime()}}
directly. This way metrics will only work on those JVMs that have
{{com.sun.management.OperatingSystemMXBean}}, which is platform-specific.
Another way is to figure out how to call {{getProcessCpuTime()}} via reflection
without violating any checks. It's possible that there are other
implementations of {{java.lang.management.OperatingSystemMXBean}} that have
this method. But even if you remove the call to {{setAccessible(true)}}, then
the exception will be thrown anyways, since the internal class
{{OperatingSystemImpl}} will be used, even though a public interface is present.
So, I suggest merging this change as a temporary workaround that will work for
most cases, and see how it can be fixed properly in a separate ticket.
> CpuLoad metric return -1 under Java 11
> --
>
> Key: IGNITE-13306
> URL: https://issues.apache.org/jira/browse/IGNITE-13306
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8.1
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Start cluster under Java 11.
> Observed:
> CpuLoad metric will return -1
> Expected:
> Real CpuLoad.
> We investigated this issue and found that under Java 11 code failed with
> following trace:
> {code:java}
> class org.apache.ignite.IgniteException: Failed to get property value
> [property=processCpuTime,
> obj=com.sun.management.internal.OperatingSystemImpl@1dd92fe2] at
> org.apache.ignite.internal.util.IgniteUtils.property(IgniteUtils.java:8306)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$MetricsUpdater.getCpuLoad(GridDiscoveryManager.java:3131)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$MetricsUpdater.run(GridDiscoveryManager.java:3093)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$CancelableTask.onTimeout(GridTimeoutProcessor.java:364)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:233)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) at
> java.base/java.lang.Thread.run(Thread.java:834) Caused by:
> java.lang.reflect.InaccessibleObjectException: Unable to make public long
> com.sun.management.internal.OperatingSystemImpl.getProcessCpuTime()
> accessible: module jdk.management does not "opens
> com.sun.management.internal" to unnamed module @35fb3008 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280)
> at java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:198)
> at java.base/java.lang.reflect.Method.setAccessible(Method.java:192) at
> org.apache.ignite.internal.util.IgniteUtils.property(IgniteUtils.java:8297)
> ... 6 more
> {code}
> Under Java 8 metric has expected value.
>
> Solution:
> The behaviour is expected because in Java 11 the CPU load metrics is moved to
> JDK internal module which is not accessible by default. Adding the following
> line to the jvm in which Ignite node is started should solve the issue:
> {noformat}
> --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13304) Improve javadocs for classes related to cache configuration enrichment
[ https://issues.apache.org/jira/browse/IGNITE-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167154#comment-17167154 ] Vyacheslav Koptilin commented on IGNITE-13304: -- Cache (Restarts) 1 timeout does not relate to the proposed Javadoc change. > Improve javadocs for classes related to cache configuration enrichment > --- > > Key: IGNITE-13304 > URL: https://issues.apache.org/jira/browse/IGNITE-13304 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.8.1 >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Minor > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > In my opinion, Javadocs for some classes related to cache configuration > enrichment need to be improved. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13304) Improve javadocs for classes related to cache configuration enrichment
[
https://issues.apache.org/jira/browse/IGNITE-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167152#comment-17167152
]
Ignite TC Bot commented on IGNITE-13304:
{panel:title=Branch: [pull/8086/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Restarts) 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5497309]]
{panel}
{panel:title=Branch: [pull/8086/head] Base: [master] : New Tests
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid (legacy mode){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5496064]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=ef30bc32-a39e-4e2f-a118-05da65fc8d08, topVer=0,
msgTemplate=null, span=null, nodeId8=02ad7b2b, msg=, type=NODE_JOINED,
tstamp=1595938923101], val2=AffinityTopologyVersion
[topVer=-7473517627470142229, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=ef30bc32-a39e-4e2f-a118-05da65fc8d08, topVer=0,
msgTemplate=null, span=null, nodeId8=02ad7b2b, msg=, type=NODE_JOINED,
tstamp=1595938923101], val2=AffinityTopologyVersion
[topVer=-7473517627470142229, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=1626f559371-76001705-f809-46e4-ae86-895f8c028737, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=92033b77-f0f3-481e-b6d4-07ff069b52aa, topVer=0, msgTemplate=null,
span=null, nodeId8=92033b77, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1595938923101]], val2=AffinityTopologyVersion
[topVer=7970082989389142300, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=1626f559371-76001705-f809-46e4-ae86-895f8c028737, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=92033b77-f0f3-481e-b6d4-07ff069b52aa, topVer=0, msgTemplate=null,
span=null, nodeId8=92033b77, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1595938923101]], val2=AffinityTopologyVersion
[topVer=7970082989389142300, minorTopVer=0]]] - PASSED{color}
{color:#8b}Service Grid{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5496063]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=88b5afca-b5eb-4023-abb4-058bd26d4f6f, topVer=0,
msgTemplate=null, span=null, nodeId8=e08c, msg=, type=NODE_JOINED,
tstamp=1595938867532], val2=AffinityTopologyVersion
[topVer=-1178555691555277085, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=88b5afca-b5eb-4023-abb4-058bd26d4f6f, topVer=0,
msgTemplate=null, span=null, nodeId8=e08c, msg=, type=NODE_JOINED,
tstamp=1595938867532], val2=AffinityTopologyVersion
[topVer=-1178555691555277085, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=0598e559371-9406e3de-07fe-4422-93ff-b23b63762c77, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=afee2c2c-4cd5-4159-8c14-f7165698d55b, topVer=0, msgTemplate=null,
span=null, nodeId8=afee2c2c, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1595938867532]], val2=AffinityTopologyVersion
[topVer=-8759338445134259941, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=0598e559371-9406e3de-07fe-4422-93ff-b23b63762c77, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=afee2c2c-4cd5-4159-8c14-f7165698d55b, topVer=0, msgTemplate=null,
span=null, nodeId8=afee2c2c, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1595938867532]], val2=AffinityTopologyVersion
[topVer=-8759338445134259941, minorTopVer=0]]] - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5496086buildTypeId=IgniteTests24Java8_RunAll]
> Improve javadocs for classes related to cache configuration
[jira] [Updated] (IGNITE-13297) The TcpDiscoveryZooKeeperIpFinder does not work properly in Hadoop YARN environment.
[ https://issues.apache.org/jira/browse/IGNITE-13297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YuJue Li updated IGNITE-13297: -- Description: The TcpDiscoveryZooKeeperIpFinder does not work properly in Hadoop YARN environment, the issue should be related to the version conflict of curator, the errors are as follows: !image-2020-07-25-10-03-54-464.png! was: The ignite-zookeeper module does not work properly in Hadoop YARN environment, the issue should be related to the version conflict of curator, the errors are as follows: !image-2020-07-25-10-03-54-464.png! > The TcpDiscoveryZooKeeperIpFinder does not work properly in Hadoop YARN > environment. > > > Key: IGNITE-13297 > URL: https://issues.apache.org/jira/browse/IGNITE-13297 > Project: Ignite > Issue Type: Bug > Components: zookeeper >Affects Versions: 2.8.1 >Reporter: YuJue Li >Priority: Critical > Fix For: 2.10 > > Attachments: image-2020-07-25-10-03-54-464.png > > > The TcpDiscoveryZooKeeperIpFinder does not work properly in Hadoop YARN > environment, the issue should be related to the version conflict of curator, > the errors are as follows: > !image-2020-07-25-10-03-54-464.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13297) The TcpDiscoveryZooKeeperIpFinder does not work properly in Hadoop YARN environment.
[ https://issues.apache.org/jira/browse/IGNITE-13297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YuJue Li updated IGNITE-13297: -- Summary: The TcpDiscoveryZooKeeperIpFinder does not work properly in Hadoop YARN environment. (was: The ignite-zookeeper module does not work properly in Hadoop YARN environment.) > The TcpDiscoveryZooKeeperIpFinder does not work properly in Hadoop YARN > environment. > > > Key: IGNITE-13297 > URL: https://issues.apache.org/jira/browse/IGNITE-13297 > Project: Ignite > Issue Type: Bug > Components: zookeeper >Affects Versions: 2.8.1 >Reporter: YuJue Li >Priority: Critical > Fix For: 2.10 > > Attachments: image-2020-07-25-10-03-54-464.png > > > The ignite-zookeeper module does not work properly in Hadoop YARN > environment, the issue should be related to the version conflict of curator, > the errors are as follows: > !image-2020-07-25-10-03-54-464.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13301) IgniteScheduler has to run inside the Ignite Sandbox with appropriate security context.
[
https://issues.apache.org/jira/browse/IGNITE-13301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Garus updated IGNITE-13301:
-
Summary: IgniteScheduler has to run inside the Ignite Sandbox with
appropriate security context. (was: IgniteScheduler has to run inside the
Ignite Sandbox.)
> IgniteScheduler has to run inside the Ignite Sandbox with appropriate
> security context.
> ---
>
> Key: IGNITE-13301
> URL: https://issues.apache.org/jira/browse/IGNITE-13301
> Project: Ignite
> Issue Type: Task
> Components: security
>Reporter: Denis Garus
>Assignee: Denis Garus
>Priority: Major
> Labels: iep-38
>
> IgniteScheduler has to run inside the Ignite Sandbox on a remote node.
> For example:
> {code:java}
> Ignition.localIgnite().compute().run(() -> {
> IgniteScheduler scheduler = Ignition.localIgnite().scheduler();
> scheduler.runLocal(AbstractSandboxTest::controlAction).get();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13297) The TcpDiscoveryZooKeeperIpFinder does not work properly in Hadoop YARN environment.
[ https://issues.apache.org/jira/browse/IGNITE-13297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YuJue Li updated IGNITE-13297: -- Summary: The TcpDiscoveryZooKeeperIpFinder does not work properly in Hadoop YARN environment. (was: The ignite-zookeeper module does not work properly in Hadoop YARN environment.) > The TcpDiscoveryZooKeeperIpFinder does not work properly in Hadoop YARN > environment. > > > Key: IGNITE-13297 > URL: https://issues.apache.org/jira/browse/IGNITE-13297 > Project: Ignite > Issue Type: Bug > Components: zookeeper >Affects Versions: 2.8.1 >Reporter: YuJue Li >Priority: Critical > Fix For: 2.10 > > Attachments: image-2020-07-25-10-03-54-464.png > > > The ignite-zookeeper module does not work properly in Hadoop YARN > environment, the issue should be related to the version conflict of curator, > the errors are as follows: > !image-2020-07-25-10-03-54-464.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13297) The ignite-zookeeper module does not work properly in Hadoop YARN environment.
[ https://issues.apache.org/jira/browse/IGNITE-13297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YuJue Li updated IGNITE-13297: -- Summary: The ignite-zookeeper module does not work properly in Hadoop YARN environment. (was: The TcpDiscoveryZooKeeperIpFinder does not work properly in Hadoop YARN environment.) > The ignite-zookeeper module does not work properly in Hadoop YARN environment. > -- > > Key: IGNITE-13297 > URL: https://issues.apache.org/jira/browse/IGNITE-13297 > Project: Ignite > Issue Type: Bug > Components: zookeeper >Affects Versions: 2.8.1 >Reporter: YuJue Li >Priority: Critical > Fix For: 2.10 > > Attachments: image-2020-07-25-10-03-54-464.png > > > The ignite-zookeeper module does not work properly in Hadoop YARN > environment, the issue should be related to the version conflict of curator, > the errors are as follows: > !image-2020-07-25-10-03-54-464.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13309) Extend c++ build documentation.
[ https://issues.apache.org/jira/browse/IGNITE-13309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166953#comment-17166953 ] Stanilovsky Evgeny commented on IGNITE-13309: - [~isapego] [~ivandasch] can you review this minor, but i hope helpful fix in cpp build process documentation ? > Extend c++ build documentation. > --- > > Key: IGNITE-13309 > URL: https://issues.apache.org/jira/browse/IGNITE-13309 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.8.1 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Minor > > Need to append additional boost dependencies: > *boost-regex* > And additional steps for QTCreator running. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13306) CpuLoad metric return -1 under Java 11
[
https://issues.apache.org/jira/browse/IGNITE-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166695#comment-17166695
]
Mirza Aliev edited comment on IGNITE-13306 at 7/29/20, 6:52 AM:
Hi [Ivan
Bessonov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ibessonov]!
Thank you for your comments!
On the one hand I agree with you that your ideas might be more correct in terms
of simplification of the existing code, namely MetricsUpdater. On the other
hand the way we fixed this problem is more reliable because we do not change
MetricsUpdater at all, we only add a key for jvm to support existing
functionality.
There is another point for this fix, we discussed with [Denis
Mekhanikov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dmekhanikov]
and agreed that this fix is critical and it would be nice to have it in the
upcoming 2.9 release, given the fact that this fix was properly tested on a
fork.
Therefore, to sum up, I would propose the following: merge this fix and
cherry-pick to 2.9 release, and create another ticket for improvements for
retrieving properties using reflection and for MetricsUpdater.
What do you think [Ivan
Bessonov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ibessonov]
, [Denis
Mekhanikov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dmekhanikov]
?
was (Author: maliev):
Hi [Ivan
Bessonov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ibessonov]!
Thank you for your comments!
On the one hand I agree with you that your ideas might be more correct in terms
of simplification of the existing code, namely MetricsUpdater. On the other
hand the way we fixed this problem is more reliable because we do not change
MetricsUpdater at all, we only add a key for jvm to support existing
functionality.
There is another point for this fix, we discussed with [Denis
Mekhanikov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dmekhanikov]
and agreed that this fix is critical fix and it would be nice to have it in
the upcoming 2.9 release, given the fact that this fix was properly tested on a
fork.
Therefore, to sum up, I would propose the following: merge this fix and
cherry-pick to 2.9 release, and create another ticket for improvements for
retrieving properties using reflection and for MetricsUpdater.
What do you think [Ivan
Bessonov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ibessonov]
, [Denis
Mekhanikov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dmekhanikov]
?
> CpuLoad metric return -1 under Java 11
> --
>
> Key: IGNITE-13306
> URL: https://issues.apache.org/jira/browse/IGNITE-13306
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8.1
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Fix For: 2.9
>
>
> Start cluster under Java 11.
> Observed:
> CpuLoad metric will return -1
> Expected:
> Real CpuLoad.
> We investigated this issue and found that under Java 11 code failed with
> following trace:
> {code:java}
> class org.apache.ignite.IgniteException: Failed to get property value
> [property=processCpuTime,
> obj=com.sun.management.internal.OperatingSystemImpl@1dd92fe2] at
> org.apache.ignite.internal.util.IgniteUtils.property(IgniteUtils.java:8306)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$MetricsUpdater.getCpuLoad(GridDiscoveryManager.java:3131)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$MetricsUpdater.run(GridDiscoveryManager.java:3093)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$CancelableTask.onTimeout(GridTimeoutProcessor.java:364)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:233)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) at
> java.base/java.lang.Thread.run(Thread.java:834) Caused by:
> java.lang.reflect.InaccessibleObjectException: Unable to make public long
> com.sun.management.internal.OperatingSystemImpl.getProcessCpuTime()
> accessible: module jdk.management does not "opens
> com.sun.management.internal" to unnamed module @35fb3008 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280)
> at java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:198)
> at java.base/java.lang.reflect.Method.setAccessible(Method.java:192) at
> org.apache.ignite.internal.util.IgniteUtils.property(IgniteUtils.java:8297)
> ... 6 more
> {code}
> Under Java 8 metric has expected value.
>
> Solution:
>
[jira] [Comment Edited] (IGNITE-13306) CpuLoad metric return -1 under Java 11
[
https://issues.apache.org/jira/browse/IGNITE-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166695#comment-17166695
]
Mirza Aliev edited comment on IGNITE-13306 at 7/29/20, 6:51 AM:
Hi [Ivan
Bessonov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ibessonov]!
Thank you for your comments!
On the one hand I agree with you that your ideas might be more correct in terms
of simplification of the existing code, namely MetricsUpdater. On the other
hand the way we fixed this problem is more reliable because we do not change
MetricsUpdater at all, we only add a key for jvm to support existing
functionality.
There is another point for this fix, we discussed with [Denis
Mekhanikov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dmekhanikov]
and agreed that this fix is critical fix and it would be nice to have it in
the upcoming 2.9 release, given the fact that this fix was properly tested on a
fork.
Therefore, to sum up, I would propose the following: merge this fix and
cherry-pick to 2.9 release, and create another ticket for improvements for
retrieving properties using reflection and for MetricsUpdater.
What do you think [Ivan
Bessonov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ibessonov]
, [Denis
Mekhanikov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dmekhanikov]
?
was (Author: maliev):
Hi [Ivan
Bessonov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ibessonov]!
Thank you for your comments!
On the one hand I agree with you that your ideas might be more correct in terms
of simplification of the existing code, namely MetricsUpdater. On the other
hand the way we fixed this problem is more reliable because we do not change
MetricsUpdater at all, we only add a key for jvm to support existing
functionality.
There is another point for this fix, we discussed with [Denis
Mekhanikov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dmekhanikov]
and agreed that this fix is critical for Control Center and it would be nice
to have it in the upcoming 2.9 release, given the fact that this fix was
properly tested on a fork.
Therefore, to sum up, I would propose the following: merge this fix and
cherry-pick to 2.9 release, and create another ticket for improvements for
retrieving properties using reflection and for MetricsUpdater.
What do you think [Ivan
Bessonov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ibessonov]
, [Denis
Mekhanikov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dmekhanikov]
?
> CpuLoad metric return -1 under Java 11
> --
>
> Key: IGNITE-13306
> URL: https://issues.apache.org/jira/browse/IGNITE-13306
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8.1
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Fix For: 2.9
>
>
> Start cluster under Java 11.
> Observed:
> CpuLoad metric will return -1
> Expected:
> Real CpuLoad.
> We investigated this issue and found that under Java 11 code failed with
> following trace:
> {code:java}
> class org.apache.ignite.IgniteException: Failed to get property value
> [property=processCpuTime,
> obj=com.sun.management.internal.OperatingSystemImpl@1dd92fe2] at
> org.apache.ignite.internal.util.IgniteUtils.property(IgniteUtils.java:8306)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$MetricsUpdater.getCpuLoad(GridDiscoveryManager.java:3131)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$MetricsUpdater.run(GridDiscoveryManager.java:3093)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$CancelableTask.onTimeout(GridTimeoutProcessor.java:364)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:233)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) at
> java.base/java.lang.Thread.run(Thread.java:834) Caused by:
> java.lang.reflect.InaccessibleObjectException: Unable to make public long
> com.sun.management.internal.OperatingSystemImpl.getProcessCpuTime()
> accessible: module jdk.management does not "opens
> com.sun.management.internal" to unnamed module @35fb3008 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280)
> at java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:198)
> at java.base/java.lang.reflect.Method.setAccessible(Method.java:192) at
> org.apache.ignite.internal.util.IgniteUtils.property(IgniteUtils.java:8297)
> ... 6 more
> {code}
> Under Java 8 metric has expected value.
[jira] [Commented] (IGNITE-13299) Flacky GridServiceDeployClusterReadOnlyModeTest and all including tests.
[ https://issues.apache.org/jira/browse/IGNITE-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166915#comment-17166915 ] Stanilovsky Evgeny commented on IGNITE-13299: - [~alex_pl] can you make review or suggest who can make it plz? > Flacky GridServiceDeployClusterReadOnlyModeTest and all including tests. > > > Key: IGNITE-13299 > URL: https://issues.apache.org/jira/browse/IGNITE-13299 > Project: Ignite > Issue Type: Bug > Components: managed services >Affects Versions: 2.8.1 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > > Starting > GridServiceDeployClusterReadOnlyModeTest#testDeployClusterSingletonAllowed > until failure and catch assertion on 200 iteration. This failure is due > incorrect assumption that if service already deployed > org.apache.ignite.services.Service#execute would be called before returning > from deployment would be happened. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13299) Flacky GridServiceDeployClusterReadOnlyModeTest and all including tests.
[
https://issues.apache.org/jira/browse/IGNITE-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166913#comment-17166913
]
Ignite TC Bot commented on IGNITE-13299:
{panel:title=Branch: [pull/8085/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8085/head] Base: [master] : New Tests
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid (legacy mode){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5493608]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=f6a5bcd6-15d6-421c-b239-c2fd36d1a204, topVer=0,
msgTemplate=null, span=null, nodeId8=db1d2911, msg=, type=NODE_JOINED,
tstamp=1595856340811], val2=AffinityTopologyVersion [topVer=774183791821004692,
minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=f6a5bcd6-15d6-421c-b239-c2fd36d1a204, topVer=0,
msgTemplate=null, span=null, nodeId8=db1d2911, msg=, type=NODE_JOINED,
tstamp=1595856340811], val2=AffinityTopologyVersion [topVer=774183791821004692,
minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=4e72d709371-c10f21f4-5e77-4ad5-a46c-3b5221a0d803, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=c71185f4-6b1f-4466-a153-95d2be1c2b9b, topVer=0, msgTemplate=null,
span=null, nodeId8=c71185f4, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1595856340811]], val2=AffinityTopologyVersion
[topVer=4769396777681838822, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=4e72d709371-c10f21f4-5e77-4ad5-a46c-3b5221a0d803, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=c71185f4-6b1f-4466-a153-95d2be1c2b9b, topVer=0, msgTemplate=null,
span=null, nodeId8=c71185f4, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1595856340811]], val2=AffinityTopologyVersion
[topVer=4769396777681838822, minorTopVer=0]]] - PASSED{color}
{color:#8b}Service Grid{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5493607]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=a4153709371-9ba71d6b-01fe-47e6-964a-3007b98b0f7c, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=d3d4a4fb-c344-41ec-83d2-481a289e2edf, topVer=0, msgTemplate=null,
span=null, nodeId8=d3d4a4fb, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1595856343366]], val2=AffinityTopologyVersion
[topVer=-853300981416305, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=356f1811-ee98-4e20-ac76-7ebd411e2eb7, topVer=0,
msgTemplate=null, span=null, nodeId8=c11a3d30, msg=, type=NODE_JOINED,
tstamp=1595856343366], val2=AffinityTopologyVersion
[topVer=-3688845892644530662, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=356f1811-ee98-4e20-ac76-7ebd411e2eb7, topVer=0,
msgTemplate=null, span=null, nodeId8=c11a3d30, msg=, type=NODE_JOINED,
tstamp=1595856343366], val2=AffinityTopologyVersion
[topVer=-3688845892644530662, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=a4153709371-9ba71d6b-01fe-47e6-964a-3007b98b0f7c, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=d3d4a4fb-c344-41ec-83d2-481a289e2edf, topVer=0, msgTemplate=null,
span=null, nodeId8=d3d4a4fb, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1595856343366]], val2=AffinityTopologyVersion
[topVer=-853300981416305, minorTopVer=0]]] - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5493749buildTypeId=IgniteTests24Java8_RunAll]
> Flacky GridServiceDeployClusterReadOnlyModeTest and all including tests.
>
>
> Key: IGNITE-13299
> URL:
[jira] [Commented] (IGNITE-13306) CpuLoad metric return -1 under Java 11
[
https://issues.apache.org/jira/browse/IGNITE-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166905#comment-17166905
]
Ivan Bessonov commented on IGNITE-13306:
[~maliev] I'm fine with the current change if it's urgent and if we'll fix it
properly in the future.
> CpuLoad metric return -1 under Java 11
> --
>
> Key: IGNITE-13306
> URL: https://issues.apache.org/jira/browse/IGNITE-13306
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8.1
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Fix For: 2.9
>
>
> Start cluster under Java 11.
> Observed:
> CpuLoad metric will return -1
> Expected:
> Real CpuLoad.
> We investigated this issue and found that under Java 11 code failed with
> following trace:
> {code:java}
> class org.apache.ignite.IgniteException: Failed to get property value
> [property=processCpuTime,
> obj=com.sun.management.internal.OperatingSystemImpl@1dd92fe2] at
> org.apache.ignite.internal.util.IgniteUtils.property(IgniteUtils.java:8306)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$MetricsUpdater.getCpuLoad(GridDiscoveryManager.java:3131)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$MetricsUpdater.run(GridDiscoveryManager.java:3093)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$CancelableTask.onTimeout(GridTimeoutProcessor.java:364)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:233)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) at
> java.base/java.lang.Thread.run(Thread.java:834) Caused by:
> java.lang.reflect.InaccessibleObjectException: Unable to make public long
> com.sun.management.internal.OperatingSystemImpl.getProcessCpuTime()
> accessible: module jdk.management does not "opens
> com.sun.management.internal" to unnamed module @35fb3008 at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280)
> at java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:198)
> at java.base/java.lang.reflect.Method.setAccessible(Method.java:192) at
> org.apache.ignite.internal.util.IgniteUtils.property(IgniteUtils.java:8297)
> ... 6 more
> {code}
> Under Java 8 metric has expected value.
>
> Solution:
> The behaviour is expected because in Java 11 the CPU load metrics is moved to
> JDK internal module which is not accessible by default. Adding the following
> line to the jvm in which Ignite node is started should solve the issue:
> {noformat}
> --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13280) Improper index usage, fields enumeration not used with pk index creation.
[
https://issues.apache.org/jira/browse/IGNITE-13280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166904#comment-17166904
]
Stanilovsky Evgeny commented on IGNITE-13280:
-
[~tledkov-gridgain] is it appropriate fix ?
> Improper index usage, fields enumeration not used with pk index creation.
> -
>
> Key: IGNITE-13280
> URL: https://issues.apache.org/jira/browse/IGNITE-13280
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.8.1
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> For example:
> {code:java}
> CREATE TABLE PUBLIC.TEST_TABLE (FIRST_NAME VARCHAR, LAST_NAME VARCHAR,
> ADDRESS VARCHAR, LANG VARCHAR, CONSTRAINT PK_PERSON PRIMARY KEY (FIRST_NAME,
> LAST_NAME));
> CREATE INDEX "idx2" ON PUBLIC.TEST_TABLE (LANG, ADDRESS);
> {code}
> and further explain:
> {code:java}
> SELECT
> "__Z0"."FIRST_NAME" AS "__C0_0",
> "__Z0"."LAST_NAME" AS "__C0_1",
> "__Z0"."ADDRESS" AS "__C0_2",
> "__Z0"."LANG" AS "__C0_3"
> FROM "PUBLIC"."TEST_TABLE" "__Z0"
> /* PUBLIC.IDX2: ADDRESS > 0 */
> WHERE "__Z0"."ADDRESS" > 0
> {code}
> this is erroneous to use "idx2" here, because first index field LANG not
> equals to predicate ADDRESS.
> Looks like this bug brings this ticket [1]
> [1] https://issues.apache.org/jira/browse/IGNITE-10217
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
