[jira] [Updated] (IGNITE-9221) Uncomment 25 test classes in various Indexing test suites
[
https://issues.apache.org/jira/browse/IGNITE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-9221:
---
Fix Version/s: 2.8
> Uncomment 25 test classes in various Indexing test suites
> -
>
> Key: IGNITE-9221
> URL: https://issues.apache.org/jira/browse/IGNITE-9221
> Project: Ignite
> Issue Type: Sub-task
> Components: binary, sql
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Fix For: 2.8
>
>
> modules/indexing/src/test/java/org/apache/ignite/testsuites/IgniteCacheQuerySelfTestSuite.java
> {code}
> // suite.addTest(new TestSuite(QueryEntityValidationSelfTest.class));
> // suite.addTest(new TestSuite(GridH2TableSelfTest.class));
> //suite.addTestSuite(IgniteCacheUnionDuplicatesTest.class);
> //suite.addTestSuite(IgniteCacheConfigVariationsQueryTest.class);
>
> //suite.addTestSuite(IgniteCacheJoinPartitionedAndReplicatedCollocationTest.class);
>
> //suite.addTestSuite(IgniteClientReconnectCacheQueriesFailoverTest.class);
> //suite.addTestSuite(IgniteErrorOnRebalanceTest.class);
> //suite.addTestSuite(CacheQueryBuildValueTest.class);
> //suite.addTestSuite(CacheOffheapBatchIndexingMultiTypeTest.class);
> //suite.addTestSuite(CacheOffheapBatchIndexingBaseTest.class);
> //suite.addTestSuite(GridCircularQueueTest.class);
> //suite.addTestSuite(IndexingSpiQueryWithH2IndexingSelfTest.class);
> //suite.addTestSuite(H2DynamicIndexingComplexAbstractTest.class);
>
> //suite.addTestSuite(H2DynamicIndexingComplexClientAtomicPartitionedNoBackupsTest.class);
>
> //suite.addTestSuite(H2DynamicIndexingComplexClientTransactionalPartitionedNoBackupsTest.class);
>
> //suite.addTestSuite(H2DynamicIndexingComplexServerAtomicPartitionedNoBackupsTest.class);
>
> //suite.addTestSuite(H2DynamicIndexingComplexServerTransactionalPartitionedNoBackupsTest.class);
> {code}
> modules/indexing/src/test/java/org/apache/ignite/testsuites/IgniteCacheQuerySelfTestSuite3.java
> {code}
>
> //suite.addTestSuite(CacheContinuousQueryCounterPartitionedAtomicTest.class);
>
> //suite.addTestSuite(CacheContinuousQueryCounterPartitionedTxTest.class);
>
> //suite.addTestSuite(CacheContinuousQueryCounterReplicatedAtomicTest.class);
>
> //suite.addTestSuite(CacheContinuousQueryCounterReplicatedTxTest.class);
>
> //suite.addTestSuite(CacheContinuousQueryFailoverAtomicNearEnabledSelfSelfTest.class);
> {code}
> modules/indexing/src/test/java/org/apache/ignite/testsuites/IgniteBinaryCacheQueryTestSuite.java
> {code}
> //suite.addTestSuite(GridCacheBinarySwapScanQuerySelfTest.class);
> //suite.addTestSuite(IgniteSqlSchemaIndexingTest.class);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-7730) Improve WAL history size documentation
[
https://issues.apache.org/jira/browse/IGNITE-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov resolved IGNITE-7730.
Resolution: Done
According there is a new approach to specify WAL history size in bytes
IGNITE-6552
there is no need to deep specification calculation algorithm.
The algorithm is specified in wiki
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-underthehood-Estimatingdiskspace
for an advanced user/Ignite developer
> Improve WAL history size documentation
> --
>
> Key: IGNITE-7730
> URL: https://issues.apache.org/jira/browse/IGNITE-7730
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.7
>
>
> Until IGNITE-6552 is not implemented, we have only ability to configure WAL
> hist. size in checkpoints.
> It is needed to improve description for this parameter.
> I've added draft notes to wiki
> [https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-underthehood-Estimatingdiskspace]
> about ways how wer can estimate WAL sizes without exact bytes/time
> specification:
> {panel}
> WAL Work max used size: walSegmentSize * walSegments = 640Mb (default)
> in case Default WAL mode - this size is used always,
> in case other modes best case is 1 segment * walSegmentSize
> WAL Work+WAL Archive max size may be estimated by
> 1. average load or
> 2. by maximum size.
> 1st way is applicable if checkpoints are triggered mostly by timer trigger.
> Wal size = 2*Average load(bytes/sec) * trigger interval (sec) * walHistSize
> (number of checkpoints)
> Where 2 multiplier coming from physical & logical WAL Records.
> 2nd way: Checkpoint is triggered by segments max dirty pages percent. Use
> persisted data regions max sizes:
> sum(Max configured DataRegionConfiguration.maxSize) * 75% - est. maximum
> data volume to be writen on 1 checkpoint.
> Overall WAL size (before archiving) = 2* est. data volume * walHistSize =
> 1,5 * sum(DataRegionConfiguration.maxSize) * walHistSize
> Note applying WAL compressor may significiantly reduce archive size.
> {panel}
> One more note from [~ivan.glukos] on dev.list we need to include. It is
> answer to question how user can determine if segment from archive folder can
> be safely removed:
> {quote}By the way: WAL compression is already implemented that way. If there
> are any ".zip" segments in archive dir, they are free to delete.
> This can be a safe workaround for users who experience lack of free
> space - just delete compressed segments. We should mention it in
> documentation for 2.4 release.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-10030) [TC Bot] Background upload of changes, problems, and statistics
[ https://issues.apache.org/jira/browse/IGNITE-10030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-10030. - Resolution: Fixed Done in V20181029, deployed to server > [TC Bot] Background upload of changes, problems, and statistics > --- > > Key: IGNITE-10030 > URL: https://issues.apache.org/jira/browse/IGNITE-10030 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Minor > > After the implementation of [IGNITE-9848] load time is still long because of > statistics and changes requires significant time to be loaded > Refs: > BuildChainProcessor#loadTestsAndProblems > TeamcityIgnitedImpl#reloadBuild -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9848) [TC Bot] Background upload of all builds from TC to the bot DB
[ https://issues.apache.org/jira/browse/IGNITE-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-9848. Resolution: Fixed Done in V20181026, additional entities to be loaded in a separate issue. > [TC Bot] Background upload of all builds from TC to the bot DB > --- > > Key: IGNITE-9848 > URL: https://issues.apache.org/jira/browse/IGNITE-9848 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > To fix slow loading of PR report and Master trends page. > Upload all tracked and observed branches related builds into TC Bot's Ignite > DB. > Prepare compacted entities to reduce storage size. > Implement idea of having fat build, which will represent replies from a > number of REST services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10030) [TC Bot] Background upload of changes, problems, and statistics
Dmitriy Pavlov created IGNITE-10030: --- Summary: [TC Bot] Background upload of changes, problems, and statistics Key: IGNITE-10030 URL: https://issues.apache.org/jira/browse/IGNITE-10030 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov After the implementation of [IGNITE-9848] load time is still long because of statistics and changes requires significant time to be loaded Refs: BuildChainProcessor#loadTestsAndProblems TeamcityIgnitedImpl#reloadBuild -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9938) Update ScalaTest from 2.2.4 to 2.2.6
[
https://issues.apache.org/jira/browse/IGNITE-9938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660425#comment-16660425
]
Dmitriy Pavlov commented on IGNITE-9938:
[~kuaw26] LGTM both test and change.
> Update ScalaTest from 2.2.4 to 2.2.6
>
>
> Key: IGNITE-9938
> URL: https://issues.apache.org/jira/browse/IGNITE-9938
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> There a newer version of ScalaTest available.
> Also lets introduce a variable ${scala.test.version} in order to simplify
> future updates
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-9869) [TC Bot] Running builds not uploaded into prefetched builds collection
[ https://issues.apache.org/jira/browse/IGNITE-9869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-9869. Resolution: Fixed Fixed in V181012, not yet deployed to server > [TC Bot] Running builds not uploaded into prefetched builds collection > -- > > Key: IGNITE-9869 > URL: https://issues.apache.org/jira/browse/IGNITE-9869 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > PR inspection page shows there are running builds, > Reproduced during > #2744 IGNITE-6444: Validate that copyOnRead flag is configured with on-heap > cache enabled. > build check. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9869) [TC Bot] Running builds not uploaded into prefetched builds collection
Dmitriy Pavlov created IGNITE-9869: -- Summary: [TC Bot] Running builds not uploaded into prefetched builds collection Key: IGNITE-9869 URL: https://issues.apache.org/jira/browse/IGNITE-9869 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov PR inspection page shows there are running builds, Reproduced during #2744 IGNITE-6444: Validate that copyOnRead flag is configured with on-heap cache enabled. build check. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9848) [TC Bot] Background upload of all builds from TC to the bot DB
Dmitriy Pavlov created IGNITE-9848: -- Summary: [TC Bot] Background upload of all builds from TC to the bot DB Key: IGNITE-9848 URL: https://issues.apache.org/jira/browse/IGNITE-9848 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov To fix slow loading of PR report and Master trends page. Upload all tracked and observed branches related builds into TC Bot's Ignite DB. Prepare compacted entities to reduce storage size. Implement idea of having fat build, which will represent replies from a number of REST services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9652) Fix `Missorted modifiers' according inspections profile`
[ https://issues.apache.org/jira/browse/IGNITE-9652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16645025#comment-16645025 ] Dmitriy Pavlov commented on IGNITE-9652: I agree, why not to improve code in other modules. We can apply these changes now and process remaining changes in a separate ticket. > Fix `Missorted modifiers' according inspections profile` > > > Key: IGNITE-9652 > URL: https://issues.apache.org/jira/browse/IGNITE-9652 > Project: Ignite > Issue Type: Bug >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Minor > Labels: inspections > Fix For: 2.8 > > > New `Code Inspections` profile can be found > \idea\ignite_inspections.xml. > We need to fix rule `Missorted modifiers` in ignite-core module. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9126) Update Apache Kafka dependency
[ https://issues.apache.org/jira/browse/IGNITE-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16645015#comment-16645015 ] Dmitriy Pavlov commented on IGNITE-9126: Folks, I sill appreciate if someday you can review, even in CTR mode :) > Update Apache Kafka dependency > -- > > Key: IGNITE-9126 > URL: https://issues.apache.org/jira/browse/IGNITE-9126 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Maxim Pudov >Priority: Major > Fix For: 2.7 > > > It is suggested to update kafka in accordance with scala update, e.g. to > https://mvnrepository.com/artifact/org.apache.kafka/kafka_2.11/1.0.2 > or to Kafka 1.1.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9770) Re-run possible blockers from pr.html
[ https://issues.apache.org/jira/browse/IGNITE-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-9770. Resolution: Fixed [~zzzadruga] thank you for contribution. Merged to master and deployed to server. > Re-run possible blockers from pr.html > - > > Key: IGNITE-9770 > URL: https://issues.apache.org/jira/browse/IGNITE-9770 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Minor > > Show button for re-run possible blockers. Also show merged button with re-run > possible blockers JIRA, so the user re-run the possible tests and > does not wait for them to complete,but learn about the completed tests from > the comment to GitHib. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9800) Ignite TC bot: Simplify initial PR search and main navigation path for checking contribution
[ https://issues.apache.org/jira/browse/IGNITE-9800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-9800. Resolution: Fixed Done in V20181010. More UI improvement may be done later for particular contribution check > Ignite TC bot: Simplify initial PR search and main navigation path for > checking contribution > > > Key: IGNITE-9800 > URL: https://issues.apache.org/jira/browse/IGNITE-9800 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > Show list of open PRs and provide an easy way to search PR or ticket. > Show a reasonably simple index page with just a number of major use cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9126) Update Apache Kafka dependency
[ https://issues.apache.org/jira/browse/IGNITE-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643645#comment-16643645 ] Dmitriy Pavlov commented on IGNITE-9126: [~vozerov] I tend to merge it, but I still hope Nikolay will be able to take a brief look. > Update Apache Kafka dependency > -- > > Key: IGNITE-9126 > URL: https://issues.apache.org/jira/browse/IGNITE-9126 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Maxim Pudov >Priority: Major > Fix For: 2.7 > > > It is suggested to update kafka in accordance with scala update, e.g. to > https://mvnrepository.com/artifact/org.apache.kafka/kafka_2.11/1.0.2 > or to Kafka 1.1.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9550) Get operation returns null for a lost partition with READ_SAFE policy
[ https://issues.apache.org/jira/browse/IGNITE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642901#comment-16642901 ] Dmitriy Pavlov commented on IGNITE-9550: [~DmitriyGovorukhin] any updates on this? I see https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1332314705000986815=%3Cdefault%3E=testDetails is failing for a long time. > Get operation returns null for a lost partition with READ_SAFE policy > - > > Key: IGNITE-9550 > URL: https://issues.apache.org/jira/browse/IGNITE-9550 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.6 >Reporter: Pavel Vinokurov >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.7 > > Attachments: PartitionLostReproducer.java > > > See reproduced attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9126) Update Apache Kafka dependency
[ https://issues.apache.org/jira/browse/IGNITE-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642488#comment-16642488 ] Dmitriy Pavlov commented on IGNITE-9126: These tests are known problems, which were recently fixed in master. So from the point of TC view, ticket passed the review. IMO looks good, so let's wait for some feedback from [~NIzhikov] and [~roman_s] > Update Apache Kafka dependency > -- > > Key: IGNITE-9126 > URL: https://issues.apache.org/jira/browse/IGNITE-9126 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Maxim Pudov >Priority: Major > Fix For: 2.7 > > > It is suggested to update kafka in accordance with scala update, e.g. to > https://mvnrepository.com/artifact/org.apache.kafka/kafka_2.11/1.0.2 > or to Kafka 1.1.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9126) Update Apache Kafka dependency
[ https://issues.apache.org/jira/browse/IGNITE-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642187#comment-16642187 ] Dmitriy Pavlov commented on IGNITE-9126: A number of suspicious failures occurred, so I've re-triggered failed builds on TC. Let's wait for its results before the final merge. I found the code in the PR as good. But to be absolutely sure, changes are or, I would like someone more experienced in Kafka will do additional PR check. [~NIzhikov], [~roman_s], could you please take a look to https://github.com/apache/ignite/pull/4909/ ? > Update Apache Kafka dependency > -- > > Key: IGNITE-9126 > URL: https://issues.apache.org/jira/browse/IGNITE-9126 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Maxim Pudov >Priority: Major > Fix For: 2.7 > > > It is suggested to update kafka in accordance with scala update, e.g. to > https://mvnrepository.com/artifact/org.apache.kafka/kafka_2.11/1.0.2 > or to Kafka 1.1.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9126) Update Apache Kafka dependency
[ https://issues.apache.org/jira/browse/IGNITE-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642187#comment-16642187 ] Dmitriy Pavlov edited comment on IGNITE-9126 at 10/8/18 5:21 PM: - A number of suspicious failures occurred, so I've re-triggered failed builds on TC. Let's wait for its results before the final merge. I found the code in the PR as good. But to be absolutely sure, changes are Ok, I would like someone more experienced in Kafka will do additional PR check. [~NIzhikov], [~roman_s], could you please take a look to https://github.com/apache/ignite/pull/4909/ ? was (Author: dpavlov): A number of suspicious failures occurred, so I've re-triggered failed builds on TC. Let's wait for its results before the final merge. I found the code in the PR as good. But to be absolutely sure, changes are or, I would like someone more experienced in Kafka will do additional PR check. [~NIzhikov], [~roman_s], could you please take a look to https://github.com/apache/ignite/pull/4909/ ? > Update Apache Kafka dependency > -- > > Key: IGNITE-9126 > URL: https://issues.apache.org/jira/browse/IGNITE-9126 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Maxim Pudov >Priority: Major > Fix For: 2.7 > > > It is suggested to update kafka in accordance with scala update, e.g. to > https://mvnrepository.com/artifact/org.apache.kafka/kafka_2.11/1.0.2 > or to Kafka 1.1.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9815) [TC Bot] Muted tests shouldn't considered as blocker
[
https://issues.apache.org/jira/browse/IGNITE-9815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641764#comment-16641764
]
Dmitriy Pavlov commented on IGNITE-9815:
Bot never shows muted test. Do you mean failed from code e.g fail(IGNITE-)?
If yes, from the point of view of the bot (as well as TC), it is still
test-failure, which should be muted using TC interface.
Please note there is Ignored test opportunity presented in JUnit4+, but
currently, Grid Test Framework still uses JUnit3 API.
> [TC Bot] Muted tests shouldn't considered as blocker
>
>
> Key: IGNITE-9815
> URL: https://issues.apache.org/jira/browse/IGNITE-9815
> Project: Ignite
> Issue Type: Bug
>Reporter: Nikolay Izhikov
>Priority: Major
>
> Currently, TC bot doesn't analyze stack trace of test fail [1].
> If some test failed with the link to Ignite ticket it shouldn't be considered
> as a blocker.
> Link with examples of such behaviour:
> {noformat}
> IgniteCacheMvccTestSuite: DataStreamProcessorMvccSelfTest.testColocated -
> 0,0% fails in last 100 master runs.
> IgniteCacheMvccTestSuite: DataStreamProcessorMvccSelfTest.testPartitioned -
> 0,0% fails in last 100 master runs.
> IgniteCacheMvccTestSuite: DataStreamProcessorMvccSelfTest.testReplicated -
> 0,0% fails in last 100 master runs.
> {noformat}
> stack trace:
> {noformat}
> unit.framework.AssertionFailedError:
> https://issues.apache.org/jira/browse/IGNITE-9722
> at
> org.apache.ignite.internal.processors.cache.mvcc.CacheMvccTransactionsTest.testMvccCoordinatorChangeSimple(CacheMvccTransactionsTest.java:2387)
> {noformat}
> https://issues.apache.org/jira/browse/IGNITE-9272?focusedCommentId=16641617=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16641617
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7196) Exchange can stuck and wait while new node restoring state from disk and starting caches
[
https://issues.apache.org/jira/browse/IGNITE-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-7196:
---
Description:
Exchange can stuck and wait while new node restoring state from disk and
starting caches, there's a log snippet from a just joined new node that shows
the issue:
{noformat}
[21:36:13,023][INFO][exchange-worker-#62%statement_grid%][time] Started
exchange init [topVer=AffinityTopologyVersion [topVer=57, minorTopVer=0],
crd=false, evt=NODE_JOINED, evtNode=3ac1160e-0de4-41bc-a366-59292c9f03c1,
customEvt=null, allowMerge=true]
[21:36:13,023][INFO][exchange-worker-#62%statement_grid%][FilePageStoreManager]
Resolved page store work directory:
/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
[21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
Resolved write ahead log work directory:
/mnt/wal/WAL/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
[21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
Resolved write ahead log archive directory:
/mnt/wal/WAL_archive/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
[21:36:13,046][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
Started write-ahead log manager [mode=DEFAULT]
[21:36:13,065][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl]
Started page memory [memoryAllocated=100.0 MiB, pages=6352, tableSize=373.4
KiB, checkpointBuffer=100.0 MiB]
[21:36:13,105][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl]
Started page memory [memoryAllocated=32.0 GiB, pages=2083376, tableSize=119.6
MiB, checkpointBuffer=896.0 MiB]
[21:36:13,428][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
Read checkpoint status
[startMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930965253-306c0895-1f5f-4237-bebf-8bf2b49682af-START.bin,
endMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930869357-1c24b6dc-d64c-4b83-8166-11edf1bfdad3-END.bin]
[21:36:13,429][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
Checking memory state [lastValidPos=FileWALPointer [idx=3582,
fileOffset=59186076, len=9229, forceFlush=false], lastMarked=FileWALPointer
[idx=3629, fileOffset=50829700, len=9229, forceFlush=false],
lastCheckpointId=306c0895-1f5f-4237-bebf-8bf2b49682af]
[21:36:13,429][WARNING][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
Ignite node stopped in the middle of checkpoint. Will restore memory state and
finish checkpoint on node start.
[21:36:18,312][INFO][grid-nio-worker-tcp-comm-0-#41%statement_grid%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
rmtAddr=/172.31.17.115:57148]
[21:36:21,619][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
Found last checkpoint marker [cpId=306c0895-1f5f-4237-bebf-8bf2b49682af,
pos=FileWALPointer [idx=3629, fileOffset=50829700, len=9229, forceFlush=false]]
[21:36:21,620][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
Finished applying memory changes [changesApplied=165103, time=8189ms]
[21:36:22,403][INFO][grid-nio-worker-tcp-comm-1-#42%statement_grid%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
rmtAddr=/172.31.28.10:47964]
[21:36:23,414][INFO][grid-nio-worker-tcp-comm-2-#43%statement_grid%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
rmtAddr=/172.31.27.101:46000]
[21:36:33,019][WARNING][main][GridCachePartitionExchangeManager] Failed to wait
for initial partition map exchange. Possible reasons are:
^-- Transactions in deadlock.
^-- Long running transactions (ignore if this is the case).
^-- Unreleased explicit locks.
[21:36:53,021][WARNING][main][GridCachePartitionExchangeManager] Still waiting
for initial partition map exchange [fut=GridDhtPartitionsExchangeFuture
[firstDiscoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=3ac1160e-0de4-41bc-a366-59292c9f03c1, addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1,
172.31.20.209], sockAddrs=[/0:0:0:0:0:0:0:1%lo:48500, /127.0.0.1:48500,
ip-172-31-20-209.eu-central-1.compute.internal/172.31.20.209:48500],
discPort=48500, order=57, intOrder=36, lastExchangeTime=1512931012268,
loc=true, ver=2.3.1#20171129-sha1:4b1ec0fe, isClient=false], topVer=57,
nodeId8=3ac1160e, msg=null, type=NODE_JOINED, tstamp=1512930972992],
crd=TcpDiscoveryNode [id=56c97317-26cf-43d2-bf76-0cab59c6fa5f,
addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.31.27.101],
sockAddrs=[/0:0:0:0:0:0:0:1%lo:48500, /127.0.0.1:48500,
ip-172-31-27-101.eu-central-1.compute.internal/172.31.27.101:48500],
discPort=48500, order=1, intOrder=1, lastExchangeTime=1512930972830, loc=false,
ver=2.3.1#20171129-sha1:4b1ec0fe, isClient=false],
exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion
[jira] [Commented] (IGNITE-7196) Exchange can stuck and wait while new node restoring state from disk and starting caches
[ https://issues.apache.org/jira/browse/IGNITE-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641132#comment-16641132 ] Dmitriy Pavlov commented on IGNITE-7196: Please check if it is not the same problem as in [IGNITE-]. If it is same tests affected, probably there is nothing to worry about. > Exchange can stuck and wait while new node restoring state from disk and > starting caches > > > Key: IGNITE-7196 > URL: https://issues.apache.org/jira/browse/IGNITE-7196 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.3 >Reporter: Mikhail Cherkasov >Assignee: Maxim Muzafarov >Priority: Critical > Fix For: 2.7 > > > Exchange can stuck and wait while new node restoring state from disk and > starting caches, there's a log snippet from a just joined new node that shows > the issue: > [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][time] Started > exchange init [topVer=AffinityTopologyVersion [topVer=57, minorTopVer=0], > crd=false, evt=NODE_JOINED, evtNode=3ac1160e-0de4-41bc-a366-59292c9f03c1, > customEvt=null, allowMerge=true] > [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][FilePageStoreManager] > Resolved page store work directory: > /mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Resolved write ahead log work directory: > /mnt/wal/WAL/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Resolved write ahead log archive directory: > /mnt/wal/WAL_archive/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,046][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Started write-ahead log manager [mode=DEFAULT] > [21:36:13,065][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl] > Started page memory [memoryAllocated=100.0 MiB, pages=6352, tableSize=373.4 > KiB, checkpointBuffer=100.0 MiB] > [21:36:13,105][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl] > Started page memory [memoryAllocated=32.0 GiB, pages=2083376, tableSize=119.6 > MiB, checkpointBuffer=896.0 MiB] > [21:36:13,428][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Read checkpoint status > [startMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930965253-306c0895-1f5f-4237-bebf-8bf2b49682af-START.bin, > > endMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930869357-1c24b6dc-d64c-4b83-8166-11edf1bfdad3-END.bin] > [21:36:13,429][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Checking memory state [lastValidPos=FileWALPointer [idx=3582, > fileOffset=59186076, len=9229, forceFlush=false], lastMarked=FileWALPointer > [idx=3629, fileOffset=50829700, len=9229, forceFlush=false], > lastCheckpointId=306c0895-1f5f-4237-bebf-8bf2b49682af] > [21:36:13,429][WARNING][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Ignite node stopped in the middle of checkpoint. Will restore memory state > and finish checkpoint on node start. > [21:36:18,312][INFO][grid-nio-worker-tcp-comm-0-#41%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.17.115:57148] > [21:36:21,619][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Found last checkpoint marker [cpId=306c0895-1f5f-4237-bebf-8bf2b49682af, > pos=FileWALPointer [idx=3629, fileOffset=50829700, len=9229, > forceFlush=false]] > [21:36:21,620][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Finished applying memory changes [changesApplied=165103, time=8189ms] > [21:36:22,403][INFO][grid-nio-worker-tcp-comm-1-#42%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.28.10:47964] > [21:36:23,414][INFO][grid-nio-worker-tcp-comm-2-#43%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.27.101:46000] > [21:36:33,019][WARNING][main][GridCachePartitionExchangeManager] Failed to > wait for initial partition map exchange. Possible reasons are: > ^-- Transactions in deadlock. > ^-- Long running transactions (ignore if this is the case). > ^-- Unreleased explicit locks. > [21:36:53,021][WARNING][main][GridCachePartitionExchangeManager] Still > waiting for initial partition map exchange > [fut=GridDhtPartitionsExchangeFuture [firstDiscoEvt=DiscoveryEvent > [evtNode=TcpDiscoveryNode [id=3ac1160e-0de4-41bc-a366-59292c9f03c1, > addrs=[0:0:0:0:0:0:0:1%lo,
[jira] [Commented] (IGNITE-9719) Extra rebalanceThreadPoolSize check on client node.
[ https://issues.apache.org/jira/browse/IGNITE-9719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16639686#comment-16639686 ] Dmitriy Pavlov commented on IGNITE-9719: [~zstan] I hope nobody will merge because there is no test run currently :). I will trigger it and TC Bot visa should be here in a couple of hours. > Extra rebalanceThreadPoolSize check on client node. > --- > > Key: IGNITE-9719 > URL: https://issues.apache.org/jira/browse/IGNITE-9719 > Project: Ignite > Issue Type: Improvement > Components: clients >Affects Versions: 2.6 >Reporter: Stanilovsky Evgeny >Assignee: Luchnikov Alexander >Priority: Minor > Fix For: 2.8 > > > No need to check rebalance thread pool size on client side in > IgniteKernal#ackRebalanceConfiguration method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module
[
https://issues.apache.org/jira/browse/IGNITE-9165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16639633#comment-16639633
]
Dmitriy Pavlov commented on IGNITE-9165:
The test is flaky ^ it seems it is not related to the fix.
> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
> Attachments:
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields,
> pass it to other methods that might close it, or return it, and does not
> appear to close the stream on all paths out of the method. This may result
> in a file descriptor leak.
> Example:
>
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
> props.load(new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
>
> One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
> List of classes in "core" module:
>
> +org.apache.ignite.internal:+
> * *BinaryContext*#classesInPackage(String)
> * *GridClientJdkMarshaller*#marshal(Object, int)
> *
> *IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute()
> * *OptimizedObjectStreamSelfTest*#testReadLine()
> * *PageIdDistributionTest*#_testRealHistory()
> * *HttpIgniteUpdatesChecker*#getUpdates(boolean)
> * *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process)
> +org.apache.ignite:+
> * *GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest()
> * *GridTestUtils*.sslContext()
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9800) Ignite TC bot: Simplify initial PR search and main navigation path for checking contribution
Dmitriy Pavlov created IGNITE-9800: -- Summary: Ignite TC bot: Simplify initial PR search and main navigation path for checking contribution Key: IGNITE-9800 URL: https://issues.apache.org/jira/browse/IGNITE-9800 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Show list of open PRs and provide an easy way to search PR or ticket. Show a reasonably simple index page with just a number of major use cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9431) Documentation for zk paths used by ZookeeperDiscovery.
[ https://issues.apache.org/jira/browse/IGNITE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16639532#comment-16639532 ] Dmitriy Pavlov commented on IGNITE-9431: [~zstan] [~Artem Budnikov] I find perfectly OK if we have such a description in the wiki. We can later add a link between user doc and wiki. We did it for persistence. The main thing is to have a documentation somewhere. > Documentation for zk paths used by ZookeeperDiscovery. > -- > > Key: IGNITE-9431 > URL: https://issues.apache.org/jira/browse/IGNITE-9431 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.6 >Reporter: Stanilovsky Evgeny >Priority: Major > > I found that under /apacheIgnite zk directory, there are also: > /jd, /ce, /cp, /ca and some other dirs, from source i found that they take > place from : org.apache.ignite.spi.discovery.zk.internal.ZkIgnitePaths. Plz > document this paths purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9792) Setting system property IGNITE_MBEANS_DISABLED to true lead to NPE.
[
https://issues.apache.org/jira/browse/IGNITE-9792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16639345#comment-16639345
]
Dmitriy Pavlov commented on IGNITE-9792:
I've checked all these tests, and it seems they are rare flaky ^. So there are
no issues from TC here.
> Setting system property IGNITE_MBEANS_DISABLED to true lead to NPE.
> ---
>
> Key: IGNITE-9792
> URL: https://issues.apache.org/jira/browse/IGNITE-9792
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.7
>
>
> Javadocs for IGNITE_MBEANS_DISABLED: "This may be helpful if MBeans are not
> allowed e.g. for security reasons."
> So I set in code:
> {code}
> System.setProperty(IgniteSystemProperties.IGNITE_MBEANS_DISABLED, "true")
> {code}
>
> And on node start node failed with NPE:
> {code}
> Caused by: class org.apache.ignite.IgniteCheckedException: Unexpected
> exception when starting grid.
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2079)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1728)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1156)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:676)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:601)
> at org.apache.ignite.Ignition.start(Ignition.java:323)
> ... 3 more
> Caused by: java.lang.NullPointerException: Ouch! Argument cannot be null:
> cfg.getMBeanServer()
> at
> org.apache.ignite.internal.util.GridArgumentCheck.notNull(GridArgumentCheck.java:48)
> at
> org.apache.ignite.internal.IgniteKernal.validateCommon(IgniteKernal.java:1355)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:833)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2033)
> ... 8 more
> {code}
>
> The fix is trivial: in org.apache.ignite.internal.IgniteKernal#validateCommon
> {code}
> if (!U.IGNITE_MBEANS_DISABLED) // <<< The fix
> A.notNull(cfg.getMBeanServer(), "cfg.getMBeanServer()");
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9719) Extra rebalanceThreadPoolSize check on client node.
[ https://issues.apache.org/jira/browse/IGNITE-9719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638481#comment-16638481 ] Dmitriy Pavlov commented on IGNITE-9719: [~zstan] could you please take a look? > Extra rebalanceThreadPoolSize check on client node. > --- > > Key: IGNITE-9719 > URL: https://issues.apache.org/jira/browse/IGNITE-9719 > Project: Ignite > Issue Type: Improvement > Components: clients >Affects Versions: 2.6 >Reporter: Stanilovsky Evgeny >Assignee: Luchnikov Alexander >Priority: Minor > Fix For: 2.8 > > > No need to check rebalance thread pool size on client side in > IgniteKernal#ackRebalanceConfiguration method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9282) [ML] Add Naive Bayes classifier
[ https://issues.apache.org/jira/browse/IGNITE-9282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638474#comment-16638474 ] Dmitriy Pavlov commented on IGNITE-9282: [~chief] could you please take a look? > [ML] Add Naive Bayes classifier > --- > > Key: IGNITE-9282 > URL: https://issues.apache.org/jira/browse/IGNITE-9282 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Aleksey Zinoviev >Assignee: Ravil Galeyev >Priority: Major > Labels: new-feature > Fix For: 2.8 > > > Naive Bayes classifiers are a family of simple probabilistic classifiers > based on applying Bayes' theorem with strong (naive) independence assumptions > between the features. > So we want to add this algorithm to Apache Ignite ML module. > Ideally, implementation should support both multinomial naive Bayes and > Bernoulli naive Bayes. > Requirements for successful PR: > # PartitionedDataset usage > # Trainer-Model paradigm support > # Tests for Model and for Trainer (and other stuff) > # Example of usage with small, but famous dataset like IRIS, Titanic or > House Prices > # Javadocs/codestyle according guidelines > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9769) IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 is flaky
[
https://issues.apache.org/jira/browse/IGNITE-9769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-9769:
---
Labels: MakeTeamcityGreenAgain (was: )
> IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 is flaky
> ---
>
> Key: IGNITE-9769
> URL: https://issues.apache.org/jira/browse/IGNITE-9769
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Trivial
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> {{IgniteCacheAtomicProtocolTest.testPutReaderUpdate1}} and
> {{IgniteCacheAtomicProtocolTest.testPutReaderUpdate2}} are flaky.
> In the {{#readerUpdateDhtFails}} method we blocks
> {{GridDhtAtomicNearResponse}} messages and do put operation. Put should hangs
> always, but sometimes it doesn't.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9792) Setting system property IGNITE_MBEANS_DISABLED to true lead to NPE.
[
https://issues.apache.org/jira/browse/IGNITE-9792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638319#comment-16638319
]
Dmitriy Pavlov commented on IGNITE-9792:
Change looks good to me, I've triggered tests, once it completes JIRA ticket
IGNITE-9792 will be notified.
> Setting system property IGNITE_MBEANS_DISABLED to true lead to NPE.
> ---
>
> Key: IGNITE-9792
> URL: https://issues.apache.org/jira/browse/IGNITE-9792
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.7
>
>
> Javadocs for IGNITE_MBEANS_DISABLED: "This may be helpful if MBeans are not
> allowed e.g. for security reasons."
> So I set in code:
> {code}
> System.setProperty(IgniteSystemProperties.IGNITE_MBEANS_DISABLED, "true")
> {code}
>
> And on node start node failed with NPE:
> {code}
> Caused by: class org.apache.ignite.IgniteCheckedException: Unexpected
> exception when starting grid.
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2079)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1728)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1156)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:676)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:601)
> at org.apache.ignite.Ignition.start(Ignition.java:323)
> ... 3 more
> Caused by: java.lang.NullPointerException: Ouch! Argument cannot be null:
> cfg.getMBeanServer()
> at
> org.apache.ignite.internal.util.GridArgumentCheck.notNull(GridArgumentCheck.java:48)
> at
> org.apache.ignite.internal.IgniteKernal.validateCommon(IgniteKernal.java:1355)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:833)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2033)
> ... 8 more
> {code}
>
> The fix is trivial: in org.apache.ignite.internal.IgniteKernal#validateCommon
> {code}
> if (!U.IGNITE_MBEANS_DISABLED) // <<< The fix
> A.notNull(cfg.getMBeanServer(), "cfg.getMBeanServer()");
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9550) Get operation returns null for a lost partition with READ_SAFE policy
[ https://issues.apache.org/jira/browse/IGNITE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9550: --- Description: See reproduced attached. (was: See reproducer attached.) > Get operation returns null for a lost partition with READ_SAFE policy > - > > Key: IGNITE-9550 > URL: https://issues.apache.org/jira/browse/IGNITE-9550 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.6 >Reporter: Pavel Vinokurov >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.7 > > Attachments: PartitionLostReproducer.java > > > See reproduced attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9298) control.sh does not support SSL (org.apache.ignite.internal.commandline.CommandHandler)
[ https://issues.apache.org/jira/browse/IGNITE-9298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637510#comment-16637510 ] Dmitriy Pavlov commented on IGNITE-9298: Hi [~vozerov], I wanted to ask the same, but you were first :) [~deviljelly] I would like you could continue with the fix, so would you like to contribute tests? Or if you would like we can ask Alex P to finish this ticket? > control.sh does not support SSL > (org.apache.ignite.internal.commandline.CommandHandler) > --- > > Key: IGNITE-9298 > URL: https://issues.apache.org/jira/browse/IGNITE-9298 > Project: Ignite > Issue Type: Bug > Components: clients >Affects Versions: 2.6 >Reporter: Paul Anderson >Assignee: Paul Anderson >Priority: Major > Fix For: 2.7 > > Attachments: Arguments.patch, CommandHandler.patch > > > We required SSL on the connector port and to use control.sh to work with the > baseline configuration. > This morning I added support, see attached patches against 2.6.0 for > org/apache/ignite/internal/commandline/CommandHandler.java > org/apache/ignite/internal/commandline/Arguments.java > No tests, no docs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9390) MVCC: add MVCC support to .NET configuration.
[ https://issues.apache.org/jira/browse/IGNITE-9390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637505#comment-16637505 ] Dmitriy Pavlov commented on IGNITE-9390: Additional fix 95b6597638a5a6b0348d6919507db3f534841eaa merged to master and cherry-picked to 2.7 beb7eb0b26b647c221157e0f734202981eb47ff5. [~rkondakov] thank you for contribution. > MVCC: add MVCC support to .NET configuration. > - > > Key: IGNITE-9390 > URL: https://issues.apache.org/jira/browse/IGNITE-9390 > Project: Ignite > Issue Type: Task > Components: mvcc, platforms >Reporter: Andrew Mashenkov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 2.7 > > > We should make MVCC configurable from .NET client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8623) NPE during cache access
[ https://issues.apache.org/jira/browse/IGNITE-8623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636879#comment-16636879 ] Dmitriy Pavlov commented on IGNITE-8623: Hi [~astelmak], could I ask you to add the ticket description? > NPE during cache access > --- > > Key: IGNITE-8623 > URL: https://issues.apache.org/jira/browse/IGNITE-8623 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Stelmak >Assignee: Alexey Stelmak >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9390) MVCC: add MVCC support to .NET configuration.
[ https://issues.apache.org/jira/browse/IGNITE-9390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16635689#comment-16635689 ] Dmitriy Pavlov commented on IGNITE-9390: [~vozerov] tests *New test failure in master DataRegionMetricsTest.TestMemoryMetrics https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=6742613397597284603=%3Cdefault%3E=testDetails *New test failure in master MemoryMetricsTest.TestMemoryMetrics https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7558087625238261420=%3Cdefault%3E=testDetails are still failed in the master after this change merge. Is it expected behavior? > MVCC: add MVCC support to .NET configuration. > - > > Key: IGNITE-9390 > URL: https://issues.apache.org/jira/browse/IGNITE-9390 > Project: Ignite > Issue Type: Task > Components: mvcc, platforms >Reporter: Andrew Mashenkov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 2.7 > > > We should make MVCC configurable from .NET client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8485) TDE - Phase-1
[ https://issues.apache.org/jira/browse/IGNITE-8485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16635481#comment-16635481 ] Dmitriy Pavlov commented on IGNITE-8485: We should definitely fix .NET compilation before the merge, we agreed to avoid tests failure, here I can see compilation failure Compilation error: modules\platforms\dotnet\Apache.Ignite.Core\Apache.Ignite.Core.csproj Open in IDE IgniteConfiguration.cs(42, 30): error CS0234: The type or namespace name 'Encryption' does not exist in the namespace 'Apache.Ignite.Core' (are you missing an assembly reference?) IgniteConfiguration.cs(43, 30): error CS0234: The type or namespace name 'Encryption' does not exist in the namespace 'Apache.Ignite.Core' (are you missing an assembly reference?) IgniteConfiguration.cs(1067, 16): error CS0246: The type or namespace name 'IEncryptionSpi' could not be found (are you missing a using directive or an assembly reference?) > TDE - Phase-1 > - > > Key: IGNITE-8485 > URL: https://issues.apache.org/jira/browse/IGNITE-8485 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Critical > Fix For: 2.7 > > Attachments: IGNITE-8485-encryption-disabled-1.png, > IGNITE-8485-encryption-disabled-2.png, Screen Shot 2018-10-01 at 10.27.37 > AM.png, Screen Shot 2018-10-01 at 10.27.51 AM.png, master.png > > > Basic support for a Transparent Data Encryption should be implemented: > 1. Usage of standard JKS, Java Security. > 2. Persistent Data Encryption/Decryption. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8485) TDE - Phase-1
[ https://issues.apache.org/jira/browse/IGNITE-8485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16635406#comment-16635406 ] Dmitriy Pavlov commented on IGNITE-8485: I left several comments in the PR about API uniformity, I'm going to finish this review shortly. And could we also issue TC Bot visa with more or less absent new test failures? > TDE - Phase-1 > - > > Key: IGNITE-8485 > URL: https://issues.apache.org/jira/browse/IGNITE-8485 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Critical > Fix For: 2.7 > > Attachments: IGNITE-8485-encryption-disabled-1.png, > IGNITE-8485-encryption-disabled-2.png, Screen Shot 2018-10-01 at 10.27.37 > AM.png, Screen Shot 2018-10-01 at 10.27.51 AM.png, master.png > > > Basic support for a Transparent Data Encryption should be implemented: > 1. Usage of standard JKS, Java Security. > 2. Persistent Data Encryption/Decryption. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9760) NPE is possible during WAL flushing for FSYNC mode
[
https://issues.apache.org/jira/browse/IGNITE-9760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-9760:
---
Fix Version/s: 2.7
> NPE is possible during WAL flushing for FSYNC mode
> --
>
> Key: IGNITE-9760
> URL: https://issues.apache.org/jira/browse/IGNITE-9760
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.7
>
>
> {noformat}
> class org.apache.ignite.IgniteCheckedException: Failed to update keys (retry
> update if possible).: [9483]
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7409)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:261)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:172)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runMultiThreadedAsync$96d302c5$1(GridTestUtils.java:853)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$2(GridTestUtils.java:1005)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:1295)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by: org.apache.ignite.cache.CachePartialUpdateException: Failed to
> update keys (retry update if possible).: [9483]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1307)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1742)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1092)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.wal.WalRolloverRecordLoggingTest.lambda$testAvoidInfinityWaitingOnRolloverOfSegment$0(WalRolloverRecordLoggingTest.java:119)
> ... 2 more
> Caused by: class
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
> Failed to update keys (retry update if possible).: [9483]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:397)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onPrimaryResponse(GridNearAtomicSingleUpdateFuture.java:253)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:303)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:300)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1855)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1668)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at
>
[jira] [Updated] (IGNITE-9760) NPE is possible during WAL flushing for FSYNC mode
[
https://issues.apache.org/jira/browse/IGNITE-9760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-9760:
---
Priority: Critical (was: Major)
> NPE is possible during WAL flushing for FSYNC mode
> --
>
> Key: IGNITE-9760
> URL: https://issues.apache.org/jira/browse/IGNITE-9760
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Critical
> Fix For: 2.7
>
>
> {noformat}
> class org.apache.ignite.IgniteCheckedException: Failed to update keys (retry
> update if possible).: [9483]
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7409)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:261)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:172)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runMultiThreadedAsync$96d302c5$1(GridTestUtils.java:853)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$2(GridTestUtils.java:1005)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:1295)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by: org.apache.ignite.cache.CachePartialUpdateException: Failed to
> update keys (retry update if possible).: [9483]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1307)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1742)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1092)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.wal.WalRolloverRecordLoggingTest.lambda$testAvoidInfinityWaitingOnRolloverOfSegment$0(WalRolloverRecordLoggingTest.java:119)
> ... 2 more
> Caused by: class
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
> Failed to update keys (retry update if possible).: [9483]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:397)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onPrimaryResponse(GridNearAtomicSingleUpdateFuture.java:253)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:303)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:300)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1855)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1668)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at
>
[jira] [Updated] (IGNITE-9761) Deadlock SegmentArchivedStorage <-> SegmentLockStorage
[
https://issues.apache.org/jira/browse/IGNITE-9761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-9761:
---
Priority: Blocker (was: Major)
> Deadlock SegmentArchivedStorage <-> SegmentLockStorage
> --
>
> Key: IGNITE-9761
> URL: https://issues.apache.org/jira/browse/IGNITE-9761
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Blocker
>
> {noformat}
> Found one Java-level deadlock:
> =
> "wal-file-archiver%cache.IgniteClusterActivateDeactivateTestWithPersistence2-#11729%cache.IgniteClusterActivateDeactivateTestWithPersistence2%":
> waiting to lock monitor 0x7fa33c0121e8 (object 0xf7142560, a
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentLockStorage),
> which is held by
> "exchange-worker-#11646%cache.IgniteClusterActivateDeactivateTestWithPersistence2%"
> "exchange-worker-#11646%cache.IgniteClusterActivateDeactivateTestWithPersistence2%":
> waiting to lock monitor 0x7fa3503b6058 (object 0xf7142578, a
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentArchivedStorage),
> which is held by
> "wal-file-archiver%cache.IgniteClusterActivateDeactivateTestWithPersistence2-#11729%cache.IgniteClusterActivateDeactivateTestWithPersistence2%"
> Java stack information for the threads listed above:
> ===
> "wal-file-archiver%cache.IgniteClusterActivateDeactivateTestWithPersistence2-#11729%cache.IgniteClusterActivateDeactivateTestWithPersistence2%":
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentLockStorage.locked(SegmentLockStorage.java:41)
> - waiting to lock <0xf7142560> (a
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentLockStorage)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentArchivedStorage.markAsMovedToArchive(SegmentArchivedStorage.java:101)
> - locked <0xf7142578> (a
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentArchivedStorage)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentAware.markAsMovedToArchive(SegmentAware.java:91)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileArchiver.body(FileWriteAheadLogManager.java:1643)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> "exchange-worker-#11646%cache.IgniteClusterActivateDeactivateTestWithPersistence2%":
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentArchivedStorage.onSegmentUnlocked(SegmentArchivedStorage.java:135)
> - waiting to lock <0xf7142578> (a
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentArchivedStorage)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentArchivedStorage$$Lambda$2/2113450692.accept(Unknown
> Source)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentObservable.lambda$notifyObservers$0(SegmentObservable.java:44)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentObservable$$Lambda$6/688404745.accept(Unknown
> Source)
> at java.util.ArrayList.forEach(ArrayList.java:1257)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentObservable.notifyObservers(SegmentObservable.java:44)
> - locked <0xf7142560> (a
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentLockStorage)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentLockStorage.releaseWorkSegment(SegmentLockStorage.java:74)
> - locked <0xf7142560> (a
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentLockStorage)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentAware.releaseWorkSegment(SegmentAware.java:226)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.io.LockedReadFileInput.ensure(LockedReadFileInput.java:81)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readSegmentHeader(RecordV1Serializer.java:260)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.initReadHandle(AbstractWalRecordsIterator.java:381)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$RecordsIterator.initReadHandle(FileWriteAheadLogManager.java:2942)
> at
>
[jira] [Updated] (IGNITE-9716) Document partition distribution and reset lost partitions commands of control script
[ https://issues.apache.org/jira/browse/IGNITE-9716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9716: --- Description: See [IGNITE-9549] - control.sh add command to collect information on the distribution of partitions and reset lost partitions for details. > Document partition distribution and reset lost partitions commands of control > script > > > Key: IGNITE-9716 > URL: https://issues.apache.org/jira/browse/IGNITE-9716 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.7 >Reporter: Alexey Goncharuk >Priority: Major > Fix For: 2.7 > > > See [IGNITE-9549] - > control.sh add command to collect information on the distribution of > partitions and reset lost partitions > for details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8617) Node Discovery Using AWS Application ELB
[ https://issues.apache.org/jira/browse/IGNITE-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16634556#comment-16634556 ] Dmitriy Pavlov commented on IGNITE-8617: JCache TCK1.1 passed, so tests are completely OK. > Node Discovery Using AWS Application ELB > > > Key: IGNITE-8617 > URL: https://issues.apache.org/jira/browse/IGNITE-8617 > Project: Ignite > Issue Type: New Feature > Components: aws >Reporter: Uday Kale >Assignee: Uday Kale >Priority: Major > Fix For: 2.7 > > > Support for Node discovery using AWS Application ELB. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8617) Node Discovery Using AWS Application ELB
[ https://issues.apache.org/jira/browse/IGNITE-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16634393#comment-16634393 ] Dmitriy Pavlov commented on IGNITE-8617: I've checked all these tests history manually and it still seems to be flaky ^, so I can consider this bot result as ok. I've retriggered JCache TCK1.1. https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11_IgniteTests24Java8=pull%2F4076%2Fhead=buildTypeStatusDiv - we have only 1 failure and a number of canceled builds. > Node Discovery Using AWS Application ELB > > > Key: IGNITE-8617 > URL: https://issues.apache.org/jira/browse/IGNITE-8617 > Project: Ignite > Issue Type: New Feature > Components: aws >Reporter: Uday Kale >Assignee: Uday Kale >Priority: Major > Fix For: 2.7 > > > Support for Node discovery using AWS Application ELB. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-6042) Update KafkaStreamer dependencies to Kafka 0.11.x
[ https://issues.apache.org/jira/browse/IGNITE-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16634279#comment-16634279 ] Dmitriy Pavlov edited comment on IGNITE-6042 at 10/1/18 4:30 PM: - Hi [~roman_s], because of the existence of https://issues.apache.org/jira/browse/IGNITE-9126 probably this ticket is not more actual. Could you please confirm/close ticket? was (Author: dpavlov): Hi [~roman_s], because of the existence of https://issues.apache.org/jira/browse/IGNITE-9126 probably this ticket is not more actual? > Update KafkaStreamer dependencies to Kafka 0.11.x > - > > Key: IGNITE-6042 > URL: https://issues.apache.org/jira/browse/IGNITE-6042 > Project: Ignite > Issue Type: Task > Components: streaming >Reporter: Roman Shtykh >Assignee: Roman Shtykh >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6042) Update KafkaStreamer dependencies to Kafka 0.11.x
[ https://issues.apache.org/jira/browse/IGNITE-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16634279#comment-16634279 ] Dmitriy Pavlov commented on IGNITE-6042: Hi [~roman_s], because of the existence of https://issues.apache.org/jira/browse/IGNITE-9126 probably this ticket is not more actual? > Update KafkaStreamer dependencies to Kafka 0.11.x > - > > Key: IGNITE-6042 > URL: https://issues.apache.org/jira/browse/IGNITE-6042 > Project: Ignite > Issue Type: Task > Components: streaming >Reporter: Roman Shtykh >Assignee: Roman Shtykh >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6757) to bring serializable versions of java 8 functional interfaces
[ https://issues.apache.org/jira/browse/IGNITE-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16634277#comment-16634277 ] Dmitriy Pavlov commented on IGNITE-6757: Hi [~aboudnik] could you please add a ticket description? Is it still valid ticket? > to bring serializable versions of java 8 functional interfaces > -- > > Key: IGNITE-6757 > URL: https://issues.apache.org/jira/browse/IGNITE-6757 > Project: Ignite > Issue Type: Improvement >Reporter: Alexandre Boudnik >Assignee: Alexandre Boudnik >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7510) IgnitePdsClientNearCachePutGetTest fails flaky on TC
[ https://issues.apache.org/jira/browse/IGNITE-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7510: --- Environment: (was: Muting this test until this ticket is fixed) > IgnitePdsClientNearCachePutGetTest fails flaky on TC > > > Key: IGNITE-7510 > URL: https://issues.apache.org/jira/browse/IGNITE-7510 > Project: Ignite > Issue Type: Test > Components: persistence >Affects Versions: 2.4 >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5652) Print slow query warnings on client node
[ https://issues.apache.org/jira/browse/IGNITE-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5652: --- Environment: (was: Currently, only worker (MAP) nodes of the query print long query execution time warning to their console, for usability it would be nice to propagate this to the client node as well.) > Print slow query warnings on client node > > > Key: IGNITE-5652 > URL: https://issues.apache.org/jira/browse/IGNITE-5652 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Alexander Paschenko >Priority: Major > Labels: sql-stability, usability > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5652) Print slow query warnings on client node
[ https://issues.apache.org/jira/browse/IGNITE-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5652: --- Description: Currently, only worker (MAP) nodes of the query print long query execution time warning to their console, for usability it would be nice to propagate this to the client node as well. > Print slow query warnings on client node > > > Key: IGNITE-5652 > URL: https://issues.apache.org/jira/browse/IGNITE-5652 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Alexander Paschenko >Priority: Major > Labels: sql-stability, usability > > Currently, only worker (MAP) nodes of the query print long query execution > time warning to their console, for usability it would be nice to propagate > this to the client node as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9032) Remove extra dependecy from web console frontend
[ https://issues.apache.org/jira/browse/IGNITE-9032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9032: --- Description: Currently links checking tool for frontend uses 'app-root-path' package, but it can be imple,ented with native nodejs 'path' module. Extra module should be deleted. > Remove extra dependecy from web console frontend > > > Key: IGNITE-9032 > URL: https://issues.apache.org/jira/browse/IGNITE-9032 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexander Kalinin >Priority: Minor > Original Estimate: 2h > Remaining Estimate: 2h > > Currently links checking tool for frontend uses 'app-root-path' package, but > it can be imple,ented with native nodejs 'path' module. Extra module should > be deleted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7440) .NET: Thin client: AddCacheConfiguration
[
https://issues.apache.org/jira/browse/IGNITE-7440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-7440:
---
Description: Add {{IIgniteClient.AddCacheConfiguration}}, see IGNITE-6598.
> .NET: Thin client: AddCacheConfiguration
>
>
> Key: IGNITE-7440
> URL: https://issues.apache.org/jira/browse/IGNITE-7440
> Project: Ignite
> Issue Type: Improvement
> Components: platforms, thin client
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
>
> Add {{IIgniteClient.AddCacheConfiguration}}, see IGNITE-6598.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7510) IgnitePdsClientNearCachePutGetTest fails flaky on TC
[ https://issues.apache.org/jira/browse/IGNITE-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7510: --- Description: Muting this test until this ticket is fixed > IgnitePdsClientNearCachePutGetTest fails flaky on TC > > > Key: IGNITE-7510 > URL: https://issues.apache.org/jira/browse/IGNITE-7510 > Project: Ignite > Issue Type: Test > Components: persistence >Affects Versions: 2.4 >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > Muting this test until this ticket is fixed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7440) .NET: Thin client: AddCacheConfiguration
[
https://issues.apache.org/jira/browse/IGNITE-7440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-7440:
---
Environment: (was: Add {{IIgniteClient.AddCacheConfiguration}}, see
IGNITE-6598.)
> .NET: Thin client: AddCacheConfiguration
>
>
> Key: IGNITE-7440
> URL: https://issues.apache.org/jira/browse/IGNITE-7440
> Project: Ignite
> Issue Type: Improvement
> Components: platforms, thin client
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8600) SQL: lazy row materialization
[ https://issues.apache.org/jira/browse/IGNITE-8600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8600: --- Environment: (was: Currently our index cursor materializes rows as soon as they are encountered in an index page. This is necessary to protect ourselves from concurrent data modification. However, materialized rows might be filtered out later due to additional filters. In addition, there is a chance that only indexed fields is needed by query. We can do the following: 1) Introduce new mode that will return partially materialized rows, with only inline index fields initialized. When some non-initialized attribute is requested, we go to data page and materialize the whole row 2) Enable this mode for MVCC by default 3) Optionally enable this mode for non-MVCC read-only mode through additional flag.) > SQL: lazy row materialization > - > > Key: IGNITE-8600 > URL: https://issues.apache.org/jira/browse/IGNITE-8600 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.5 >Reporter: Vladimir Ozerov >Priority: Major > Labels: performance > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8600) SQL: lazy row materialization
[ https://issues.apache.org/jira/browse/IGNITE-8600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8600: --- Description: Currently our index cursor materializes rows as soon as they are encountered in an index page. This is necessary to protect ourselves from concurrent data modification. However, materialized rows might be filtered out later due to additional filters. In addition, there is a chance that only indexed fields is needed by query. We can do the following: 1) Introduce new mode that will return partially materialized rows, with only inline index fields initialized. When some non-initialized attribute is requested, we go to data page and materialize the whole row 2) Enable this mode for MVCC by default 3) Optionally enable this mode for non-MVCC read-only mode through additional flag. > SQL: lazy row materialization > - > > Key: IGNITE-8600 > URL: https://issues.apache.org/jira/browse/IGNITE-8600 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.5 >Reporter: Vladimir Ozerov >Priority: Major > Labels: performance > > Currently our index cursor materializes rows as soon as they are encountered > in an index page. This is necessary to protect ourselves from concurrent data > modification. However, materialized rows might be filtered out later due to > additional filters. In addition, there is a chance that only indexed fields > is needed by query. > We can do the following: > 1) Introduce new mode that will return partially materialized rows, with only > inline index fields initialized. When some non-initialized attribute is > requested, we go to data page and materialize the whole row > 2) Enable this mode for MVCC by default > 3) Optionally enable this mode for non-MVCC read-only mode through additional > flag. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9032) Remove extra dependecy from web console frontend
[ https://issues.apache.org/jira/browse/IGNITE-9032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9032: --- Environment: (was: Currently links checking tool for frontend uses 'app-root-path' package, but it can be imple,ented with native nodejs 'path' module. Extra module should be deleted.) > Remove extra dependecy from web console frontend > > > Key: IGNITE-9032 > URL: https://issues.apache.org/jira/browse/IGNITE-9032 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexander Kalinin >Priority: Minor > Original Estimate: 2h > Remaining Estimate: 2h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5989) Add logic to striped pool to allow threads exit on timeout
[ https://issues.apache.org/jira/browse/IGNITE-5989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5989: --- Description: It's going to be really helpful for simplifying thread dumps > Add logic to striped pool to allow threads exit on timeout > -- > > Key: IGNITE-5989 > URL: https://issues.apache.org/jira/browse/IGNITE-5989 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Igor Seliverstov >Priority: Major > > It's going to be really helpful for simplifying thread dumps -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5989) Add logic to striped pool to allow threads exit on timeout
[ https://issues.apache.org/jira/browse/IGNITE-5989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5989: --- Environment: (was: It's going to be really helpful for simplifying thread dumps) > Add logic to striped pool to allow threads exit on timeout > -- > > Key: IGNITE-5989 > URL: https://issues.apache.org/jira/browse/IGNITE-5989 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Igor Seliverstov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5653) Add to query execution plan debug data for joins
[ https://issues.apache.org/jira/browse/IGNITE-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5653: --- Environment: (was: Plan should output table type (replicated/partitioned) and colocation information if possible. If we have this than we can warn (or throw exception) if users try to join non colocated tables with local joins.) > Add to query execution plan debug data for joins > > > Key: IGNITE-5653 > URL: https://issues.apache.org/jira/browse/IGNITE-5653 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Alexander Paschenko >Priority: Major > Labels: sql-stability, usability > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5653) Add to query execution plan debug data for joins
[ https://issues.apache.org/jira/browse/IGNITE-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5653: --- Description: Plan should output table type (replicated/partitioned) and colocation information if possible. If we have this than we can warn (or throw exception) if users try to join non colocated tables with local joins. > Add to query execution plan debug data for joins > > > Key: IGNITE-5653 > URL: https://issues.apache.org/jira/browse/IGNITE-5653 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Alexander Paschenko >Priority: Major > Labels: sql-stability, usability > > Plan should output table type (replicated/partitioned) and colocation > information if possible. If we have this than we can warn (or throw > exception) if users try to join non colocated tables with local joins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6753) Allow plugable page memory for testing purpose
[ https://issues.apache.org/jira/browse/IGNITE-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-6753: --- Description: Allow plugable page memory for testing proposes. We need this ability to force fast IgniteOOM in tests. > Allow plugable page memory for testing purpose > -- > > Key: IGNITE-6753 > URL: https://issues.apache.org/jira/browse/IGNITE-6753 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Mikhail Cherkasov >Priority: Minor > Fix For: 2.8 > > > Allow plugable page memory for testing proposes. We need this ability to > force fast IgniteOOM in tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9405) Update documentation for metrics for remains to evict keys/partitions
[ https://issues.apache.org/jira/browse/IGNITE-9405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16634266#comment-16634266 ] Dmitriy Pavlov commented on IGNITE-9405: [~agoncharuck], could you please fill the ticket description? > Update documentation for metrics for remains to evict keys/partitions > - > > Key: IGNITE-9405 > URL: https://issues.apache.org/jira/browse/IGNITE-9405 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6753) Allow plugable page memory for testing purpose
[ https://issues.apache.org/jira/browse/IGNITE-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-6753: --- Environment: (was: Allow plugable page memory for testing proposes. We need this ability to force fast IgniteOOM in tests.) > Allow plugable page memory for testing purpose > -- > > Key: IGNITE-6753 > URL: https://issues.apache.org/jira/browse/IGNITE-6753 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Mikhail Cherkasov >Priority: Minor > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9463) [ML] Update ML tutorial with new model composition/update features
[ https://issues.apache.org/jira/browse/IGNITE-9463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16634265#comment-16634265 ] Dmitriy Pavlov commented on IGNITE-9463: [~zaleslaw] could you please fill ticket description? > [ML] Update ML tutorial with new model composition/update features > -- > > Key: IGNITE-9463 > URL: https://issues.apache.org/jira/browse/IGNITE-9463 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9435) Document MVCC
[ https://issues.apache.org/jira/browse/IGNITE-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16634264#comment-16634264 ] Dmitriy Pavlov commented on IGNITE-9435: [~vozerov] could you please fill ticket description? > Document MVCC > - > > Key: IGNITE-9435 > URL: https://issues.apache.org/jira/browse/IGNITE-9435 > Project: Ignite > Issue Type: Task > Components: documentation, mvcc >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9656) Automate RPM and DEB packages version increase on release
[ https://issues.apache.org/jira/browse/IGNITE-9656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9656: --- Environment: (was: RPM and DEB packages version increase after release should be automated and done in the same commit as pom.xml version are increased.) > Automate RPM and DEB packages version increase on release > - > > Key: IGNITE-9656 > URL: https://issues.apache.org/jira/browse/IGNITE-9656 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9656) Automate RPM and DEB packages version increase on release
[ https://issues.apache.org/jira/browse/IGNITE-9656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9656: --- Description: RPM and DEB packages version increase after release should be automated and done in the same commit as pom.xml version are increased. > Automate RPM and DEB packages version increase on release > - > > Key: IGNITE-9656 > URL: https://issues.apache.org/jira/browse/IGNITE-9656 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Priority: Major > > RPM and DEB packages version increase after release should be automated and > done in the same commit as pom.xml version are increased. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9755) PutAllSyncFailover test fail
[ https://issues.apache.org/jira/browse/IGNITE-9755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16634256#comment-16634256 ] Dmitriy Pavlov commented on IGNITE-9755: [~astelmak] Could you please fill ticket description? You can mention links to a failure of tests, suites affected, provide a stack trace. > PutAllSyncFailover test fail > > > Key: IGNITE-9755 > URL: https://issues.apache.org/jira/browse/IGNITE-9755 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Stelmak >Assignee: Alexey Stelmak >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9155) Exception during cluster state change terminates ExchangeWorker
[ https://issues.apache.org/jira/browse/IGNITE-9155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16634250#comment-16634250 ] Dmitriy Pavlov commented on IGNITE-9155: Tests seem to be Ok, but I can't provide final sign-off because of lack of understanding impact of this change. I hope [~agoncharuk] can do a final review. > Exception during cluster state change terminates ExchangeWorker > --- > > Key: IGNITE-9155 > URL: https://issues.apache.org/jira/browse/IGNITE-9155 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Lantukh >Assignee: Ilya Lantukh >Priority: Major > > After IGNITE-8311 we throw an exception in ExchangeFuture instead swallowing > it. > ClusterStateChangeProcessor has it's own exception handling mechanism, which > doesn't require ExchangeWorker termination (and leaving node in broken state). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9748) Web console: Add possibility to configure distributed MVCC
[ https://issues.apache.org/jira/browse/IGNITE-9748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16633784#comment-16633784 ] Dmitriy Pavlov commented on IGNITE-9748: [~vsisko], Could you please fill the ticket description? It is very useful for all community members to understand why and how it is going to be supported. > Web console: Add possibility to configure distributed MVCC > -- > > Key: IGNITE-9748 > URL: https://issues.apache.org/jira/browse/IGNITE-9748 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7618) validateCache synchronously waits for state change
[
https://issues.apache.org/jira/browse/IGNITE-7618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16632901#comment-16632901
]
Dmitriy Pavlov commented on IGNITE-7618:
Folks, let me remind that MTCGA was not handled
[MTCGA]: new failures in builds [1871897] needs to be handled
https://lists.apache.org/thread.html/16c8718047b6514f41c5987b8571a8fb64d20893ad5803dfe23d2ab7@%3Cdev.ignite.apache.org%3E
the test is still fail
> validateCache synchronously waits for state change
> --
>
> Key: IGNITE-7618
> URL: https://issues.apache.org/jira/browse/IGNITE-7618
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.4
>Reporter: Alexey Goncharuk
>Assignee: Ivan Bessonov
>Priority: Major
> Fix For: 2.7
>
>
> Currently, we call publicApiActiveState(waitForTransition=true) in
> GridDhtTopologyFutureAdapter#validateCache. This is incorrect, because the
> cluster state is updated from discovery thread, and mapping may be happening
> on a previous topology version. We must capture the cluster active state flag
> to the exchange future (I believe we already have all the mechanics for this
> in ExchangeActions class) and validate the state in the exchange future
> itself, without touching ClusterStateProcessor.
> Below is an example of a deadlock happened because of synchronous wait:
> {code}
> "db-checkpoint-thread-#12318%database.IgniteDbBaselineTopologySelfTest0%"
> #15498 prio=5 os_prio=0 tid=0x7fa173e80800 nid=0x3d08 waiting on
> condition [0x7fa2069a8000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x0007abfc16e8> (a
> java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
> at
> java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:943)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:2991)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:2797)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:2722)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> "snapshot-scheduler-restats-#12202%database.IgniteDbBaselineTopologySelfTest0%"
> #15332 prio=5 os_prio=0 tid=0x7fa228143000 nid=0x3c65 waiting on
> condition [0x7fa2be919000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
> at
> org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.publicApiActiveState(GridClusterStateProcessor.java:194)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTopologyFutureAdapter.validateCache(GridDhtTopologyFutureAdapter.java:83)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.mapOnTopology(GridDhtColocatedLockFuture.java:787)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.map(GridDhtColocatedLockFuture.java:763)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.lockAllAsync(GridDhtColocatedCache.java:646)
> at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedCacheAdapter.txLockAsync(GridDistributedCacheAdapter.java:109)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.getAllAsync(GridNearTxLocal.java:1723)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache$4.op(GridDhtColocatedCache.java:197)
> at
>
[jira] [Issue Comment Deleted] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.
[
https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-7616:
---
Comment: was deleted
(was: {panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC Cache{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=1928601]]
* IgniteCacheMvccTestSuite:
CacheMvccTransactionsTest.testAccountsTxScan_WithRemoves_ClientServer_Backups1
- 0,0% fails in last 100 master runs.
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=1928604buildTypeId=IgniteTests24Java8_RunAll])
> GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect
> values due to invalid interface registration.
>
>
> Key: IGNITE-7616
> URL: https://issues.apache.org/jira/browse/IGNITE-7616
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Max Shonichev
>Assignee: David Harvey
>Priority: Major
> Labels: jmx
> Fix For: 2.7
>
> Attachments: master_1b3742f4d7_mxbeans_threads2.patch
>
>
> Two of newly added management beans as a result of implementing feature
> request https://issues.apache.org/jira/browse/IGNITE-7217 have bugs:
> # GridDataStreamExecutor is registered as conforming to ThreadPoolMXBean
> interface, though actually it is an incompatible StripedExecutor.
> # GridCallbackExecutor is registered as conforming to ThreadPoolMXBean
> interface, though actually it is an incompatible
> IgniteStripedThreadPoolExecutor.
> # ThreadPoolMXBeanAdapter checks whether adapted instance is
> ThreadPoolExecutor, and as interfaces are incompatible, most of the JMX
> attributes of GridCallbackExecutor and GridDataStreamExecutor are returned as
> -1 or null.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9126) Update Apache Kafka dependency
[ https://issues.apache.org/jira/browse/IGNITE-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov reassigned IGNITE-9126: -- Assignee: (was: Dmitriy Pavlov) > Update Apache Kafka dependency > -- > > Key: IGNITE-9126 > URL: https://issues.apache.org/jira/browse/IGNITE-9126 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Priority: Major > Fix For: 2.7 > > > It is suggested to update kafka in accordance with scala update, e.g. to > https://mvnrepository.com/artifact/org.apache.kafka/kafka_2.11/1.0.2 > or to Kafka 1.1.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8617) Node Discovery Using AWS Application ELB
[ https://issues.apache.org/jira/browse/IGNITE-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630584#comment-16630584 ] Dmitriy Pavlov commented on IGNITE-8617: [~uday], thanks, I retriggered failed suites for PR. > Node Discovery Using AWS Application ELB > > > Key: IGNITE-8617 > URL: https://issues.apache.org/jira/browse/IGNITE-8617 > Project: Ignite > Issue Type: New Feature > Components: aws >Reporter: Uday Kale >Assignee: Uday Kale >Priority: Major > Fix For: 2.7 > > > Support for Node discovery using AWS Application ELB. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8220) Discovery worker termination in PDS test
[
https://issues.apache.org/jira/browse/IGNITE-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630577#comment-16630577
]
Dmitriy Pavlov edited comment on IGNITE-8220 at 9/27/18 3:03 PM:
-
I've checked all possible blockers: It seems these tests were already fixed in
master. Some of them continued to have floating failures. So IMO it is not a
blocker.
Merged to master and cherry-picked to 2.7
[~EdShangGG] [~alex_pl] [~akalashnikov] thank you for contribution.
[~ibessonov] thank you for review.
was (Author: dpavlov):
I've checked all possible blockers: It seems these tests were already fixed in
master. Some of them continued to have floating failures. So IMO it is not a
blocker.
Merged to master and cherry-picked to 2.7
[~EdShangGG] [~alex_pl] thank you for contribution.
[~ibessonov] thank you for review.
> Discovery worker termination in PDS test
>
>
> Key: IGNITE-8220
> URL: https://issues.apache.org/jira/browse/IGNITE-8220
> Project: Ignite
> Issue Type: Test
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Eduard Shangareev
>Priority: Critical
> Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.7
>
>
> 3 suites failed
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePds1_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsDirectIo1_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ActivateDeactivateCluster_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv
> Example of tests failed:
> - IgniteClusterActivateDeactivateTestWithPersistence.testActivateFailover3
> - IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateFailover3
> {noformat}
> [2018-04-11
> 02:43:09,769][ERROR][tcp-disco-srvr-#2298%cache.IgniteClusterActivateDeactivateTestWithPersistence0%][IgniteTestResources]
> Critical failure. Will be handled accordingly to configured handler
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread
> tcp-disco-srvr-#2298%cache.IgniteClusterActivateDeactivateTestWithPersistence0%
> is terminated unexpectedly.]]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-6454) Data structure suite timeout: test is not able to fail after interruption
[
https://issues.apache.org/jira/browse/IGNITE-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-6454:
---
Fix Version/s: (was: 2.7)
2.8
> Data structure suite timeout: test is not able to fail after interruption
> -
>
> Key: IGNITE-6454
> URL: https://issues.apache.org/jira/browse/IGNITE-6454
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Attachments:
> lastStartedTest_GridCacheReplicatedDataStructuresFailoverSelfTest.testFairReentrantLockConstantMultipleTopologyChangeNonFailoverSafe.log.zip,
>
> lastStartedTest_GridCacheReplicatedDataStructuresFailoverSelfTest.testReentrantLockConstantMultipleTopologyChangeNonFailoverSafe.log.zip
>
>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteDataStrucutures=%3Cdefault%3E=buildTypeStatusDiv
> Most often timeout is caused by following tests:
> GridCacheReplicatedDataStructuresFailoverSelfTest
> - testReentrantLockConstantMultipleTopologyChangeNonFailoverSafe()
> - testFairReentrantLockConstantMultipleTopologyChangeNonFailoverSafe()
> And most of thread dumps contains the following
> {noformat}
> ] :[Step 4/5] Thread
> [name="test-runner-#35143%replicated.GridCacheReplicatedDataStructuresFailoverSelfTest%",
> id=38586, state=RUNNABLE, blockCnt=0, waitCnt=60]
> [20:34:26] : [Step 4/5] at
> java.lang.Throwable.fillInStackTrace(Native Method)
> [20:34:26] : [Step 4/5] at
> java.lang.Throwable.fillInStackTrace(Throwable.java:783)
> [20:34:26] : [Step 4/5] - locked o.a.i.IgniteException@754033e
> [20:34:26] : [Step 4/5] at
> java.lang.Throwable.(Throwable.java:265)
> [20:34:26] : [Step 4/5] at
> java.lang.Exception.(Exception.java:66)
> [20:34:26] : [Step 4/5] at
> java.lang.RuntimeException.(RuntimeException.java:62)
> [20:34:26] : [Step 4/5] at
> o.a.i.IgniteException.(IgniteException.java:44)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.datastructures.GridCacheLockImpl$Sync.validate(GridCacheLockImpl.java:275)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.datastructures.GridCacheLockImpl$Sync.access$1000(GridCacheLockImpl.java:122)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.datastructures.GridCacheLockImpl.lock(GridCacheLockImpl.java:1200)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.doTestReentrantLock(GridCacheAbstractDataStructuresFailoverSelfTest.java:785)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testFairReentrantLockConstantMultipleTopologyChangeNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:739)
> [20:34:26] : [Step 4/5] at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [20:34:26] : [Step 4/5] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [20:34:26] : [Step 4/5] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [20:34:26] : [Step 4/5] at
> java.lang.reflect.Method.invoke(Method.java:606)
> [20:34:26] : [Step 4/5] at
> junit.framework.TestCase.runTest(TestCase.java:176)
> [20:34:26] : [Step 4/5] at
> o.a.i.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> [20:34:26] : [Step 4/5] at
> o.a.i.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> [20:34:26] : [Step 4/5] at
> o.a.i.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> [20:34:26] : [Step 4/5] at java.lang.Thread.run(Thread.java:745)
> [20:34:26] : [Step 4/5]
> {noformat}
> That can be indicator that threads are interrupted and flag
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl#interruptAll
> is set,
> than org.apache.ignite.IgniteException is thrown, but it is ignored by test
> and test continues to execute
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8617) Node Discovery Using AWS Application ELB
[ https://issues.apache.org/jira/browse/IGNITE-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630537#comment-16630537 ] Dmitriy Pavlov commented on IGNITE-8617: [~uday], it seems a lot of failed tests were already fixed. Could you please merge current master into your branch? > Node Discovery Using AWS Application ELB > > > Key: IGNITE-8617 > URL: https://issues.apache.org/jira/browse/IGNITE-8617 > Project: Ignite > Issue Type: New Feature > Components: aws >Reporter: Uday Kale >Assignee: Uday Kale >Priority: Major > Fix For: 2.7 > > > Support for Node discovery using AWS Application ELB. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9716) Document partition distribution and reset lost partitions commands of control script
[ https://issues.apache.org/jira/browse/IGNITE-9716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630532#comment-16630532 ] Dmitriy Pavlov commented on IGNITE-9716: [~agoncharuk] please feel ticket description. How will a contributor know what needs to be documented? Will you communicate privately with contributor? > Document partition distribution and reset lost partitions commands of control > script > > > Key: IGNITE-9716 > URL: https://issues.apache.org/jira/browse/IGNITE-9716 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.7 >Reporter: Alexey Goncharuk >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9716) Document partition distribution and reset lost partitions commands of control script
[ https://issues.apache.org/jira/browse/IGNITE-9716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630532#comment-16630532 ] Dmitriy Pavlov edited comment on IGNITE-9716 at 9/27/18 2:35 PM: - [~agoncharuk] please fill ticket description. How will a contributor know what needs to be documented? Will you communicate privately with contributor? was (Author: dpavlov): [~agoncharuk] please feel ticket description. How will a contributor know what needs to be documented? Will you communicate privately with contributor? > Document partition distribution and reset lost partitions commands of control > script > > > Key: IGNITE-9716 > URL: https://issues.apache.org/jira/browse/IGNITE-9716 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.7 >Reporter: Alexey Goncharuk >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7196) Exchange can stuck and wait while new node restoring state from disk and starting caches
[ https://issues.apache.org/jira/browse/IGNITE-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630526#comment-16630526 ] Dmitriy Pavlov commented on IGNITE-7196: I think we almost did this change, no reason to move it to 2.8. Am I missing something? > Exchange can stuck and wait while new node restoring state from disk and > starting caches > > > Key: IGNITE-7196 > URL: https://issues.apache.org/jira/browse/IGNITE-7196 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.3 >Reporter: Mikhail Cherkasov >Assignee: Maxim Muzafarov >Priority: Critical > Fix For: 2.7 > > > Exchange can stuck and wait while new node restoring state from disk and > starting caches, there's a log snippet from a just joined new node that shows > the issue: > [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][time] Started > exchange init [topVer=AffinityTopologyVersion [topVer=57, minorTopVer=0], > crd=false, evt=NODE_JOINED, evtNode=3ac1160e-0de4-41bc-a366-59292c9f03c1, > customEvt=null, allowMerge=true] > [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][FilePageStoreManager] > Resolved page store work directory: > /mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Resolved write ahead log work directory: > /mnt/wal/WAL/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Resolved write ahead log archive directory: > /mnt/wal/WAL_archive/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,046][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Started write-ahead log manager [mode=DEFAULT] > [21:36:13,065][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl] > Started page memory [memoryAllocated=100.0 MiB, pages=6352, tableSize=373.4 > KiB, checkpointBuffer=100.0 MiB] > [21:36:13,105][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl] > Started page memory [memoryAllocated=32.0 GiB, pages=2083376, tableSize=119.6 > MiB, checkpointBuffer=896.0 MiB] > [21:36:13,428][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Read checkpoint status > [startMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930965253-306c0895-1f5f-4237-bebf-8bf2b49682af-START.bin, > > endMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930869357-1c24b6dc-d64c-4b83-8166-11edf1bfdad3-END.bin] > [21:36:13,429][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Checking memory state [lastValidPos=FileWALPointer [idx=3582, > fileOffset=59186076, len=9229, forceFlush=false], lastMarked=FileWALPointer > [idx=3629, fileOffset=50829700, len=9229, forceFlush=false], > lastCheckpointId=306c0895-1f5f-4237-bebf-8bf2b49682af] > [21:36:13,429][WARNING][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Ignite node stopped in the middle of checkpoint. Will restore memory state > and finish checkpoint on node start. > [21:36:18,312][INFO][grid-nio-worker-tcp-comm-0-#41%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.17.115:57148] > [21:36:21,619][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Found last checkpoint marker [cpId=306c0895-1f5f-4237-bebf-8bf2b49682af, > pos=FileWALPointer [idx=3629, fileOffset=50829700, len=9229, > forceFlush=false]] > [21:36:21,620][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Finished applying memory changes [changesApplied=165103, time=8189ms] > [21:36:22,403][INFO][grid-nio-worker-tcp-comm-1-#42%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.28.10:47964] > [21:36:23,414][INFO][grid-nio-worker-tcp-comm-2-#43%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.27.101:46000] > [21:36:33,019][WARNING][main][GridCachePartitionExchangeManager] Failed to > wait for initial partition map exchange. Possible reasons are: > ^-- Transactions in deadlock. > ^-- Long running transactions (ignore if this is the case). > ^-- Unreleased explicit locks. > [21:36:53,021][WARNING][main][GridCachePartitionExchangeManager] Still > waiting for initial partition map exchange > [fut=GridDhtPartitionsExchangeFuture [firstDiscoEvt=DiscoveryEvent > [evtNode=TcpDiscoveryNode [id=3ac1160e-0de4-41bc-a366-59292c9f03c1, > addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.31.20.209], >
[jira] [Updated] (IGNITE-7196) Exchange can stuck and wait while new node restoring state from disk and starting caches
[ https://issues.apache.org/jira/browse/IGNITE-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7196: --- Fix Version/s: (was: 2.8) 2.7 > Exchange can stuck and wait while new node restoring state from disk and > starting caches > > > Key: IGNITE-7196 > URL: https://issues.apache.org/jira/browse/IGNITE-7196 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.3 >Reporter: Mikhail Cherkasov >Assignee: Maxim Muzafarov >Priority: Critical > Fix For: 2.7 > > > Exchange can stuck and wait while new node restoring state from disk and > starting caches, there's a log snippet from a just joined new node that shows > the issue: > [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][time] Started > exchange init [topVer=AffinityTopologyVersion [topVer=57, minorTopVer=0], > crd=false, evt=NODE_JOINED, evtNode=3ac1160e-0de4-41bc-a366-59292c9f03c1, > customEvt=null, allowMerge=true] > [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][FilePageStoreManager] > Resolved page store work directory: > /mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Resolved write ahead log work directory: > /mnt/wal/WAL/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Resolved write ahead log archive directory: > /mnt/wal/WAL_archive/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,046][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Started write-ahead log manager [mode=DEFAULT] > [21:36:13,065][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl] > Started page memory [memoryAllocated=100.0 MiB, pages=6352, tableSize=373.4 > KiB, checkpointBuffer=100.0 MiB] > [21:36:13,105][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl] > Started page memory [memoryAllocated=32.0 GiB, pages=2083376, tableSize=119.6 > MiB, checkpointBuffer=896.0 MiB] > [21:36:13,428][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Read checkpoint status > [startMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930965253-306c0895-1f5f-4237-bebf-8bf2b49682af-START.bin, > > endMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930869357-1c24b6dc-d64c-4b83-8166-11edf1bfdad3-END.bin] > [21:36:13,429][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Checking memory state [lastValidPos=FileWALPointer [idx=3582, > fileOffset=59186076, len=9229, forceFlush=false], lastMarked=FileWALPointer > [idx=3629, fileOffset=50829700, len=9229, forceFlush=false], > lastCheckpointId=306c0895-1f5f-4237-bebf-8bf2b49682af] > [21:36:13,429][WARNING][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Ignite node stopped in the middle of checkpoint. Will restore memory state > and finish checkpoint on node start. > [21:36:18,312][INFO][grid-nio-worker-tcp-comm-0-#41%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.17.115:57148] > [21:36:21,619][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Found last checkpoint marker [cpId=306c0895-1f5f-4237-bebf-8bf2b49682af, > pos=FileWALPointer [idx=3629, fileOffset=50829700, len=9229, > forceFlush=false]] > [21:36:21,620][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Finished applying memory changes [changesApplied=165103, time=8189ms] > [21:36:22,403][INFO][grid-nio-worker-tcp-comm-1-#42%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.28.10:47964] > [21:36:23,414][INFO][grid-nio-worker-tcp-comm-2-#43%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.27.101:46000] > [21:36:33,019][WARNING][main][GridCachePartitionExchangeManager] Failed to > wait for initial partition map exchange. Possible reasons are: > ^-- Transactions in deadlock. > ^-- Long running transactions (ignore if this is the case). > ^-- Unreleased explicit locks. > [21:36:53,021][WARNING][main][GridCachePartitionExchangeManager] Still > waiting for initial partition map exchange > [fut=GridDhtPartitionsExchangeFuture [firstDiscoEvt=DiscoveryEvent > [evtNode=TcpDiscoveryNode [id=3ac1160e-0de4-41bc-a366-59292c9f03c1, > addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.31.20.209], > sockAddrs=[/0:0:0:0:0:0:0:1%lo:48500, /127.0.0.1:48500, >
[jira] [Comment Edited] (IGNITE-9305) Wrong off-heap size is reported for a node
[
https://issues.apache.org/jira/browse/IGNITE-9305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16629143#comment-16629143
]
Dmitriy Pavlov edited comment on IGNITE-9305 at 9/27/18 12:25 PM:
--
Merged to master, cherry-picked to 2.7.
[~xtern] thank you for contribution, [~alex_pl], thank you for review.
was (Author: dpavlov):
Merged to master.
[~xtern] thank you for contribution, [~alex_pl], thank you for review.
> Wrong off-heap size is reported for a node
> --
>
> Key: IGNITE-9305
> URL: https://issues.apache.org/jira/browse/IGNITE-9305
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.6
>Reporter: Denis Magda
>Assignee: Pavel Pereslegin
>Priority: Blocker
> Fix For: 2.7
>
>
> Was troubleshooting an Ignite deployment today and couldn't find out from the
> logs what was the actual off-heap space used.
> Those were the given memory resoures (Ignite 2.6):
> {code}
> [2018-08-16 15:07:49,961][INFO ][main][GridDiscoveryManager] Topology
> snapshot [ver=1, servers=1, clients=0, CPUs=64, offheap=30.0GB, heap=24.0GB]
> {code}
> And that weird stuff was reported by the node (pay attention to the last
> line):
> {code}
> [2018-08-16 15:45:50,211][INFO
> ][grid-timeout-worker-#135%cluster_31-Dec-2017%][IgniteKernal%cluster_31-Dec-2017]
>
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=c033026e, name=cluster_31-Dec-2017, uptime=00:38:00.257]
> ^-- H/N/C [hosts=1, nodes=1, CPUs=64]
> ^-- CPU [cur=0.03%, avg=5.54%, GC=0%]
> ^-- PageMemory [pages=6997377]
> ^-- Heap [used=9706MB, free=61.18%, comm=22384MB]
> ^-- Non heap [used=144MB, free=-1%, comm=148MB] - this line is always the
> same!
> {code}
> Had to change the code by using
> {code}dataRegion.getPhysicalMemoryPages(){code} to find out that actual
> off-heap usage size was
> {code}
> >>> Physical Memory Size: 28651614208 => 27324 MB, 26 GB
> {code}
> The logs have to report the following instead:
> {code}
> ^-- Off-heap {Data Region 1} [used={dataRegion1.getPhysicalMemorySize()},
> free=X%, comm=dataRegion1.maxSize()]
> ^-- Off-heap {Data Region 2} [used={dataRegion2.getPhysicalMemorySize()},
> free=X%, comm=dataRegion2.maxSize()]
> {code}
> If Ignite persistence is enabled then the following extra lines have to be
> added to see the disk used space:
> {code}
> ^-- Ignite persistence {Data Region 1}:
> used={dataRegion1.getTotalAllocatedSize() -
> dataRegion1.getPhysicalMemorySize()}
> ^-- Ignite persistence {Data Region 2}
> [used={dataRegion2.getTotalAllocatedSize() -
> dataRegion2.getPhysicalMemorySize()}]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9298) control.sh does not support SSL (org.apache.ignite.internal.commandline.CommandHandler)
[ https://issues.apache.org/jira/browse/IGNITE-9298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16628880#comment-16628880 ] Dmitriy Pavlov commented on IGNITE-9298: [~deviljelly] do you mind if we apply your commit with your authorship and then someone else will do this test in the separate commit? I think it could be ok If there is only concern about a test and some volunteer will come and create it. > control.sh does not support SSL > (org.apache.ignite.internal.commandline.CommandHandler) > --- > > Key: IGNITE-9298 > URL: https://issues.apache.org/jira/browse/IGNITE-9298 > Project: Ignite > Issue Type: Bug > Components: clients >Affects Versions: 2.6 >Reporter: Paul Anderson >Assignee: Paul Anderson >Priority: Major > Fix For: 2.7 > > Attachments: Arguments.patch, CommandHandler.patch > > > We required SSL on the connector port and to use control.sh to work with the > baseline configuration. > This morning I added support, see attached patches against 2.6.0 for > org/apache/ignite/internal/commandline/CommandHandler.java > org/apache/ignite/internal/commandline/Arguments.java > No tests, no docs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9698) Add tests to control.sh with ssl authentication
[ https://issues.apache.org/jira/browse/IGNITE-9698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16628653#comment-16628653 ] Dmitriy Pavlov commented on IGNITE-9698: [~macrergate], please fill ticket description. It will help community members to understand what and why should be done. [~a-polyakov] how can you understand what to do if there is no data in the ticket? Do you communicate with other members privately? > Add tests to control.sh with ssl authentication > > > Key: IGNITE-9698 > URL: https://issues.apache.org/jira/browse/IGNITE-9698 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Kosarev >Assignee: Alexand Polyakov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-3303) Apache Flink Integration - Flink source to run a continuous query against one or multiple caches
[ https://issues.apache.org/jira/browse/IGNITE-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16628520#comment-16628520 ] Dmitriy Pavlov commented on IGNITE-3303: Hi [~samaitra] usually we don't reassign issue to a reviewer. I've started the discussion related to the introduction of an additional field. Let's see what will be the community opinion. > Apache Flink Integration - Flink source to run a continuous query against one > or multiple caches > > > Key: IGNITE-3303 > URL: https://issues.apache.org/jira/browse/IGNITE-3303 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Attachments: Screen Shot 2016-10-07 at 12.44.47 AM.png, > testFlinkIgniteSourceWithLargeBatch.log, win7.PNG > > > Apache Flink integration > +++ *Ignite as a bidirectional Connector* +++ > As a Flink source => run a continuous query against one or multiple > caches [4]. > Related discussion : > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Flink-lt-gt-Apache-Ignite-integration-td8163.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9573) ZookeeperDiscoverySpiSaslFailedAuthTest fails after added to suite
[ https://issues.apache.org/jira/browse/IGNITE-9573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9573: --- Fix Version/s: 2.8 > ZookeeperDiscoverySpiSaslFailedAuthTest fails after added to suite > -- > > Key: IGNITE-9573 > URL: https://issues.apache.org/jira/browse/IGNITE-9573 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Minor > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > Due to proliferation of static fields in Zk and Security code it fails when a > part of suite and/or will cause other tests to fail. Needs to be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9305) Wrong off-heap size is reported for a node
[
https://issues.apache.org/jira/browse/IGNITE-9305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627539#comment-16627539
]
Dmitriy Pavlov commented on IGNITE-9305:
Thank you, [~xtern], it seems it is not related to the fix.
> Wrong off-heap size is reported for a node
> --
>
> Key: IGNITE-9305
> URL: https://issues.apache.org/jira/browse/IGNITE-9305
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.6
>Reporter: Denis Magda
>Assignee: Pavel Pereslegin
>Priority: Blocker
> Fix For: 2.7
>
>
> Was troubleshooting an Ignite deployment today and couldn't find out from the
> logs what was the actual off-heap space used.
> Those were the given memory resoures (Ignite 2.6):
> {code}
> [2018-08-16 15:07:49,961][INFO ][main][GridDiscoveryManager] Topology
> snapshot [ver=1, servers=1, clients=0, CPUs=64, offheap=30.0GB, heap=24.0GB]
> {code}
> And that weird stuff was reported by the node (pay attention to the last
> line):
> {code}
> [2018-08-16 15:45:50,211][INFO
> ][grid-timeout-worker-#135%cluster_31-Dec-2017%][IgniteKernal%cluster_31-Dec-2017]
>
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=c033026e, name=cluster_31-Dec-2017, uptime=00:38:00.257]
> ^-- H/N/C [hosts=1, nodes=1, CPUs=64]
> ^-- CPU [cur=0.03%, avg=5.54%, GC=0%]
> ^-- PageMemory [pages=6997377]
> ^-- Heap [used=9706MB, free=61.18%, comm=22384MB]
> ^-- Non heap [used=144MB, free=-1%, comm=148MB] - this line is always the
> same!
> {code}
> Had to change the code by using
> {code}dataRegion.getPhysicalMemoryPages(){code} to find out that actual
> off-heap usage size was
> {code}
> >>> Physical Memory Size: 28651614208 => 27324 MB, 26 GB
> {code}
> The logs have to report the following instead:
> {code}
> ^-- Off-heap {Data Region 1} [used={dataRegion1.getPhysicalMemorySize()},
> free=X%, comm=dataRegion1.maxSize()]
> ^-- Off-heap {Data Region 2} [used={dataRegion2.getPhysicalMemorySize()},
> free=X%, comm=dataRegion2.maxSize()]
> {code}
> If Ignite persistence is enabled then the following extra lines have to be
> added to see the disk used space:
> {code}
> ^-- Ignite persistence {Data Region 1}:
> used={dataRegion1.getTotalAllocatedSize() -
> dataRegion1.getPhysicalMemorySize()}
> ^-- Ignite persistence {Data Region 2}
> [used={dataRegion2.getTotalAllocatedSize() -
> dataRegion2.getPhysicalMemorySize()}]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7196) Exchange can stuck and wait while new node restoring state from disk and starting caches
[ https://issues.apache.org/jira/browse/IGNITE-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627420#comment-16627420 ] Dmitriy Pavlov commented on IGNITE-7196: [~Mmuzaf] if all tests passed you can re-issue TC Bot visa and it will be green. > Exchange can stuck and wait while new node restoring state from disk and > starting caches > > > Key: IGNITE-7196 > URL: https://issues.apache.org/jira/browse/IGNITE-7196 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.3 >Reporter: Mikhail Cherkasov >Assignee: Maxim Muzafarov >Priority: Critical > Fix For: 2.7 > > > Exchange can stuck and wait while new node restoring state from disk and > starting caches, there's a log snippet from a just joined new node that shows > the issue: > [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][time] Started > exchange init [topVer=AffinityTopologyVersion [topVer=57, minorTopVer=0], > crd=false, evt=NODE_JOINED, evtNode=3ac1160e-0de4-41bc-a366-59292c9f03c1, > customEvt=null, allowMerge=true] > [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][FilePageStoreManager] > Resolved page store work directory: > /mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Resolved write ahead log work directory: > /mnt/wal/WAL/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Resolved write ahead log archive directory: > /mnt/wal/WAL_archive/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463 > [21:36:13,046][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager] > Started write-ahead log manager [mode=DEFAULT] > [21:36:13,065][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl] > Started page memory [memoryAllocated=100.0 MiB, pages=6352, tableSize=373.4 > KiB, checkpointBuffer=100.0 MiB] > [21:36:13,105][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl] > Started page memory [memoryAllocated=32.0 GiB, pages=2083376, tableSize=119.6 > MiB, checkpointBuffer=896.0 MiB] > [21:36:13,428][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Read checkpoint status > [startMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930965253-306c0895-1f5f-4237-bebf-8bf2b49682af-START.bin, > > endMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930869357-1c24b6dc-d64c-4b83-8166-11edf1bfdad3-END.bin] > [21:36:13,429][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Checking memory state [lastValidPos=FileWALPointer [idx=3582, > fileOffset=59186076, len=9229, forceFlush=false], lastMarked=FileWALPointer > [idx=3629, fileOffset=50829700, len=9229, forceFlush=false], > lastCheckpointId=306c0895-1f5f-4237-bebf-8bf2b49682af] > [21:36:13,429][WARNING][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Ignite node stopped in the middle of checkpoint. Will restore memory state > and finish checkpoint on node start. > [21:36:18,312][INFO][grid-nio-worker-tcp-comm-0-#41%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.17.115:57148] > [21:36:21,619][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Found last checkpoint marker [cpId=306c0895-1f5f-4237-bebf-8bf2b49682af, > pos=FileWALPointer [idx=3629, fileOffset=50829700, len=9229, > forceFlush=false]] > [21:36:21,620][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager] > Finished applying memory changes [changesApplied=165103, time=8189ms] > [21:36:22,403][INFO][grid-nio-worker-tcp-comm-1-#42%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.28.10:47964] > [21:36:23,414][INFO][grid-nio-worker-tcp-comm-2-#43%statement_grid%][TcpCommunicationSpi] > Accepted incoming communication connection [locAddr=/172.31.20.209:48100, > rmtAddr=/172.31.27.101:46000] > [21:36:33,019][WARNING][main][GridCachePartitionExchangeManager] Failed to > wait for initial partition map exchange. Possible reasons are: > ^-- Transactions in deadlock. > ^-- Long running transactions (ignore if this is the case). > ^-- Unreleased explicit locks. > [21:36:53,021][WARNING][main][GridCachePartitionExchangeManager] Still > waiting for initial partition map exchange > [fut=GridDhtPartitionsExchangeFuture [firstDiscoEvt=DiscoveryEvent > [evtNode=TcpDiscoveryNode [id=3ac1160e-0de4-41bc-a366-59292c9f03c1, > addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.31.20.209], >
[jira] [Resolved] (IGNITE-8599) Remove LocalWalModeChangeDuringRebalancingSelfTest.testWithExchangesMerge from Direct IO suite
[ https://issues.apache.org/jira/browse/IGNITE-8599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-8599. Resolution: Fixed Test was replaced with shorter version of it: IgniteNativeIoLocalWalModeChangeDuringRebalancingSelfTest. > Remove LocalWalModeChangeDuringRebalancingSelfTest.testWithExchangesMerge > from Direct IO suite > --- > > Key: IGNITE-8599 > URL: https://issues.apache.org/jira/browse/IGNITE-8599 > Project: Ignite > Issue Type: Test >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=6346758468206865681=%3Cdefault%3E=testDetails > It falls only in Direct IO > It is necessary to exclude it from direct IO because it gives a lot of load. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8599) Remove LocalWalModeChangeDuringRebalancingSelfTest.testWithExchangesMerge from Direct IO suite
[ https://issues.apache.org/jira/browse/IGNITE-8599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16626100#comment-16626100 ] Dmitriy Pavlov edited comment on IGNITE-8599 at 9/24/18 4:43 PM: - Test was replaced with shorter version of it: IgniteNativeIoLocalWalModeChangeDuringRebalancingSelfTest. Link to new history is: https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3866517477466180589=testDetails was (Author: dpavlov): Test was replaced with shorter version of it: IgniteNativeIoLocalWalModeChangeDuringRebalancingSelfTest. > Remove LocalWalModeChangeDuringRebalancingSelfTest.testWithExchangesMerge > from Direct IO suite > --- > > Key: IGNITE-8599 > URL: https://issues.apache.org/jira/browse/IGNITE-8599 > Project: Ignite > Issue Type: Test >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=6346758468206865681=%3Cdefault%3E=testDetails > It falls only in Direct IO > It is necessary to exclude it from direct IO because it gives a lot of load. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-6500) POJO fields of java wrapper type are not retaining null values from Cassandra persistent store, while using ignite's CassandraCacheStoreFactory
[
https://issues.apache.org/jira/browse/IGNITE-6500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16626029#comment-16626029
]
Dmitriy Pavlov edited comment on IGNITE-6500 at 9/24/18 4:23 PM:
-
[~kotamrajuyashasvi] thank you for contribution,
[~irudyak] thank you for review.
Merged to master, cherry-picked to 2.7
was (Author: dpavlov):
[~kotamrajuyashasvi] thank you for contribution,
[~irudyak] thank you for review.
Merged to master.
> POJO fields of java wrapper type are not retaining null values from Cassandra
> persistent store, while using ignite's CassandraCacheStoreFactory
> ---
>
> Key: IGNITE-6500
> URL: https://issues.apache.org/jira/browse/IGNITE-6500
> Project: Ignite
> Issue Type: Bug
> Components: cassandra
>Affects Versions: 2.1
>Reporter: Yashasvi Kotamraju
>Assignee: Yashasvi Kotamraju
>Priority: Minor
> Labels: patch
> Fix For: 2.7
>
>
> While using ignite's CassandraCacheStoreFactory(part of
> ignite-cassandra-store.jar) as cacheStoreFactory for a cache, if a POJO field
> is of wrapper class type, and the column value mapped in Cassandra persistent
> store is null then the POJO field is getting set to default primitive type
> instead of null.
> For Example: Assume a table 'person' in a Cassandra persistent store with the
> following structure and data.
> *table person:*
> *column*person_no(int)phno(text) address(text) age(int)
> name(text)
> *data* 1 12353 null
> nullyash
> person_no is the PRIMARY_KEY.
> This table is mapped to person POJO for ignite cache.
> public class person{
> private int person_no;
> private String name;
> private Integer age=null;
> private String phno;
> private String address;
> .getters and setters etc..
> }
> Now we load the row from Cassandra into ignite cache using cache.get(1) or
> cache.load(..) And we are using ignite's CassandraCacheStoreFactory for this
> cache.
> Let person p1 = cache.get(1);
> now p1.getName returns "yash", p1.getAddress returns null.
> But p1.getAge returns 0 instead of null. It is expected null value since the
> value is null in Cassandra persistent store.
> Hence if the value is 0 for the age field there is no way differentiate if it
> was null or it was actually 0. The similar problem exists for other wrapper
> types -> Long, Float, Double, Boolean.
> This problem cause is as follows.
> In
> org.apache.ignite.cache.store.cassandra.persistence.PojoField.setValueFromRow(..)
> method first the Cassandra field value is obtained by using the method
> PropertyMappingHelper.getCassandraColumnValue(..). This method calls DataStax
> Driver methods Row.getInt() or Row.getFloat() or Row.getDouble() etc..
> depending upon the column. This value obtained from this method is then set
> to the respective POJO field. But According to Datastax documentation getInt
> returns 0 if column value is null and similarly getLong returns 0L ,
> getDouble return 0.0 etc. Hence PropertyMappingHelper.
> getCassandraColumnValue returns 0 or 0L or 0.0 or false even if the value is
> null. And then this value is set to the wrapper type POJO fields. The problem
> only persists with the primitive data types in Cassandra mapped to wrapper
> type fields in POJO. For other types like String , Date etc.. the null values
> are retained in the POJO fields.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8022) Need to add README.txt for ignite-direct-io
[ https://issues.apache.org/jira/browse/IGNITE-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625877#comment-16625877 ] Dmitriy Pavlov commented on IGNITE-8022: [~ibessonov] I've updated readme, thank you for noticing. > Need to add README.txt for ignite-direct-io > --- > > Key: IGNITE-8022 > URL: https://issues.apache.org/jira/browse/IGNITE-8022 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.4 >Reporter: Ksenia Rybakova >Assignee: Dmitriy Pavlov >Priority: Major > Fix For: 2.7 > > > Need to add README.txt for ignite-direct-io -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8022) Need to add README.txt for ignite-direct-io
[ https://issues.apache.org/jira/browse/IGNITE-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625852#comment-16625852 ] Dmitriy Pavlov commented on IGNITE-8022: [~ibessonov] could you please check https://github.com/apache/ignite/pull/4815 > Need to add README.txt for ignite-direct-io > --- > > Key: IGNITE-8022 > URL: https://issues.apache.org/jira/browse/IGNITE-8022 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.4 >Reporter: Ksenia Rybakova >Assignee: Dmitriy Pavlov >Priority: Major > Fix For: 2.7 > > > Need to add README.txt for ignite-direct-io -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8619) Remote node could not start in ssh connection
[ https://issues.apache.org/jira/browse/IGNITE-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625839#comment-16625839 ] Dmitriy Pavlov commented on IGNITE-8619: [~ivanan.fed] [~SomeFire] it may be unrelated failure, so rerun of one suite may be perfectly ok > Remote node could not start in ssh connection > - > > Key: IGNITE-8619 > URL: https://issues.apache.org/jira/browse/IGNITE-8619 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > Now there is a problem with launch remote node via ssh. Initially was an > assumption that it's due to remote process has not enough time to write > information into log: > [IGNITE-8085|https://issues.apache.org/jira/browse/IGNITE-8085]. But this > correction didn't fix [TeamCity > |https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=6814497542781613621=testDetails] > (IgniteProjectionStartStopRestartSelfTest.testStartFiveNodesInTwoCalls). > So it's necessary to make launch remote node via ssh always succesful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8619) Remote node could not start in ssh connection
[ https://issues.apache.org/jira/browse/IGNITE-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625696#comment-16625696 ] Dmitriy Pavlov commented on IGNITE-8619: [~ivanan.fed] could you please check your PR runs and trigger bot to comment this issue? > Remote node could not start in ssh connection > - > > Key: IGNITE-8619 > URL: https://issues.apache.org/jira/browse/IGNITE-8619 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > Now there is a problem with launch remote node via ssh. Initially was an > assumption that it's due to remote process has not enough time to write > information into log: > [IGNITE-8085|https://issues.apache.org/jira/browse/IGNITE-8085]. But this > correction didn't fix [TeamCity > |https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=6814497542781613621=testDetails] > (IgniteProjectionStartStopRestartSelfTest.testStartFiveNodesInTwoCalls). > So it's necessary to make launch remote node via ssh always succesful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7182) Slow sorting of pages collection on checkpoint begin can cause zero dropdown even with throttling enabled
[
https://issues.apache.org/jira/browse/IGNITE-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-7182:
---
Fix Version/s: (was: 2.7)
2.8
> Slow sorting of pages collection on checkpoint begin can cause zero dropdown
> even with throttling enabled
> -
>
> Key: IGNITE-7182
> URL: https://issues.apache.org/jira/browse/IGNITE-7182
> Project: Ignite
> Issue Type: Improvement
> Components: persistence
>Affects Versions: 2.3
>Reporter: Ivan Rakov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
>
> Tests show that GridCacheDatabaseSharedManager#splitAndSortCpPagesIfNeeded
> call can last several seconds on nodes with big amount of memory (>10GB). We
> should optimize sorting algorithm, possibly making it multithreaded.
> Another option to make pages write throttling more smooth is to get rid of
> this heuristic:
> {noformat}
> // Starting with 0.05 to avoid throttle right after
> checkpoint start
> // 7/12 is maximum ratio of dirty pages
> dirtyRatioThreshold = (dirtyRatioThreshold * 0.95 + 0.05) * 7
> / 12;
> {noformat}
> We should replace "magic" lower bound 0.05 * 7 / 12 with the real percentage
> of dirty pages at the moment of
> GridCacheDatabaseSharedManager.Checkpointer#markCheckpointBegin call return.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8227) Research possibility and implement JUnit test failure handler for TeamCity
[ https://issues.apache.org/jira/browse/IGNITE-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8227: --- Fix Version/s: (was: 2.7) 2.8 > Research possibility and implement JUnit test failure handler for TeamCity > -- > > Key: IGNITE-8227 > URL: https://issues.apache.org/jira/browse/IGNITE-8227 > Project: Ignite > Issue Type: Test >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > Fix For: 2.8 > > > After IEP-14 > (https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling) > we found a lot of TC failures involving unexpected nodes stop. > To avoid suites exit codes, tests have NoOpFailureHandler as default. > But instead of this, better handler could be > stopNode + fail currenly running test with message. > This default allows to identify such failures without log-message fail > condition. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5759) IgniteCache 6 suite timed out by GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent
[
https://issues.apache.org/jira/browse/IGNITE-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5759:
---
Fix Version/s: (was: 2.7)
2.8
> IgniteCache 6 suite timed out by
> GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent
> --
>
> Key: IGNITE-5759
> URL: https://issues.apache.org/jira/browse/IGNITE-5759
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Labels: MakeTeamcityGreenAgain, test-fail
> Fix For: 2.8
>
> Attachments: threadDumpFromLogs.log
>
>
> Test history:
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests20=-7061194995222816963=testDetails
> There is no 'Test has been timed out' message in logs.
> Last 'Starting test:' message was
> GridCachePartitionEvictionDuringReadThroughSelfTest#testPartitionRent
> Latest exception from working test was as follows;
> {noformat}
> [23:19:11]W: [org.apache.ignite:ignite-core] [2017-07-14
> 20:19:11,392][ERROR][tcp-comm-worker-#8980%distributed.GridCachePartitionEvictionDuringReadThroughSelfTest4%][TcpCommunicationSpi]
> TcpCommunicationSpi failed to establish connection to node, node will be
> dropped from cluster [rmtNode=TcpDiscoveryNode
> [id=a93fce57-6b2d-4947-8c23-8a677b93, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47503], discPort=47503, order=4, intOrder=4,
> lastExchangeTime=1500063443391, loc=false, ver=2.1.0#19700101-sha1:,
> isClient=false]]
> [23:19:11]W: [org.apache.ignite:ignite-core] class
> org.apache.ignite.IgniteCheckedException: Failed to connect to node (is node
> still alive?). Make sure that each ComputeTask and cache Transaction has a
> timeout set in order to prevent parties from waiting forever in case of
> network issues [nodeId=a93fce57-6b2d-4947-8c23-8a677b93,
> addrs=[/127.0.0.1:45273]]
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3173)
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2757)
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2649)
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.access$5900(TcpCommunicationSpi.java:245)
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$CommunicationWorker.processDisconnect(TcpCommunicationSpi.java:4065)
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$CommunicationWorker.body(TcpCommunicationSpi.java:3891)
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [23:19:11]W: [org.apache.ignite:ignite-core]Suppressed:
> class org.apache.ignite.IgniteCheckedException: Failed to connect to address
> [addr=/127.0.0.1:45273, err=Connection refused]
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3178)
> [23:19:11]W: [org.apache.ignite:ignite-core]... 6
> more
> [23:19:11]W: [org.apache.ignite:ignite-core]Caused by:
> java.net.ConnectException: Connection refused
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:117)
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3024)
> [23:19:11]W: [org.apache.ignite:ignite-core]... 6
> more
> {noformat}
> and then
> {noformat}
> [23:19:11]W: [org.apache.ignite:ignite-core] [2017-07-14
> 20:19:11,895][WARN ][main][root] Interrupting threads started so far: 5
> [23:19:11] : [Step 4/5] [2017-07-14 20:19:11,895][INFO ][main][root] >>>
> Stopping test class:
[jira] [Updated] (IGNITE-5555) Ignite PDS 1: JVM crash on teamcity (Rare)
[
https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-:
---
Fix Version/s: (was: 2.7)
2.8
> Ignite PDS 1: JVM crash on teamcity (Rare)
> --
>
> Key: IGNITE-
> URL: https://issues.apache.org/jira/browse/IGNITE-
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Labels: MakeTeamcityGreenAgain, test-fail
> Fix For: 2.8
>
> Attachments: crash_report, hs_err_pid7100.log.txt, thread_dump
>
>
> Most recent crashes
> https://ci.ignite.apache.org/viewLog.html?buildId=1095007=IgniteTests24Java8_IgnitePds1=buildResultsDiv
> {noformat}
>Ignite PDS 1 [ tests 0 JVM CRASH ]
> BPlusTreeReuseListPageMemoryImplTest.testEmptyCursors (last started)
> {noformat}
> https://ci.ignite.apache.org/viewLog.html?buildId=1086130=buildResultsDiv=IgniteTests24Java8_IgnitePds1
> {noformat}
>Ignite PDS 1 [ tests 0 JVM CRASH ]
> BPlusTreeReuseListPageMemoryImplTest.testEmptyCursors (last started)
> {noformat}
> (older failure
> http://ci.ignite.apache.org/viewLog.html?buildId=675694=buildResultsDiv=Ignite20Tests_IgnitePds1#)
> Stacktrace indicates failure was in ignite code related to B+tree
> {noformat}J 34156 C2
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.readLockPage(JLorg/apache/ignite/internal/pagemem/FullPageId;ZZ)J
> (88 bytes) @ 0x7f98cfc24a5a [0x7f98cfc24540+0x51a]
> J 34634 C2
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(JJJLorg/apache/ignite/internal/processors/cache/persistence/tree/io/BPlusIO;Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Get;I)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
> (380 bytes) @ 0x7f98d32dd524 [0x7f98d32dd100+0x424]
> J 34633 C2
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(Lorg/apache/ignite/internal/pagemem/PageMemory;IJJLorg/apache/ignite/internal/processors/cache/persistence/tree/util/PageLockListener;Lorg/apache/ignite/internal/processors/cache/persistence/tree/util/PageHandler;Ljava/lang/Object;ILjava/lang/Object;)Ljava/lang/Object;
> (81 bytes) @ 0x7f98d2091c94 [0x7f98d2091a40+0x254]
> J 34888 C2
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
> (561 bytes) @ 0x7f98d2ca146c [0x7f98d2ca1180+0x2ec]
> J 34888 C2
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
> (561 bytes) @ 0x7f98d2ca17f8 [0x7f98d2ca1180+0x678]
> J 34888 C2
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
> (561 bytes) @ 0x7f98d2ca17f8 [0x7f98d2ca1180+0x678]
> J 34888 C2
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
> (561 bytes) @ 0x7f98d2ca17f8 [0x7f98d2ca1180+0x678]
> J 35053 C2
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(Ljava/lang/Object;Ljava/lang/Object;Lorg/apache/ignite/internal/util/Igni
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7584) Smooth decrease WAL write speed if low work segments left
[ https://issues.apache.org/jira/browse/IGNITE-7584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7584: --- Fix Version/s: (was: 2.7) 2.8 > Smooth decrease WAL write speed if low work segments left > - > > Key: IGNITE-7584 > URL: https://issues.apache.org/jira/browse/IGNITE-7584 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > Fix For: 2.8 > > > Smooth decrease of the write speed in WAL when approaching the exhaustion of > current segments in the working directory. > Now archiver segment switch involves file copying and may be bottleneck of > speed of grid operation. > Now if out of work segments occurs, grid put speed drop down to 0 ops/sec > ocurred. > This isssue was fixed under IGNITE-7017 with providing new 'NoArchvier' mode, > but in case archiver based WAL is already used by end-user, it is required to > have opportunity to smooth decrease speed instead of drop to 0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
