[jira] [Closed] (IGNITE-12951) Update documents for migrated extensions
[
https://issues.apache.org/jira/browse/IGNITE-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra closed IGNITE-12951.
--
> Update documents for migrated extensions
>
>
> Key: IGNITE-12951
> URL: https://issues.apache.org/jira/browse/IGNITE-12951
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> # Update README for migrated extensions.The newly migrated extensions modules
> have suffix -ext in the artifact name.Review and update extensions README
> docs to correct artifact name. An example for correct artifact name would be
> ignite-flink-ext
> # We need to update some sections (maven artifacts name, a paragraph about
> the extensions repository) in existing docs before the extension is released:
> https://github.com/apache/ignite/tree/master/docs/_docs/extensions-and-integrations
> #
> {quote}{{As for the extensions web page, I see its structure as follows. It
> goeswith a header introducing the extensions repository and covering types
> ofcontributions that are welcomed there. Then down below in the body we
> listall the available extensions - it can be a simple table with an
> extensionname, description, URL or a bit more advanced interface with a grid
> layoutlike on this page [1]. With the grid layout, we can add logos of
> theprojects Ignite is integrated with in addition to the
> name/description/URL.Let me know what you think.[1]
> [https://ignite.apache.org/screencasts.html]}}{quote}
>
> {{[http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-12358-Migrate-ZeroMQ-module-to-ignite-extensions-td45067.html#a46863]}}
>
--
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=17306634#comment-17306634
]
Ignite TC Bot commented on IGNITE-12033:
{panel:title=Branch: [pull/8870/head] Base: [master] : Possible Blockers
(13)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5929185]]
* IgniteCacheTestSuite2:
GridCachePartitionedTxMultiThreadedSelfTest.testPessimisticReadCommittedCommitMultithreaded
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}SPI{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5929158]]
* IgniteSpiTestSuite:
GridTcpCommunicationSpiSkipWaitHandshakeOnClientTest.clientCanNotSendHandshakeWaitMessage
- Test has low fail rate in base branch 1,3% and is not flaky
{color:#d04437}Platform .NET (Long Running){color} [[tests 0 Exit Code ,
Compilation Error |https://ci.ignite.apache.org/viewLog.html?buildId=5929207]]
{color:#d04437}JDBC Driver{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5929151]]
* IgniteJdbcDriverTestSuite:
JdbcThinJdbcToCacheDataTypesCoverageTest.testIntDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=0, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
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=5929184]]
* IgniteBinaryCacheTestSuite:
GridCacheBalancingStoreSelfTest.testConcurrentLoadAllCustomThreshold - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5929197]]
{color:#d04437}Platform .NET (Core Linux){color} [[tests 2 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=5929204]]
* dll: ComputeApiTest.TestRunActionAsyncCancel - Test has low fail rate in base
branch 0,0% and is not flaky
* dll: ProjectFilesTest.TestAllCsharpFilesAreIncludedInProject - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET{color} [[tests 0 Exit Code , Compilation Error
|https://ci.ignite.apache.org/viewLog.html?buildId=5929203]]
{color:#d04437}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5929199]]
* IgnitePdsTestSuite:
IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateSimple_5_Servers_5_Clients_FromClient
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET (NuGet)*{color} [[tests 0 Exit Code , Compilation
Error |https://ci.ignite.apache.org/viewLog.html?buildId=5929208]]
{color:#d04437}Platform .NET (Integrations){color} [[tests 0 Exit Code ,
Compilation Error |https://ci.ignite.apache.org/viewLog.html?buildId=5929206]]
{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Exit Code ,
Compilation Error , Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=5929205]]
{panel}
{panel:title=Branch: [pull/8870/head] Base: [master] : New Tests
(11)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 1{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5929184]]
* {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
7|https://ci.ignite.apache.org/viewLog.html?buildId=5929204]]
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeExecuteAsyncContinuation
- PASSED{color}
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeRunAsyncContinuation -
PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestSynchronousExecutorRunsContinuationsOnStripedPool -
PASSED{color}
* {color:#013220}dll:
ComputeTestAsyncAwait.TestComputeAffinityRunAsyncContinuation - 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*
[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=17306632#comment-17306632
]
Igor Sapego commented on IGNITE-12033:
--
[~ptupitsyn] overall looks good, take a look at comments in PR. Also, maybe it
makes sense to ask for review of someone who is more familiar with core product
functionality.
> 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: 20m
> 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] [Updated] (IGNITE-14202) Provide REST-based server endpoint in order to interact with Ignite cluster via CLI tool
[ https://issues.apache.org/jira/browse/IGNITE-14202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-14202: - Reviewer: Vyacheslav Koptilin > Provide REST-based server endpoint in order to interact with Ignite cluster > via CLI tool > > > Key: IGNITE-14202 > URL: https://issues.apache.org/jira/browse/IGNITE-14202 > Project: Ignite > Issue Type: New Feature >Reporter: Vyacheslav Koptilin >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Time Spent: 20m > Remaining Estimate: 0h > > Provide REST-based server endpoint in order to interact with Ignite cluster. > - need to investigate existing implementations that can be easily used > (RESTEasy, CXF, Jersey, etc) > - prototype REST API (schema, versioning, etc) > - Documentation of API (OpenAPI/Swagger) > - integrate with CLI -- 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
(27)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Restarts) 1{color} [[tests
9|https://ci.ignite.apache.org/viewLog.html?buildId=5910039]]
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxPutAllTenNodesTwoBackups
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutEightNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxSixNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutSixNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxEightNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxPutAllFourNodesTwoBackups
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackupsOffheapEvict
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesOneBackupsOffheapEvict
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Control Utility{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5910080]]
{color:#d04437}Basic 1{color} [[tests 12 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5910026]]
* IgniteBasicTestSuite: GridUnsafeDataOutputArraySizingSelfTest.testChanged2 -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testFutureIgniteException -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testAsyncListeners - Test has
low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChain - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainAsyncOnError - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testListeners - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testFutureException - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testAsyncListenersOnError -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainAsync - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainError - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testListenersOnError - Test
has low fail rate in base branch 0,0% and is not flaky
... and 1 tests blockers
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5910068]]
* ZookeeperDiscoverySpiTestSuite3: GridEventConsumeSelfTest.testResources -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET (Core Linux){color} [[tests 1 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=5910062]]
* dll: ProjectFilesTest.TestAllCsharpFilesAreIncludedInProject - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5910044]]
* IgniteBinaryObjectsCacheTestSuite3:
GridCacheInterceptorTransactionalRebalanceTest.testPutIfAbsent - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}[Build]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5928801]]
{panel}
{panel:title=Branch: [pull/8870/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5910062]]
* {color:#013220}dll:
[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=17306552#comment-17306552
]
Ignite TC Bot commented on IGNITE-12033:
{panel:title=Branch: [pull/8870/head] Base: [master] : Possible Blockers
(27)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Restarts) 1{color} [[tests
9|https://ci.ignite.apache.org/viewLog.html?buildId=5910039]]
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxPutAllTenNodesTwoBackups
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutEightNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxSixNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutSixNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxEightNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxPutAllFourNodesTwoBackups
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackupsOffheapEvict
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesOneBackupsOffheapEvict
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Control Utility{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5910080]]
{color:#d04437}Basic 1{color} [[tests 12 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5910026]]
* IgniteBasicTestSuite: GridUnsafeDataOutputArraySizingSelfTest.testChanged2 -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testFutureIgniteException -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testAsyncListeners - Test has
low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChain - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainAsyncOnError - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testListeners - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testFutureException - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testAsyncListenersOnError -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainAsync - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainError - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testListenersOnError - Test
has low fail rate in base branch 0,0% and is not flaky
... and 1 tests blockers
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5910068]]
* ZookeeperDiscoverySpiTestSuite3: GridEventConsumeSelfTest.testResources -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET (Core Linux){color} [[tests 1 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=5910062]]
* dll: ProjectFilesTest.TestAllCsharpFilesAreIncludedInProject - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5910044]]
* IgniteBinaryObjectsCacheTestSuite3:
GridCacheInterceptorTransactionalRebalanceTest.testPutIfAbsent - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}[Build]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5928801]]
{panel}
{panel:title=Branch: [pull/8870/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5910062]]
* {color:#013220}dll:
[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
(27)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Restarts) 1{color} [[tests
9|https://ci.ignite.apache.org/viewLog.html?buildId=5910039]]
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxPutAllTenNodesTwoBackups
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutEightNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxSixNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutSixNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxEightNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxPutAllFourNodesTwoBackups
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackupsOffheapEvict
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesOneBackupsOffheapEvict
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Control Utility{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5910080]]
{color:#d04437}Basic 1{color} [[tests 12 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5910026]]
* IgniteBasicTestSuite: GridUnsafeDataOutputArraySizingSelfTest.testChanged2 -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testFutureIgniteException -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testAsyncListeners - Test has
low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChain - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainAsyncOnError - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testListeners - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testFutureException - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testAsyncListenersOnError -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainAsync - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainError - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testListenersOnError - Test
has low fail rate in base branch 0,0% and is not flaky
... and 1 tests blockers
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5910068]]
* ZookeeperDiscoverySpiTestSuite3: GridEventConsumeSelfTest.testResources -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET (Core Linux){color} [[tests 1 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=5910062]]
* dll: ProjectFilesTest.TestAllCsharpFilesAreIncludedInProject - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5910044]]
* IgniteBinaryObjectsCacheTestSuite3:
GridCacheInterceptorTransactionalRebalanceTest.testPutIfAbsent - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}[Build]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5928575]]
{panel}
{panel:title=Branch: [pull/8870/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5910062]]
* {color:#013220}dll:
[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=17306522#comment-17306522
]
Ignite TC Bot commented on IGNITE-12033:
{panel:title=Branch: [pull/8870/head] Base: [master] : Possible Blockers
(27)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Restarts) 1{color} [[tests
9|https://ci.ignite.apache.org/viewLog.html?buildId=5910039]]
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxPutAllTenNodesTwoBackups
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutEightNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxSixNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutSixNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxEightNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxPutAllFourNodesTwoBackups
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackupsOffheapEvict
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesOneBackupsOffheapEvict
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Control Utility{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5910080]]
{color:#d04437}Basic 1{color} [[tests 12 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5910026]]
* IgniteBasicTestSuite: GridUnsafeDataOutputArraySizingSelfTest.testChanged2 -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testFutureIgniteException -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testAsyncListeners - Test has
low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChain - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainAsyncOnError - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testListeners - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testFutureException - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testAsyncListenersOnError -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainAsync - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainError - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testListenersOnError - Test
has low fail rate in base branch 0,0% and is not flaky
... and 1 tests blockers
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5910068]]
* ZookeeperDiscoverySpiTestSuite3: GridEventConsumeSelfTest.testResources -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET (Core Linux){color} [[tests 1 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=5910062]]
* dll: ProjectFilesTest.TestAllCsharpFilesAreIncludedInProject - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5910044]]
* IgniteBinaryObjectsCacheTestSuite3:
GridCacheInterceptorTransactionalRebalanceTest.testPutIfAbsent - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}[Build]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5928575]]
{panel}
{panel:title=Branch: [pull/8870/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5910062]]
* {color:#013220}dll:
[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
(28)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Restarts) 1{color} [[tests
9|https://ci.ignite.apache.org/viewLog.html?buildId=5910039]]
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxPutAllTenNodesTwoBackups
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutEightNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxSixNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutSixNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxEightNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxPutAllFourNodesTwoBackups
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackupsOffheapEvict
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesOneBackupsOffheapEvict
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Control Utility{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5910080]]
{color:#d04437}Basic 1{color} [[tests 12 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5910026]]
* IgniteBasicTestSuite: GridUnsafeDataOutputArraySizingSelfTest.testChanged2 -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testFutureIgniteException -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testAsyncListeners - Test has
low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChain - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainAsyncOnError - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testListeners - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testFutureException - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testAsyncListenersOnError -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainAsync - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainError - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testListenersOnError - Test
has low fail rate in base branch 0,0% and is not flaky
... and 1 tests blockers
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5910068]]
* ZookeeperDiscoverySpiTestSuite3: GridEventConsumeSelfTest.testResources -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET (Core Linux){color} [[tests 1 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=5910062]]
* dll: ProjectFilesTest.TestAllCsharpFilesAreIncludedInProject - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5910044]]
* IgniteBinaryObjectsCacheTestSuite3:
GridCacheInterceptorTransactionalRebalanceTest.testPutIfAbsent - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}[Build]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5926299]]
{color:#d04437}[Missing Tests]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5926399]]
{panel}
{panel:title=Branch: [pull/8870/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Core
[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
(28)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Restarts) 1{color} [[tests
9|https://ci.ignite.apache.org/viewLog.html?buildId=5910039]]
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxPutAllTenNodesTwoBackups
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutEightNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxSixNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutSixNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxEightNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxPutAllFourNodesTwoBackups
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackupsOffheapEvict
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesOneBackupsOffheapEvict
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Control Utility{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5910080]]
{color:#d04437}Basic 1{color} [[tests 12 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5910026]]
* IgniteBasicTestSuite: GridUnsafeDataOutputArraySizingSelfTest.testChanged2 -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testFutureIgniteException -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testAsyncListeners - Test has
low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChain - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainAsyncOnError - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testListeners - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testFutureException - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testAsyncListenersOnError -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainAsync - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainError - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: IgniteCacheFutureImplTest.testListenersOnError - Test
has low fail rate in base branch 0,0% and is not flaky
... and 1 tests blockers
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5910068]]
* ZookeeperDiscoverySpiTestSuite3: GridEventConsumeSelfTest.testResources -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET (Core Linux){color} [[tests 1 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=5910062]]
* dll: ProjectFilesTest.TestAllCsharpFilesAreIncludedInProject - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5910044]]
* IgniteBinaryObjectsCacheTestSuite3:
GridCacheInterceptorTransactionalRebalanceTest.testPutIfAbsent - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}[Build]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5926523]]
{color:#d04437}[Missing Tests]{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5926623]]
{panel}
{panel:title=Branch: [pull/8870/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Core
[jira] [Commented] (IGNITE-13858) Enabling near cache on a client node may lead to blocking eviction on server nodes
[ https://issues.apache.org/jira/browse/IGNITE-13858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306501#comment-17306501 ] Stanislav Lukyanov commented on IGNITE-13858: - Talked about this with [~agoncharuk]. It seems that there is a relatively cheap way of improving this. First, we can throw away the value from the entry stored on-heap. We only need the key for the near cache algorithm to work. Second, we can have a background thread iterating over the entries and removing the ones that don't have any alive readers (near cache clients). Third, we can have the same background thread perform no-op updates (e.g. no-op EntryProcessor invocations) which will automatically remove unneeded entries from the heap using the existing protocol. > Enabling near cache on a client node may lead to blocking eviction on server > nodes > -- > > Key: IGNITE-13858 > URL: https://issues.apache.org/jira/browse/IGNITE-13858 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8, 2.9, 2.9.1 >Reporter: Vyacheslav Koptilin >Priority: Major > > When Native Persistence is off, creating near-cache on client node enforces > (to be more accurate, near-cache entries) to maintain a list client node ids > (aka readers) per-entry basis. > Unfortunately, this list is not cleaned even though the eviction policy is > configured on the near cache. Moreover, such entries cannot be evicted on the > server-side, with corresponding pages, and this may lead to hanging cache > operations. > Originally discussed at user-list: > http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-Clientside-NearCache-and-Serverside-Eviction-blocking-cluster-tt34645.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14379) Fix vulnerability of commons-codec <1.13
[
https://issues.apache.org/jira/browse/IGNITE-14379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306472#comment-17306472
]
Ignite TC Bot commented on IGNITE-14379:
{panel:title=Branch: [pull/8915/head] Base: [master] : Possible Blockers
(110)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5928170]]
* IgniteCacheTestSuite6: CacheExchangeMergeTest.testMergeServersFail1_8 - Test
has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Basic 1{color} [[tests 19 TIMEOUT , Out Of Memory Error , Exit
Code |https://ci.ignite.apache.org/viewLog.html?buildId=5928149]]
* IgniteBasicTestSuite: GridMbeansMiscTest.testMbeansSet1 - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: GridMbeansMiscTest.testMbeansSet2 - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite:
OdbcConfigurationValidationSelfTest.testAddressInvalidHost - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: OdbcConfigurationValidationSelfTest.testThreadPoolSize
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: OdbcConfigurationValidationSelfTest.testAddressHostOnly
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite:
OdbcConfigurationValidationSelfTest.testConnectionParams - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite:
OdbcConfigurationValidationSelfTest.testAddressHostAndPort - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite:
OdbcConfigurationValidationSelfTest.testAddressInvalidFormat - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: OdbcConfigurationValidationSelfTest.testAddressDefault
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite:
OdbcConfigurationValidationSelfTest.testAddressHostAndPortRange - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite:
OdbcEscapeSequenceSelfTest.testTimeEscapeSequenceWithWhitespaces - Test has low
fail rate in base branch 0,0% and is not flaky
... and 8 tests blockers
{color:#d04437}PDS (Indexing){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5928178]]
* IgnitePdsWithIndexingCoreTestSuite:
IgnitePdsBinaryMetadataAsyncWritingTest.testParallelUpdatesToBinaryMetadata -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}PDS 1{color} [[tests 86 Out Of Memory Error
|https://ci.ignite.apache.org/viewLog.html?buildId=5928180]]
* org.apache.ignite.testsuites.IgnitePdsTestSuite:
org.apache.ignite.internal.processors.diagnostic.DiagnosticProcessorTest. -
History for base branch is absent.
* org.apache.ignite.testsuites.IgnitePdsTestSuite:
org.apache.ignite.internal.processors.metastorage.DistributedMetaStoragePersistentTest.
- History for base branch is absent.
* IgnitePdsTestSuite:
PageMemoryLazyAllocationWithPDSTest.testCreateCacheFailsInHugeMemoryRegion -
Test has low fail rate in base branch 0,0% and is not flaky
* IgnitePdsTestSuite:
PageMemoryLazyAllocationWithPDSTest.testCreateCacheFromClientFailsInHugeMemoryRegion
- Test has low fail rate in base branch 0,0% and is not flaky
* IgnitePdsTestSuite: ActiveOnStartPropertyTest.testInMemoryInactive - Test has
low fail rate in base branch 0,0% and is not flaky
* IgnitePdsTestSuite: ActiveOnStartPropertyTest.testInMemoryActive - Test has
low fail rate in base branch 0,0% and is not flaky
* IgnitePdsTestSuite:
ClusterStateOnStartPropertyTest.testInactiveInactiveOnStartInMemory - Test has
low fail rate in base branch 0,0% and is not flaky
* IgnitePdsTestSuite:
ClusterStateOnStartPropertyTest.testActiveDisableAutoActivation - Test has low
fail rate in base branch 0,0% and is not flaky
* IgnitePdsTestSuite:
ClusterStateOnStartPropertyTest.testReadOnlyInactiveOnStartInMemory - Test has
low fail rate in base branch 0,0% and is not flaky
* IgnitePdsTestSuite: ClusterStateOnStartPropertyTest.testInactiveInMemory -
Test has low fail rate in base branch 0,0% and is not flaky
* IgnitePdsTestSuite:
ClusterStateOnStartPropertyTest.testInactiveActiveOnStartInMemory - Test has
low fail rate in base branch 0,0% and is not flaky
... and 75 tests blockers
{color:#d04437}Platform C++ CMake (Linux Clang){color} [[tests 0 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=5928201]]
{panel}
{panel:title=Branch: [pull/8915/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}PDS 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5928180]]
* {color:#8b}org.apache.ignite.testsuites.IgnitePdsTestSuite:
org.apache.ignite.internal.processors.diagnostic.DiagnosticProcessorTest. -
[jira] [Created] (IGNITE-14379) Fix vulnerability of commons-codec <1.13
Ilya Kasnacheev created IGNITE-14379: Summary: Fix vulnerability of commons-codec <1.13 Key: IGNITE-14379 URL: https://issues.apache.org/jira/browse/IGNITE-14379 Project: Ignite Issue Type: Bug Components: build Reporter: Ilya Kasnacheev Assignee: Ilya Kasnacheev Fix For: 2.11 https://www.whitesourcesoftware.com/vulnerability-database/WS-2019-0379 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14378) Remove delay from node ping.
Vladimir Steshin created IGNITE-14378: - Summary: Remove delay from node ping. Key: IGNITE-14378 URL: https://issues.apache.org/jira/browse/IGNITE-14378 Project: Ignite Issue Type: Bug Reporter: Vladimir Steshin Assignee: Vladimir Steshin Remove U.sleep(200) from the node ping. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14377) Enchance log of node ping failure.
Vladimir Steshin created IGNITE-14377: - Summary: Enchance log of node ping failure. Key: IGNITE-14377 URL: https://issues.apache.org/jira/browse/IGNITE-14377 Project: Ignite Issue Type: Sub-task Reporter: Vladimir Steshin Assignee: Vladimir Steshin Log of unsuccessful ping during the joining is insufficient. No failure reason is logged. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14373) There's a race between auto rollover WAL segment and deactivate of WAL
[
https://issues.apache.org/jira/browse/IGNITE-14373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-14373:
-
Release Note: Fixes the race between auto rollover segments and
deactivation WAL.
> There's a race between auto rollover WAL segment and deactivate of WAL
> --
>
> Key: IGNITE-14373
> URL: https://issues.apache.org/jira/browse/IGNITE-14373
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> A race was detected between auto rollover WAL segments and deactivation of
> WAL, which can lead to an error and a fall of the node by FH.
> Error:
> {noformat}
> Error when executing timeout callback:
> o.a.i.i.processors.cache.persistence.wal.FileWriteAheadLogManager$2@421a963a
> java.lang.AssertionError: Concurrent updates on rollover are not allowed
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.rollOver(FileWriteAheadLogManager.java:1325)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.closeBufAndRollover(FileWriteAheadLogManager.java:928)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.checkWalRolloverRequiredDuringInactivityPeriod(FileWriteAheadLogManager.java:819)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.access$900(FileWriteAheadLogManager.java:159)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$2.onTimeout(FileWriteAheadLogManager.java:782)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:234)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14373) There's a race between auto rollover WAL segment and deactivate of WAL
[
https://issues.apache.org/jira/browse/IGNITE-14373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-14373:
---
Reviewer: Ivan Bessonov
> There's a race between auto rollover WAL segment and deactivate of WAL
> --
>
> Key: IGNITE-14373
> URL: https://issues.apache.org/jira/browse/IGNITE-14373
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> A race was detected between auto rollover WAL segments and deactivation of
> WAL, which can lead to an error and a fall of the node by FH.
> Error:
> {noformat}
> Error when executing timeout callback:
> o.a.i.i.processors.cache.persistence.wal.FileWriteAheadLogManager$2@421a963a
> java.lang.AssertionError: Concurrent updates on rollover are not allowed
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.rollOver(FileWriteAheadLogManager.java:1325)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.closeBufAndRollover(FileWriteAheadLogManager.java:928)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.checkWalRolloverRequiredDuringInactivityPeriod(FileWriteAheadLogManager.java:819)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.access$900(FileWriteAheadLogManager.java:159)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$2.onTimeout(FileWriteAheadLogManager.java:782)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:234)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14373) There's a race between auto rollover WAL segment and deactivate of WAL
[
https://issues.apache.org/jira/browse/IGNITE-14373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306174#comment-17306174
]
Ignite TC Bot commented on IGNITE-14373:
{panel:title=Branch: [pull/8912/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8912/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=5927561]]
* {color:#013220}IgnitePdsTestSuite2:
WriteAheadLogManagerSelfTest.testNoRaceAutoArchiveAndDeactivation -
PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5927591buildTypeId=IgniteTests24Java8_RunAll]
> There's a race between auto rollover WAL segment and deactivate of WAL
> --
>
> Key: IGNITE-14373
> URL: https://issues.apache.org/jira/browse/IGNITE-14373
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> A race was detected between auto rollover WAL segments and deactivation of
> WAL, which can lead to an error and a fall of the node by FH.
> Error:
> {noformat}
> Error when executing timeout callback:
> o.a.i.i.processors.cache.persistence.wal.FileWriteAheadLogManager$2@421a963a
> java.lang.AssertionError: Concurrent updates on rollover are not allowed
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.rollOver(FileWriteAheadLogManager.java:1325)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.closeBufAndRollover(FileWriteAheadLogManager.java:928)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.checkWalRolloverRequiredDuringInactivityPeriod(FileWriteAheadLogManager.java:819)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.access$900(FileWriteAheadLogManager.java:159)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$2.onTimeout(FileWriteAheadLogManager.java:782)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:234)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (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 reassigned IGNITE-14376:
---
Assignee: Mikhail Petrov
> 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
>
> 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)
[jira] [Updated] (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 updated IGNITE-14376:
Description:
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).
was:
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).
> 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
>Priority: Major
>
> 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)
[jira] [Updated] (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 updated IGNITE-14376:
Description:
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).
was:
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, but discovery metrics do not obey this
naming convection -see TcpDiscoveryStatistics/ZookeeperDiscoveryStatistics
> 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
>Priority: Major
>
> 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)
[jira] [Created] (IGNITE-14376) JmxMetricExporter fails to export discovery metrics
Mikhail Petrov created IGNITE-14376:
---
Summary: 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
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, but discovery metrics do not obey this
naming convection -see TcpDiscoveryStatistics/ZookeeperDiscoveryStatistics
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14375) Pending cache destroy messages can be erroneously send.
Stanilovsky Evgeny created IGNITE-14375: --- Summary: Pending cache destroy messages can be erroneously send. Key: IGNITE-14375 URL: https://issues.apache.org/jira/browse/IGNITE-14375 Project: Ignite Issue Type: Improvement Components: cache Affects Versions: 2.10 Reporter: Stanilovsky Evgeny Assignee: Stanilovsky Evgeny Due to pending messages logic implementation its possible to process already outdated _DynamicCacheChangeBatch_ message. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14374) Optimize SQL inline indexes format for Ignite 3.0
Yury Gerzhedovich created IGNITE-14374: -- Summary: Optimize SQL inline indexes format for Ignite 3.0 Key: IGNITE-14374 URL: https://issues.apache.org/jira/browse/IGNITE-14374 Project: Ignite Issue Type: Improvement Components: sql Reporter: Yury Gerzhedovich As of now, we always use 1 extra byte per column to keep type. It adds significant effort to index size. We should rethink the format of store for Ignite 3.0. At first glance, it could be a separate single byte to keep the null value for nullable types. In this case, we could inline not more than 8 columns that see as reasonable. May be index record format should be the same as we use for the data records. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13641) More logs for debugging DiscoveryTcpSpi
[ https://issues.apache.org/jira/browse/IGNITE-13641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-13641: -- Description: Logs in DiscoveryTcp (ServerImpl) are insufficient. We do not see actual passed timeouts in sockets. It's difficult to realise why the timeouts, awaits happened are what they are. Often, failure reasons are skipped. (was: Logs in DiscoveryTcp (ServerImpl) are insufficient. We do not see actual passed timeouts in sockets. It's difficult to realise why the timeouts, awaits happened are what they are.) > More logs for debugging DiscoveryTcpSpi > --- > > Key: IGNITE-13641 > URL: https://issues.apache.org/jira/browse/IGNITE-13641 > Project: Ignite > Issue Type: Improvement >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > > Logs in DiscoveryTcp (ServerImpl) are insufficient. We do not see actual > passed timeouts in sockets. It's difficult to realise why the timeouts, > awaits happened are what they are. Often, failure reasons are skipped. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13873) Milti-cell transaction changes may be not visible (during some time) after the Cellular switch
[
https://issues.apache.org/jira/browse/IGNITE-13873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306100#comment-17306100
]
Alexey Scherbakov commented on IGNITE-13873:
[~av]
I've left two comments.
> Milti-cell transaction changes may be not visible (during some time) after
> the Cellular switch
> --
>
> Key: IGNITE-13873
> URL: https://issues.apache.org/jira/browse/IGNITE-13873
> Project: Ignite
> Issue Type: Improvement
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Critical
> Labels: iep-45
> Fix For: 2.11, 2.10.1
>
> Attachments: master (as 2.9) vs improved (as dev) .png
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Transactions over some cells may be recovered after the stale data read.
> For example:
> We have 2 cells, the first contains partitions for k1, second for k2.
> Tx with put(k1,v1) and put(k2,v2) started and prepared.
> Then node from the first cell, which is the primary for k1, failed.
> Currently, the second cell (with key2) may finish the cellular switch before
> tx recovered and stale data read is possible.
> Primaries from the {{tx.transactionNodes()}} should be taken into account
> instead of the current logic that awaits for all transactions located on
> nodes who are backups to the failed primary.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-8719) Index left partially built if a node crashes during index create or rebuild
[ https://issues.apache.org/jira/browse/IGNITE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-8719: Assignee: Kirill Tkalenko (was: Peter Ivanov) > Index left partially built if a node crashes during index create or rebuild > --- > > Key: IGNITE-8719 > URL: https://issues.apache.org/jira/browse/IGNITE-8719 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Goncharuk >Assignee: Kirill Tkalenko >Priority: Critical > Attachments: IndexRebuildAfterNodeCrashTest.java, > IndexRebuildingTest.java > > > Currently, we do not have any state associated with the index tree. Consider > the following scenario: > 1) Start node, put some data > 2) start CREATE INDEX operation > 3) Wait for a checkpoint and stop node before index create finished > 4) Restart node > Since the checkpoint finished, the new index tree will be persisted to the > disk, but not all data will be present in the index. > We should somehow store information about initializing index tree and mark it > valid only after all data is indexed. The state should be persisted as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-8719) Index left partially built if a node crashes during index create or rebuild
[ https://issues.apache.org/jira/browse/IGNITE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-8719: Assignee: Peter Ivanov (was: Kirill Tkalenko) > Index left partially built if a node crashes during index create or rebuild > --- > > Key: IGNITE-8719 > URL: https://issues.apache.org/jira/browse/IGNITE-8719 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Goncharuk >Assignee: Peter Ivanov >Priority: Critical > Attachments: IndexRebuildAfterNodeCrashTest.java, > IndexRebuildingTest.java > > > Currently, we do not have any state associated with the index tree. Consider > the following scenario: > 1) Start node, put some data > 2) start CREATE INDEX operation > 3) Wait for a checkpoint and stop node before index create finished > 4) Restart node > Since the checkpoint finished, the new index tree will be persisted to the > disk, but not all data will be present in the index. > We should somehow store information about initializing index tree and mark it > valid only after all data is indexed. The state should be persisted as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14330) Implement table binary views.
[ https://issues.apache.org/jira/browse/IGNITE-14330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-14330: - Assignee: Andrey Mashenkov > Implement table binary views. > - > > Key: IGNITE-14330 > URL: https://issues.apache.org/jira/browse/IGNITE-14330 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > Fix For: 3.0.0-alpha2 > > > Implement KV and Table - binary projections over table. > Implement builders for binary objects\rows. > Add tests for all operations. Example class is a good start point. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14304) .NET Examples: Thick/Misc/ClienReconnect/client_reconnect_without_server_nodes ran into a timeout on windows + java 11
[
https://issues.apache.org/jira/browse/IGNITE-14304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn reassigned IGNITE-14304:
---
Assignee: Pavel Tupitsyn
> .NET Examples:
> Thick/Misc/ClienReconnect/client_reconnect_without_server_nodes ran into a
> timeout on windows + java 11
> ---
>
> Key: IGNITE-14304
> URL: https://issues.apache.org/jira/browse/IGNITE-14304
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 2.9.1
>Reporter: Fedor Malchikov
>Assignee: Pavel Tupitsyn
>Priority: Major
> Attachments: dotnet_example.log
>
>
> Problem reproduced only on windows server with java 11.
> From the unusual here are these 2 warnings:
> {code:java}
> [15:18:17] [Warn]
> [org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager]
> Transaction wal logging is disabled, because point-in-time recovery is
> disabled.
> [15:18:23] [Warn] [org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi]
> Failed to connect to any address from IP finder (will retry to join topology
> every 2000 ms; change 'reconnectDelay' to configure the frequency of
> retries): [/127.0.0.1:47500, /127.0.0.1:47501, /127.0.0.1:47502]
> {code}
> full log in attach.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14304) .NET Examples: Thick/Misc/ClienReconnect/client_reconnect_without_server_nodes ran into a timeout on windows + java 11
[
https://issues.apache.org/jira/browse/IGNITE-14304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306046#comment-17306046
]
Pavel Tupitsyn commented on IGNITE-14304:
-
The flakiness is most likely caused by this:
{code}
// Wait a moment for server to begin startup.
Thread.Sleep(200);
{code}
200ms is not enough in some cases. We should not rely on Sleep and make this
deterministic.
> .NET Examples:
> Thick/Misc/ClienReconnect/client_reconnect_without_server_nodes ran into a
> timeout on windows + java 11
> ---
>
> Key: IGNITE-14304
> URL: https://issues.apache.org/jira/browse/IGNITE-14304
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 2.9.1
>Reporter: Fedor Malchikov
>Priority: Major
> Attachments: dotnet_example.log
>
>
> Problem reproduced only on windows server with java 11.
> From the unusual here are these 2 warnings:
> {code:java}
> [15:18:17] [Warn]
> [org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager]
> Transaction wal logging is disabled, because point-in-time recovery is
> disabled.
> [15:18:23] [Warn] [org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi]
> Failed to connect to any address from IP finder (will retry to join topology
> every 2000 ms; change 'reconnectDelay' to configure the frequency of
> retries): [/127.0.0.1:47500, /127.0.0.1:47501, /127.0.0.1:47502]
> {code}
> full log in attach.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14254) Graceful stop rebuilding indexes when deactivating a cluster
[ https://issues.apache.org/jira/browse/IGNITE-14254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306025#comment-17306025 ] Stanilovsky Evgeny commented on IGNITE-14254: - [~ktkale...@gridgain.com] plz check my comments, additionally it can`t found test for sequential same indexes rebuild command, does it exist ? Thanks ! > Graceful stop rebuilding indexes when deactivating a cluster > > > Key: IGNITE-14254 > URL: https://issues.apache.org/jira/browse/IGNITE-14254 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.11 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > If in the process of rebuilding the indexes to deactivate the cluster, then a > number of errors may appear, including a node fail. It is necessary to stop > index rebuilding before stopping the cache. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14373) There's a race between auto rollover WAL segment and deactivate of WAL
[
https://issues.apache.org/jira/browse/IGNITE-14373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-14373:
-
Summary: There's a race between auto rollover WAL segment and deactivate of
WAL (was: There's a race in auto rollover WAL segment and deactivate of WAL)
> There's a race between auto rollover WAL segment and deactivate of WAL
> --
>
> Key: IGNITE-14373
> URL: https://issues.apache.org/jira/browse/IGNITE-14373
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> A race was detected between auto rollover WAL segments and deactivation of
> WAL, which can lead to an error and a fall of the node by FH.
> Error:
> {noformat}
> Error when executing timeout callback:
> o.a.i.i.processors.cache.persistence.wal.FileWriteAheadLogManager$2@421a963a
> java.lang.AssertionError: Concurrent updates on rollover are not allowed
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.rollOver(FileWriteAheadLogManager.java:1325)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.closeBufAndRollover(FileWriteAheadLogManager.java:928)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.checkWalRolloverRequiredDuringInactivityPeriod(FileWriteAheadLogManager.java:819)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.access$900(FileWriteAheadLogManager.java:159)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$2.onTimeout(FileWriteAheadLogManager.java:782)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:234)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14373) There's a race in auto rollover WAL segment and deactivate of WAL
Kirill Tkalenko created IGNITE-14373:
Summary: There's a race in auto rollover WAL segment and
deactivate of WAL
Key: IGNITE-14373
URL: https://issues.apache.org/jira/browse/IGNITE-14373
Project: Ignite
Issue Type: Bug
Components: persistence
Reporter: Kirill Tkalenko
Assignee: Kirill Tkalenko
Fix For: 2.11
A race was detected between auto rollover WAL segments and deactivation of WAL,
which can lead to an error and a fall of the node by FH.
Error:
{noformat}
Error when executing timeout callback:
o.a.i.i.processors.cache.persistence.wal.FileWriteAheadLogManager$2@421a963a
java.lang.AssertionError: Concurrent updates on rollover are not allowed
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.rollOver(FileWriteAheadLogManager.java:1325)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.closeBufAndRollover(FileWriteAheadLogManager.java:928)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.checkWalRolloverRequiredDuringInactivityPeriod(FileWriteAheadLogManager.java:819)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.access$900(FileWriteAheadLogManager.java:159)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$2.onTimeout(FileWriteAheadLogManager.java:782)
at
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:234)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14372) Fix REST json configuration update requests
Ivan Bessonov created IGNITE-14372: -- Summary: Fix REST json configuration update requests Key: IGNITE-14372 URL: https://issues.apache.org/jira/browse/IGNITE-14372 Project: Ignite Issue Type: Sub-task Reporter: Ivan Bessonov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14371) Fix REST json representation for configuration
Ivan Bessonov created IGNITE-14371: -- Summary: Fix REST json representation for configuration Key: IGNITE-14371 URL: https://issues.apache.org/jira/browse/IGNITE-14371 Project: Ignite Issue Type: Sub-task Reporter: Ivan Bessonov Assignee: Ivan Bessonov REST code is completely broken, it's time to fix it, partially at least. -- This message was sent by Atlassian Jira (v8.3.4#803005)
