[jira] [Commented] (IGNITE-12835) Thin client: compute support
[ https://issues.apache.org/jira/browse/IGNITE-12835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076925#comment-17076925 ] Dmitriy Sorokin commented on IGNITE-12835: -- [~alex_pl], I reviewed your patch, LGTM, thanks for contribution! > Thin client: compute support > > > Key: IGNITE-12835 > URL: https://issues.apache.org/jira/browse/IGNITE-12835 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: iep-42 > Time Spent: 2h 10m > Remaining Estimate: 0h > > Add compute grid functionality to thin clients. > As a first step execution of task by task name should be added. > Implement a compute facade in java thin client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-7153) Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for values > 8kb
[
https://issues.apache.org/jira/browse/IGNITE-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076518#comment-17076518
]
Ignite TC Bot commented on IGNITE-7153:
---
{panel:title=Branch: [pull/5044/head] Base: [master] : Possible Blockers
(244)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform C++ (Linux)*{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5197063]]
{color:#d04437}PDS (Indexing){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5197102]]
* IgnitePdsWithIndexingCoreTestSuite: TestSuite$1.warning - History for base
branch is absent.
* IgnitePdsWithIndexingTestSuite: TestSuite$1.warning - History for base branch
is absent.
{color:#d04437}Cache 6{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5197092]]
* IgniteCacheTestSuite6: TestSuite$1.warning - History for base branch is
absent.
{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5197062]]
* ZookeeperDiscoverySpiTestSuite2: TestSuite$1.warning - History for base
branch is absent.
{color:#d04437}Cache 5{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5197091]]
* IgniteCacheWithIndexingTestSuite: TestSuite$1.warning - History for base
branch is absent.
* IgniteCacheTestSuite5: TestSuite$1.warning - History for base branch is
absent.
{color:#d04437}Cache 7{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5197093]]
* IgniteCacheWithIndexingAndPersistenceTestSuite: TestSuite$1.warning - History
for base branch is absent.
* IgniteCacheTestSuite7: TestSuite$1.warning - History for base branch is
absent.
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5197061]]
* ZookeeperDiscoverySpiTestSuite1: TestSuite$1.warning - History for base
branch is absent.
{color:#d04437}SPI{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5197054]]
* IgniteSpiTestSuite: TestSuite$1.warning - History for base branch is absent.
{color:#d04437}Basic 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5197066]]
* org.apache.ignite.testsuites.IgniteBasicTestSuite.initializationError -
History for base branch is absent.
{color:#d04437}Cache (Expiry Policy){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5197077]]
* IgniteCacheExpiryPolicyTestSuite: TestSuite$1.warning - History for base
branch is absent.
{color:#d04437}Examples{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5197035]]
* IgniteExamplesSparkSelfTestSuite: TestSuite$1.warning - History for base
branch is absent.
{color:#d04437}Scala (Examples){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5197059]]
*
org.apache.ignite.scalar.testsuites.ScalarExamplesSelfTestSuite.initializationError
- History for base branch is absent.
{color:#d04437}Cache 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5197088]]
* IgniteCacheTestSuite2: TestSuite$1.warning - History for base branch is
absent.
{color:#d04437}Platform .NET{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=5197108]]
* exe: CacheQueriesTestSimpleName.TestScanQuery(False) - Test has low fail rate
in base branch 0,0% and is not flaky
* exe: CacheAbstractTest.TestWithExpiryPolicy - Test has low fail rate in base
branch 0,0% and is not flaky
* exe: CacheAbstractTest.TestWithExpiryPolicy - Test has low fail rate in base
branch 0,0% and is not flaky
{color:#d04437}Queries 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5197114]]
* IgniteBinaryCacheQueryTestSuite: TestSuite$1.warning - History for base
branch is absent.
{color:#d04437}Start Nodes{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5197053]]
*
org.apache.ignite.internal.IgniteStartStopRestartTestSuite.initializationError
- History for base branch is absent.
{color:#d04437}Streamers{color} [[tests
8|https://ci.ignite.apache.org/viewLog.html?buildId=5197052]]
* IgniteStreamSelfTestSuite: TestSuite$1.warning - History for base branch is
absent.
* IgniteJmsStreamerTestSuite: TestSuite$1.warning - History for base branch is
absent.
* IgniteKafkaStreamerSelfTestSuite: TestSuite$1.warning - History for base
branch is absent.
* IgniteZeroMqStreamerTestSuite: TestSuite$1.warning - History for base branch
is absent.
* IgniteMqttStreamerTestSuite: TestSuite$1.warning - History for base branch is
absent.
* IgniteTwitterStreamerTestSuite: TestSuite$1.warning - History for base branch
is absent.
* IgniteStormStreamerSelfTestSuite: TestSuite$1.warning - History for base
branch is absent.
* IgniteCamelStreamerTestSuite: TestSuite$1.warning - History for base branch
is absent.
{color:#d04437}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildI
[jira] [Commented] (IGNITE-12828) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-12828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076471#comment-17076471
]
Amelchev Nikita commented on IGNITE-12828:
--
[~PetrovMikhail], LGTM.
> Intermittent [Failed to notify direct custom event listener] exception on
> node shutdown
> ---
>
> Key: IGNITE-12828
> URL: https://issues.apache.org/jira/browse/IGNITE-12828
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Alexey Kukushkin
>Assignee: PetrovMikhail
>Priority: Major
> Labels: sbcf
> Fix For: 2.9
>
> Attachments: ignite-12828-vs-2.8.patch
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> +*Reproducer*+:
> Run a server node
> Run a client node that:
> * Creates cache "cache1"
> * Deploys a grid service that starts a continuous query against "cache1" in
> method init()
> * Leaves the cluster
> +*Actual result*+
> Intermittent exception in the client node:
> {noformat}
> [16:54:38,758][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@63ae71a9,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@594bf5b8,
> cacheName=CALC_REQUESTS, rmtFilter=null, rmtFilterDep=null, internal=false,
> notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
> taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=true,
> ackBuf=null, cacheId=-1608655250, initTopVer=null, nodeLeft=false,
> ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=true,
> routineId=021dd2ce-3d8a-41c1-a4d0-b625ea1284f4]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:110)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:202)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:193)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:722)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:601)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2683)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2721)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at java.lang.Thread.run(Thread.java:745)
> [16:54:39,725][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@7462c96c,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@6451dd70,
> cacheName=DISTRIBUTED_REQUESTS, rmtFilter=null, rmtFilterDep=null,
> internal=false, notifyExisting=false, oldValRequired=true, sync=false,
> ignoreExpired=true, taskHash=0, skipPrimaryCheck=false, locOnly=false,
> keepBinary=true, ackBuf=null, cacheId=1419803136, initTopVer=null,
> nodeLeft=false, ignoreClsNotFound=false, nodeId=null, routineId=null],
> bufSize=1, interval=0, autoUnsubscribe=true], keepBinary=true,
> routineId=1fca5f04-d220-49ac-850a-0d4527e22eef]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
> at
[jira] [Updated] (IGNITE-12828) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-12828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-12828:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Intermittent [Failed to notify direct custom event listener] exception on
> node shutdown
> ---
>
> Key: IGNITE-12828
> URL: https://issues.apache.org/jira/browse/IGNITE-12828
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Alexey Kukushkin
>Assignee: PetrovMikhail
>Priority: Major
> Labels: sbcf
> Fix For: 2.9
>
> Attachments: ignite-12828-vs-2.8.patch
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> +*Reproducer*+:
> Run a server node
> Run a client node that:
> * Creates cache "cache1"
> * Deploys a grid service that starts a continuous query against "cache1" in
> method init()
> * Leaves the cluster
> +*Actual result*+
> Intermittent exception in the client node:
> {noformat}
> [16:54:38,758][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@63ae71a9,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@594bf5b8,
> cacheName=CALC_REQUESTS, rmtFilter=null, rmtFilterDep=null, internal=false,
> notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
> taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=true,
> ackBuf=null, cacheId=-1608655250, initTopVer=null, nodeLeft=false,
> ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=true,
> routineId=021dd2ce-3d8a-41c1-a4d0-b625ea1284f4]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:110)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:202)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:193)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:722)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:601)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2683)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2721)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at java.lang.Thread.run(Thread.java:745)
> [16:54:39,725][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@7462c96c,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@6451dd70,
> cacheName=DISTRIBUTED_REQUESTS, rmtFilter=null, rmtFilterDep=null,
> internal=false, notifyExisting=false, oldValRequired=true, sync=false,
> ignoreExpired=true, taskHash=0, skipPrimaryCheck=false, locOnly=false,
> keepBinary=true, ackBuf=null, cacheId=1419803136, initTopVer=null,
> nodeLeft=false, ignoreClsNotFound=false, nodeId=null, routineId=null],
> bufSize=1, interval=0, autoUnsubscribe=true], keepBinary=true,
> routineId=1fca5f04-d220-49ac-850a-0d4527e22eef]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
> at
> org.apache.ignit
[jira] [Updated] (IGNITE-12828) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-12828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-12828:
-
Fix Version/s: 2.9
> Intermittent [Failed to notify direct custom event listener] exception on
> node shutdown
> ---
>
> Key: IGNITE-12828
> URL: https://issues.apache.org/jira/browse/IGNITE-12828
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Alexey Kukushkin
>Assignee: PetrovMikhail
>Priority: Major
> Labels: sbcf
> Fix For: 2.9
>
> Attachments: ignite-12828-vs-2.8.patch
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> +*Reproducer*+:
> Run a server node
> Run a client node that:
> * Creates cache "cache1"
> * Deploys a grid service that starts a continuous query against "cache1" in
> method init()
> * Leaves the cluster
> +*Actual result*+
> Intermittent exception in the client node:
> {noformat}
> [16:54:38,758][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@63ae71a9,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@594bf5b8,
> cacheName=CALC_REQUESTS, rmtFilter=null, rmtFilterDep=null, internal=false,
> notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
> taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=true,
> ackBuf=null, cacheId=-1608655250, initTopVer=null, nodeLeft=false,
> ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=true,
> routineId=021dd2ce-3d8a-41c1-a4d0-b625ea1284f4]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:110)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:202)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:193)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:722)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:601)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2683)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2721)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at java.lang.Thread.run(Thread.java:745)
> [16:54:39,725][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@7462c96c,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@6451dd70,
> cacheName=DISTRIBUTED_REQUESTS, rmtFilter=null, rmtFilterDep=null,
> internal=false, notifyExisting=false, oldValRequired=true, sync=false,
> ignoreExpired=true, taskHash=0, skipPrimaryCheck=false, locOnly=false,
> keepBinary=true, ackBuf=null, cacheId=1419803136, initTopVer=null,
> nodeLeft=false, ignoreClsNotFound=false, nodeId=null, routineId=null],
> bufSize=1, interval=0, autoUnsubscribe=true], keepBinary=true,
> routineId=1fca5f04-d220-49ac-850a-0d4527e22eef]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
> at
> org.apache.ignite.internal.processors.continuous.GridCont
[jira] [Commented] (IGNITE-12828) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-12828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076466#comment-17076466
]
PetrovMikhail commented on IGNITE-12828:
There is another case when the mentioned NPE can occur. It is described by
https://issues.apache.org/jira/browse/IGNITE-12865.
> Intermittent [Failed to notify direct custom event listener] exception on
> node shutdown
> ---
>
> Key: IGNITE-12828
> URL: https://issues.apache.org/jira/browse/IGNITE-12828
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Alexey Kukushkin
>Assignee: PetrovMikhail
>Priority: Major
> Labels: sbcf
> Attachments: ignite-12828-vs-2.8.patch
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> +*Reproducer*+:
> Run a server node
> Run a client node that:
> * Creates cache "cache1"
> * Deploys a grid service that starts a continuous query against "cache1" in
> method init()
> * Leaves the cluster
> +*Actual result*+
> Intermittent exception in the client node:
> {noformat}
> [16:54:38,758][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@63ae71a9,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@594bf5b8,
> cacheName=CALC_REQUESTS, rmtFilter=null, rmtFilterDep=null, internal=false,
> notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
> taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=true,
> ackBuf=null, cacheId=-1608655250, initTopVer=null, nodeLeft=false,
> ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=true,
> routineId=021dd2ce-3d8a-41c1-a4d0-b625ea1284f4]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:110)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:202)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:193)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:722)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:601)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2683)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2721)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at java.lang.Thread.run(Thread.java:745)
> [16:54:39,725][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@7462c96c,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@6451dd70,
> cacheName=DISTRIBUTED_REQUESTS, rmtFilter=null, rmtFilterDep=null,
> internal=false, notifyExisting=false, oldValRequired=true, sync=false,
> ignoreExpired=true, taskHash=0, skipPrimaryCheck=false, locOnly=false,
> keepBinary=true, ackBuf=null, cacheId=1419803136, initTopVer=null,
> nodeLeft=false, ignoreClsNotFound=false, nodeId=null, routineId=null],
> bufSize=1, interval=0, autoUnsubscribe=true], keepBinary=true,
> routineId=1fca5f04-d220-49ac-850a-0d4527e22eef]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscovery
[jira] [Commented] (IGNITE-12828) Intermittent [Failed to notify direct custom event listener] exception on node shutdown
[
https://issues.apache.org/jira/browse/IGNITE-12828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076463#comment-17076463
]
Ignite TC Bot commented on IGNITE-12828:
{panel:title=Branch: [pull/7620/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5193245&buildTypeId=IgniteTests24Java8_RunAll]
> Intermittent [Failed to notify direct custom event listener] exception on
> node shutdown
> ---
>
> Key: IGNITE-12828
> URL: https://issues.apache.org/jira/browse/IGNITE-12828
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Alexey Kukushkin
>Assignee: PetrovMikhail
>Priority: Major
> Labels: sbcf
> Attachments: ignite-12828-vs-2.8.patch
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> +*Reproducer*+:
> Run a server node
> Run a client node that:
> * Creates cache "cache1"
> * Deploys a grid service that starts a continuous query against "cache1" in
> method init()
> * Leaves the cluster
> +*Actual result*+
> Intermittent exception in the client node:
> {noformat}
> [16:54:38,758][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@63ae71a9,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@594bf5b8,
> cacheName=CALC_REQUESTS, rmtFilter=null, rmtFilterDep=null, internal=false,
> notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
> taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=true,
> ackBuf=null, cacheId=-1608655250, initTopVer=null, nodeLeft=false,
> ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=true,
> routineId=021dd2ce-3d8a-41c1-a4d0-b625ea1284f4]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:82)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:96)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1424)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:110)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:202)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:193)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:722)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:601)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2683)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2721)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at java.lang.Thread.run(Thread.java:745)
> [16:54:39,725][SEVERE][disco-notifier-worker-#43%CashFlowCluster_16b67e98563f4cfbac95ae055a00e67f%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=sbt.cashflow.grid.services.cachefactory.ignite.NodeAttributeFilter@7462c96c,
> clsName=null, depInfo=null, hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@6451dd70,
> cacheName=DISTRIBUTED_REQUESTS, rmtFilter=null, rmtFilterDep=null,
> internal=false, notifyExisting=false, oldValRequired=true, sync=false,
> ignoreExpired=true, taskHash=0, skipPrimaryCheck=false, locOnly=false,
> keepBinary=true, ackBuf=null, cacheId=1419803136, initTopVer=null,
> nodeLeft=false, ignoreClsNotFound=false, nodeId=null, routineId=null],
> bufSize=1, interval=0, autoUnsubscribe=true], keepBinary=true,
> routineId=1fca5f04-d220-49ac-850a-0d4527e22eef]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscove
[jira] [Commented] (IGNITE-7153) Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for values > 8kb
[
https://issues.apache.org/jira/browse/IGNITE-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076446#comment-17076446
]
Dmitry Pavlov commented on IGNITE-7153:
---
Hi [~palnabarun] , [~mcfongtw]
I've triggered one more build on TC to double check. It is expected that too
old build is not available now. Let's check results tomorrow.
Sincerely,
Dmitriy Pavlov
> Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for
> values > 8kb
> ---
>
> Key: IGNITE-7153
> URL: https://issues.apache.org/jira/browse/IGNITE-7153
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.3
> Environment: Win, PHP 7, php_redis-3.1.1-7.0
>Reporter: Alexey Popov
>Assignee: Michael Fong
>Priority: Major
> Labels: redis
>
> Exception:
> {noformat}
> [15:03:23,690][SEVERE][grid-nio-worker-tcp-rest-0-#36][GridTcpRestProtocol]
> Failed to process selector key [ses=GridSelectorNioSessionImpl
> [worker=ByteBufferNioClientWorker [readBuf=java.nio.HeapByteBuffer[pos=28
> lim=8192 cap=8192], super=AbstractNioClientWorker [idx=0, bytesRcvd=0,
> bytesSent=0, bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker
> [name=grid-nio-worker-tcp-rest-0, igniteInstanceName=null, finished=false,
> hashCode=396395638, interrupted=false,
> runner=grid-nio-worker-tcp-rest-0-#36]]], writeBuf=null, readBuf=null,
> inRecovery=null, outRecovery=null, super=GridNioSessionImpl
> [locAddr=/127.0.0.1:6380, rmtAddr=/127.0.0.1:51794, createTime=1512734602674,
> closeTime=0, bytesSent=0, bytesRcvd=8192, bytesSent0=0, bytesRcvd0=8192,
> sndSchedTime=1512734602674, lastSndTime=1512734602674,
> lastRcvTime=1512734602674, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioCodecFilter [parser=GridTcpRestParser
> [jdkMarshaller=JdkMarshaller [], routerClient=false], directMode=false]],
> accepted=true]]]
> java.nio.BufferUnderflowException
> at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:107)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readArray(GridRedisProtocolParser.java:86)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:150)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:70)
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3392)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1096)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2272)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1717)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> [15:03:23,691][SEVERE][grid-nio-worker-tcp-rest-0-#36][GridTcpRestProtocol]
> Closing NIO session because of unhandled exception.
> class org.apache.ignite.internal.util.nio.GridNioException: null
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2296)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1717)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.nio.BufferUnderflowException
> at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:107)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readA
[jira] [Created] (IGNITE-12869) Management API to kill a node that started user provided tasks and queries
Sergei Ryzhov created IGNITE-12869: -- Summary: Management API to kill a node that started user provided tasks and queries Key: IGNITE-12869 URL: https://issues.apache.org/jira/browse/IGNITE-12869 Project: Ignite Issue Type: Improvement Reporter: Sergei Ryzhov Assignee: Sergei Ryzhov Ignite provides many API to deploy and execute user-provided code on the server nodes inside the same JVM as the Ignite process runs. Ignite has many APIs that allocate many resources on the server nodes, also. In case of some buggy code that consumes many system resources(CPU, RAM, flood network) or heavy query the whole cluster can become unstable. We should provide to the cluster administrator the ability to stop the node that started the task if it did not may be cancel. A new API should use the same identifier that is used in corresponding System View. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12863) NPE while initializing Cassandra Store
[
https://issues.apache.org/jira/browse/IGNITE-12863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076390#comment-17076390
]
Alex Serbin commented on IGNITE-12863:
--
Thank you!
> NPE while initializing Cassandra Store
> --
>
> Key: IGNITE-12863
> URL: https://issues.apache.org/jira/browse/IGNITE-12863
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Alex Serbin
>Priority: Major
> Fix For: 2.8.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When trying to create a simple cache with Cassandra store and have value
> persistence strategy POJO, the following exception occurs
> {code:java}
> Caused by: java.lang.NullPointerException: nullCaused by:
> java.lang.NullPointerException: null at
> org.apache.ignite.cache.store.cassandra.persistence.PojoField.calculatedField(PojoField.java:155)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.prepareLoadStatements(PersistenceController.java:311)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.(PersistenceController.java:85)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStore.(CassandraCacheStore.java:106)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory.create(CassandraCacheStoreFactory.java:59)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory.create(CassandraCacheStoreFactory.java:34)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCacheContext(GridCacheProcessor.java:1199)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheContext(GridCacheProcessor.java:1995)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$null$6a5b31b9$1(GridCacheProcessor.java:1830)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$8(GridCacheProcessor.java:1754)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$926b6886$1(GridCacheProcessor.java:1827)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.util.IgniteUtils.lambda$null$1(IgniteUtils.java:11138)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266)
> ~[na:1.8.0_181] at java.util.concurrent.FutureTask.run(FutureTask.java)
> ~[na:1.8.0_181] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> ~[na:1.8.0_181] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> ~[na:1.8.0_181] at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_181]
> {code}
> It looks like that recent changes of IGNITE-1903 are leading to this issue,
> as we are starting to serialize {{CacheStoreFactory}}, which contains
> {{PojoFiled}}, which in its turn has transient field accessor. This leads to
> accessor being null after deserialization. Note, that this happens only when
> passing {{persistenceSettings}} (not {{persistenceSettingsBean}})
> Works fine with Ignite 2.7.6.
> Probably related to IGNITE-8500
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-7609) .NET: FieldsQueryCursor should expose data types too
[
https://issues.apache.org/jira/browse/IGNITE-7609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076384#comment-17076384
]
Pavel Tupitsyn commented on IGNITE-7609:
[~GuruStron] please see my comments on GitHub
> .NET: FieldsQueryCursor should expose data types too
>
>
> Key: IGNITE-7609
> URL: https://issues.apache.org/jira/browse/IGNITE-7609
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Sergey Stronchinskiy
>Priority: Major
> Labels: .NET
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> See IGNITE-7607 for Java, add same thing to .NET:
> {code}
> public interface IFieldsQueryCursor
> {
> ...
> IList FieldTypes
> }
> {code}
> T could be string or Type, needs investigation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12863) NPE while initializing Cassandra Store
[
https://issues.apache.org/jira/browse/IGNITE-12863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-12863:
-
Fix Version/s: 2.8.1
> NPE while initializing Cassandra Store
> --
>
> Key: IGNITE-12863
> URL: https://issues.apache.org/jira/browse/IGNITE-12863
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Alex Serbin
>Priority: Major
> Fix For: 2.8.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When trying to create a simple cache with Cassandra store and have value
> persistence strategy POJO, the following exception occurs
> {code:java}
> Caused by: java.lang.NullPointerException: nullCaused by:
> java.lang.NullPointerException: null at
> org.apache.ignite.cache.store.cassandra.persistence.PojoField.calculatedField(PojoField.java:155)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.prepareLoadStatements(PersistenceController.java:311)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.(PersistenceController.java:85)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStore.(CassandraCacheStore.java:106)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory.create(CassandraCacheStoreFactory.java:59)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory.create(CassandraCacheStoreFactory.java:34)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCacheContext(GridCacheProcessor.java:1199)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheContext(GridCacheProcessor.java:1995)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$null$6a5b31b9$1(GridCacheProcessor.java:1830)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$8(GridCacheProcessor.java:1754)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$926b6886$1(GridCacheProcessor.java:1827)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.util.IgniteUtils.lambda$null$1(IgniteUtils.java:11138)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266)
> ~[na:1.8.0_181] at java.util.concurrent.FutureTask.run(FutureTask.java)
> ~[na:1.8.0_181] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> ~[na:1.8.0_181] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> ~[na:1.8.0_181] at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_181]
> {code}
> It looks like that recent changes of IGNITE-1903 are leading to this issue,
> as we are starting to serialize {{CacheStoreFactory}}, which contains
> {{PojoFiled}}, which in its turn has transient field accessor. This leads to
> accessor being null after deserialization. Note, that this happens only when
> passing {{persistenceSettings}} (not {{persistenceSettingsBean}})
> Works fine with Ignite 2.7.6.
> Probably related to IGNITE-8500
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12779) Split implementations of Ignite and IgniteMXBean, make behavior of their active(boolean) different
[
https://issues.apache.org/jira/browse/IGNITE-12779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-12779:
--
Description:
To make cluster deactivation through JMX without sudden erasure of in-memory
data we should:
1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
an exception if deactivation would clear in-memory data.
2) Extract IgniteMXBean from IgniteKernal.
3) Add IgniteMXBean.state(String, boolean)
Additionally, as discussed, we should improve comments
{code:java}
/** If {@code true}, cluster deactivation will be forced. */
{code}
Let's add a link to a full description.
was:
To make cluster deactivation through JMX without sudden erasure of in-memory
data we should:
1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
an exception if deactivation would clear in-memory data.
2) Extract IgniteMXBean from IgniteKernal.
3) Add IgniteMXBean.state(String, boolean)
Additionally, as discussed, we should improve comments
{code:java}
/** If {@code true}, cluster deactivation will be forced. */
{code}
Let's add a link to a full description.
> Split implementations of Ignite and IgniteMXBean, make behavior of their
> active(boolean) different
> ---
>
> Key: IGNITE-12779
> URL: https://issues.apache.org/jira/browse/IGNITE-12779
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> To make cluster deactivation through JMX without sudden erasure of in-memory
> data we should:
> 1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
> an exception if deactivation would clear in-memory data.
> 2) Extract IgniteMXBean from IgniteKernal.
> 3) Add IgniteMXBean.state(String, boolean)
> Additionally, as discussed, we should improve comments
> {code:java}
> /** If {@code true}, cluster deactivation will be forced. */
> {code}
> Let's add a link to a full description.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12779) Split implementations of Ignite and IgniteMXBean, make behavior of their active(boolean) different
[
https://issues.apache.org/jira/browse/IGNITE-12779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-12779:
--
Description:
To make cluster deactivation through JMX without sudden erasure of in-memory
data we should:
1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
an exception if deactivation would clear in-memory data.
2) Extract IgniteMXBean from IgniteKernal.
3) Add IgniteMXBean.state(String, boolean)
Additionally, as discussed, we should improve comments
{code:java}
/** If {@code true}, cluster deactivation will be forced. */
{code}
Let's add a link to a full description.
was:
To make cluster deactivation through JMX without sudden erasure of in-memory
data we should:
1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
an exception if deactivation would clear in-memory data.
2) Extract IgniteMXBean from IgniteKernal.
3) Add IgniteMXBean.state(String, boolean)
Additionally, as discussed, improve comments
{code:java}
/** If {@code true}, cluster deactivation will be forced. */
{code}
- add a link to full description.
> Split implementations of Ignite and IgniteMXBean, make behavior of their
> active(boolean) different
> ---
>
> Key: IGNITE-12779
> URL: https://issues.apache.org/jira/browse/IGNITE-12779
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> To make cluster deactivation through JMX without sudden erasure of in-memory
> data we should:
> 1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
> an exception if deactivation would clear in-memory data.
> 2) Extract IgniteMXBean from IgniteKernal.
> 3) Add IgniteMXBean.state(String, boolean)
> Additionally, as discussed, we should improve comments
> {code:java}
> /** If {@code true}, cluster deactivation will be forced. */
> {code}
> Let's add a link to a full description.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12779) Split implementations of Ignite and IgniteMXBean, make behavior of their active(boolean) different
[
https://issues.apache.org/jira/browse/IGNITE-12779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-12779:
--
Description:
To make cluster deactivation through JMX without sudden erasure of in-memory
data we should:
1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
an exception if deactivation would clear in-memory data.
2) Extract IgniteMXBean from IgniteKernal.
3) Add IgniteMXBean.state(String, boolean)
Additionally, as discussed, improve comments
{code:java}
/** If {@code true}, cluster deactivation will be forced. */
{code}
- add a link to full description.
was:
To make cluster deactivation through JMX without sudden erasure of in-memory
data we should:
1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
an exception if deactivation would clear in-memory data.
2) Extract IgniteMXBean from IgniteKernal.
3) Add IgniteMXBean.state(String, boolean)
Additionally, as discussed, improve comments
_If {@code true}, cluster deactivation will be forced._ :
add a link to full description.
> Split implementations of Ignite and IgniteMXBean, make behavior of their
> active(boolean) different
> ---
>
> Key: IGNITE-12779
> URL: https://issues.apache.org/jira/browse/IGNITE-12779
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> To make cluster deactivation through JMX without sudden erasure of in-memory
> data we should:
> 1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
> an exception if deactivation would clear in-memory data.
> 2) Extract IgniteMXBean from IgniteKernal.
> 3) Add IgniteMXBean.state(String, boolean)
> Additionally, as discussed, improve comments
> {code:java}
> /** If {@code true}, cluster deactivation will be forced. */
> {code}
> - add a link to full description.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12779) Split implementations of Ignite and IgniteMXBean, make behavior of their active(boolean) different
[
https://issues.apache.org/jira/browse/IGNITE-12779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-12779:
--
Description:
To make cluster deactivation through JMX without sudden erasure of in-memory
data we should:
1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
an exception if deactivation would clear in-memory data.
2) Extract IgniteMXBean from IgniteKernal.
3) Add IgniteMXBean.state(String, boolean)
Additionally, as discussed, improve comments _"If {@code true}, cluster
deactivation will be forced."_ :
add a link to full description.
was:
To make cluster deactivation through JMX without sudden erasure of in-memory
data we should:
1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
an exception if deactivation would clear in-memory data.
2) Extract IgniteMXBean from IgniteKernal.
3) Add IgniteMXBean.state(String, boolean)
> Split implementations of Ignite and IgniteMXBean, make behavior of their
> active(boolean) different
> ---
>
> Key: IGNITE-12779
> URL: https://issues.apache.org/jira/browse/IGNITE-12779
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> To make cluster deactivation through JMX without sudden erasure of in-memory
> data we should:
> 1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
> an exception if deactivation would clear in-memory data.
> 2) Extract IgniteMXBean from IgniteKernal.
> 3) Add IgniteMXBean.state(String, boolean)
> Additionally, as discussed, improve comments _"If {@code true}, cluster
> deactivation will be forced."_ :
> add a link to full description.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12863) NPE while initializing Cassandra Store
[
https://issues.apache.org/jira/browse/IGNITE-12863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-12863:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> NPE while initializing Cassandra Store
> --
>
> Key: IGNITE-12863
> URL: https://issues.apache.org/jira/browse/IGNITE-12863
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Alex Serbin
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When trying to create a simple cache with Cassandra store and have value
> persistence strategy POJO, the following exception occurs
> {code:java}
> Caused by: java.lang.NullPointerException: nullCaused by:
> java.lang.NullPointerException: null at
> org.apache.ignite.cache.store.cassandra.persistence.PojoField.calculatedField(PojoField.java:155)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.prepareLoadStatements(PersistenceController.java:311)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.(PersistenceController.java:85)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStore.(CassandraCacheStore.java:106)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory.create(CassandraCacheStoreFactory.java:59)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory.create(CassandraCacheStoreFactory.java:34)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCacheContext(GridCacheProcessor.java:1199)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheContext(GridCacheProcessor.java:1995)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$null$6a5b31b9$1(GridCacheProcessor.java:1830)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$8(GridCacheProcessor.java:1754)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$926b6886$1(GridCacheProcessor.java:1827)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.util.IgniteUtils.lambda$null$1(IgniteUtils.java:11138)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266)
> ~[na:1.8.0_181] at java.util.concurrent.FutureTask.run(FutureTask.java)
> ~[na:1.8.0_181] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> ~[na:1.8.0_181] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> ~[na:1.8.0_181] at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_181]
> {code}
> It looks like that recent changes of IGNITE-1903 are leading to this issue,
> as we are starting to serialize {{CacheStoreFactory}}, which contains
> {{PojoFiled}}, which in its turn has transient field accessor. This leads to
> accessor being null after deserialization. Note, that this happens only when
> passing {{persistenceSettings}} (not {{persistenceSettingsBean}})
> Works fine with Ignite 2.7.6.
> Probably related to IGNITE-8500
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12779) Split implementations of Ignite and IgniteMXBean, make behavior of their active(boolean) different
[
https://issues.apache.org/jira/browse/IGNITE-12779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-12779:
--
Description:
To make cluster deactivation through JMX without sudden erasure of in-memory
data we should:
1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
an exception if deactivation would clear in-memory data.
2) Extract IgniteMXBean from IgniteKernal.
3) Add IgniteMXBean.state(String, boolean)
Additionally, as discussed, improve comments
_If {@code true}, cluster deactivation will be forced._ :
add a link to full description.
was:
To make cluster deactivation through JMX without sudden erasure of in-memory
data we should:
1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
an exception if deactivation would clear in-memory data.
2) Extract IgniteMXBean from IgniteKernal.
3) Add IgniteMXBean.state(String, boolean)
Additionally, as discussed, improve comments _"If {@code true}, cluster
deactivation will be forced."_ :
add a link to full description.
> Split implementations of Ignite and IgniteMXBean, make behavior of their
> active(boolean) different
> ---
>
> Key: IGNITE-12779
> URL: https://issues.apache.org/jira/browse/IGNITE-12779
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> To make cluster deactivation through JMX without sudden erasure of in-memory
> data we should:
> 1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
> an exception if deactivation would clear in-memory data.
> 2) Extract IgniteMXBean from IgniteKernal.
> 3) Add IgniteMXBean.state(String, boolean)
> Additionally, as discussed, improve comments
> _If {@code true}, cluster deactivation will be forced._ :
> add a link to full description.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12863) NPE while initializing Cassandra Store
[
https://issues.apache.org/jira/browse/IGNITE-12863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076375#comment-17076375
]
Nikolay Izhikov commented on IGNITE-12863:
--
[~zstan] I'm ok to include this patch to 2.8.1
> NPE while initializing Cassandra Store
> --
>
> Key: IGNITE-12863
> URL: https://issues.apache.org/jira/browse/IGNITE-12863
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Alex Serbin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When trying to create a simple cache with Cassandra store and have value
> persistence strategy POJO, the following exception occurs
> {code:java}
> Caused by: java.lang.NullPointerException: nullCaused by:
> java.lang.NullPointerException: null at
> org.apache.ignite.cache.store.cassandra.persistence.PojoField.calculatedField(PojoField.java:155)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.prepareLoadStatements(PersistenceController.java:311)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.(PersistenceController.java:85)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStore.(CassandraCacheStore.java:106)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory.create(CassandraCacheStoreFactory.java:59)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory.create(CassandraCacheStoreFactory.java:34)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCacheContext(GridCacheProcessor.java:1199)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheContext(GridCacheProcessor.java:1995)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$null$6a5b31b9$1(GridCacheProcessor.java:1830)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$8(GridCacheProcessor.java:1754)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$926b6886$1(GridCacheProcessor.java:1827)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.util.IgniteUtils.lambda$null$1(IgniteUtils.java:11138)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266)
> ~[na:1.8.0_181] at java.util.concurrent.FutureTask.run(FutureTask.java)
> ~[na:1.8.0_181] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> ~[na:1.8.0_181] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> ~[na:1.8.0_181] at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_181]
> {code}
> It looks like that recent changes of IGNITE-1903 are leading to this issue,
> as we are starting to serialize {{CacheStoreFactory}}, which contains
> {{PojoFiled}}, which in its turn has transient field accessor. This leads to
> accessor being null after deserialization. Note, that this happens only when
> passing {{persistenceSettings}} (not {{persistenceSettingsBean}})
> Works fine with Ignite 2.7.6.
> Probably related to IGNITE-8500
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-7609) .NET: FieldsQueryCursor should expose data types too
[
https://issues.apache.org/jira/browse/IGNITE-7609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076367#comment-17076367
]
Sergey Stronchinskiy commented on IGNITE-7609:
--
[~ptupitsyn], Please take a look.
> .NET: FieldsQueryCursor should expose data types too
>
>
> Key: IGNITE-7609
> URL: https://issues.apache.org/jira/browse/IGNITE-7609
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Sergey Stronchinskiy
>Priority: Major
> Labels: .NET
> Time Spent: 10m
> Remaining Estimate: 0h
>
> See IGNITE-7607 for Java, add same thing to .NET:
> {code}
> public interface IFieldsQueryCursor
> {
> ...
> IList FieldTypes
> }
> {code}
> T could be string or Type, needs investigation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12805) Node fails to restart
[
https://issues.apache.org/jira/browse/IGNITE-12805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-12805:
-
Fix Version/s: 2.8.1
> Node fails to restart
> -
>
> Key: IGNITE-12805
> URL: https://issues.apache.org/jira/browse/IGNITE-12805
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.8
>Reporter: Sarunas Valaskevicius
>Assignee: Vyacheslav Koptilin
>Priority: Blocker
> Fix For: 2.8.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 1. nodes have default persistence false, but there is a cache region with
> persistence on.
> 2. a cluster starts ok with ignite data directory clean
> 3. but when the nodes are restarted, they fail and can never join the cluster
> again:
>
> {code:java}
> 12:352020-03-19_13:34:30.273 [main-0] ERROR
> o.a.ignite.internal.IgniteKernal:137 <> - Exception during start processors,
> node will be stopped and close connections
> java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.affinityNode(GridCacheUtils.java:1374)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$CachePredicate.dataNode(GridDiscoveryManager.java:3205)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.cacheAffinityNode(GridDiscoveryManager.java:1894)
> at
> org.apache.ignite.internal.processors.cache.ValidationOnNodeJoinUtils.validate(ValidationOnNodeJoinUtils.java:330)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCacheContext(GridCacheProcessor.java:1201)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheInRecoveryMode(GridCacheProcessor.java:2291)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.access$1700(GridCacheProcessor.java:202)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.afterBinaryMemoryRestore(GridCacheProcessor.java:5387)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreBinaryMemory(GridCacheDatabaseSharedManager.java:1075)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.startMemoryRestore(GridCacheDatabaseSharedManager.java:2068)
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1254)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:637)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12802) Move checkpoint state fields to CheckpointProgress
[
https://issues.apache.org/jira/browse/IGNITE-12802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076336#comment-17076336
]
Alexey Goncharuk commented on IGNITE-12802:
---
Merged to master.
> Move checkpoint state fields to CheckpointProgress
> --
>
> Key: IGNITE-12802
> URL: https://issues.apache.org/jira/browse/IGNITE-12802
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> This is a review follow-up for IGNITE-7792. I've noticed that quite a few
> fields in {{GridCacheDatabaseSharedManager}} are related to the state of
> current checkpoint:
> {code}
> writtenPagesCntr
> syncedPagesCntr
> evictedPagesCntr
> currCheckpointPagesCnt
> {code}
> After checkpoint is completed, these fields are reset. On the other hand, we
> have a separate class to track the state of current checkpoint:
> {{CheckpointProgressImpl}}. I believe it makes sense to move these fields to
> the separate class. Perhaps, it also makes sense to make this class a
> top-level class.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12802) Move checkpoint state fields to CheckpointProgress
[
https://issues.apache.org/jira/browse/IGNITE-12802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-12802:
--
Ignite Flags: (was: Docs Required,Release Notes Required)
> Move checkpoint state fields to CheckpointProgress
> --
>
> Key: IGNITE-12802
> URL: https://issues.apache.org/jira/browse/IGNITE-12802
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This is a review follow-up for IGNITE-7792. I've noticed that quite a few
> fields in {{GridCacheDatabaseSharedManager}} are related to the state of
> current checkpoint:
> {code}
> writtenPagesCntr
> syncedPagesCntr
> evictedPagesCntr
> currCheckpointPagesCnt
> {code}
> After checkpoint is completed, these fields are reset. On the other hand, we
> have a separate class to track the state of current checkpoint:
> {{CheckpointProgressImpl}}. I believe it makes sense to move these fields to
> the separate class. Perhaps, it also makes sense to make this class a
> top-level class.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12868) Calcite integration. LEFT, RIGHT join support.
Igor Seliverstov created IGNITE-12868: - Summary: Calcite integration. LEFT, RIGHT join support. Key: IGNITE-12868 URL: https://issues.apache.org/jira/browse/IGNITE-12868 Project: Ignite Issue Type: New Feature Reporter: Igor Seliverstov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12464) Service metrics
[ https://issues.apache.org/jira/browse/IGNITE-12464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076282#comment-17076282 ] Ivan Daschinskiy commented on IGNITE-12464: --- [~vladsz83] Great job, your patch looks good for me. > Service metrics > --- > > Key: IGNITE-12464 > URL: https://issues.apache.org/jira/browse/IGNITE-12464 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.8 >Reporter: Nikolay Izhikov >Assignee: Vladimir Steshin >Priority: Minor > Labels: IEP-35 > Time Spent: 20.5h > Remaining Estimate: 0h > > We should provide the following metrics for each deployed service: > * -Count of executions- - this number seems useless, because, we can compute > it just by summing all histograms values. > * Histogram of executions duration -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12464) Service metrics
[
https://issues.apache.org/jira/browse/IGNITE-12464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076277#comment-17076277
]
Ignite TC Bot commented on IGNITE-12464:
{panel:title=Branch: [pull/7622/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5195913&buildTypeId=IgniteTests24Java8_RunAll]
> Service metrics
> ---
>
> Key: IGNITE-12464
> URL: https://issues.apache.org/jira/browse/IGNITE-12464
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.8
>Reporter: Nikolay Izhikov
>Assignee: Vladimir Steshin
>Priority: Minor
> Labels: IEP-35
> Time Spent: 20.5h
> Remaining Estimate: 0h
>
> We should provide the following metrics for each deployed service:
> * -Count of executions- - this number seems useless, because, we can compute
> it just by summing all histograms values.
> * Histogram of executions duration
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-12766) Node startup can be broken in case of using Local cache with persistence enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin resolved IGNITE-12766.
--
Resolution: Fixed
> Node startup can be broken in case of using Local cache with persistence
> enabled.
> -
>
> Key: IGNITE-12766
> URL: https://issues.apache.org/jira/browse/IGNITE-12766
> Project: Ignite
> Issue Type: Bug
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Trying to upgrade from the previous version of Apache Ignite (AI 2.7.6 for
> example) may result in the following exception when Local cache is used and
> persistence enabled.
> {code}
> [2020-03-05 16:47:39,222][ERROR][main][IgniteKernal] Exception during start
> processors, node will be stopped and close connections[2020-03-05
> 16:47:39,222][ERROR][main][IgniteKernal] Exception during start processors,
> node will be stopped and close connectionsclass
> org.apache.ignite.IgniteCheckedException: An error occurred during cache
> configuration loading from file [file=...] at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:965)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheConfigurations(FilePageStoreManager.java:907)
> at
> org.apache.ignite.internal.processors.cache.GridLocalConfigManager.restoreCaches(GridLocalConfigManager.java:171)
> at
> org.apache.ignite.internal.processors.cache.GridLocalConfigManager.restoreCacheConfigurations(GridLocalConfigManager.java:124)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onReadyForRead(GridCacheProcessor.java:5198)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetastorageReadyForRead(GridCacheDatabaseSharedManager.java:488)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:824)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:5378)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1286) at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2054)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1704)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117) at
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1035)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:921) at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:820) at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:690) at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:659) at
> org.apache.ignite.Ignition.start(Ignition.java:346) at
> org.apache.ignite.examples.ExampleNodeStartup.main(ExampleNodeStartup.java:38)Caused
> by: class org.apache.ignite.IgniteCheckedException: Failed to find class
> with given class loader for unmarshalling (make sure same versions of all
> classes are available on all nodes or enable peer-class-loading)
> [clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2,
> cls=org.apache.ignite.internal.processors.cache.GridCacheProcessor$LocalAffinityFunction]
> at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:129)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:93)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:961)
> ... 18 moreCaused by: java.lang.ClassNotFoundException:
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$LocalAffinityFunction
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at
> java.lang.ClassLoader.loadClass(ClassLoader.java:424) at
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335) at
> java.lang.ClassLoader.loadClass(ClassLoader.java:357) at
> java.lang.Class.forName0(Native Method) at
> java.lang.Class.forName(Class.java:348) at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8870) at
> org.apache.ignite.marshaller.jdk.JdkMarshallerObjectInputStream.resolveClass(JdkMarshallerObjectInputStream.java:59)
> at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1826)
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1713) at
> java.io.ObjectInputStream.re
[jira] [Commented] (IGNITE-12867) Python thin client: support for DB-API
[ https://issues.apache.org/jira/browse/IGNITE-12867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076241#comment-17076241 ] Stephen Darlington commented on IGNITE-12867: - More investigation is needed -- hence adding as a comment rather than another ticket -- but we should also make sure we can interoperate with [SQLAlchemy|https://github.com/sqlalchemy/sqlalchemy]. This may Just Work once the DB-API change is implemented or may require some tweaks. > Python thin client: support for DB-API > -- > > Key: IGNITE-12867 > URL: https://issues.apache.org/jira/browse/IGNITE-12867 > Project: Ignite > Issue Type: Improvement > Components: python >Affects Versions: 2.8 >Reporter: Stephen Darlington >Priority: Major > > Python has a database connection standard called > [DB-API|http://example.com/]. It would make the Ignite Python thin client a > lot more useful if it could use this in addition to its current > Ignite-specific APIs. Implementing this would enable other Apache tools such > as SuperSet and Airflow to connect to and use Ignite. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12867) Python thin client: support for DB-API
Stephen Darlington created IGNITE-12867: --- Summary: Python thin client: support for DB-API Key: IGNITE-12867 URL: https://issues.apache.org/jira/browse/IGNITE-12867 Project: Ignite Issue Type: Improvement Components: python Affects Versions: 2.8 Reporter: Stephen Darlington Python has a database connection standard called [DB-API|http://example.com/]. It would make the Ignite Python thin client a lot more useful if it could use this in addition to its current Ignite-specific APIs. Implementing this would enable other Apache tools such as SuperSet and Airflow to connect to and use Ignite. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12764) Regression: Thin JDBC streaming fails/BatchUpdateException if function is used
[ https://issues.apache.org/jira/browse/IGNITE-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076230#comment-17076230 ] Nikolay Izhikov commented on IGNITE-12764: -- Hello [~cyberdemon] I left some comments on GitHub. Please, take a look. > Regression: Thin JDBC streaming fails/BatchUpdateException if function is used > -- > > Key: IGNITE-12764 > URL: https://issues.apache.org/jira/browse/IGNITE-12764 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: Ilya Kasnacheev >Assignee: Dmitriy Sorokin >Priority: Blocker > Fix For: 2.8.1 > > Attachments: SqlMain.java > > Time Spent: 50m > Remaining Estimate: 0h > > insert INTO city1(id,name,name1) VALUES(?,?,RANDOM_UUID()) > happily worked in 2.7.6 but will fail on 2.8.0 with: > Exception in thread "main" java.sql.BatchUpdateException: class > org.apache.ignite.IgniteCheckedException: null > at > org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1364) > at java.base/java.lang.Thread.run(Thread.java:834) > Suspected reason is that function RANDOM_UUID() is not processed correctly > here. Column type does not matter between UUID and VARCHAR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12802) Move checkpoint state fields to CheckpointProgress
[
https://issues.apache.org/jira/browse/IGNITE-12802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-12802:
--
Fix Version/s: 2.9
> Move checkpoint state fields to CheckpointProgress
> --
>
> Key: IGNITE-12802
> URL: https://issues.apache.org/jira/browse/IGNITE-12802
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This is a review follow-up for IGNITE-7792. I've noticed that quite a few
> fields in {{GridCacheDatabaseSharedManager}} are related to the state of
> current checkpoint:
> {code}
> writtenPagesCntr
> syncedPagesCntr
> evictedPagesCntr
> currCheckpointPagesCnt
> {code}
> After checkpoint is completed, these fields are reset. On the other hand, we
> have a separate class to track the state of current checkpoint:
> {{CheckpointProgressImpl}}. I believe it makes sense to move these fields to
> the separate class. Perhaps, it also makes sense to make this class a
> top-level class.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12760) Prevent AssertionError on message unmarshalling, when classLoaderId contains id of node that already left
[
https://issues.apache.org/jira/browse/IGNITE-12760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076213#comment-17076213
]
Denis Chudov commented on IGNITE-12760:
---
[~agoncharuk] fixed.
> Prevent AssertionError on message unmarshalling, when classLoaderId contains
> id of node that already left
> -
>
> Key: IGNITE-12760
> URL: https://issues.apache.org/jira/browse/IGNITE-12760
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Following assertion error triggers failure handler and crashes the node. Can
> possibly crash the whole cluster.
> {code:java}
> 2020-02-18
> 14:34:09.775\[ERROR]\[query-#146129%DPL_GRID%DplGridNodeName%]\[o.a.i.i.p.cache.GridCacheIoManager]
> Failed to process message \[senderId=727757ed-4ad4-4779-bda9-081525725cce,
> msg=GridCacheQueryRequest \[id=178,
> cacheName=com.sbt.tokenization.data.entity.KEKEntity_DPL_union-module,
> type=SCAN, fields=false, clause=null, clsName=null, keyValFilter=null,
> rdc=null, trans=null, pageSize=1024, incBackups=false, cancel=false,
> incMeta=false, all=false, keepBinary=true,
> subjId=727757ed-4ad4-4779-bda9-081525725cce, taskHash=0, part=-1,
> topVer=AffinityTopologyVersion \[topVer=97, minorTopVer=0], sendTimestamp=-1,
> receiveTimestamp=-1, super=GridCacheIdMessage \[cacheId=-1129073400,
> super=GridCacheMessage \[msgId=179, depInfo=GridDeploymentInfoBean
> \[clsLdrId=c32670e3071-d30ee64b-0833-45d4-abbe-fb6282669caa, depMode=SHARED,
> userVer=0, locDepOwner=false, participants=null],
> lastAffChangedTopVer=AffinityTopologyVersion \[topVer=8, minorTopVer=6],
> err=null, skipPrepare=false
> java.lang.AssertionError: null
> at
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:918)
> at
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:889)
> at
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.p2pContext(GridCacheDeploymentManager.java:422)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1576)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:584)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:386)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:312)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:102)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:301)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1565)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1189)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4300(GridIoManager.java:130)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1092)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748){code}
> There is no fair reproducer for now, but it seems that we should prevent such
> situation in general like following:
> 1) check the correctness of the message before it will be sent - inside of
> GridCacheDeploymentManager#prepare. If we have the corresponding class loader
> on local node, we can try to fix message and replace wrong class loader with
> local one.
> 2) log suspicious deployments which we receive from
> GridDeploymentManager#deploy - maybe we have obsolete deployments in caches.
> 3) possibly we can remove this assertion, we should have this class on sender
> node and use it as class loader id, and if we don't, we will receive
> exception on finishUnmarshall (Failed to peer load class) and try to process
> this situation with GridCacheIoManager#processFailedMessage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12865) NPE occurs during CQ registration with cache node filter specified.
[
https://issues.apache.org/jira/browse/IGNITE-12865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076202#comment-17076202
]
PetrovMikhail commented on IGNITE-12865:
[~Pavlukhin], reproducer in the ticket was updated according to your
suggestion. The stack trace is specified.
> NPE occurs during CQ registration with cache node filter specified.
> ---
>
> Key: IGNITE-12865
> URL: https://issues.apache.org/jira/browse/IGNITE-12865
> Project: Ignite
> Issue Type: Bug
>Reporter: PetrovMikhail
>Priority: Minor
>
> NPE occurs during CQ registration if
> 1. Node that starts cache does not match cache node filter.
> 2. CQ is started on node that matches cache node filter.
> Exception:
> {code:java}
> [2020-04-06
> 12:49:23,863][ERROR][disco-notifier-worker-#36%ignite.CacheContinousQueryProjectionPredicateTest0%][GridDiscoveryManager]
> Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
> [startReqData=StartRequestData
> [prjPred=o.a.i.CacheContinousQueryProjectionPredicateTest$$Lambda$514/265747429@3529eb45,
>
> clsName=o.a.i.CacheContinousQueryProjectionPredicateTest$$Lambda$514/265747429,
> depInfo=GridDeploymentInfoBean
> [clsLdrId=9ddf4ee4171-9647add4-b66c-4a10-9bb7-f5ecf7d1, depMode=SHARED,
> userVer=0, locDepOwner=false, participants=null],
> hnd=CacheContinuousQueryHandler
> [returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@7dfdf92a,
> cacheName=default, rmtFilter=null, rmtFilterDep=null, internal=false,
> notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
> taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=false,
> ackBuf=null, cacheId=1544803905, initTopVer=null, nodeLeft=false,
> ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
> autoUnsubscribe=true], keepBinary=false, deserEx=null,
> routineId=b2b363ed-a9d7-4e4e-a91d-f17e09ba7d7f]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
> at
> org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:670)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:533)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2635)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2673)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Reproducer:
> {code:java}
> /** */
> @Test
> public void test() throws Exception {
> IgniteEx filteredNode = startGrid(0);
> IgniteEx cacheStoreNode = startGrid(1);
> filteredNode.cluster().state(ClusterState.ACTIVE);
> UUID filteredNodeId = filteredNode.localNode().id();
> filteredNode.createCache(new CacheConfiguration<>(DEFAULT_CACHE_NAME)
> .setNodeFilter(node -> !node.id().equals(filteredNodeId)));
> ContinuousQuery qry = new ContinuousQuery<>();
> qry.setLocalListener(evts -> {
> //No-op.
> });
> cacheStoreNode.cache(DEFAULT_CACHE_NAME).query(qry);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12865) NPE occurs during CQ registration with cache node filter specified.
[
https://issues.apache.org/jira/browse/IGNITE-12865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-12865:
---
Description:
NPE occurs during CQ registration if
1. Node that starts cache does not match cache node filter.
2. CQ is started on node that matches cache node filter.
Exception:
{code:java}
[2020-04-06
12:49:23,863][ERROR][disco-notifier-worker-#36%ignite.CacheContinousQueryProjectionPredicateTest0%][GridDiscoveryManager]
Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
[startReqData=StartRequestData
[prjPred=o.a.i.CacheContinousQueryProjectionPredicateTest$$Lambda$514/265747429@3529eb45,
clsName=o.a.i.CacheContinousQueryProjectionPredicateTest$$Lambda$514/265747429,
depInfo=GridDeploymentInfoBean
[clsLdrId=9ddf4ee4171-9647add4-b66c-4a10-9bb7-f5ecf7d1, depMode=SHARED,
userVer=0, locDepOwner=false, participants=null],
hnd=CacheContinuousQueryHandler
[returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@7dfdf92a,
cacheName=default, rmtFilter=null, rmtFilterDep=null, internal=false,
notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=false,
ackBuf=null, cacheId=1544803905, initTopVer=null, nodeLeft=false,
ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
autoUnsubscribe=true], keepBinary=false, deserEx=null,
routineId=b2b363ed-a9d7-4e4e-a91d-f17e09ba7d7f]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:670)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:533)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2635)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2673)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{code}
Reproducer:
{code:java}
/** */
@Test
public void test() throws Exception {
IgniteEx filteredNode = startGrid(0);
IgniteEx cacheStoreNode = startGrid(1);
filteredNode.cluster().state(ClusterState.ACTIVE);
UUID filteredNodeId = filteredNode.localNode().id();
filteredNode.createCache(new CacheConfiguration<>(DEFAULT_CACHE_NAME)
.setNodeFilter(node -> !node.id().equals(filteredNodeId)));
ContinuousQuery qry = new ContinuousQuery<>();
qry.setLocalListener(evts -> {
//No-op.
});
cacheStoreNode.cache(DEFAULT_CACHE_NAME).query(qry);
}
{code}
was:
NPE occurs during CQ registration if
1. Node that starts cache does not match cache node filter.
2. CQ is started on node that matches cache node filter.
Exception:
[2020-04-06
12:49:23,863][ERROR][disco-notifier-worker-#36%ignite.CacheContinousQueryProjectionPredicateTest0%][GridDiscoveryManager]
Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
[startReqData=StartRequestData
[prjPred=o.a.i.CacheContinousQueryProjectionPredicateTest$$Lambda$514/265747429@3529eb45,
clsName=o.a.i.CacheContinousQueryProjectionPredicateTest$$Lambda$514/265747429,
depInfo=GridDeploymentInfoBean
[clsLdrId=9ddf4ee4171-9647add4-b66c-4a10-9bb7-f5ecf7d1, depMode=SHARED,
userVer=0, locDepOwner=false, participants=null],
hnd=CacheContinuousQueryHandler
[returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@7dfdf92a,
cacheName=default, rmtFilter=null, rmtFilterDep=null, internal=false,
notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=false,
ackBuf=null, cacheId=1544803905, initTopVer=null, nodeLeft=false,
ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
autoUnsub
[jira] [Updated] (IGNITE-12865) NPE occurs during CQ registration with cache node filter specified.
[
https://issues.apache.org/jira/browse/IGNITE-12865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-12865:
---
Description:
NPE occurs during CQ registration if
1. Node that starts cache does not match cache node filter.
2. CQ is started on node that matches cache node filter.
Exception:
[2020-04-06
12:49:23,863][ERROR][disco-notifier-worker-#36%ignite.CacheContinousQueryProjectionPredicateTest0%][GridDiscoveryManager]
Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
[startReqData=StartRequestData
[prjPred=o.a.i.CacheContinousQueryProjectionPredicateTest$$Lambda$514/265747429@3529eb45,
clsName=o.a.i.CacheContinousQueryProjectionPredicateTest$$Lambda$514/265747429,
depInfo=GridDeploymentInfoBean
[clsLdrId=9ddf4ee4171-9647add4-b66c-4a10-9bb7-f5ecf7d1, depMode=SHARED,
userVer=0, locDepOwner=false, participants=null],
hnd=CacheContinuousQueryHandler
[returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@7dfdf92a,
cacheName=default, rmtFilter=null, rmtFilterDep=null, internal=false,
notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=false,
ackBuf=null, cacheId=1544803905, initTopVer=null, nodeLeft=false,
ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
autoUnsubscribe=true], keepBinary=false, deserEx=null,
routineId=b2b363ed-a9d7-4e4e-a91d-f17e09ba7d7f]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:670)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:533)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2635)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2673)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Reproducer:
{code:java}
/** */
@Test
public void test() throws Exception {
IgniteEx filteredNode = startGrid(0);
IgniteEx cacheStoreNode = startGrid(1);
filteredNode.cluster().state(ClusterState.ACTIVE);
UUID filteredNodeId = filteredNode.localNode().id();
filteredNode.createCache(new CacheConfiguration<>(DEFAULT_CACHE_NAME)
.setNodeFilter(node -> !node.id().equals(filteredNodeId)));
ContinuousQuery qry = new ContinuousQuery<>();
qry.setLocalListener(evts -> {
//No-op.
});
cacheStoreNode.cache(DEFAULT_CACHE_NAME).query(qry);
}
{code}
was:
NPE occurs during CQ registration if
1. Node that starts cache does not match cache node filter.
2. CQ is started on node that matches cache node filter.
Exception:
{code:java}
[2020-04-06
12:49:23,863][ERROR][disco-notifier-worker-#36%ignite.CacheContinousQueryProjectionPredicateTest0%][GridDiscoveryManager]
Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
[startReqData=StartRequestData
[prjPred=o.a.i.CacheContinousQueryProjectionPredicateTest$$Lambda$514/265747429@3529eb45,
clsName=o.a.i.CacheContinousQueryProjectionPredicateTest$$Lambda$514/265747429,
depInfo=GridDeploymentInfoBean
[clsLdrId=9ddf4ee4171-9647add4-b66c-4a10-9bb7-f5ecf7d1, depMode=SHARED,
userVer=0, locDepOwner=false, participants=null],
hnd=CacheContinuousQueryHandler
[returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@7dfdf92a,
cacheName=default, rmtFilter=null, rmtFilterDep=null, internal=false,
notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=false,
ackBuf=null, cacheId=1544803905, initTopVer=null, nodeLeft=false,
ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
autoUnsubscribe=t
[jira] [Updated] (IGNITE-12865) NPE occurs during CQ registration with cache node filter specified.
[
https://issues.apache.org/jira/browse/IGNITE-12865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-12865:
---
Description:
NPE occurs during CQ registration if
1. Node that starts cache does not match cache node filter.
2. CQ is started on node that matches cache node filter.
Exception:
{code:java}
[2020-04-06
12:49:23,863][ERROR][disco-notifier-worker-#36%ignite.CacheContinousQueryProjectionPredicateTest0%][GridDiscoveryManager]
Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
[startReqData=StartRequestData
[prjPred=o.a.i.CacheContinousQueryProjectionPredicateTest$$Lambda$514/265747429@3529eb45,
clsName=o.a.i.CacheContinousQueryProjectionPredicateTest$$Lambda$514/265747429,
depInfo=GridDeploymentInfoBean
[clsLdrId=9ddf4ee4171-9647add4-b66c-4a10-9bb7-f5ecf7d1, depMode=SHARED,
userVer=0, locDepOwner=false, participants=null],
hnd=CacheContinuousQueryHandler
[returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@7dfdf92a,
cacheName=default, rmtFilter=null, rmtFilterDep=null, internal=false,
notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=false,
ackBuf=null, cacheId=1544803905, initTopVer=null, nodeLeft=false,
ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
autoUnsubscribe=true], keepBinary=false, deserEx=null,
routineId=b2b363ed-a9d7-4e4e-a91d-f17e09ba7d7f][2020-04-06
12:49:23,863][ERROR][disco-notifier-worker-#36%ignite.CacheContinousQueryProjectionPredicateTest0%][GridDiscoveryManager]
Failed to notify direct custom event listener: StartRoutineDiscoveryMessage
[startReqData=StartRequestData
[prjPred=o.a.i.CacheContinousQueryProjectionPredicateTest$$Lambda$514/265747429@3529eb45,
clsName=o.a.i.CacheContinousQueryProjectionPredicateTest$$Lambda$514/265747429,
depInfo=GridDeploymentInfoBean
[clsLdrId=9ddf4ee4171-9647add4-b66c-4a10-9bb7-f5ecf7d1, depMode=SHARED,
userVer=0, locDepOwner=false, participants=null],
hnd=CacheContinuousQueryHandler
[returnValTrans=o.a.i.i.processors.cache.query.continuous.CacheContinuousQueryHandler$1@7dfdf92a,
cacheName=default, rmtFilter=null, rmtFilterDep=null, internal=false,
notifyExisting=false, oldValRequired=true, sync=false, ignoreExpired=true,
taskHash=0, skipPrimaryCheck=false, locOnly=false, keepBinary=false,
ackBuf=null, cacheId=1544803905, initTopVer=null, nodeLeft=false,
ignoreClsNotFound=false, nodeId=null, routineId=null], bufSize=1, interval=0,
autoUnsubscribe=true], keepBinary=false, deserEx=null,
routineId=b2b363ed-a9d7-4e4e-a91d-f17e09ba7d7f]java.lang.NullPointerException
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:95)
at
org.apache.ignite.internal.processors.continuous.StartRoutineDiscoveryMessage.addUpdateCounters(StartRoutineDiscoveryMessage.java:109)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1482)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:117)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:220)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:211)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:670)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:533)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2635)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2673)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748){code}
Reproducer:
{code:java}
/** */
@Test
public void test() throws Exception {
IgniteEx filteredNode = startGrid(0);
IgniteEx cacheStoreNode = startGrid(1);
filteredNode.cluster().state(ClusterState.ACTIVE);
UUID filteredNodeId = filteredNode.localNode().id();
filteredNode.createCache(new CacheConfiguration<>(DEFAULT_CACHE_NAME)
.setNodeFilter(node -> !node.id().equals(filteredNodeId)));
ContinuousQuery qry = new ContinuousQuery<>();
qry.setLocalListener(evts -> {
//No-op.
});
cacheStoreNode.cache(DEFAULT_CACHE_NAME).query(qry);
}
{code}
was:
NPE occurs during CQ registration if
1. Node that starts cache does not match cache node filter.
2. CQ is started on node that matches cache node filter.
Reprod
[jira] [Updated] (IGNITE-12865) NPE occurs during CQ registration with cache node filter specified.
[
https://issues.apache.org/jira/browse/IGNITE-12865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-12865:
---
Description:
NPE occurs during CQ registration if
1. Node that starts cache does not match cache node filter.
2. CQ is started on node that matches cache node filter.
Reproducer:
{code:java}
/** */
@Test
public void test() throws Exception {
IgniteEx filteredNode = startGrid(0);
IgniteEx cacheStoreNode = startGrid(1);
filteredNode.cluster().state(ClusterState.ACTIVE);
UUID filteredNodeId = filteredNode.localNode().id();
filteredNode.createCache(new CacheConfiguration<>(DEFAULT_CACHE_NAME)
.setNodeFilter(node -> !node.id().equals(filteredNodeId)));
ContinuousQuery qry = new ContinuousQuery<>();
qry.setLocalListener(evts -> {
//No-op.
});
cacheStoreNode.cache(DEFAULT_CACHE_NAME).query(qry);
}
{code}
was:
NPE occurs during CQ registration if
1. Node that starts cache does not match cache node filter.
2. CQ is started on node that matches cache node filter.
Reproducer:
{code:java}
/** */
@Test
public void test() throws Exception {
IgniteEx filteredNode = startGrid(0);
IgniteEx cacheStoreNode = startGrid(1);
filteredNode.cluster().state(ClusterState.ACTIVE);
filteredNode.createCache(new CacheConfiguration<>(DEFAULT_CACHE_NAME)
.setNodeFilter(node ->
!node.id().equals(filteredNode.localNode().id(;
ContinuousQuery qry = new ContinuousQuery<>();
qry.setLocalListener(evts -> {
//No-op.
});
cacheStoreNode.cache(DEFAULT_CACHE_NAME).query(qry);
}
{code}
> NPE occurs during CQ registration with cache node filter specified.
> ---
>
> Key: IGNITE-12865
> URL: https://issues.apache.org/jira/browse/IGNITE-12865
> Project: Ignite
> Issue Type: Bug
>Reporter: PetrovMikhail
>Priority: Minor
>
> NPE occurs during CQ registration if
> 1. Node that starts cache does not match cache node filter.
> 2. CQ is started on node that matches cache node filter.
> Reproducer:
> {code:java}
> /** */
> @Test
> public void test() throws Exception {
> IgniteEx filteredNode = startGrid(0);
> IgniteEx cacheStoreNode = startGrid(1);
> filteredNode.cluster().state(ClusterState.ACTIVE);
> UUID filteredNodeId = filteredNode.localNode().id();
> filteredNode.createCache(new CacheConfiguration<>(DEFAULT_CACHE_NAME)
> .setNodeFilter(node -> !node.id().equals(filteredNodeId)));
> ContinuousQuery qry = new ContinuousQuery<>();
> qry.setLocalListener(evts -> {
> //No-op.
> });
> cacheStoreNode.cache(DEFAULT_CACHE_NAME).query(qry);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12865) NPE occurs during CQ registration with cache node filter specified.
[
https://issues.apache.org/jira/browse/IGNITE-12865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076180#comment-17076180
]
Ivan Pavlukhin commented on IGNITE-12865:
-
[~PetrovMikhail], could you please provide a stack trace? From the first glance
it seems that there is a problem with {{filteredNode}} variable node usage in a
node filter in the test. By some reason it can be serialized and I suppose
deserialized not ready to use.
Will changing code in a following way fix the test?
{code}
Object filteredId = filteredNode.localNode().id();
filteredNode.createCache(new CacheConfiguration<>(DEFAULT_CACHE_NAME)
.setNodeFilter(node -> !node.id().equals(filteredId)));
{code}
> NPE occurs during CQ registration with cache node filter specified.
> ---
>
> Key: IGNITE-12865
> URL: https://issues.apache.org/jira/browse/IGNITE-12865
> Project: Ignite
> Issue Type: Bug
>Reporter: PetrovMikhail
>Priority: Minor
>
> NPE occurs during CQ registration if
> 1. Node that starts cache does not match cache node filter.
> 2. CQ is started on node that matches cache node filter.
> Reproducer:
> {code:java}
> /** */
> @Test
> public void test() throws Exception {
> IgniteEx filteredNode = startGrid(0);
> IgniteEx cacheStoreNode = startGrid(1);
> filteredNode.cluster().state(ClusterState.ACTIVE);
> filteredNode.createCache(new CacheConfiguration<>(DEFAULT_CACHE_NAME)
> .setNodeFilter(node ->
> !node.id().equals(filteredNode.localNode().id(;
> ContinuousQuery qry = new ContinuousQuery<>();
> qry.setLocalListener(evts -> {
> //No-op.
> });
> cacheStoreNode.cache(DEFAULT_CACHE_NAME).query(qry);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-11494) Change message log message in case of too small IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter
[ https://issues.apache.org/jira/browse/IGNITE-11494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikita Alemaskin reassigned IGNITE-11494: - Assignee: Nikita Alemaskin > Change message log message in case of too small > IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter > - > > Key: IGNITE-11494 > URL: https://issues.apache.org/jira/browse/IGNITE-11494 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.7 >Reporter: Evgenii Zhuravlev >Assignee: Nikita Alemaskin >Priority: Major > Labels: newbie, usability > > Message "Fetched result set was too large." should be changed to some > recommendations regarding IGNITE_SQL_MERGE_TABLE_MAX_SIZE property -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12866) CQ fails due to CQ filter deserialization exception.
PetrovMikhail created IGNITE-12866: -- Summary: CQ fails due to CQ filter deserialization exception. Key: IGNITE-12866 URL: https://issues.apache.org/jira/browse/IGNITE-12866 Project: Ignite Issue Type: Bug Reporter: PetrovMikhail CQ fails if CQ filter deserialization exception occurred on a node that does not match the cache node filter in case cache node filter must be loaded via p2p. Reproducer is linked as PR to the ticket. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12865) NPE occurs during CQ registration with cache node filter specified.
PetrovMikhail created IGNITE-12865:
--
Summary: NPE occurs during CQ registration with cache node filter
specified.
Key: IGNITE-12865
URL: https://issues.apache.org/jira/browse/IGNITE-12865
Project: Ignite
Issue Type: Bug
Reporter: PetrovMikhail
NPE occurs during CQ registration if
1. Node that starts cache does not match cache node filter.
2. CQ is started on node that matches cache node filter.
Reproducer:
{code:java}
/** */
@Test
public void test() throws Exception {
IgniteEx filteredNode = startGrid(0);
IgniteEx cacheStoreNode = startGrid(1);
filteredNode.cluster().state(ClusterState.ACTIVE);
filteredNode.createCache(new CacheConfiguration<>(DEFAULT_CACHE_NAME)
.setNodeFilter(node ->
!node.id().equals(filteredNode.localNode().id(;
ContinuousQuery qry = new ContinuousQuery<>();
qry.setLocalListener(evts -> {
//No-op.
});
cacheStoreNode.cache(DEFAULT_CACHE_NAME).query(qry);
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12864) Calcite integration. UNION support.
Igor Seliverstov created IGNITE-12864: - Summary: Calcite integration. UNION support. Key: IGNITE-12864 URL: https://issues.apache.org/jira/browse/IGNITE-12864 Project: Ignite Issue Type: New Feature Reporter: Igor Seliverstov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12344) Remote listener of IgniteMessaging has to run with appropriate SecurityContext.
[ https://issues.apache.org/jira/browse/IGNITE-12344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Garus updated IGNITE-12344: - Release Note: Remote listener of IgniteMessaging runs on a remote node with the SecurityContext of the initiator node. > Remote listener of IgniteMessaging has to run with appropriate > SecurityContext. > --- > > Key: IGNITE-12344 > URL: https://issues.apache.org/jira/browse/IGNITE-12344 > Project: Ignite > Issue Type: Improvement > Components: security >Reporter: Denis Garus >Assignee: Denis Garus >Priority: Major > Labels: iep-38 > Fix For: 2.9 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Remote listener of IgniteMessaging has to run on a remote node with the > SecurityContext of the initiator node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12863) NPE while initializing Cassandra Store
[
https://issues.apache.org/jira/browse/IGNITE-12863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076142#comment-17076142
]
Stanilovsky Evgeny commented on IGNITE-12863:
-
[~northdragon] Nikolay, what do you think about including this fix into 2.8.1 ?
+ who can merge it ?
> NPE while initializing Cassandra Store
> --
>
> Key: IGNITE-12863
> URL: https://issues.apache.org/jira/browse/IGNITE-12863
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Alex Serbin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When trying to create a simple cache with Cassandra store and have value
> persistence strategy POJO, the following exception occurs
> {code:java}
> Caused by: java.lang.NullPointerException: nullCaused by:
> java.lang.NullPointerException: null at
> org.apache.ignite.cache.store.cassandra.persistence.PojoField.calculatedField(PojoField.java:155)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.prepareLoadStatements(PersistenceController.java:311)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.(PersistenceController.java:85)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStore.(CassandraCacheStore.java:106)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory.create(CassandraCacheStoreFactory.java:59)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory.create(CassandraCacheStoreFactory.java:34)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCacheContext(GridCacheProcessor.java:1199)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheContext(GridCacheProcessor.java:1995)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$null$6a5b31b9$1(GridCacheProcessor.java:1830)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$8(GridCacheProcessor.java:1754)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$926b6886$1(GridCacheProcessor.java:1827)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.util.IgniteUtils.lambda$null$1(IgniteUtils.java:11138)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266)
> ~[na:1.8.0_181] at java.util.concurrent.FutureTask.run(FutureTask.java)
> ~[na:1.8.0_181] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> ~[na:1.8.0_181] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> ~[na:1.8.0_181] at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_181]
> {code}
> It looks like that recent changes of IGNITE-1903 are leading to this issue,
> as we are starting to serialize {{CacheStoreFactory}}, which contains
> {{PojoFiled}}, which in its turn has transient field accessor. This leads to
> accessor being null after deserialization. Note, that this happens only when
> passing {{persistenceSettings}} (not {{persistenceSettingsBean}})
> Works fine with Ignite 2.7.6.
> Probably related to IGNITE-8500
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12863) NPE while initializing Cassandra Store
[
https://issues.apache.org/jira/browse/IGNITE-12863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076139#comment-17076139
]
Ignite TC Bot commented on IGNITE-12863:
{panel:title=Branch: [pull/7624/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5194868&buildTypeId=IgniteTests24Java8_RunAll]
> NPE while initializing Cassandra Store
> --
>
> Key: IGNITE-12863
> URL: https://issues.apache.org/jira/browse/IGNITE-12863
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Alex Serbin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When trying to create a simple cache with Cassandra store and have value
> persistence strategy POJO, the following exception occurs
> {code:java}
> Caused by: java.lang.NullPointerException: nullCaused by:
> java.lang.NullPointerException: null at
> org.apache.ignite.cache.store.cassandra.persistence.PojoField.calculatedField(PojoField.java:155)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.prepareLoadStatements(PersistenceController.java:311)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.(PersistenceController.java:85)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStore.(CassandraCacheStore.java:106)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory.create(CassandraCacheStoreFactory.java:59)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory.create(CassandraCacheStoreFactory.java:34)
> ~[ignite-cassandra-store-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCacheContext(GridCacheProcessor.java:1199)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheContext(GridCacheProcessor.java:1995)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$null$6a5b31b9$1(GridCacheProcessor.java:1830)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$8(GridCacheProcessor.java:1754)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$926b6886$1(GridCacheProcessor.java:1827)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> org.apache.ignite.internal.util.IgniteUtils.lambda$null$1(IgniteUtils.java:11138)
> ~[ignite-core-2.8.0.jar:2.8.0] at
> java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266)
> ~[na:1.8.0_181] at java.util.concurrent.FutureTask.run(FutureTask.java)
> ~[na:1.8.0_181] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> ~[na:1.8.0_181] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> ~[na:1.8.0_181] at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_181]
> {code}
> It looks like that recent changes of IGNITE-1903 are leading to this issue,
> as we are starting to serialize {{CacheStoreFactory}}, which contains
> {{PojoFiled}}, which in its turn has transient field accessor. This leads to
> accessor being null after deserialization. Note, that this happens only when
> passing {{persistenceSettings}} (not {{persistenceSettingsBean}})
> Works fine with Ignite 2.7.6.
> Probably related to IGNITE-8500
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12825) Serialize Java and .NET dates using same calendars
[ https://issues.apache.org/jira/browse/IGNITE-12825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076126#comment-17076126 ] Nikolay Izhikov commented on IGNITE-12825: -- While investigating this issue I've found that DateTime arguments not supported in .Net services. I fixed this issue in IGNITE-12859. As for timezone. As far as I can see from source code Ignite Dotnet integration not supported timezones other than UTC. https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Binary/BinaryUtils.cs#L1615 [~kukushal] Can you, please, provide a reproducer for the issue you described. For now, I close this ticket as "Won't fix". Feel free to reopen if the issue still there. > Serialize Java and .NET dates using same calendars > -- > > Key: IGNITE-12825 > URL: https://issues.apache.org/jira/browse/IGNITE-12825 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.8 >Reporter: Alexey Kukushkin >Assignee: Nikolay Izhikov >Priority: Major > Labels: .NET, sbcf > Attachments: ignite-12825-vs-2.8.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Java and .NET use different calendars for dates serialization. That results > in some dates written using Java API deserialized into different dates using > .NET API and vise versa. For example, 1-Jan-1992 00:00:00 MSK written using > Java API will be read as 31-Dec-1991 1:00:00 MSK using .NET API. > Java and .NET API must use same calendars for dates serialization. > +*Note:*+ > Java uses IANA Time Zone database ([https://www.iana.org/time-zones]) stored > locally that could be manually updated using Timezone Updater Tool > ([https://www.oracle.com/technetwork/java/javase/documentation/tzupdater-readme-136440.html]) > .NET uses its own calendars that cannot be manually updated. > For all the Java/.NET calendar differences I saw the Java version was valid > and .NET version was not. > We need to use IANA time zone database in .NET as well and, if possible, > provide a mechanism to update the time zone database -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12764) Regression: Thin JDBC streaming fails/BatchUpdateException if function is used
[ https://issues.apache.org/jira/browse/IGNITE-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076113#comment-17076113 ] Dmitriy Sorokin commented on IGNITE-12764: -- [~nizhikov], [~ilyak], review my patch, please! > Regression: Thin JDBC streaming fails/BatchUpdateException if function is used > -- > > Key: IGNITE-12764 > URL: https://issues.apache.org/jira/browse/IGNITE-12764 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: Ilya Kasnacheev >Assignee: Dmitriy Sorokin >Priority: Blocker > Fix For: 2.8.1 > > Attachments: SqlMain.java > > Time Spent: 10m > Remaining Estimate: 0h > > insert INTO city1(id,name,name1) VALUES(?,?,RANDOM_UUID()) > happily worked in 2.7.6 but will fail on 2.8.0 with: > Exception in thread "main" java.sql.BatchUpdateException: class > org.apache.ignite.IgniteCheckedException: null > at > org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1364) > at java.base/java.lang.Thread.run(Thread.java:834) > Suspected reason is that function RANDOM_UUID() is not processed correctly > here. Column type does not matter between UUID and VARCHAR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12839) IGNITE-12789 broke WALRecordSerializationTest
[ https://issues.apache.org/jira/browse/IGNITE-12839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-12839: -- Ignite Flags: (was: Docs Required,Release Notes Required) > IGNITE-12789 broke WALRecordSerializationTest > - > > Key: IGNITE-12839 > URL: https://issues.apache.org/jira/browse/IGNITE-12839 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Fix For: 2.9 > > Time Spent: 20m > Remaining Estimate: 0h > > [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-3192056576753991319&branch=%3Cdefault%3E&tab=testDetails] > > Sorry, too bad that I skipped it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12839) IGNITE-12789 broke WALRecordSerializationTest
[ https://issues.apache.org/jira/browse/IGNITE-12839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-12839: -- Fix Version/s: 2.9 > IGNITE-12789 broke WALRecordSerializationTest > - > > Key: IGNITE-12839 > URL: https://issues.apache.org/jira/browse/IGNITE-12839 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-3192056576753991319&branch=%3Cdefault%3E&tab=testDetails] > > Sorry, too bad that I skipped it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12789) Tracking page repairing has no WAL record associated with it
[ https://issues.apache.org/jira/browse/IGNITE-12789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-12789: -- Fix Version/s: 2.9 > Tracking page repairing has no WAL record associated with it > > > Key: IGNITE-12789 > URL: https://issues.apache.org/jira/browse/IGNITE-12789 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Fix For: 2.9 > > Time Spent: 0.5h > Remaining Estimate: 0h > > org.apache.ignite.internal.processors.cache.persistence.tree.io.TrackingPageIO#resetCorruptFlag(long) > > In order for tracking pages to work properly they should be persisted on > disk, it means that failed checkpoint scenario should be supported. Tracking > pages restoration has no associated WAL record so in that case binary > recovery could leave them broken after a valid repair. -- This message was sent by Atlassian Jira (v8.3.4#803005)
