[jira] [Issue Comment Deleted] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster
[
https://issues.apache.org/jira/browse/IGNITE-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-12033:
Comment: was deleted
(was: {panel:title=Branch: [pull/8870/head] Base: [master] : Possible Blockers
(6)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Control Utility{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5935810]]
{color:#d04437}Cache 7{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5935778]]
* IgniteCacheTestSuite7: GracefulShutdownTest.testNodeForceShutdown - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5935772]]
* IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationChainContinuesOnDefaultExecutor
- History for base branch is absent.
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5935785]]
{color:#d04437}Thin Client: Java{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5935738]]
* ClientTestSuite: ComputeTaskTest.testActiveTasksLimit - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Cassandra Store{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5935804]]
* org.apache.ignite.testsuites.cassandra.store.IgniteCassandraStoreTestSuite:
org.apache.ignite.tests.IgnitePersistentStoreTest. - History for base branch is
absent.
{panel}
{panel:title=Branch: [pull/8870/head] Base: [master] : New Tests
(15)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Cache 1{color} [[tests
8|https://ci.ignite.apache.org/viewLog.html?buildId=5935772]]
* {color:#8b}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationChainContinuesOnDefaultExecutor
- FAILED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testLocalOperationListenerExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testLocalOperationChainExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationListenContinuesOnDefaultExecutor
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testRemoteOperationChainContinuesOnDefaultExecutor
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testLocalOperationListenerExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testLocalOperationChainExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testRemoteOperationListenContinuesOnDefaultExecutor
- PASSED{color}
{color:#8b}Platform .NET (Core Linux){color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=5935792]]
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeExecuteAsyncContinuation
- PASSED{color}
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeRunAsyncContinuation -
PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestSynchronousExecutorRunsContinuationsOnStripedPool -
PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestInvalidExecutorConfigurationFailsOnStart - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestLocalOperationExecutesSynchronously - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestAsyncAwaitContinuationIsExecutedWithConfiguredExecutor
- PASSED{color}
{color:#8b}Cassandra Store{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5935804]]
*
{color:#8b}org.apache.ignite.testsuites.cassandra.store.IgniteCassandraStoreTestSuite:
org.apache.ignite.tests.IgnitePersistentStoreTest. - FAILED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5935818buildTypeId=IgniteTests24Java8_RunAll])
> Callbacks from striped pool due to async/await may hang cluster
> ---
>
> Key: IGNITE-12033
> URL: https://issues.apache.org/jira/browse/IGNITE-12033
> Project: Ignite
> Issue Type: Bug
> Components: cache, platforms
>Affects Versions: 2.7.5
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: iep-70
> Fix For: 2.11
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Discussed on dev-list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Re-EXTERNAL-Re-Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td42921.html
>
[jira] [Commented] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster
[
https://issues.apache.org/jira/browse/IGNITE-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320705#comment-17320705
]
Ignite TC Bot commented on IGNITE-12033:
{panel:title=Branch: [pull/8870/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8870/head] Base: [master] : New Tests
(16)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=5964703]]
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeExecuteAsyncContinuation
- PASSED{color}
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeRunAsyncContinuation -
PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestSynchronousExecutorRunsContinuationsOnStripedPool -
PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestInvalidExecutorConfigurationFailsOnStart - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestLocalOperationExecutesSynchronously - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestAsyncAwaitContinuationIsExecutedWithConfiguredExecutor
- PASSED{color}
{color:#8b}Cache 1{color} [[tests
10|https://ci.ignite.apache.org/viewLog.html?buildId=5965676]]
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationListenerExecutesOnStripedPoolWhenCustomExecutorIsProvided
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testRemoteOperationListenerExecutesOnStripedPoolWhenCustomExecutorIsProvided
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationChainContinuesOnDefaultExecutor
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testLocalOperationListenerExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testLocalOperationChainExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationListenContinuesOnDefaultExecutor
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testRemoteOperationChainContinuesOnDefaultExecutor
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testLocalOperationListenerExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testLocalOperationChainExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testRemoteOperationListenContinuesOnDefaultExecutor
- PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5964729buildTypeId=IgniteTests24Java8_RunAll]
> Callbacks from striped pool due to async/await may hang cluster
> ---
>
> Key: IGNITE-12033
> URL: https://issues.apache.org/jira/browse/IGNITE-12033
> Project: Ignite
> Issue Type: Bug
> Components: cache, platforms
>Affects Versions: 2.7.5
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: iep-70
> Fix For: 2.11
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Discussed on dev-list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Re-EXTERNAL-Re-Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td42921.html
> *Must use the public pool for callbacks as the most obvious step.*
>
> http://apache-ignite-users.70518.x6.nabble.com/Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td27871.html#a28051
> There's a reproducer project. Long story short, .Net can invoke cache
> operations with future callbacks, which will be invoked from striped pool. If
> such callbacks are to use cache operations, those will be possibly sheduled
> to the same stripe and cause a deadlock.
> The code is very simple:
> {code}
> Console.WriteLine("PutAsync");
> await cache.PutAsync(1, "Test");
> Console.WriteLine("Replace");
> cache.Replace(1, "Testing"); // Hangs here
> Console.WriteLine("Wait");
> await Task.Delay(Timeout.Infinite);
> {code}
> async/await should absolutely not allow any client code to be run from
> stripes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster
[
https://issues.apache.org/jira/browse/IGNITE-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-12033:
Comment: was deleted
(was: {panel:title=Branch: [pull/8870/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8870/head] Base: [master] : New Tests
(10)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 1{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5930546]]
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationContinuesOnDefaultExecutor
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testLocalOperationExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testLocalOperationExecutesSynchronously -
PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testRemoteOperationContinuesOnDefaultExecutor
- PASSED{color}
{color:#8b}Platform .NET (Core Linux){color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=5930608]]
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeExecuteAsyncContinuation
- PASSED{color}
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeRunAsyncContinuation -
PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestSynchronousExecutorRunsContinuationsOnStripedPool -
PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestInvalidExecutorConfigurationFailsOnStart - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestLocalOperationExecutesSynchronously - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestAsyncAwaitContinuationIsExecutedWithConfiguredExecutor
- PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5930592buildTypeId=IgniteTests24Java8_RunAll])
> Callbacks from striped pool due to async/await may hang cluster
> ---
>
> Key: IGNITE-12033
> URL: https://issues.apache.org/jira/browse/IGNITE-12033
> Project: Ignite
> Issue Type: Bug
> Components: cache, platforms
>Affects Versions: 2.7.5
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: iep-70
> Fix For: 2.11
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Discussed on dev-list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Re-EXTERNAL-Re-Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td42921.html
> *Must use the public pool for callbacks as the most obvious step.*
>
> http://apache-ignite-users.70518.x6.nabble.com/Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td27871.html#a28051
> There's a reproducer project. Long story short, .Net can invoke cache
> operations with future callbacks, which will be invoked from striped pool. If
> such callbacks are to use cache operations, those will be possibly sheduled
> to the same stripe and cause a deadlock.
> The code is very simple:
> {code}
> Console.WriteLine("PutAsync");
> await cache.PutAsync(1, "Test");
> Console.WriteLine("Replace");
> cache.Replace(1, "Testing"); // Hangs here
> Console.WriteLine("Wait");
> await Task.Delay(Timeout.Infinite);
> {code}
> async/await should absolutely not allow any client code to be run from
> stripes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster
[
https://issues.apache.org/jira/browse/IGNITE-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-12033:
Comment: was deleted
(was: {panel:title=Branch: [pull/8870/head] Base: [master] : Possible Blockers
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Java Client{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5964646]]
{color:#d04437}Cache 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5964683]]
* IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationListenerExecutesOnStripedPoolWhenCustomExecutorIsProvided
- History for base branch is absent.
* IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationChainContinuesOnDefaultExecutor
- History for base branch is absent.
{color:#d04437}Thin Client: Java{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5964649]]
{panel}
{panel:title=Branch: [pull/8870/head] Base: [master] : New Tests
(16)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=5964703]]
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeExecuteAsyncContinuation
- PASSED{color}
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeRunAsyncContinuation -
PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestSynchronousExecutorRunsContinuationsOnStripedPool -
PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestInvalidExecutorConfigurationFailsOnStart - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestLocalOperationExecutesSynchronously - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestAsyncAwaitContinuationIsExecutedWithConfiguredExecutor
- PASSED{color}
{color:#8b}Cache 1{color} [[tests
10|https://ci.ignite.apache.org/viewLog.html?buildId=5964683]]
* {color:#8b}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationListenerExecutesOnStripedPoolWhenCustomExecutorIsProvided
- FAILED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testRemoteOperationListenerExecutesOnStripedPoolWhenCustomExecutorIsProvided
- PASSED{color}
* {color:#8b}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationChainContinuesOnDefaultExecutor
- FAILED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testLocalOperationListenerExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testLocalOperationChainExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationListenContinuesOnDefaultExecutor
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testRemoteOperationChainContinuesOnDefaultExecutor
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testLocalOperationListenerExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testLocalOperationChainExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testRemoteOperationListenContinuesOnDefaultExecutor
- PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5964729buildTypeId=IgniteTests24Java8_RunAll])
> Callbacks from striped pool due to async/await may hang cluster
> ---
>
> Key: IGNITE-12033
> URL: https://issues.apache.org/jira/browse/IGNITE-12033
> Project: Ignite
> Issue Type: Bug
> Components: cache, platforms
>Affects Versions: 2.7.5
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: iep-70
> Fix For: 2.11
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Discussed on dev-list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Re-EXTERNAL-Re-Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td42921.html
> *Must use the public pool for callbacks as the most obvious step.*
>
> http://apache-ignite-users.70518.x6.nabble.com/Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td27871.html#a28051
> There's a reproducer project. Long story short, .Net can invoke cache
> operations with future callbacks, which will be invoked from striped pool. If
> such callbacks are to use cache operations, those will be possibly sheduled
> to the same stripe and cause a deadlock.
[jira] [Updated] (IGNITE-14331) Possible distributed race related to a data streamer flushing leading to a thread being stuck forever trying to close the streamer
[
https://issues.apache.org/jira/browse/IGNITE-14331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-14331:
-
Reviewer: Vyacheslav Koptilin (was: Slava Koptilin)
> Possible distributed race related to a data streamer flushing leading to a
> thread being stuck forever trying to close the streamer
> --
>
> Key: IGNITE-14331
> URL: https://issues.apache.org/jira/browse/IGNITE-14331
> Project: Ignite
> Issue Type: Bug
> Components: streaming
>Affects Versions: 2.10
>Reporter: Vladimir Pligin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It seems that a streamer could stuck forever flushing internal buffers on a
> client side.
> It will stay in a busy-loop forever hoping on remapping but it's possible
> that it won't happen for example in case of long GC pauses on server(s) and
> long timeouts.
> It that case a streamer would be trapped inside this
> [loop|https://github.com/apache/ignite/blob/ignite-2.10/modules/core/src/main/java/org/apache/ignite/internal/processors/datastreamer/DataStreamerImpl.java#L1168].
> Stack trace snippet:
> {code:java}
> java.lang.Thread.State: RUNNABLE at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.flush(DataStreamerImpl.java:1706)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.doFlush(DataStreamerImpl.java:1170)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.closeEx(DataStreamerImpl.java:1365)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.closeEx(DataStreamerImpl.java:1323)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.close(DataStreamerImpl.java:1311)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.close(DataStreamerImpl.java:1415){code}
>
> It becomes possible when a
> IgniteSpiOperationTimeoutException
> is being thrown from
> org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic()
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14533) [Ignite Website] Update for top line event promotion
[ https://issues.apache.org/jira/browse/IGNITE-14533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kseniya Romanova updated IGNITE-14533: -- Description: [~mstekl], please change the topline event promotion for the next meetup: April 28, 2021: Apache Ignite Native Persistence Storage. Overview by Ignite Developer [https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/277298901/] was: @mstekl please change the topline event promotion for the next meetup: April 28, 2021: Apache Ignite Native Persistence Storage. Overview by Ignite Developer https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/277298901/ > [Ignite Website] Update for top line event promotion > > > Key: IGNITE-14533 > URL: https://issues.apache.org/jira/browse/IGNITE-14533 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Priority: Minor > > [~mstekl], please change the topline event promotion for the next meetup: > > April 28, 2021: Apache Ignite Native Persistence Storage. Overview by Ignite > Developer > [https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/277298901/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14533) [Ignite Website] Update for top line event promotion
[ https://issues.apache.org/jira/browse/IGNITE-14533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kseniya Romanova updated IGNITE-14533: -- Description: @mstekl please change the topline event promotion for the next meetup: April 28, 2021: Apache Ignite Native Persistence Storage. Overview by Ignite Developer https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/277298901/ was: @mstekl please change the topline event promotion for the next meetup: [April 28, 2021: Apache Ignite Native Persistence Storage. Overview by Ignite Developer|https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/277298901/ > [Ignite Website] Update for top line event promotion > > > Key: IGNITE-14533 > URL: https://issues.apache.org/jira/browse/IGNITE-14533 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Priority: Minor > > @mstekl please change the topline event promotion for the next meetup: > > April 28, 2021: Apache Ignite Native Persistence Storage. Overview by Ignite > Developer > https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/277298901/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14533) [Ignite Website] Update for top line event promotion
Kseniya Romanova created IGNITE-14533: - Summary: [Ignite Website] Update for top line event promotion Key: IGNITE-14533 URL: https://issues.apache.org/jira/browse/IGNITE-14533 Project: Ignite Issue Type: Task Components: website Reporter: Kseniya Romanova @mstekl please change the topline event promotion for the next meetup: [April 28, 2021: Apache Ignite Native Persistence Storage. Overview by Ignite Developer|https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/277298901/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14532) Thin client: Unordered map used for putAll warning is unavoidable
[
https://issues.apache.org/jira/browse/IGNITE-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14532:
Description:
Thin client uses LinkedHashMap to preserve client-side entry order. Ignite logs
a warning and there is no way to fix it for the user:
{code}
Unordered map java.util.HashMap is used for putAll operation on cache exact.
This can lead to a distributed deadlock. Switch to a sorted map like TreeMap
instead.
{code}
We should suppress this warning for thin client operations, since it does not
make sense. Thin clients have different language-specific APIs, some of them
don't even use maps. The same applies to PlatformCache (thick C# & C++).
We should have an internal method that does not produce a warning, and,
ideally, does not require a Map. Using LinkedHashMap as an intermediate
collection produces unnecessary overhead and allocations, we could use an array
of key-value pairs instead.
was:
Thin client uses LinkedHashMap to preserve client-side entry order. Ignite logs
a warning and there is no way to fix it for the user:
{code}
Unordered map java.util.HashMap is used for putAll operation on cache exact.
This can lead to a distributed deadlock. Switch to a sorted map like TreeMap
instead.
{code}
We should suppress this warning for thin client operations, since it does not
make sense. Thin clients have different language-specific APIs, some of them
don't even use maps.
The same applies to PlatformCache (thick C# & C++).
> Thin client: Unordered map used for putAll warning is unavoidable
> -
>
> Key: IGNITE-14532
> URL: https://issues.apache.org/jira/browse/IGNITE-14532
> Project: Ignite
> Issue Type: New Feature
> Components: thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.11
>
>
> Thin client uses LinkedHashMap to preserve client-side entry order. Ignite
> logs a warning and there is no way to fix it for the user:
> {code}
> Unordered map java.util.HashMap is used for putAll operation on cache exact.
> This can lead to a distributed deadlock. Switch to a sorted map like TreeMap
> instead.
> {code}
> We should suppress this warning for thin client operations, since it does not
> make sense. Thin clients have different language-specific APIs, some of them
> don't even use maps. The same applies to PlatformCache (thick C# & C++).
> We should have an internal method that does not produce a warning, and,
> ideally, does not require a Map. Using LinkedHashMap as an intermediate
> collection produces unnecessary overhead and allocations, we could use an
> array of key-value pairs instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[
https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320434#comment-17320434
]
Ignite TC Bot commented on IGNITE-14346:
{panel:title=Branch: [pull/8897/head] Base: [master] : Possible Blockers
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Core Linux){color} [[tests 1 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=5965398]]
* dll: CacheQueriesTest.TestScanQueryPartitions(True) - Test has low fail rate
in base branch 0,0% and is not flaky
{color:#d04437}[Missing Tests]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5965422]]
{panel}
{panel:title=Branch: [pull/8897/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5965424buildTypeId=IgniteTests24Java8_RunAll]
> Implement Azure Blob Storage Based IP Finder
>
>
> Key: IGNITE-14346
> URL: https://issues.apache.org/jira/browse/IGNITE-14346
> Project: Ignite
> Issue Type: Improvement
>Reporter: Atri Sharma
>Assignee: Atri Sharma
>Priority: Major
> Labels: ReviewNeeded
> Attachments: Screenshot 2021-03-23 at 8.42.31 PM.png, Screenshot
> 2021-03-23 at 8.43.31 PM.png, Screenshot 2021-03-23 at 8.44.11 PM.png,
> Screenshot 2021-03-23 at 8.45.05 PM.png, azure-container.png
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14523) Support for string.Compare method in Apache Ignite LINQ provider
[ https://issues.apache.org/jira/browse/IGNITE-14523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-14523: Labels: .NET (was: ) > Support for string.Compare method in Apache Ignite LINQ provider > > > Key: IGNITE-14523 > URL: https://issues.apache.org/jira/browse/IGNITE-14523 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 2.9.1 >Reporter: Oleg Bevz >Assignee: Oleg Bevz >Priority: Critical > Labels: .NET > Fix For: 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Hello, currently Apache Ignite does not support string comparison for LINQ > provider (Apache.Ignite.Linq project). > For example following modified query > insideThinClientQueryExample.ScanQueryExample method will throw Exception: > var employees = cache.AsCacheQueryable().Select(x => x.Value).Where(x => > string.Compare(x.Name, "Daniel Adams") >= 0); > Business case: in our project we use DevExteme.AspNet.Data library to build > LINQ queries for Apache Ignite and in some cases the library builds complex > queries with string.Compare method call. > Exception details: > Exception has been thrown by the target of an invocation. > System.Reflection.TargetInvocationException System.Object > InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) > System.Reflection.TargetInvocationException: Exception has been thrown by the > target of an invocation. ---> System.NotSupportedException: Method not > supported: System.String.(Int32 Compare(System.String, System.String)) > at > Apache.Ignite.Linq.Impl.MethodVisitor.VisitMethodCall(MethodCallExpression > expression, CacheQueryExpressionVisitor visitor) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitMethodCall(MethodCallExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitWhereClause(WhereClause > whereClause, Int32 index, Boolean hasGroups) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.ProcessGroupings(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitBodyClauses(ObservableCollection`1 > bodyClauses, QueryModel queryModel) > at Remotion.Linq.QueryModelVisitorBase.VisitQueryModel(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitQueryModel(QueryModel > queryModel, Boolean includeAllFields, Boolean copyAliases) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.GenerateQuery(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryExecutor.ExecuteCollection[T](QueryModel > queryModel) > at > Remotion.Linq.Clauses.StreamedData.StreamedSequenceInfo.ExecuteQueryModel(QueryModel > queryModel, IQueryExecutor executor) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryProvider.Execute[TResult](Expression > expression) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14523) Support for string.Compare method in Apache Ignite LINQ provider
[ https://issues.apache.org/jira/browse/IGNITE-14523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-14523: Component/s: (was: thin client) platforms > Support for string.Compare method in Apache Ignite LINQ provider > > > Key: IGNITE-14523 > URL: https://issues.apache.org/jira/browse/IGNITE-14523 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 2.9.1 >Reporter: Oleg Bevz >Assignee: Oleg Bevz >Priority: Critical > Fix For: 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Hello, currently Apache Ignite does not support string comparison for LINQ > provider (Apache.Ignite.Linq project). > For example following modified query > insideThinClientQueryExample.ScanQueryExample method will throw Exception: > var employees = cache.AsCacheQueryable().Select(x => x.Value).Where(x => > string.Compare(x.Name, "Daniel Adams") >= 0); > Business case: in our project we use DevExteme.AspNet.Data library to build > LINQ queries for Apache Ignite and in some cases the library builds complex > queries with string.Compare method call. > Exception details: > Exception has been thrown by the target of an invocation. > System.Reflection.TargetInvocationException System.Object > InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) > System.Reflection.TargetInvocationException: Exception has been thrown by the > target of an invocation. ---> System.NotSupportedException: Method not > supported: System.String.(Int32 Compare(System.String, System.String)) > at > Apache.Ignite.Linq.Impl.MethodVisitor.VisitMethodCall(MethodCallExpression > expression, CacheQueryExpressionVisitor visitor) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitMethodCall(MethodCallExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitWhereClause(WhereClause > whereClause, Int32 index, Boolean hasGroups) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.ProcessGroupings(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitBodyClauses(ObservableCollection`1 > bodyClauses, QueryModel queryModel) > at Remotion.Linq.QueryModelVisitorBase.VisitQueryModel(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitQueryModel(QueryModel > queryModel, Boolean includeAllFields, Boolean copyAliases) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.GenerateQuery(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryExecutor.ExecuteCollection[T](QueryModel > queryModel) > at > Remotion.Linq.Clauses.StreamedData.StreamedSequenceInfo.ExecuteQueryModel(QueryModel > queryModel, IQueryExecutor executor) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryProvider.Execute[TResult](Expression > expression) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14523) Support for string.Compare method in Apache Ignite LINQ provider
[ https://issues.apache.org/jira/browse/IGNITE-14523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-14523: Priority: Minor (was: Critical) > Support for string.Compare method in Apache Ignite LINQ provider > > > Key: IGNITE-14523 > URL: https://issues.apache.org/jira/browse/IGNITE-14523 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 2.9.1 >Reporter: Oleg Bevz >Assignee: Oleg Bevz >Priority: Minor > Labels: .NET > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > Hello, currently Apache Ignite does not support string comparison for LINQ > provider (Apache.Ignite.Linq project). > For example following modified query > insideThinClientQueryExample.ScanQueryExample method will throw Exception: > var employees = cache.AsCacheQueryable().Select(x => x.Value).Where(x => > string.Compare(x.Name, "Daniel Adams") >= 0); > Business case: in our project we use DevExteme.AspNet.Data library to build > LINQ queries for Apache Ignite and in some cases the library builds complex > queries with string.Compare method call. > Exception details: > Exception has been thrown by the target of an invocation. > System.Reflection.TargetInvocationException System.Object > InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) > System.Reflection.TargetInvocationException: Exception has been thrown by the > target of an invocation. ---> System.NotSupportedException: Method not > supported: System.String.(Int32 Compare(System.String, System.String)) > at > Apache.Ignite.Linq.Impl.MethodVisitor.VisitMethodCall(MethodCallExpression > expression, CacheQueryExpressionVisitor visitor) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitMethodCall(MethodCallExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitWhereClause(WhereClause > whereClause, Int32 index, Boolean hasGroups) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.ProcessGroupings(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitBodyClauses(ObservableCollection`1 > bodyClauses, QueryModel queryModel) > at Remotion.Linq.QueryModelVisitorBase.VisitQueryModel(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitQueryModel(QueryModel > queryModel, Boolean includeAllFields, Boolean copyAliases) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.GenerateQuery(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryExecutor.ExecuteCollection[T](QueryModel > queryModel) > at > Remotion.Linq.Clauses.StreamedData.StreamedSequenceInfo.ExecuteQueryModel(QueryModel > queryModel, IQueryExecutor executor) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryProvider.Execute[TResult](Expression > expression) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14523) Support for string.Compare method in Apache Ignite LINQ provider
[ https://issues.apache.org/jira/browse/IGNITE-14523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-14523: Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Support for string.Compare method in Apache Ignite LINQ provider > > > Key: IGNITE-14523 > URL: https://issues.apache.org/jira/browse/IGNITE-14523 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 2.9.1 >Reporter: Oleg Bevz >Assignee: Oleg Bevz >Priority: Minor > Labels: .NET > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > Hello, currently Apache Ignite does not support string comparison for LINQ > provider (Apache.Ignite.Linq project). > For example following modified query > insideThinClientQueryExample.ScanQueryExample method will throw Exception: > var employees = cache.AsCacheQueryable().Select(x => x.Value).Where(x => > string.Compare(x.Name, "Daniel Adams") >= 0); > Business case: in our project we use DevExteme.AspNet.Data library to build > LINQ queries for Apache Ignite and in some cases the library builds complex > queries with string.Compare method call. > Exception details: > Exception has been thrown by the target of an invocation. > System.Reflection.TargetInvocationException System.Object > InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) > System.Reflection.TargetInvocationException: Exception has been thrown by the > target of an invocation. ---> System.NotSupportedException: Method not > supported: System.String.(Int32 Compare(System.String, System.String)) > at > Apache.Ignite.Linq.Impl.MethodVisitor.VisitMethodCall(MethodCallExpression > expression, CacheQueryExpressionVisitor visitor) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitMethodCall(MethodCallExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitWhereClause(WhereClause > whereClause, Int32 index, Boolean hasGroups) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.ProcessGroupings(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitBodyClauses(ObservableCollection`1 > bodyClauses, QueryModel queryModel) > at Remotion.Linq.QueryModelVisitorBase.VisitQueryModel(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitQueryModel(QueryModel > queryModel, Boolean includeAllFields, Boolean copyAliases) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.GenerateQuery(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryExecutor.ExecuteCollection[T](QueryModel > queryModel) > at > Remotion.Linq.Clauses.StreamedData.StreamedSequenceInfo.ExecuteQueryModel(QueryModel > queryModel, IQueryExecutor executor) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryProvider.Execute[TResult](Expression > expression) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14523) Support for string.Compare method in Apache Ignite LINQ provider
[ https://issues.apache.org/jira/browse/IGNITE-14523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-14523: Fix Version/s: (was: 2.9.1) 2.11 > Support for string.Compare method in Apache Ignite LINQ provider > > > Key: IGNITE-14523 > URL: https://issues.apache.org/jira/browse/IGNITE-14523 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 2.9.1 >Reporter: Oleg Bevz >Assignee: Oleg Bevz >Priority: Critical > Labels: .NET > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > Hello, currently Apache Ignite does not support string comparison for LINQ > provider (Apache.Ignite.Linq project). > For example following modified query > insideThinClientQueryExample.ScanQueryExample method will throw Exception: > var employees = cache.AsCacheQueryable().Select(x => x.Value).Where(x => > string.Compare(x.Name, "Daniel Adams") >= 0); > Business case: in our project we use DevExteme.AspNet.Data library to build > LINQ queries for Apache Ignite and in some cases the library builds complex > queries with string.Compare method call. > Exception details: > Exception has been thrown by the target of an invocation. > System.Reflection.TargetInvocationException System.Object > InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) > System.Reflection.TargetInvocationException: Exception has been thrown by the > target of an invocation. ---> System.NotSupportedException: Method not > supported: System.String.(Int32 Compare(System.String, System.String)) > at > Apache.Ignite.Linq.Impl.MethodVisitor.VisitMethodCall(MethodCallExpression > expression, CacheQueryExpressionVisitor visitor) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitMethodCall(MethodCallExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitWhereClause(WhereClause > whereClause, Int32 index, Boolean hasGroups) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.ProcessGroupings(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitBodyClauses(ObservableCollection`1 > bodyClauses, QueryModel queryModel) > at Remotion.Linq.QueryModelVisitorBase.VisitQueryModel(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitQueryModel(QueryModel > queryModel, Boolean includeAllFields, Boolean copyAliases) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.GenerateQuery(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryExecutor.ExecuteCollection[T](QueryModel > queryModel) > at > Remotion.Linq.Clauses.StreamedData.StreamedSequenceInfo.ExecuteQueryModel(QueryModel > queryModel, IQueryExecutor executor) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryProvider.Execute[TResult](Expression > expression) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14523) Support for string.Compare method in Apache Ignite LINQ provider
[ https://issues.apache.org/jira/browse/IGNITE-14523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320417#comment-17320417 ] Pavel Tupitsyn commented on IGNITE-14523: - [~olegbevz] thank you for the contribution - please see my comments on GitHub. > Support for string.Compare method in Apache Ignite LINQ provider > > > Key: IGNITE-14523 > URL: https://issues.apache.org/jira/browse/IGNITE-14523 > Project: Ignite > Issue Type: New Feature > Components: thin client >Affects Versions: 2.9.1 >Reporter: Oleg Bevz >Assignee: Oleg Bevz >Priority: Critical > Fix For: 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Hello, currently Apache Ignite does not support string comparison for LINQ > provider (Apache.Ignite.Linq project). > For example following modified query > insideThinClientQueryExample.ScanQueryExample method will throw Exception: > var employees = cache.AsCacheQueryable().Select(x => x.Value).Where(x => > string.Compare(x.Name, "Daniel Adams") >= 0); > Business case: in our project we use DevExteme.AspNet.Data library to build > LINQ queries for Apache Ignite and in some cases the library builds complex > queries with string.Compare method call. > Exception details: > Exception has been thrown by the target of an invocation. > System.Reflection.TargetInvocationException System.Object > InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) > System.Reflection.TargetInvocationException: Exception has been thrown by the > target of an invocation. ---> System.NotSupportedException: Method not > supported: System.String.(Int32 Compare(System.String, System.String)) > at > Apache.Ignite.Linq.Impl.MethodVisitor.VisitMethodCall(MethodCallExpression > expression, CacheQueryExpressionVisitor visitor) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitMethodCall(MethodCallExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitWhereClause(WhereClause > whereClause, Int32 index, Boolean hasGroups) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.ProcessGroupings(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitBodyClauses(ObservableCollection`1 > bodyClauses, QueryModel queryModel) > at Remotion.Linq.QueryModelVisitorBase.VisitQueryModel(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitQueryModel(QueryModel > queryModel, Boolean includeAllFields, Boolean copyAliases) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.GenerateQuery(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryExecutor.ExecuteCollection[T](QueryModel > queryModel) > at > Remotion.Linq.Clauses.StreamedData.StreamedSequenceInfo.ExecuteQueryModel(QueryModel > queryModel, IQueryExecutor executor) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryProvider.Execute[TResult](Expression > expression) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14532) Thin client: Unordered map used for putAll warning is unavoidable
[
https://issues.apache.org/jira/browse/IGNITE-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14532:
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> Thin client: Unordered map used for putAll warning is unavoidable
> -
>
> Key: IGNITE-14532
> URL: https://issues.apache.org/jira/browse/IGNITE-14532
> Project: Ignite
> Issue Type: New Feature
> Components: thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.11
>
>
> Thin client uses LinkedHashMap to preserve client-side entry order. Ignite
> logs a warning and there is no way to fix it for the user:
> {code}
> Unordered map java.util.HashMap is used for putAll operation on cache exact.
> This can lead to a distributed deadlock. Switch to a sorted map like TreeMap
> instead.
> {code}
> We should suppress this warning for thin client operations, since it does not
> make sense. Thin clients have different language-specific APIs, some of them
> don't even use maps.
> The same applies to PlatformCache (thick C# & C++).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14532) Thin client: Unordered map used for putAll warning is unavoidable
Pavel Tupitsyn created IGNITE-14532:
---
Summary: Thin client: Unordered map used for putAll warning is
unavoidable
Key: IGNITE-14532
URL: https://issues.apache.org/jira/browse/IGNITE-14532
Project: Ignite
Issue Type: New Feature
Components: thin client
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: 2.11
Thin client uses LinkedHashMap to preserve client-side entry order. Ignite logs
a warning and there is no way to fix it for the user:
{code}
Unordered map java.util.HashMap is used for putAll operation on cache exact.
This can lead to a distributed deadlock. Switch to a sorted map like TreeMap
instead.
{code}
We should suppress this warning for thin client operations, since it does not
make sense. Thin clients have different language-specific APIs, some of them
don't even use maps.
The same applies to PlatformCache (thick C# & C++).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14523) Support for string.Compare method in Apache Ignite LINQ provider
[ https://issues.apache.org/jira/browse/IGNITE-14523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-14523: --- Assignee: Oleg Bevz > Support for string.Compare method in Apache Ignite LINQ provider > > > Key: IGNITE-14523 > URL: https://issues.apache.org/jira/browse/IGNITE-14523 > Project: Ignite > Issue Type: New Feature > Components: thin client >Affects Versions: 2.9.1 >Reporter: Oleg Bevz >Assignee: Oleg Bevz >Priority: Critical > Fix For: 2.9.1 > > Time Spent: 10m > Remaining Estimate: 0h > > Hello, currently Apache Ignite does not support string comparison for LINQ > provider (Apache.Ignite.Linq project). > For example following modified query > insideThinClientQueryExample.ScanQueryExample method will throw Exception: > var employees = cache.AsCacheQueryable().Select(x => x.Value).Where(x => > string.Compare(x.Name, "Daniel Adams") >= 0); > Business case: in our project we use DevExteme.AspNet.Data library to build > LINQ queries for Apache Ignite and in some cases the library builds complex > queries with string.Compare method call. > Exception details: > Exception has been thrown by the target of an invocation. > System.Reflection.TargetInvocationException System.Object > InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) > System.Reflection.TargetInvocationException: Exception has been thrown by the > target of an invocation. ---> System.NotSupportedException: Method not > supported: System.String.(Int32 Compare(System.String, System.String)) > at > Apache.Ignite.Linq.Impl.MethodVisitor.VisitMethodCall(MethodCallExpression > expression, CacheQueryExpressionVisitor visitor) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitMethodCall(MethodCallExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitWhereClause(WhereClause > whereClause, Int32 index, Boolean hasGroups) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.ProcessGroupings(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitBodyClauses(ObservableCollection`1 > bodyClauses, QueryModel queryModel) > at Remotion.Linq.QueryModelVisitorBase.VisitQueryModel(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitQueryModel(QueryModel > queryModel, Boolean includeAllFields, Boolean copyAliases) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.GenerateQuery(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryExecutor.ExecuteCollection[T](QueryModel > queryModel) > at > Remotion.Linq.Clauses.StreamedData.StreamedSequenceInfo.ExecuteQueryModel(QueryModel > queryModel, IQueryExecutor executor) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryProvider.Execute[TResult](Expression > expression) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14523) Support for string.Compare method in Apache Ignite LINQ provider
[ https://issues.apache.org/jira/browse/IGNITE-14523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-14523: --- Assignee: Pavel Tupitsyn (was: Oleg Bevz) > Support for string.Compare method in Apache Ignite LINQ provider > > > Key: IGNITE-14523 > URL: https://issues.apache.org/jira/browse/IGNITE-14523 > Project: Ignite > Issue Type: New Feature > Components: thin client >Affects Versions: 2.9.1 >Reporter: Oleg Bevz >Assignee: Pavel Tupitsyn >Priority: Critical > Fix For: 2.9.1 > > Time Spent: 10m > Remaining Estimate: 0h > > Hello, currently Apache Ignite does not support string comparison for LINQ > provider (Apache.Ignite.Linq project). > For example following modified query > insideThinClientQueryExample.ScanQueryExample method will throw Exception: > var employees = cache.AsCacheQueryable().Select(x => x.Value).Where(x => > string.Compare(x.Name, "Daniel Adams") >= 0); > Business case: in our project we use DevExteme.AspNet.Data library to build > LINQ queries for Apache Ignite and in some cases the library builds complex > queries with string.Compare method call. > Exception details: > Exception has been thrown by the target of an invocation. > System.Reflection.TargetInvocationException System.Object > InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) > System.Reflection.TargetInvocationException: Exception has been thrown by the > target of an invocation. ---> System.NotSupportedException: Method not > supported: System.String.(Int32 Compare(System.String, System.String)) > at > Apache.Ignite.Linq.Impl.MethodVisitor.VisitMethodCall(MethodCallExpression > expression, CacheQueryExpressionVisitor visitor) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitMethodCall(MethodCallExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitWhereClause(WhereClause > whereClause, Int32 index, Boolean hasGroups) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.ProcessGroupings(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitBodyClauses(ObservableCollection`1 > bodyClauses, QueryModel queryModel) > at Remotion.Linq.QueryModelVisitorBase.VisitQueryModel(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitQueryModel(QueryModel > queryModel, Boolean includeAllFields, Boolean copyAliases) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.GenerateQuery(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryExecutor.ExecuteCollection[T](QueryModel > queryModel) > at > Remotion.Linq.Clauses.StreamedData.StreamedSequenceInfo.ExecuteQueryModel(QueryModel > queryModel, IQueryExecutor executor) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryProvider.Execute[TResult](Expression > expression) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14523) Support for string.Compare method in Apache Ignite LINQ provider
[ https://issues.apache.org/jira/browse/IGNITE-14523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-14523: --- Assignee: Oleg Bevz (was: Pavel Tupitsyn) > Support for string.Compare method in Apache Ignite LINQ provider > > > Key: IGNITE-14523 > URL: https://issues.apache.org/jira/browse/IGNITE-14523 > Project: Ignite > Issue Type: New Feature > Components: thin client >Affects Versions: 2.9.1 >Reporter: Oleg Bevz >Assignee: Oleg Bevz >Priority: Critical > Fix For: 2.9.1 > > Time Spent: 10m > Remaining Estimate: 0h > > Hello, currently Apache Ignite does not support string comparison for LINQ > provider (Apache.Ignite.Linq project). > For example following modified query > insideThinClientQueryExample.ScanQueryExample method will throw Exception: > var employees = cache.AsCacheQueryable().Select(x => x.Value).Where(x => > string.Compare(x.Name, "Daniel Adams") >= 0); > Business case: in our project we use DevExteme.AspNet.Data library to build > LINQ queries for Apache Ignite and in some cases the library builds complex > queries with string.Compare method call. > Exception details: > Exception has been thrown by the target of an invocation. > System.Reflection.TargetInvocationException System.Object > InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) > System.Reflection.TargetInvocationException: Exception has been thrown by the > target of an invocation. ---> System.NotSupportedException: Method not > supported: System.String.(Int32 Compare(System.String, System.String)) > at > Apache.Ignite.Linq.Impl.MethodVisitor.VisitMethodCall(MethodCallExpression > expression, CacheQueryExpressionVisitor visitor) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitMethodCall(MethodCallExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitWhereClause(WhereClause > whereClause, Int32 index, Boolean hasGroups) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.ProcessGroupings(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitBodyClauses(ObservableCollection`1 > bodyClauses, QueryModel queryModel) > at Remotion.Linq.QueryModelVisitorBase.VisitQueryModel(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitQueryModel(QueryModel > queryModel, Boolean includeAllFields, Boolean copyAliases) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.GenerateQuery(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryExecutor.ExecuteCollection[T](QueryModel > queryModel) > at > Remotion.Linq.Clauses.StreamedData.StreamedSequenceInfo.ExecuteQueryModel(QueryModel > queryModel, IQueryExecutor executor) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryProvider.Execute[TResult](Expression > expression) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14385) Add checkpoit information to performance statistics.
[
https://issues.apache.org/jira/browse/IGNITE-14385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320232#comment-17320232
]
Ignite TC Bot commented on IGNITE-14385:
{panel:title=Branch: [pull/8928/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8928/head] Base: [master] : New Tests
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Basic 3{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=5964771]]
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
CheckpointTest.testThrottleTargetRatioBased - PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
CheckpointTest.testThrottleSpeedBased - PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
CheckpointTest.testCheckpoint - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5964832buildTypeId=IgniteTests24Java8_RunAll]
> Add checkpoit information to performance statistics.
>
>
> Key: IGNITE-14385
> URL: https://issues.apache.org/jira/browse/IGNITE-14385
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Sergei Ryzhov
>Assignee: Sergei Ryzhov
>Priority: Minor
> Labels: IEP-35
> Time Spent: 8h
> Remaining Estimate: 0h
>
> Add start/end time and other parameters of checkpoint to performance
> statistics.
> Add information about throttling if necessary
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14531) Calcite improvements. Support DISTINCT for aggregates call at the execution
Taras Ledkov created IGNITE-14531:
-
Summary: Calcite improvements. Support DISTINCT for aggregates
call at the execution
Key: IGNITE-14531
URL: https://issues.apache.org/jira/browse/IGNITE-14531
Project: Ignite
Issue Type: Improvement
Reporter: Taras Ledkov
Now {{Accumulators#accumulatorFactory}} and all implementation of the
{{Accumulator}} doesn't support DISTINCT (see {{AggregateCall#isDistinct}}).
Must be implemented.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14529) Add offline utility for analyzing indexes
[ https://issues.apache.org/jira/browse/IGNITE-14529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Chudov reassigned IGNITE-14529: - Assignee: Denis Chudov > Add offline utility for analyzing indexes > - > > Key: IGNITE-14529 > URL: https://issues.apache.org/jira/browse/IGNITE-14529 > Project: Ignite > Issue Type: Improvement >Reporter: Denis Chudov >Assignee: Denis Chudov >Priority: Major > > It would be useful to have the possibility for indexes offline validation. > The utility must check that every configured index (available in MetaTree > [1]) is reachable from corresponding root page, tree structure is valid and > no orphan(unreachable) index pages are present in the index.bin persistent > page store. > [1] > org.apache.ignite.internal.processors.cache.persistence.IndexStorageImpl#getIndexNames -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14530) Add offline utility for analyzing WAL
Denis Chudov created IGNITE-14530: - Summary: Add offline utility for analyzing WAL Key: IGNITE-14530 URL: https://issues.apache.org/jira/browse/IGNITE-14530 Project: Ignite Issue Type: Improvement Reporter: Denis Chudov It would be useful for investigating problems of data consistency, PDS and other to have the possibility of reading WAL files in offline. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14529) Add offline utility for analyzing indexes
Denis Chudov created IGNITE-14529: - Summary: Add offline utility for analyzing indexes Key: IGNITE-14529 URL: https://issues.apache.org/jira/browse/IGNITE-14529 Project: Ignite Issue Type: Improvement Reporter: Denis Chudov It would be useful to have the possibility for indexes offline validation. The utility must check that every configured index (available in MetaTree [1]) is reachable from corresponding root page, tree structure is valid and no orphan(unreachable) index pages are present in the index.bin persistent page store. [1] org.apache.ignite.internal.processors.cache.persistence.IndexStorageImpl#getIndexNames -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14077) Implement distributed SchemaManager.
[ https://issues.apache.org/jira/browse/IGNITE-14077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-14077: -- Description: Create SchemaManager API and implement schema manager backed by distributed metastorage with schema versioning logic for the "strict-schema" case. was: Create SchemaManager API and implement schema versioning logic backed by distributed metastorage. > Implement distributed SchemaManager. > > > Key: IGNITE-14077 > URL: https://issues.apache.org/jira/browse/IGNITE-14077 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > Fix For: 3.0.0-alpha2 > > Time Spent: 10m > Remaining Estimate: 0h > > Create SchemaManager API and implement schema manager backed by distributed > metastorage > with schema versioning logic for the "strict-schema" case. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14462) Enable EmptyCatchBlock checkstyle check
[
https://issues.apache.org/jira/browse/IGNITE-14462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320146#comment-17320146
]
Maxim Muzafarov commented on IGNITE-14462:
--
Merged to the master branch, thank you for the review.
> Enable EmptyCatchBlock checkstyle check
> ---
>
> Key: IGNITE-14462
> URL: https://issues.apache.org/jira/browse/IGNITE-14462
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Checks for empty catch blocks. By default, check allows an empty catch block
> with any comment inside.
>
> {code}
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14523) Support for string.Compare method in Apache Ignite LINQ provider
[ https://issues.apache.org/jira/browse/IGNITE-14523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320134#comment-17320134 ] Oleg Bevz commented on IGNITE-14523: [~ptupitsyn] please review my PR > Support for string.Compare method in Apache Ignite LINQ provider > > > Key: IGNITE-14523 > URL: https://issues.apache.org/jira/browse/IGNITE-14523 > Project: Ignite > Issue Type: New Feature > Components: thin client >Affects Versions: 2.9.1 >Reporter: Oleg Bevz >Priority: Critical > Fix For: 2.9.1 > > Time Spent: 10m > Remaining Estimate: 0h > > Hello, currently Apache Ignite does not support string comparison for LINQ > provider (Apache.Ignite.Linq project). > For example following modified query > insideThinClientQueryExample.ScanQueryExample method will throw Exception: > var employees = cache.AsCacheQueryable().Select(x => x.Value).Where(x => > string.Compare(x.Name, "Daniel Adams") >= 0); > Business case: in our project we use DevExteme.AspNet.Data library to build > LINQ queries for Apache Ignite and in some cases the library builds complex > queries with string.Compare method call. > Exception details: > Exception has been thrown by the target of an invocation. > System.Reflection.TargetInvocationException System.Object > InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) > System.Reflection.TargetInvocationException: Exception has been thrown by the > target of an invocation. ---> System.NotSupportedException: Method not > supported: System.String.(Int32 Compare(System.String, System.String)) > at > Apache.Ignite.Linq.Impl.MethodVisitor.VisitMethodCall(MethodCallExpression > expression, CacheQueryExpressionVisitor visitor) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitMethodCall(MethodCallExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitWhereClause(WhereClause > whereClause, Int32 index, Boolean hasGroups) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.ProcessGroupings(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitBodyClauses(ObservableCollection`1 > bodyClauses, QueryModel queryModel) > at Remotion.Linq.QueryModelVisitorBase.VisitQueryModel(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitQueryModel(QueryModel > queryModel, Boolean includeAllFields, Boolean copyAliases) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.GenerateQuery(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryExecutor.ExecuteCollection[T](QueryModel > queryModel) > at > Remotion.Linq.Clauses.StreamedData.StreamedSequenceInfo.ExecuteQueryModel(QueryModel > queryModel, IQueryExecutor executor) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryProvider.Execute[TResult](Expression > expression) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14528) AssertionError in GridDhtPartitionDemander$RebalanceFuture.ownPartitionsAndFinishFuture:1528
Denis Chudov created IGNITE-14528:
-
Summary: AssertionError in
GridDhtPartitionDemander$RebalanceFuture.ownPartitionsAndFinishFuture:1528
Key: IGNITE-14528
URL: https://issues.apache.org/jira/browse/IGNITE-14528
Project: Ignite
Issue Type: Bug
Reporter: Denis Chudov
Assignee: Denis Chudov
the fall of the node during a rebalance
{code:java}
2021-01-31
07:45:29.174[ERROR][exchange-worker-#168%DPL_GRID%DplGridNodeName%][org.apache.ignite.Ignite]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION,
err=java.lang.AssertionError: RebalanceFuture [grp=CacheGroupContext
[grp=CACHEGROUP_OBJECT_TO_EVICTION_REGISTRY], topVer=AffinityTopologyVersion
[topVer=46, minorTopVer=0], rebalanceId=27299, routines=22, receivedBytes=0,
receivedKeys=0, partitionsLeft=1659, startTime=-1, endTime=-1,
lastCancelledTime=1612068328290, result=true]]]
java.lang.AssertionError: RebalanceFuture [grp=CacheGroupContext
[grp=CACHEGROUP_OBJECT_TO_EVICTION_REGISTRY], topVer=AffinityTopologyVersion
[topVer=46, minorTopVer=0], rebalanceId=27299, routines=22, receivedBytes=0,
receivedKeys=0, partitionsLeft=1659, startTime=-1, endTime=-1,
lastCancelledTime=1612068328290, result=true]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$RebalanceFuture.ownPartitionsAndFinishFuture(GridDhtPartitionDemander.java:1528)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.finishPreloading(GridDhtPartitionDemander.java:2064)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.finishPreloading(GridDhtPreloader.java:577)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCustomExchangeTask(GridCacheProcessor.java:419)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.processCustomTask(GridCachePartitionExchangeManager.java:3133)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3280)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3195)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster
[
https://issues.apache.org/jira/browse/IGNITE-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320080#comment-17320080
]
Ignite TC Bot commented on IGNITE-12033:
{panel:title=Branch: [pull/8870/head] Base: [master] : Possible Blockers
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Java Client{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5964646]]
{color:#d04437}Cache 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5964683]]
* IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationListenerExecutesOnStripedPoolWhenCustomExecutorIsProvided
- History for base branch is absent.
* IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationChainContinuesOnDefaultExecutor
- History for base branch is absent.
{color:#d04437}Thin Client: Java{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5964649]]
{panel}
{panel:title=Branch: [pull/8870/head] Base: [master] : New Tests
(16)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=5964703]]
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeExecuteAsyncContinuation
- PASSED{color}
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeRunAsyncContinuation -
PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestSynchronousExecutorRunsContinuationsOnStripedPool -
PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestInvalidExecutorConfigurationFailsOnStart - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestLocalOperationExecutesSynchronously - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestAsyncAwaitContinuationIsExecutedWithConfiguredExecutor
- PASSED{color}
{color:#8b}Cache 1{color} [[tests
10|https://ci.ignite.apache.org/viewLog.html?buildId=5964683]]
* {color:#8b}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationListenerExecutesOnStripedPoolWhenCustomExecutorIsProvided
- FAILED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testRemoteOperationListenerExecutesOnStripedPoolWhenCustomExecutorIsProvided
- PASSED{color}
* {color:#8b}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationChainContinuesOnDefaultExecutor
- FAILED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testLocalOperationListenerExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testLocalOperationChainExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationListenContinuesOnDefaultExecutor
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testRemoteOperationChainContinuesOnDefaultExecutor
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testLocalOperationListenerExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testLocalOperationChainExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testRemoteOperationListenContinuesOnDefaultExecutor
- PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5964729buildTypeId=IgniteTests24Java8_RunAll]
> Callbacks from striped pool due to async/await may hang cluster
> ---
>
> Key: IGNITE-12033
> URL: https://issues.apache.org/jira/browse/IGNITE-12033
> Project: Ignite
> Issue Type: Bug
> Components: cache, platforms
>Affects Versions: 2.7.5
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: iep-70
> Fix For: 2.11
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Discussed on dev-list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Re-EXTERNAL-Re-Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td42921.html
> *Must use the public pool for callbacks as the most obvious step.*
>
> http://apache-ignite-users.70518.x6.nabble.com/Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td27871.html#a28051
> There's a reproducer project. Long story short, .Net can invoke cache
> operations with future callbacks, which will be invoked from striped pool. If
> such callbacks are to use cache operations, those will be possibly sheduled
> to the same stripe and cause a
[jira] [Updated] (IGNITE-14236) Provide a new version of cache API
[
https://issues.apache.org/jira/browse/IGNITE-14236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-14236:
--
Labels: iep-72 ignite-3 (was: ignite-3)
> Provide a new version of cache API
> --
>
> Key: IGNITE-14236
> URL: https://issues.apache.org/jira/browse/IGNITE-14236
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Vyacheslav Koptilin
>Priority: Major
> Labels: iep-72, ignite-3
>
> Need to provide a minimal cache API that includes at least the following
> methods:
> - reading a value for a given key
> - writing a new value for a given key
> - remove a value for a given key
> - method that determines if the cache contains an entry for the specified
> key.
> - a way to iterate all key/value pairs
> - cache/table size (this method is questionable)
> Additionally, it can be considered adding a way to execute the user's code
> for the specified key - something like {{Cache#invoke()}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14235) Provide a minimal cache/table configuration
[ https://issues.apache.org/jira/browse/IGNITE-14235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-14235: -- Labels: iep-72 ignite-3 (was: ignite-3) > Provide a minimal cache/table configuration > --- > > Key: IGNITE-14235 > URL: https://issues.apache.org/jira/browse/IGNITE-14235 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: iep-72, ignite-3 > > Need to provide a way to configure a cache/table in accordance with IEP-55 > Unified Configuration [1] and IEP-54 Schema first approach. > [1] > https://cwiki.apache.org/confluence/display/IGNITE/IEP-55+Unified+Configuration > [2] > https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14237) Affinity function
[ https://issues.apache.org/jira/browse/IGNITE-14237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-14237: -- Labels: iep-72 ignite-3 (was: ) > Affinity function > - > > Key: IGNITE-14237 > URL: https://issues.apache.org/jira/browse/IGNITE-14237 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: iep-72, ignite-3 > > It seems that we need to adopt a well-known rendezvous affinity function to > AI-3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14238) Creating and destroying caches
[ https://issues.apache.org/jira/browse/IGNITE-14238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-14238: -- Labels: iep-72 ignite-3 (was: ) > Creating and destroying caches > -- > > Key: IGNITE-14238 > URL: https://issues.apache.org/jira/browse/IGNITE-14238 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: iep-72, ignite-3 > > Need to implement a new cluster-wide procedure that will be responsible for > creating and destroying caches. > [1] > https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14239) Raft based implementation of atomic protocol
[ https://issues.apache.org/jira/browse/IGNITE-14239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-14239: -- Labels: iep-72 ignite-3 (was: ignite-3) > Raft based implementation of atomic protocol > > > Key: IGNITE-14239 > URL: https://issues.apache.org/jira/browse/IGNITE-14239 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: iep-72, ignite-3 > > Implement a new atomic protocol based on raft client api [1] > [1] IGNITE-14149 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14331) Possible distributed race related to a data streamer flushing leading to a thread being stuck forever trying to close the streamer
[
https://issues.apache.org/jira/browse/IGNITE-14331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-14331:
-
Reviewer: Slava Koptilin
> Possible distributed race related to a data streamer flushing leading to a
> thread being stuck forever trying to close the streamer
> --
>
> Key: IGNITE-14331
> URL: https://issues.apache.org/jira/browse/IGNITE-14331
> Project: Ignite
> Issue Type: Bug
> Components: streaming
>Affects Versions: 2.10
>Reporter: Vladimir Pligin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It seems that a streamer could stuck forever flushing internal buffers on a
> client side.
> It will stay in a busy-loop forever hoping on remapping but it's possible
> that it won't happen for example in case of long GC pauses on server(s) and
> long timeouts.
> It that case a streamer would be trapped inside this
> [loop|https://github.com/apache/ignite/blob/ignite-2.10/modules/core/src/main/java/org/apache/ignite/internal/processors/datastreamer/DataStreamerImpl.java#L1168].
> Stack trace snippet:
> {code:java}
> java.lang.Thread.State: RUNNABLE at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.flush(DataStreamerImpl.java:1706)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.doFlush(DataStreamerImpl.java:1170)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.closeEx(DataStreamerImpl.java:1365)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.closeEx(DataStreamerImpl.java:1323)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.close(DataStreamerImpl.java:1311)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.close(DataStreamerImpl.java:1415){code}
>
> It becomes possible when a
> IgniteSpiOperationTimeoutException
> is being thrown from
> org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic()
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14331) Possible distributed race related to a data streamer flushing leading to a thread being stuck forever trying to close the streamer
[
https://issues.apache.org/jira/browse/IGNITE-14331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-14331:
-
Reviewer: (was: Vyacheslav Koptilin)
> Possible distributed race related to a data streamer flushing leading to a
> thread being stuck forever trying to close the streamer
> --
>
> Key: IGNITE-14331
> URL: https://issues.apache.org/jira/browse/IGNITE-14331
> Project: Ignite
> Issue Type: Bug
> Components: streaming
>Affects Versions: 2.10
>Reporter: Vladimir Pligin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It seems that a streamer could stuck forever flushing internal buffers on a
> client side.
> It will stay in a busy-loop forever hoping on remapping but it's possible
> that it won't happen for example in case of long GC pauses on server(s) and
> long timeouts.
> It that case a streamer would be trapped inside this
> [loop|https://github.com/apache/ignite/blob/ignite-2.10/modules/core/src/main/java/org/apache/ignite/internal/processors/datastreamer/DataStreamerImpl.java#L1168].
> Stack trace snippet:
> {code:java}
> java.lang.Thread.State: RUNNABLE at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.flush(DataStreamerImpl.java:1706)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.doFlush(DataStreamerImpl.java:1170)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.closeEx(DataStreamerImpl.java:1365)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.closeEx(DataStreamerImpl.java:1323)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.close(DataStreamerImpl.java:1311)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.close(DataStreamerImpl.java:1415){code}
>
> It becomes possible when a
> IgniteSpiOperationTimeoutException
> is being thrown from
> org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic()
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14516) WAL can continue to log into archived segment if auto rollover enabled
[
https://issues.apache.org/jira/browse/IGNITE-14516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320053#comment-17320053
]
Ignite TC Bot commented on IGNITE-14516:
{panel:title=Branch: [pull/9001/head] Base: [master] : Possible Blockers
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Basic 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5964449]]
{color:#d04437}SPI{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5964439]]
{panel}
{panel:title=Branch: [pull/9001/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5964626]]
* {color:#013220}IgnitePdsTestSuite2: WalRolloverOnStopTest.testWallRollover -
PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5964511buildTypeId=IgniteTests24Java8_RunAll]
> WAL can continue to log into archived segment if auto rollover enabled
> --
>
> Key: IGNITE-14516
> URL: https://issues.apache.org/jira/browse/IGNITE-14516
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, there is a possibility that WAL will continue to log into an
> archived segment after node restart.
> Bug scenario:
> # {{WalAutoArchiveAfterInactivity}} enabled.
> # Node is stopping with the {{G.stop("ign", false")}}.
> # T0: Performs last checkpoint write some records to current WAL
> segment({{Segment#0}}) and freeze.
> # T1: Auto rollover happens in
> {{FileWriteAheadLogManager#checkWalRolloverRequiredDuringInactivityPeriod}}.
> # T2({{FileArchiver}}) Archives {{Segment#0}}.
> After restart, WAL will continue to log into {{Segment#0}} which leads that
> newly logged data will not be archived after rollover because
> {{FileArchiver}} will wait for {{Segment#2}} in
> {{SegmentCurrentStateStorage#waitNextSegmentForArchivation}}.
> PR to highlight error - https://github.com/apache/ignite/pull/8997
> It seems we should to continue to log into the next segment if {{curAbsIdx ==
> lastArchivedSegment}} on start.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13547) Calcite integration. CREATE TABLE support
[ https://issues.apache.org/jira/browse/IGNITE-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320027#comment-17320027 ] Taras Ledkov commented on IGNITE-13547: --- [~korlov], the patch is OK with me. > Calcite integration. CREATE TABLE support > - > > Key: IGNITE-13547 > URL: https://issues.apache.org/jira/browse/IGNITE-13547 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Konstantin Orlov >Priority: Critical > Original Estimate: 40h > Time Spent: 1h 50m > Remaining Estimate: 38h 10m > > We need to support DDL commands. The task about the support of CREATE TABLE. > Potentially with syntaxis as we already have in the H2 engine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14262) Calcite improvements. Get rid of numerous ExecutionCancelledException.
[ https://issues.apache.org/jira/browse/IGNITE-14262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319984#comment-17319984 ] Konstantin Orlov commented on IGNITE-14262: --- [~zstan], LGTM! > Calcite improvements. Get rid of numerous ExecutionCancelledException. > -- > > Key: IGNITE-14262 > URL: https://issues.apache.org/jira/browse/IGNITE-14262 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Labels: calcite > Time Spent: 3h > Remaining Estimate: 0h > > We have numerous ExecutionCancelledException exceptions, for example while > calling: CalciteQueryProcessorTest#testCountWithJoin. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14428) Formalize the names of the metrics included in the metric registry.
[ https://issues.apache.org/jira/browse/IGNITE-14428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319952#comment-17319952 ] Mikhail Petrov commented on IGNITE-14428: - [~nizhikov], [~namelchev] Thanks for the review. > Formalize the names of the metrics included in the metric registry. > > > Key: IGNITE-14428 > URL: https://issues.apache.org/jira/browse/IGNITE-14428 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Labels: IEP-35 > Time Spent: 3.5h > Remaining Estimate: 0h > > It's needed to refactor metric names to obey the global rule - all of them > must start with name of the registry they belongs to. And add corresponding > assertion. > The purpose of this change is to make all metrics that belongs to one > MetricRegistry have the name that obeys mentioned above rule regardless how > they were registered. It helps to use a consistent approach to work with all > metrics. > The following metric names will be changed to obey this rule: > JoinedNodes -> io.discovery.JoinedNodes > LeftNodes -> io.discovery.LeftNodes > FailedNodes -> io.discovery.FailedNodes > PendingMessagesRegistered -> io.discovery.PendingMessagesRegistered > CommunicationErrors -> io.discovery.CommunicationErrors > CurrentTopologyVersion -> io.discovery.CurrentTopologyVersion -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14527) CVE-2021-2816[3,4,5] in Jetty
Alexander Belyak created IGNITE-14527: - Summary: CVE-2021-2816[3,4,5] in Jetty Key: IGNITE-14527 URL: https://issues.apache.org/jira/browse/IGNITE-14527 Project: Ignite Issue Type: Task Components: integrations Reporter: Alexander Belyak Assignee: Alexander Belyak Vulnerabilities found: [https://nvd.nist.gov/vuln/detail/CVE-2021-28163] [https://nvd.nist.gov/vuln/detail/CVE-2021-28164] [https://nvd.nist.gov/vuln/detail/CVE-2021-28165] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14376) JmxMetricExporter fails to export discovery metrics
[
https://issues.apache.org/jira/browse/IGNITE-14376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov resolved IGNITE-14376.
-
Resolution: Fixed
> JmxMetricExporter fails to export discovery metrics
> ---
>
> Key: IGNITE-14376
> URL: https://issues.apache.org/jira/browse/IGNITE-14376
> Project: Ignite
> Issue Type: Bug
>Reporter: Mikhail Petrov
>Assignee: Mikhail Petrov
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Error:
> {code:java}
> java.lang.StringIndexOutOfBoundsException: String index out of range: -2
> at java.lang.String.substring(String.java:1931)
> at
> org.apache.ignite.spi.metric.jmx.MetricRegistryMBean.lambda$getMBeanInfo$0(MetricRegistryMBean.java:105)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at
> org.apache.ignite.spi.metric.jmx.MetricRegistryMBean.getMBeanInfo(MetricRegistryMBean.java:85)
> at
> org.apache.ignite.spi.metric.jmx.MetricRegistryMBean.getAttribute(MetricRegistryMBean.java:58)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:647)
> at
> com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678)
> at
> javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:273)
> at com.sun.proxy.$Proxy32.getMBeanInfo(Unknown Source)
> at
> org.apache.ignite.internal.metric.JmxExporterSpiTest.test(JmxExporterSpiTest.java:146)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2391)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Reproducer:
> {code:java}
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi();
> cfg.setMetricExporterSpi(jmxSpi);
> return cfg;
> }
> /** */
> @Test
> public void test() throws Exception {
> IgniteEx srv = startGrid();
> DynamicMBean mBean = metricRegistry(srv.name(), "io", "discovery");
> mBean.getMBeanInfo();
> }
> {code}
> The main reason: JMX exporter assumes that each metric must starts with the
> name of the registry it belongs to (see MetricRegistryMBean#getMBeanInfo),
> but discovery metrics do not obey this naming convection (see
> TcpDiscoveryStatistics/ZookeeperDiscoveryStatistics).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
