[jira] [Commented] (IGNITE-9217) Uncomment 24 test classes in IgniteCacheTestSuite2 (Cache 2)
[
https://issues.apache.org/jira/browse/IGNITE-9217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852363#comment-16852363
]
Ignite TC Bot commented on IGNITE-9217:
---
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 2{color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=3990997]]
* IgniteCacheTestSuite2:
GridCachePartitionedEvictionSelfTest.testEvictionTxOptimisticRepeatableRead
* IgniteCacheTestSuite2:
GridCacheLocalBasicStoreMultithreadedSelfTest.testConcurrentGet
* IgniteCacheTestSuite2: dht.IgniteCacheContainsKeyColocatedSelfTest
* IgniteCacheTestSuite2: near.IgniteCacheContainsKeyNearSelfTest
* IgniteCacheTestSuite2: dht.GridCachePartitionedNearDisabledMetricsSelfTest
{color:#d04437}Queries 2{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=3990958]]
* IgniteBinaryCacheQueryTestSuite2:
GridCachePartitionedTxMultiNodeSelfTest.testPutTwoEntryInTxMultiThreaded
* IgniteBinaryCacheQueryTestSuite2:
GridCachePartitionedTxMultiNodeSelfTest.testRemoveInTxQueried
* IgniteBinaryCacheQueryTestSuite2:
GridCachePartitionedTxMultiNodeSelfTest.testPutTwoEntriesInTx
* IgniteBinaryCacheQueryTestSuite2:
GridCachePartitionedTxMultiNodeSelfTest.testRemoveInTxQueriedMultiThreaded
{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3991046]]
{color:#d04437}PDS (Indexing){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3991012]]
{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=3991020]]
{color:#d04437}MVCC Cache 2{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=3991033]]
* IgniteCacheMvccTestSuite2: GridCachePartitionedNestedTxTest.testLockAndTx
* IgniteCacheMvccTestSuite2: GridCachePartitionedNestedTxTest.testLockAndTx1
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3991047buildTypeId=IgniteTests24Java8_RunAll]
> Uncomment 24 test classes in IgniteCacheTestSuite2 (Cache 2)
>
>
> Key: IGNITE-9217
> URL: https://issues.apache.org/jira/browse/IGNITE-9217
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
>
> //suite.addTestSuite(GridCacheLocalBasicStoreMultithreadedSelfTest.class);
> //suite.addTestSuite(GridCacheLocalTxReadTest.class);
> //suite.addTest(new
> TestSuite(RendezvousAffinityFunctionSelfTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedEntryLockSelfTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedEvictionSelfTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedNestedTxTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedStorePutSelfTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedTxConcurrentGetTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedTxMultiNodeSelfTest.class));
> //suite.addTest(new TestSuite(GridCachePartitionedTxReadTest.class));
> //suite.addTest(new
> TestSuite(NearCacheMultithreadedUpdateTest.class));
> //suite.addTest(new TestSuite(NearCachePutAllMultinodeTest.class));
> //suite.addTest(new
> TestSuite(IgniteCacheContainsKeyNearSelfTest.class));
> //suite.addTest(new TestSuite(IgniteCacheNearTxRollbackTest.class));
> //suite.addTest(new TestSuite(GridCacheColocatedDebugTest.class));
> //suite.addTest(new
> TestSuite(GridCacheDhtAtomicEvictionNearReadersSelfTest.class));
> //suite.addTest(new TestSuite(GridCacheDhtEntrySetSelfTest.class));
> //suite.addTest(new
> TestSuite(GridCacheDhtEvictionNearReadersSelfTest.class));
> //suite.addTest(new TestSuite(GridCacheDhtMultiBackupTest.class));
> //suite.addTest(new
> TestSuite(GridCacheDhtPreloadMessageCountTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedNearDisabledMetricsSelfTest.class));
> //suite.addTest(new
> TestSuite(IgniteCacheContainsKeyColocatedSelfTest.class));
> //suite.addTest(new
> TestSuite(IgniteCrossCacheTxNearEnabledSelfTest.class));
> //suite.addTest(new
> TestSuite(IgniteTxConsistencyColocatedRestartSelfTest.class));
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11818) Support JMX/control.sh for debug page info
[
https://issues.apache.org/jira/browse/IGNITE-11818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852349#comment-16852349
]
Dmitriy Govorukhin commented on IGNITE-11818:
-
No need this API right now, won't do.
> Support JMX/control.sh for debug page info
> --
>
> Key: IGNITE-11818
> URL: https://issues.apache.org/jira/browse/IGNITE-11818
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Support JMX/control.sh for debug page info
> JMX
> {code}
> public interface DiagnosticMXBean {
> @MXBeanDescription("Dump page history to custom path.")
> void dumpPageHistory(boolean dumpToFile, boolean dumpToLog, String
> filePath, long... pageIds);
> @MXBeanDescription("Dump page history.")
> void dumpPageHistory(boolean dumpToFile, boolean dumpToLog, long...
> pageIds);
> }
> {code}
> console.sh command:
> {noformat}
> control.sh --diagnostic page_history print_to_log print_to_file [page_ids
> ] [dump_path ] [--yes]
> --diagnostic - command for dumping some diagnostic info
> page_history - subcommand for dumping only page_history. Required.
> page_ids {list_of_page_ids} - list of page ids for dumping
> print_to_log, print_to_file - place for dumping(file or log or both). At
> least one of them is required.
> dump_path - custom path to folder(absolute or
> relative of work_dir).
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11749) Implement automatic pages history dump on CorruptedTreeException
[
https://issues.apache.org/jira/browse/IGNITE-11749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852341#comment-16852341
]
Dmitriy Govorukhin commented on IGNITE-11749:
-
[~akalashnikov], [~ibessonov] Thanks for the contribution. Merged to master.
> Implement automatic pages history dump on CorruptedTreeException
>
>
> Key: IGNITE-11749
> URL: https://issues.apache.org/jira/browse/IGNITE-11749
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, the only way to debug possible bugs in checkpointer/recovery
> mechanics is to manually parse WAL files after the corruption happened. This
> is not practical for several reasons. First, it requires manual actions which
> depend on the content of the exception. Second, it is not always possible to
> obtain WAL files (it may contain sensitive data).
> We need to add a mechanics which will dump all information required for
> primary analysis of the corruption to the exception handler. For example, if
> an exception happened when materializing a link {{0xabcd}} written on an
> index page {{0xdcba}}, we need to dump history of both pages changes,
> checkpoint records on the analysis interval. Possibly, we should include
> FreeList pages to which the aforementioned pages were included to.
> Example of output:
> {noformat}
> [2019-05-07 11:57:57,350][INFO
> ][test-runner-#58%diagnostic.DiagnosticProcessorTest%][PageHistoryDiagnoster]
> Next WAL record :: PageSnapshot [fullPageId = FullPageId
> [pageId=0002, effectivePageId=,
> grpId=-2100569601], page = [
> Header [
> type=11 (PageMetaIO),
> ver=1,
> crc=0,
> pageId=844420635164672(offset=0, flags=10, partId=65535, index=0)
> ],
> PageMeta[
> treeRoot=844420635164675,
> lastSuccessfulFullSnapshotId=0,
> lastSuccessfulSnapshotId=0,
> nextSnapshotTag=1,
> lastSuccessfulSnapshotTag=0,
> lastAllocatedPageCount=0,
> candidatePageCount=0
> ]],
> super = [WALRecord [size=4129, chainSize=0, pos=FileWALPointer [idx=0,
> fileOff=103, len=4129], type=PAGE_RECORD]]]
> Next WAL record :: CheckpointRecord
> [cpId=c6ba7793-113b-4b54-8530-45e1708ca44c, end=false, cpMark=FileWALPointer
> [idx=0, fileOff=29, len=29], super=WALRecord [size=1963, chainSize=0,
> pos=FileWALPointer [idx=0, fileOff=39686, len=1963], type=CHECKPOINT_RECORD]]
> Next WAL record :: PageSnapshot [fullPageId = FullPageId
> [pageId=0002, effectivePageId=,
> grpId=-1368047378], page = [
> Header [
> type=11 (PageMetaIO),
> ver=1,
> crc=0,
> pageId=844420635164672(offset=0, flags=10, partId=65535, index=0)
> ],
> PageMeta[
> treeRoot=844420635164675,
> lastSuccessfulFullSnapshotId=0,
> lastSuccessfulSnapshotId=0,
> nextSnapshotTag=1,
> lastSuccessfulSnapshotTag=0,
> lastAllocatedPageCount=0,
> candidatePageCount=0
> ]],
> super = [WALRecord [size=4129, chainSize=0, pos=FileWALPointer [idx=0,
> fileOff=55961, len=4129], type=PAGE_RECORD]]]
> Next WAL record :: CheckpointRecord
> [cpId=145e599e-66fc-45f5-bde4-b0c392125968, end=false, cpMark=null,
> super=WALRecord [size=21409, chainSize=0, pos=FileWALPointer [idx=0,
> fileOff=13101788, len=21409], type=CHECKPOINT_RECORD]]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-11749) Implement automatic pages history dump on CorruptedTreeException
[
https://issues.apache.org/jira/browse/IGNITE-11749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Govorukhin resolved IGNITE-11749.
-
Resolution: Fixed
> Implement automatic pages history dump on CorruptedTreeException
>
>
> Key: IGNITE-11749
> URL: https://issues.apache.org/jira/browse/IGNITE-11749
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, the only way to debug possible bugs in checkpointer/recovery
> mechanics is to manually parse WAL files after the corruption happened. This
> is not practical for several reasons. First, it requires manual actions which
> depend on the content of the exception. Second, it is not always possible to
> obtain WAL files (it may contain sensitive data).
> We need to add a mechanics which will dump all information required for
> primary analysis of the corruption to the exception handler. For example, if
> an exception happened when materializing a link {{0xabcd}} written on an
> index page {{0xdcba}}, we need to dump history of both pages changes,
> checkpoint records on the analysis interval. Possibly, we should include
> FreeList pages to which the aforementioned pages were included to.
> Example of output:
> {noformat}
> [2019-05-07 11:57:57,350][INFO
> ][test-runner-#58%diagnostic.DiagnosticProcessorTest%][PageHistoryDiagnoster]
> Next WAL record :: PageSnapshot [fullPageId = FullPageId
> [pageId=0002, effectivePageId=,
> grpId=-2100569601], page = [
> Header [
> type=11 (PageMetaIO),
> ver=1,
> crc=0,
> pageId=844420635164672(offset=0, flags=10, partId=65535, index=0)
> ],
> PageMeta[
> treeRoot=844420635164675,
> lastSuccessfulFullSnapshotId=0,
> lastSuccessfulSnapshotId=0,
> nextSnapshotTag=1,
> lastSuccessfulSnapshotTag=0,
> lastAllocatedPageCount=0,
> candidatePageCount=0
> ]],
> super = [WALRecord [size=4129, chainSize=0, pos=FileWALPointer [idx=0,
> fileOff=103, len=4129], type=PAGE_RECORD]]]
> Next WAL record :: CheckpointRecord
> [cpId=c6ba7793-113b-4b54-8530-45e1708ca44c, end=false, cpMark=FileWALPointer
> [idx=0, fileOff=29, len=29], super=WALRecord [size=1963, chainSize=0,
> pos=FileWALPointer [idx=0, fileOff=39686, len=1963], type=CHECKPOINT_RECORD]]
> Next WAL record :: PageSnapshot [fullPageId = FullPageId
> [pageId=0002, effectivePageId=,
> grpId=-1368047378], page = [
> Header [
> type=11 (PageMetaIO),
> ver=1,
> crc=0,
> pageId=844420635164672(offset=0, flags=10, partId=65535, index=0)
> ],
> PageMeta[
> treeRoot=844420635164675,
> lastSuccessfulFullSnapshotId=0,
> lastSuccessfulSnapshotId=0,
> nextSnapshotTag=1,
> lastSuccessfulSnapshotTag=0,
> lastAllocatedPageCount=0,
> candidatePageCount=0
> ]],
> super = [WALRecord [size=4129, chainSize=0, pos=FileWALPointer [idx=0,
> fileOff=55961, len=4129], type=PAGE_RECORD]]]
> Next WAL record :: CheckpointRecord
> [cpId=145e599e-66fc-45f5-bde4-b0c392125968, end=false, cpMark=null,
> super=WALRecord [size=21409, chainSize=0, pos=FileWALPointer [idx=0,
> fileOff=13101788, len=21409], type=CHECKPOINT_RECORD]]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11256) Implement read-only mode for grid
[ https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852080#comment-16852080 ] Dmitriy Pavlov commented on IGNITE-11256: - Thanks [~antonovsergey93], I'm going to take a look at the code. > Implement read-only mode for grid > - > > Key: IGNITE-11256 > URL: https://issues.apache.org/jira/browse/IGNITE-11256 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Should be triggered from control.sh utility. > Useful for maintenance work, for example checking partition consistency > (idle_verify) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11256) Implement read-only mode for grid
[ https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852066#comment-16852066 ] Sergey Antonov commented on IGNITE-11256: - [~dpavlov] done. > Implement read-only mode for grid > - > > Key: IGNITE-11256 > URL: https://issues.apache.org/jira/browse/IGNITE-11256 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Should be triggered from control.sh utility. > Useful for maintenance work, for example checking partition consistency > (idle_verify) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix
[
https://issues.apache.org/jira/browse/IGNITE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-10663:
--
Comment: was deleted
(was: #PR with readRepair enabled for each get!
Ignore this :)
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 30 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=3988786]]
* exe: CacheAbstractTest.TestReplacex
* exe: CacheAbstractTest.TestGetAndReplace
* exe: CacheAbstractTest.TestContainsKey
* exe: CacheAbstractTransactionalTest.TestTransactionScopeAllOperations
* exe: CacheAbstractTest.TestRemovex
* exe: CacheAbstractTest.TestGetAndPut
* exe: CacheAbstractTransactionalTest.TestTransactionScopeAllOperations
* exe: CacheAbstractTest.TestInvoke
* exe: CacheAbstractTest.TestGetAndPutIfAbsent
* exe: CacheAbstractTest.TestClearKey
* exe: CacheAbstractTest.TestGetAndPut
* exe: CacheAbstractTest.TestGetAndPutIfAbsent
* exe: CacheAbstractTest.TestInvoke
* exe: CachePartitionedAtomicTest.TestPutIfAbsent(False)
* exe: CacheAbstractTest.TestRemovex
* exe: CacheAbstractTest.TestReplace
* exe: CacheAbstractTest.TestReplace
* exe: CacheAbstractTest.TestRemove
* exe: CacheAbstractTest.TestGetAndRemove
* exe: CacheAbstractTransactionalTest.TestTxDeadlockDetection
* exe: CacheAbstractTest.TestReplacex
* exe: CacheAbstractTest.TestClearKey
* exe: CacheAbstractTest.TestRemove
* exe: CacheAbstractTest.TestGetAndReplace
* exe: CacheAbstractTest.TestContainsKey
* exe: CacheAbstractTest.TestGetAndRemove
* exe: CachePartitionedTest.TestPutIfAbsent(False)
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3988790]]
{color:#d04437}Cache 6{color} [[tests
26|https://ci.ignite.apache.org/viewLog.html?buildId=3988765]]
* IgniteCacheTestSuite6: TxRollbackOnTimeoutTest.testSimple
* IgniteCacheTestSuite6:
IgniteOptimisticTxSuspendResumeTest.testCrossCacheTxInAnotherThread
* IgniteCacheTestSuite6:
ReplicatedAtomicCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6:
ReplicatedAtomicCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6:
IgniteOptimisticTxSuspendResumeTest.testSuspendTxAndStartNew
* IgniteCacheTestSuite6:
IgniteOptimisticTxSuspendResumeTest.testSuspendTxAndStartNewWithoutCommit
* IgniteCacheTestSuite6: IgniteOptimisticTxSuspendResumeTest.testTxRollback
* IgniteCacheTestSuite6: IgniteOptimisticTxSuspendResumeTest.testResumeActiveTx
* IgniteCacheTestSuite6: transactions.TxRollbackOnTopologyChangeTest
* IgniteCacheTestSuite6:
ReplicatedTransactionalOptimisticCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6:
ReplicatedTransactionalOptimisticCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6: TxRollbackOnTimeoutNoDeadlockDetectionTest.testSimple
* IgniteCacheTestSuite6:
ReplicatedTransactionalPessimisticCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6:
ReplicatedTransactionalPessimisticCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6:
IgniteOptimisticTxSuspendResumeTest.testResumeTxInAnotherThread
* IgniteCacheTestSuite6:
PartitionedAtomicCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6:
PartitionedAtomicCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6:
TxRollbackOnTimeoutNearCacheTest.testLockAndConcurrentTimeout
* IgniteCacheTestSuite6:
PartitionedTransactionalOptimisticCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6:
PartitionedTransactionalOptimisticCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6:
TxRollbackOnTopologyChangeTest.testRollbackOnTopologyChange
* IgniteCacheTestSuite6:
PartitionedTransactionalPessimisticCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6:
PartitionedTransactionalPessimisticCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6:
TxOptimisticOnPartitionExchangeTest.testConsistencyOnPartitionExchange
{color:#d04437}PDS 4{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=3988781]]
* IgnitePdsTestSuite4:
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testDestroySpecificCacheAndCacheGroupSecondGroup
{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3988761]]
{color:#d04437}MVCC PDS 2{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=3988806]]
* IgnitePdsMvccTestSuite2:
LocalWalModeChangeDuringRebalancingSelfTest.testDataClearedAfterRestartWithDisabledWal
{color:#d04437}Platform .NET{color} [[tests 58 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=3988782]]
* exe: CacheTest.TestClearAll
*
[jira] [Commented] (IGNITE-11256) Implement read-only mode for grid
[ https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852033#comment-16852033 ] Dmitriy Pavlov commented on IGNITE-11256: - [~antonovsergey93], was this feature discussed with the community? Could you please link dev. list thread or start a new one? At least, this changes public API and this is expected to be discussed using the list. > Implement read-only mode for grid > - > > Key: IGNITE-11256 > URL: https://issues.apache.org/jira/browse/IGNITE-11256 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Should be triggered from control.sh utility. > Useful for maintenance work, for example checking partition consistency > (idle_verify) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11256) Implement read-only mode for grid
[ https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov reassigned IGNITE-11256: --- Assignee: Sergey Antonov (was: Dmitriy Pavlov) > Implement read-only mode for grid > - > > Key: IGNITE-11256 > URL: https://issues.apache.org/jira/browse/IGNITE-11256 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Should be triggered from control.sh utility. > Useful for maintenance work, for example checking partition consistency > (idle_verify) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11256) Implement read-only mode for grid
[ https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov reassigned IGNITE-11256: --- Assignee: Dmitriy Pavlov (was: Sergey Antonov) > Implement read-only mode for grid > - > > Key: IGNITE-11256 > URL: https://issues.apache.org/jira/browse/IGNITE-11256 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Dmitriy Pavlov >Priority: Major > Fix For: 2.8 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Should be triggered from control.sh utility. > Useful for maintenance work, for example checking partition consistency > (idle_verify) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11256) Implement read-only mode for grid
[
https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852025#comment-16852025
]
Alexey Goncharuk commented on IGNITE-11256:
---
A few other comments:
* Remove exclamation signs from the log messages: ("Not all nodes in cluster
supports cluster read-only mode!", "Read-only mode is enabled!", "Read-only
mode is disabled!", others, if there are any). Also, it would be great to
output the node ID or client ID that triggered this change (can be done as a
separate ticket, if necessary)
* We need to add security permission for this feature (separate ticket as well
- but also the ticket should cover permissions for baseline change, and
probably for activation/deactivation)
> Implement read-only mode for grid
> -
>
> Key: IGNITE-11256
> URL: https://issues.apache.org/jira/browse/IGNITE-11256
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexei Scherbakov
>Assignee: Sergey Antonov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Should be triggered from control.sh utility.
> Useful for maintenance work, for example checking partition consistency
> (idle_verify)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11256) Implement read-only mode for grid
[
https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852024#comment-16852024
]
Roman Kondakov commented on IGNITE-11256:
-
[~antonovsergey93], [~agoncharuk] in my opinion we need to keep
{{org.h2.api.ErrorCode}} and
{{org.apache.ignite.internal.processors.odbc.SqlStateCode}} in consistent state.
> Implement read-only mode for grid
> -
>
> Key: IGNITE-11256
> URL: https://issues.apache.org/jira/browse/IGNITE-11256
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexei Scherbakov
>Assignee: Sergey Antonov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Should be triggered from control.sh utility.
> Useful for maintenance work, for example checking partition consistency
> (idle_verify)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11256) Implement read-only mode for grid
[
https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852012#comment-16852012
]
Alexey Goncharuk commented on IGNITE-11256:
---
Hm, after going deeper to the code I see that actually {{SqlStateCode}} is
related to ODBC, but {{IgniteQueryErrorCode}} is related to queries. [~isapego]
can you take a look at the change as well?
P.S. I wonder why we have two places to indicate SQL error codes?
> Implement read-only mode for grid
> -
>
> Key: IGNITE-11256
> URL: https://issues.apache.org/jira/browse/IGNITE-11256
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexei Scherbakov
>Assignee: Sergey Antonov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Should be triggered from control.sh utility.
> Useful for maintenance work, for example checking partition consistency
> (idle_verify)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11875) Thin client is unable to authenticate with long password
[
https://issues.apache.org/jira/browse/IGNITE-11875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852011#comment-16852011
]
Igor Sapego commented on IGNITE-11875:
--
[~ptupitsyn], you are right. Will do.
> Thin client is unable to authenticate with long password
>
>
> Key: IGNITE-11875
> URL: https://issues.apache.org/jira/browse/IGNITE-11875
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, odbc, thin client
>Affects Versions: 2.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Token authentication could use long usernames/passwords, that leads to
> "Invalid handshake message"
> ClientListenerNioServerBuffer:
> {code:java}
> if (cnt == msgSize) {
> byte[] data0 = data;
> reset();
> return data0;
> }
> else {
> if (checkHandshake && cnt > 0 && (msgSize >
> ClientListenerNioListener.MAX_HANDSHAKE_MSG_SIZE
> || data[0] != ClientListenerRequest.HANDSHAKE))
> throw new IgniteCheckedException("Invalid handshake message");
> return null;
> }
> {code}
> The reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11256) Implement read-only mode for grid
[
https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852007#comment-16852007
]
Alexey Goncharuk commented on IGNITE-11256:
---
[~antonovsergey93], it looks like the SQL error codes should be identical to
{{org.h2.api.ErrorCode}}, so the error for this change should be
{{ErrorCode.DATABASE_IS_READ_ONLY}}.
[~amashenkov], [~rkondakov] can you confirm?
> Implement read-only mode for grid
> -
>
> Key: IGNITE-11256
> URL: https://issues.apache.org/jira/browse/IGNITE-11256
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexei Scherbakov
>Assignee: Sergey Antonov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Should be triggered from control.sh utility.
> Useful for maintenance work, for example checking partition consistency
> (idle_verify)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11256) Implement read-only mode for grid
[ https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852001#comment-16852001 ] Sergey Antonov commented on IGNITE-11256: - [~dpavlov] Could you merge my PR to master branch please? > Implement read-only mode for grid > - > > Key: IGNITE-11256 > URL: https://issues.apache.org/jira/browse/IGNITE-11256 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Should be triggered from control.sh utility. > Useful for maintenance work, for example checking partition consistency > (idle_verify) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix
[
https://issues.apache.org/jira/browse/IGNITE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851964#comment-16851964
]
Ignite TC Bot commented on IGNITE-10663:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 30 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=3988786]]
* exe: CacheAbstractTest.TestReplacex
* exe: CacheAbstractTest.TestGetAndReplace
* exe: CacheAbstractTest.TestContainsKey
* exe: CacheAbstractTransactionalTest.TestTransactionScopeAllOperations
* exe: CacheAbstractTest.TestRemovex
* exe: CacheAbstractTest.TestGetAndPut
* exe: CacheAbstractTransactionalTest.TestTransactionScopeAllOperations
* exe: CacheAbstractTest.TestInvoke
* exe: CacheAbstractTest.TestGetAndPutIfAbsent
* exe: CacheAbstractTest.TestClearKey
* exe: CacheAbstractTest.TestGetAndPut
* exe: CacheAbstractTest.TestGetAndPutIfAbsent
* exe: CacheAbstractTest.TestInvoke
* exe: CachePartitionedAtomicTest.TestPutIfAbsent(False)
* exe: CacheAbstractTest.TestRemovex
* exe: CacheAbstractTest.TestReplace
* exe: CacheAbstractTest.TestReplace
* exe: CacheAbstractTest.TestRemove
* exe: CacheAbstractTest.TestGetAndRemove
* exe: CacheAbstractTransactionalTest.TestTxDeadlockDetection
* exe: CacheAbstractTest.TestReplacex
* exe: CacheAbstractTest.TestClearKey
* exe: CacheAbstractTest.TestRemove
* exe: CacheAbstractTest.TestGetAndReplace
* exe: CacheAbstractTest.TestContainsKey
* exe: CacheAbstractTest.TestGetAndRemove
* exe: CachePartitionedTest.TestPutIfAbsent(False)
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3988790]]
{color:#d04437}Cache 6{color} [[tests
26|https://ci.ignite.apache.org/viewLog.html?buildId=3988765]]
* IgniteCacheTestSuite6: TxRollbackOnTimeoutTest.testSimple
* IgniteCacheTestSuite6:
IgniteOptimisticTxSuspendResumeTest.testCrossCacheTxInAnotherThread
* IgniteCacheTestSuite6:
ReplicatedAtomicCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6:
ReplicatedAtomicCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6:
IgniteOptimisticTxSuspendResumeTest.testSuspendTxAndStartNew
* IgniteCacheTestSuite6:
IgniteOptimisticTxSuspendResumeTest.testSuspendTxAndStartNewWithoutCommit
* IgniteCacheTestSuite6: IgniteOptimisticTxSuspendResumeTest.testTxRollback
* IgniteCacheTestSuite6: IgniteOptimisticTxSuspendResumeTest.testResumeActiveTx
* IgniteCacheTestSuite6: transactions.TxRollbackOnTopologyChangeTest
* IgniteCacheTestSuite6:
ReplicatedTransactionalOptimisticCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6:
ReplicatedTransactionalOptimisticCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6: TxRollbackOnTimeoutNoDeadlockDetectionTest.testSimple
* IgniteCacheTestSuite6:
ReplicatedTransactionalPessimisticCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6:
ReplicatedTransactionalPessimisticCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6:
IgniteOptimisticTxSuspendResumeTest.testResumeTxInAnotherThread
* IgniteCacheTestSuite6:
PartitionedAtomicCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6:
PartitionedAtomicCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6:
TxRollbackOnTimeoutNearCacheTest.testLockAndConcurrentTimeout
* IgniteCacheTestSuite6:
PartitionedTransactionalOptimisticCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6:
PartitionedTransactionalOptimisticCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6:
TxRollbackOnTopologyChangeTest.testRollbackOnTopologyChange
* IgniteCacheTestSuite6:
PartitionedTransactionalPessimisticCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6:
PartitionedTransactionalPessimisticCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6:
TxOptimisticOnPartitionExchangeTest.testConsistencyOnPartitionExchange
{color:#d04437}PDS 4{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=3988781]]
* IgnitePdsTestSuite4:
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testDestroySpecificCacheAndCacheGroupSecondGroup
{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3988761]]
{color:#d04437}MVCC PDS 2{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=3988806]]
* IgnitePdsMvccTestSuite2:
LocalWalModeChangeDuringRebalancingSelfTest.testDataClearedAfterRestartWithDisabledWal
{color:#d04437}Platform .NET{color} [[tests 58 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=3988782]]
* exe: CacheTest.TestClearAll
* exe: CacheTest.TestClearKey
* exe:
[jira] [Commented] (IGNITE-9217) Uncomment 24 test classes in IgniteCacheTestSuite2 (Cache 2)
[
https://issues.apache.org/jira/browse/IGNITE-9217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851919#comment-16851919
]
Ignite TC Bot commented on IGNITE-9217:
---
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 2{color} [[tests
19|https://ci.ignite.apache.org/viewLog.html?buildId=3988645]]
* IgniteCacheTestSuite2:
GridCachePartitionedEvictionSelfTest.testEvictionTxPessimisticReadCommitted
* IgniteCacheTestSuite2:
GridCachePartitionedEvictionSelfTest.testEvictionTxOptimisticSerializable
* IgniteCacheTestSuite2:
GridCachePartitionedEvictionSelfTest.testEvictionTxPessimisticSerializable
* IgniteCacheTestSuite2:
GridCachePartitionedEvictionSelfTest.testEvictionTxOptimisticRepeatableRead
* IgniteCacheTestSuite2:
GridCacheLocalBasicStoreMultithreadedSelfTest.testConcurrentGet
* IgniteCacheTestSuite2:
GridCachePartitionedEvictionSelfTest.testEvictionTxOptimisticReadCommitted
* IgniteCacheTestSuite2:
GridCacheReplicatedTxMultiNodeBasicTest.testRemoveInTxSimple
* IgniteCacheTestSuite2:
GridCacheReplicatedTxMultiNodeBasicTest.testRemoveInTxQueried
* IgniteCacheTestSuite2:
GridCacheReplicatedTxMultiNodeBasicTest.testRemoveInTxQueriedMultiThreaded
* IgniteCacheTestSuite2:
GridCachePartitionedTxMultiNodeSelfTest.testRemoveInTxSimple
* IgniteCacheTestSuite2:
GridCachePartitionedTxMultiNodeSelfTest.testRemoveInTxQueried
* IgniteCacheTestSuite2:
GridCachePartitionedTxMultiNodeSelfTest.testPutTwoEntriesInTx
* IgniteCacheTestSuite2:
GridCachePartitionedTxMultiNodeSelfTest.testRemoveInTxQueriedMultiThreaded
* IgniteCacheTestSuite2: dht.IgniteCacheContainsKeyColocatedSelfTest
* IgniteCacheTestSuite2: near.IgniteCacheContainsKeyNearSelfTest
* IgniteCacheTestSuite2: dht.GridCachePartitionedNearDisabledMetricsSelfTest
* IgniteCacheTestSuite2: GridCacheDhtMultiBackupTest.testPut
* IgniteCacheTestSuite2:
GridCachePartitionedEvictionSelfTest.testEvictionTxPessimisticRepeatableRead
{color:#d04437}MVCC Queries{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3988629]]
{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3988694]]
{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=3988668]]
{color:#d04437}MVCC Cache 2{color} [[tests
87|https://ci.ignite.apache.org/viewLog.html?buildId=3988681]]
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testMissesOnEmptyCache
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testPutAvgTime
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testPutIfAbsentAsyncAvgTime
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testUpdateInvocations
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testInvokeAsyncAvgTime
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testInvokeAllAsyncAvgTime
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testCacheSizeWorksAsSize
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testRemoveAvgTime
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testInvokeAllAsyncMultipleKeysAvgTime
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testPessimisticRepeatableReadRollbacks
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testOptimisticSerializableRollbacks
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testGetAndPutAsyncAvgTime
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testRemoves
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testInvocationRemovesOnEmptyCache
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testMissHitPercentage
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testGetAndPutIfAbsentAsyncAvgTime
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testGetAndRemoveAsyncAvgTime
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testTxEvictions
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testInvokeAllAvgTime
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testReadOnlyInvocationsOnEmptyCache
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testPutAsyncAvgTime
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testUpdateInvocationsOnEmptyCache
* IgniteCacheMvccTestSuite2:
GridCachePartitionedNearDisabledMetricsSelfTest.testGetAvgTime
* IgniteCacheMvccTestSuite2:
[jira] [Commented] (IGNITE-9409) yarn IgniteProvider uses an obsolete URL for a version check
[ https://issues.apache.org/jira/browse/IGNITE-9409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851893#comment-16851893 ] Ilya Kasnacheev commented on IGNITE-9409: - [~shroman] do you have plans to work on this issue? If you don't, I will remove this check altogether, always rely on other mechanisms (which is the only what works currently). > yarn IgniteProvider uses an obsolete URL for a version check > > > Key: IGNITE-9409 > URL: https://issues.apache.org/jira/browse/IGNITE-9409 > Project: Ignite > Issue Type: Bug >Reporter: Roman Shtykh >Assignee: Roman Shtykh >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11881) Spark Data Frame examples not working
[ https://issues.apache.org/jira/browse/IGNITE-11881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-11881: - Summary: Spark Data Frame examples not working (was: Spark Data Fram example not working) > Spark Data Frame examples not working > - > > Key: IGNITE-11881 > URL: https://issues.apache.org/jira/browse/IGNITE-11881 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Blocker > > # Spark Data Frames examples fail. > # Spark Data Frame examples don't execute on TC. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11881) Spark Data Fram example not working
Nikolay Izhikov created IGNITE-11881: Summary: Spark Data Fram example not working Key: IGNITE-11881 URL: https://issues.apache.org/jira/browse/IGNITE-11881 Project: Ignite Issue Type: Improvement Reporter: Nikolay Izhikov Assignee: Nikolay Izhikov # Spark Data Frames examples fail. # Spark Data Frame examples don't execute on TC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11880) [TC Bot] Configurable notifications by build parameters/suite IDS & names
[
https://issues.apache.org/jira/browse/IGNITE-11880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11880:
Ignite Flags: (was: Docs Required)
> [TC Bot] Configurable notifications by build parameters/suite IDS & names
> -
>
> Key: IGNITE-11880
> URL: https://issues.apache.org/jira/browse/IGNITE-11880
> Project: Ignite
> Issue Type: Improvement
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> Support tagging build by custom rules, not only by build parameters, e.g.
> suite name
> Support configuring custom notification channels by tags present in suite.
> Special filtering parameters option for Tc configuration now can be used for
> filtering build and tagging it.
> {noformat}
> "filteringParameters": [
> {
> "name": "env.JAVA_HOME",
> "selection": [
> {"value":"%env.JDK_ORA_18%", "label":"JDK8"},
> {"value":"%env.JDK_ORA_9%", "label":"JDK9"},
> {"value":"%env.JDK_ORA_10%", "label":"JDK10"},
> {"value":"%env.JDK_OPEN_11%", "label":"JDK11"}
> ]
> }
> ]
> {noformat}
> Improve this feature by special parameter names, like _suiteName and regexps
> in value
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11880) [TC Bot] Configurable notifications by build parameters/suite IDS & names
Dmitriy Pavlov created IGNITE-11880:
---
Summary: [TC Bot] Configurable notifications by build
parameters/suite IDS & names
Key: IGNITE-11880
URL: https://issues.apache.org/jira/browse/IGNITE-11880
Project: Ignite
Issue Type: Improvement
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
Support tagging build by custom rules, not only by build parameters, e.g. suite
name
Support configuring custom notification channels by tags present in suite.
Special filtering parameters option for Tc configuration now can be used for
filtering build and tagging it.
{noformat}
"filteringParameters": [
{
"name": "env.JAVA_HOME",
"selection": [
{"value":"%env.JDK_ORA_18%", "label":"JDK8"},
{"value":"%env.JDK_ORA_9%", "label":"JDK9"},
{"value":"%env.JDK_ORA_10%", "label":"JDK10"},
{"value":"%env.JDK_OPEN_11%", "label":"JDK11"}
]
}
]
{noformat}
Improve this feature by special parameter names, like _suiteName and regexps in
value
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11298) TcpCommunicationSpi does not support TLSv1.3
[
https://issues.apache.org/jira/browse/IGNITE-11298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851824#comment-16851824
]
Ilya Kasnacheev commented on IGNITE-11298:
--
[~VitaliyB] Thank you for your contribution, I have merged it to master.
> TcpCommunicationSpi does not support TLSv1.3
>
>
> Key: IGNITE-11298
> URL: https://issues.apache.org/jira/browse/IGNITE-11298
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Vitaliy Biryukov
>Priority: Major
> Labels: Java11
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When started on Java 11 we cannot form a secure cluster - Discovery will
> happily use the default TLSv1.3 but Communication will fail with its custom
> SSLEngine-using code.
> Need to fix that.
> Until that, nodes may be salvaged by setProtocol("TLSv1.2") on
> SslContextFactory, or by system property -Djdk.tls.client.protocols="TLSv1.2"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11879) [TC Bot] Don't reject contribution because of ExitCodes/Timeouts if the same failure is present in master
Dmitriy Pavlov created IGNITE-11879: --- Summary: [TC Bot] Don't reject contribution because of ExitCodes/Timeouts if the same failure is present in master Key: IGNITE-11879 URL: https://issues.apache.org/jira/browse/IGNITE-11879 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov - Check failure rate for particular build problem in master, - don't add a suite to possible blockers if failure rate for the same problem (by code) is more than 25% -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11878) Rebuild index skips MOVING partitions when historical re balance
Stepachev Maksim created IGNITE-11878: - Summary: Rebuild index skips MOVING partitions when historical re balance Key: IGNITE-11878 URL: https://issues.apache.org/jira/browse/IGNITE-11878 Project: Ignite Issue Type: Bug Affects Versions: 2.7, 2.6, 2.5 Reporter: Stepachev Maksim Assignee: Stepachev Maksim Rebuild index skips MOVING partitions when historical rebalance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11708) Unable to run tests in IgniteConfigVariationsAbstractTest subclasses
[ https://issues.apache.org/jira/browse/IGNITE-11708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851786#comment-16851786 ] Ivan Pavlukhin commented on IGNITE-11708: - [~ivanan.fed], I added one note on GitHub regarding adding a comment about a test config injection. Everything looks fine to me. > Unable to run tests in IgniteConfigVariationsAbstractTest subclasses > > > Key: IGNITE-11708 > URL: https://issues.apache.org/jira/browse/IGNITE-11708 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > Labels: iep30 > Attachments: read_through_eviction_self_test.patch, > tx_out_test_fixed.patch > > Time Spent: 3.5h > Remaining Estimate: 0h > > It seems that test classes that extend from > IgniteConfigVariationsAbstractTest cannot be started with JUnit4 @Test > annotation. > It is easy to check: if throw exception in any test methods, nothing will > happen. > Reason can be in rule chain in IgniteConfigVariationsAbstractTest class [1], > maybe it destroys existing test workflow. > [1] > https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/testframework/junits/IgniteConfigVariationsAbstractTest.java#L62 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix
[
https://issues.apache.org/jira/browse/IGNITE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851771#comment-16851771
]
Anton Vinogradov edited comment on IGNITE-10663 at 5/30/19 12:00 PM:
-
#PR 5656
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Data Structures{color} [[tests 0 TIMEOUT , Exit Code ,
xmlReportParsingSurefireParsingFailure
|https://ci.ignite.apache.org/viewLog.html?buildId=3988220]]
{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3988223]]
{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=3988227]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3981818buildTypeId=IgniteTests24Java8_RunAll]
was (Author: ignitetcbot):
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Data Structures{color} [[tests 0 TIMEOUT , Exit Code ,
xmlReportParsingSurefireParsingFailure
|https://ci.ignite.apache.org/viewLog.html?buildId=3988220]]
{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3988223]]
{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=3988227]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3981818buildTypeId=IgniteTests24Java8_RunAll]
> Implement cache mode allows reads with consistency check and fix
>
>
> Key: IGNITE-10663
> URL: https://issues.apache.org/jira/browse/IGNITE-10663
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-31
> Fix For: 2.8
>
> Time Spent: 10h 10m
> Remaining Estimate: 0h
>
> The main idea is to provide special "read from cache" mode which will read a
> value from primary and all backups and will check that values are the same.
> In case values differ they should be fixed according to the appropriate
> strategy.
> ToDo list:
> 1) {{cache.withReadRepair().get(key)}} should guarantee values will be
> checked across the topology and fixed if necessary.
> 2) LWW (Last Write Wins) strategy should be used for validation.
> 3) Since LWW and any other strategy do not guarantee that the correct value
> will be chosen.
> We have to record the event contains all values and the chosen one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix
[
https://issues.apache.org/jira/browse/IGNITE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-10663:
--
Comment: was deleted
(was: {panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Data Structures{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=3981399]]
* IgniteCacheDataStructuresSelfTestSuite:
ReplicatedImplicitTransactionalCacheConsistencyTest.test[getEntry=true,
async=true]
* IgniteCacheDataStructuresSelfTestSuite:
ReplicatedImplicitTransactionalCacheConsistencyTest.test[getEntry=true,
async=false]
* IgniteCacheDataStructuresSelfTestSuite:
ReplicatedImplicitTransactionalCacheConsistencyTest.test[getEntry=false,
async=true]
* IgniteCacheDataStructuresSelfTestSuite:
ReplicatedImplicitTransactionalCacheConsistencyTest.test[getEntry=false,
async=false]
{color:#d04437}Scala (Visor Console){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3981740]]
{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3981817]]
{color:#d04437}PDS (Indexing){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3981403]]
* IgnitePdsWithIndexingCoreTestSuite:
IgnitePdsAtomicCacheHistoricalRebalancingTest.testForceRebalanceClientTopology
{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=3981791]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3981818buildTypeId=IgniteTests24Java8_RunAll])
> Implement cache mode allows reads with consistency check and fix
>
>
> Key: IGNITE-10663
> URL: https://issues.apache.org/jira/browse/IGNITE-10663
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-31
> Fix For: 2.8
>
> Time Spent: 10h 10m
> Remaining Estimate: 0h
>
> The main idea is to provide special "read from cache" mode which will read a
> value from primary and all backups and will check that values are the same.
> In case values differ they should be fixed according to the appropriate
> strategy.
> ToDo list:
> 1) {{cache.withReadRepair().get(key)}} should guarantee values will be
> checked across the topology and fixed if necessary.
> 2) LWW (Last Write Wins) strategy should be used for validation.
> 3) Since LWW and any other strategy do not guarantee that the correct value
> will be chosen.
> We have to record the event contains all values and the chosen one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11658) Ignite EntityFramework error when stored procedures
[ https://issues.apache.org/jira/browse/IGNITE-11658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851781#comment-16851781 ] Ilya Kasnacheev commented on IGNITE-11658: -- [~ptupitsyn] can you please take another look? > Ignite EntityFramework error when stored procedures > --- > > Key: IGNITE-11658 > URL: https://issues.apache.org/jira/browse/IGNITE-11658 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Alberto >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Hi, when I trying to save context in Entity Framework with a stores procedure > associated to Entity I get the error NullReferenceException. > In Apache.Ingnite.EntityFramework package InvalidateCache entitySets is NULL > because no entities is affected. In DbCommandInfo _affectedEntitySets is NULL > when stored procedures is used. > Any solution? > Thanks > en > Apache.Ignite.EntityFramework.Impl.DbTransactionInterceptor.InvalidateCache(ICollection`1 > entitySets, DbTransaction transaction) > en Apache.Ignite.EntityFramework.Impl.DbCommandProxy.InvalidateCache() > en Apache.Ignite.EntityFramework.Impl.DbCommandProxy.ExecuteNonQuery() > en > System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.b__0(DbCommand > t, DbCommandInterceptionContext`1 c) > en > System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget > target, Func`3 operation, TInterceptionContext interceptionContext, Action`3 > executing, Action`3 executed) > en > System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.NonQuery(DbCommand > command, DbCommandInterceptionContext interceptionContext) > en System.Data.Entity.Internal.InterceptableDbCommand.ExecuteNonQuery() > en > System.Data.Entity.Core.Mapping.Update.Internal.FunctionUpdateCommand.Execute(Dictionary`2 > identifierValues, List`1 generatedValues) > en System.Data.Entity.Core.Mapping.Update.Internal.UpdateTranslator.Update() > en > System.Data.Entity.Core.EntityClient.Internal.EntityAdapter.b__2(UpdateTranslator > ut) > en System.Data.Entity.Core.EntityClient.Internal.EntityAdapter.Update[T](T > noChangesResult, Func`2 updateFunction) > en System.Data.Entity.Core.EntityClient.Internal.EntityAdapter.Update() > en System.Data.Entity.Core.Objects.ObjectContext.b__35() > en > System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 > func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, > Boolean releaseConnectionOnSuccess) > en > System.Data.Entity.Core.Objects.ObjectContext.SaveChangesToStore(SaveOptions > options, IDbExecutionStrategy executionStrategy, Boolean > startLocalTransaction) > en > System.Data.Entity.Core.Objects.ObjectContext.<>c__DisplayClass2a.b__27() > en > System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 > operation) > en > System.Data.Entity.Core.Objects.ObjectContext.SaveChangesInternal(SaveOptions > options, Boolean executeInExistingTransaction) > en System.Data.Entity.Core.Objects.ObjectContext.SaveChanges(SaveOptions > options) > en System.Data.Entity.Internal.InternalContext.SaveChanges() > en System.Data.Entity.Internal.LazyInternalContext.SaveChanges() > en System.Data.Entity.DbContext.SaveChanges() > en CommonLibrary.Repositorios.GenericUnitOfWork`1.Save() en > D:\Documentos\Desarrollo\WEB\RISHT\CommonLibrary\Repositorios\GenericUnitOfWork.cs:línea > 85 > en RISHT.Services.EstudioCRUDManager.CreateOrEditEstudio(Estudio estudio) en > D:\Documentos\Desarrollo\WEB\RISHT\RISHT.Services\EstudioCRUDManager.cs:línea > 274 > en RISHT.Services.EstudioCRUDManager.Save(Estudio estudio) en > D:\Documentos\Desarrollo\WEB\RISHT\RISHT.Services\EstudioCRUDManager.cs:línea > 568 > en RISHT.Services.EstudioCRUDManager.SaveEstudio(Estudio estudio) en > D:\Documentos\Desarrollo\WEB\RISHT\RISHT.Services\EstudioCRUDManager.cs:línea > 382 > en RISHT.Controllers.EstudioController.AltaFromWizard(EstudioWizardViewModel > estudioWizardViewModel) en > D:\Documentos\Desarrollo\WEB\RISHT\RISHT\Controllers\EstudioController.cs:línea > 105 > en lambda_method(Closure , ControllerBase , Object[] ) > en System.Web.Mvc.ActionMethodDispatcher.Execute(ControllerBase controller, > Object[] parameters) > en System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext > controllerContext, IDictionary`2 parameters) > en > System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext > controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 > parameters) > en > System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c.b__9_0(IAsyncResult > asyncResult, ActionInvocation innerInvokeState) > en >
[jira] [Commented] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix
[
https://issues.apache.org/jira/browse/IGNITE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851771#comment-16851771
]
Ignite TC Bot commented on IGNITE-10663:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Data Structures{color} [[tests 0 TIMEOUT , Exit Code ,
xmlReportParsingSurefireParsingFailure
|https://ci.ignite.apache.org/viewLog.html?buildId=3988220]]
{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3988223]]
{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=3988227]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3981818buildTypeId=IgniteTests24Java8_RunAll]
> Implement cache mode allows reads with consistency check and fix
>
>
> Key: IGNITE-10663
> URL: https://issues.apache.org/jira/browse/IGNITE-10663
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-31
> Fix For: 2.8
>
> Time Spent: 10h 10m
> Remaining Estimate: 0h
>
> The main idea is to provide special "read from cache" mode which will read a
> value from primary and all backups and will check that values are the same.
> In case values differ they should be fixed according to the appropriate
> strategy.
> ToDo list:
> 1) {{cache.withReadRepair().get(key)}} should guarantee values will be
> checked across the topology and fixed if necessary.
> 2) LWW (Last Write Wins) strategy should be used for validation.
> 3) Since LWW and any other strategy do not guarantee that the correct value
> will be chosen.
> We have to record the event contains all values and the chosen one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11867) Fix flaky test GridCacheRebalancingWithAsyncClearingTest#testCorrectRebalancingCurrentlyRentingPartitions
[
https://issues.apache.org/jira/browse/IGNITE-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851750#comment-16851750
]
Alexei Scherbakov commented on IGNITE-11867:
[~ivan.glukos]
Failing suite is not related to changes.
Please review.
> Fix flaky test
> GridCacheRebalancingWithAsyncClearingTest#testCorrectRebalancingCurrentlyRentingPartitions
> -
>
> Key: IGNITE-11867
> URL: https://issues.apache.org/jira/browse/IGNITE-11867
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> java.lang.AssertionError: Value for 4 is null
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertNotNull(Assert.java:621)
> at
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRebalancingWithAsyncClearingTest.testCorrectRebalancingCurrentlyRentingPartitions(GridCacheRebalancingWithAsyncClearingTest.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2148)
> at java.lang.Thread.run(Thread.java:748){noformat}
> EDIT: The issue is related to recently contributed IGNITE-10078. In specific
> scenario due to race partition clearing could be started while partition is
> passing through ongoing rebalancing started on previous topology version.
> I fixed it by preventing partition clearing on newer topology version. In
> such case if rebalance will be finished and partition will go in OWNING state
> further clearing is not needed any more, otherwise partition should be
> scheduled for clearing again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11867) Fix flaky test GridCacheRebalancingWithAsyncClearingTest#testCorrectRebalancingCurrentlyRentingPartitions
[
https://issues.apache.org/jira/browse/IGNITE-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851748#comment-16851748
]
Ignite TC Bot commented on IGNITE-11867:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=3982429]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3982456buildTypeId=IgniteTests24Java8_RunAll]
> Fix flaky test
> GridCacheRebalancingWithAsyncClearingTest#testCorrectRebalancingCurrentlyRentingPartitions
> -
>
> Key: IGNITE-11867
> URL: https://issues.apache.org/jira/browse/IGNITE-11867
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> java.lang.AssertionError: Value for 4 is null
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertNotNull(Assert.java:621)
> at
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRebalancingWithAsyncClearingTest.testCorrectRebalancingCurrentlyRentingPartitions(GridCacheRebalancingWithAsyncClearingTest.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2148)
> at java.lang.Thread.run(Thread.java:748){noformat}
> EDIT: The issue is related to recently contributed IGNITE-10078. In specific
> scenario due to race partition clearing could be started while partition is
> passing through ongoing rebalancing started on previous topology version.
> I fixed it by preventing partition clearing on newer topology version. In
> such case if rebalance will be finished and partition will go in OWNING state
> further clearing is not needed any more, otherwise partition should be
> scheduled for clearing again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9876) .NET: Thin Client: Implement Best Effort Affinity
[ https://issues.apache.org/jira/browse/IGNITE-9876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851746#comment-16851746 ] Pavel Tupitsyn commented on IGNITE-9876: [~isapego] PR ready, please have a look. > .NET: Thin Client: Implement Best Effort Affinity > - > > Key: IGNITE-9876 > URL: https://issues.apache.org/jira/browse/IGNITE-9876 > Project: Ignite > Issue Type: New Feature > Components: platforms, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, iep-23 > Time Spent: 10m > Remaining Estimate: 0h > > See linked IEP-23. > First iteration is going to be an "experimental feature" with the following > limitations: > * No reconnect support for failed nodes > * No AffinityKeyMapped support -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9217) Uncomment 24 test classes in IgniteCacheTestSuite2 (Cache 2)
[
https://issues.apache.org/jira/browse/IGNITE-9217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-9217:
Reviewer: Dmitriy Pavlov
> Uncomment 24 test classes in IgniteCacheTestSuite2 (Cache 2)
>
>
> Key: IGNITE-9217
> URL: https://issues.apache.org/jira/browse/IGNITE-9217
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
>
> //suite.addTestSuite(GridCacheLocalBasicStoreMultithreadedSelfTest.class);
> //suite.addTestSuite(GridCacheLocalTxReadTest.class);
> //suite.addTest(new
> TestSuite(RendezvousAffinityFunctionSelfTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedEntryLockSelfTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedEvictionSelfTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedNestedTxTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedStorePutSelfTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedTxConcurrentGetTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedTxMultiNodeSelfTest.class));
> //suite.addTest(new TestSuite(GridCachePartitionedTxReadTest.class));
> //suite.addTest(new
> TestSuite(NearCacheMultithreadedUpdateTest.class));
> //suite.addTest(new TestSuite(NearCachePutAllMultinodeTest.class));
> //suite.addTest(new
> TestSuite(IgniteCacheContainsKeyNearSelfTest.class));
> //suite.addTest(new TestSuite(IgniteCacheNearTxRollbackTest.class));
> //suite.addTest(new TestSuite(GridCacheColocatedDebugTest.class));
> //suite.addTest(new
> TestSuite(GridCacheDhtAtomicEvictionNearReadersSelfTest.class));
> //suite.addTest(new TestSuite(GridCacheDhtEntrySetSelfTest.class));
> //suite.addTest(new
> TestSuite(GridCacheDhtEvictionNearReadersSelfTest.class));
> //suite.addTest(new TestSuite(GridCacheDhtMultiBackupTest.class));
> //suite.addTest(new
> TestSuite(GridCacheDhtPreloadMessageCountTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedNearDisabledMetricsSelfTest.class));
> //suite.addTest(new
> TestSuite(IgniteCacheContainsKeyColocatedSelfTest.class));
> //suite.addTest(new
> TestSuite(IgniteCrossCacheTxNearEnabledSelfTest.class));
> //suite.addTest(new
> TestSuite(IgniteTxConsistencyColocatedRestartSelfTest.class));
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9217) Uncomment 24 test classes in IgniteCacheTestSuite2 (Cache 2)
[
https://issues.apache.org/jira/browse/IGNITE-9217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-9217:
Ignite Flags: (was: Docs Required)
> Uncomment 24 test classes in IgniteCacheTestSuite2 (Cache 2)
>
>
> Key: IGNITE-9217
> URL: https://issues.apache.org/jira/browse/IGNITE-9217
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
>
> //suite.addTestSuite(GridCacheLocalBasicStoreMultithreadedSelfTest.class);
> //suite.addTestSuite(GridCacheLocalTxReadTest.class);
> //suite.addTest(new
> TestSuite(RendezvousAffinityFunctionSelfTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedEntryLockSelfTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedEvictionSelfTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedNestedTxTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedStorePutSelfTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedTxConcurrentGetTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedTxMultiNodeSelfTest.class));
> //suite.addTest(new TestSuite(GridCachePartitionedTxReadTest.class));
> //suite.addTest(new
> TestSuite(NearCacheMultithreadedUpdateTest.class));
> //suite.addTest(new TestSuite(NearCachePutAllMultinodeTest.class));
> //suite.addTest(new
> TestSuite(IgniteCacheContainsKeyNearSelfTest.class));
> //suite.addTest(new TestSuite(IgniteCacheNearTxRollbackTest.class));
> //suite.addTest(new TestSuite(GridCacheColocatedDebugTest.class));
> //suite.addTest(new
> TestSuite(GridCacheDhtAtomicEvictionNearReadersSelfTest.class));
> //suite.addTest(new TestSuite(GridCacheDhtEntrySetSelfTest.class));
> //suite.addTest(new
> TestSuite(GridCacheDhtEvictionNearReadersSelfTest.class));
> //suite.addTest(new TestSuite(GridCacheDhtMultiBackupTest.class));
> //suite.addTest(new
> TestSuite(GridCacheDhtPreloadMessageCountTest.class));
> //suite.addTest(new
> TestSuite(GridCachePartitionedNearDisabledMetricsSelfTest.class));
> //suite.addTest(new
> TestSuite(IgniteCacheContainsKeyColocatedSelfTest.class));
> //suite.addTest(new
> TestSuite(IgniteCrossCacheTxNearEnabledSelfTest.class));
> //suite.addTest(new
> TestSuite(IgniteTxConsistencyColocatedRestartSelfTest.class));
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11256) Implement read-only mode for grid
[ https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851721#comment-16851721 ] Vyacheslav Koptilin commented on IGNITE-11256: -- Hello [~antonovsergey93], Looks good to me! Thanks! > Implement read-only mode for grid > - > > Key: IGNITE-11256 > URL: https://issues.apache.org/jira/browse/IGNITE-11256 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Should be triggered from control.sh utility. > Useful for maintenance work, for example checking partition consistency > (idle_verify) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11256) Implement read-only mode for grid
[ https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851697#comment-16851697 ] Sergey Antonov commented on IGNITE-11256: - [~slava.koptilin] I fixed your comments. Please check my code again! > Implement read-only mode for grid > - > > Key: IGNITE-11256 > URL: https://issues.apache.org/jira/browse/IGNITE-11256 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Should be triggered from control.sh utility. > Useful for maintenance work, for example checking partition consistency > (idle_verify) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix
[
https://issues.apache.org/jira/browse/IGNITE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-10663:
--
Description:
The main idea is to provide special "read from cache" mode which will read a
value from primary and all backups and will check that values are the same.
In case values differ they should be fixed according to the appropriate
strategy.
ToDo list:
1) {{cache.withReadRepair().get(key)}} should guarantee values will be checked
across the topology and fixed if necessary.
2) LWW (Last Write Wins) strategy should be used for validation.
3) Since LWW and any other strategy do not guarantee that the correct value
will be chosen.
We have to record the event contains all values and the chosen one.
was:
The main idea is to provide special "read from cache" mode which will read a
value from primary and all backups and will check that values are the same.
In case values differ they should be fixed according to the appropriate
strategy.
ToDo list:
1) {{cache.withConsistency().get(key)}} should guarantee values will be checked
across the topology and fixed if necessary.
2) LWW (Last Write Wins) strategy should be used for validation.
3) Since LWW and any other strategy do not guarantee that the correct value
will be chosen.
We have to record the event contains all values and the chosen one.
> Implement cache mode allows reads with consistency check and fix
>
>
> Key: IGNITE-10663
> URL: https://issues.apache.org/jira/browse/IGNITE-10663
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-31
> Fix For: 2.8
>
> Time Spent: 10h 10m
> Remaining Estimate: 0h
>
> The main idea is to provide special "read from cache" mode which will read a
> value from primary and all backups and will check that values are the same.
> In case values differ they should be fixed according to the appropriate
> strategy.
> ToDo list:
> 1) {{cache.withReadRepair().get(key)}} should guarantee values will be
> checked across the topology and fixed if necessary.
> 2) LWW (Last Write Wins) strategy should be used for validation.
> 3) Since LWW and any other strategy do not guarantee that the correct value
> will be chosen.
> We have to record the event contains all values and the chosen one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11875) Thin client is unable to authenticate with long password
[
https://issues.apache.org/jira/browse/IGNITE-11875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851577#comment-16851577
]
Pavel Tupitsyn edited comment on IGNITE-11875 at 5/30/19 6:57 AM:
--
[~isapego] .NET part looks good to me in general.
One thing: {{TestAuthenticationLongToken}} largely duplicates
{{TestAuthentication}} method, can you please extract common parts to reduce
duplication? I think only username and password are different.
was (Author: ptupitsyn):
[~isapego] .NET part looks good to me in general.
One thing: {{TestAuthenticationLongToken}} largely duplicates
{{TestAuthentication}} method, can you please extract common parts to reduce
duplication?
> Thin client is unable to authenticate with long password
>
>
> Key: IGNITE-11875
> URL: https://issues.apache.org/jira/browse/IGNITE-11875
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, odbc, thin client
>Affects Versions: 2.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Token authentication could use long usernames/passwords, that leads to
> "Invalid handshake message"
> ClientListenerNioServerBuffer:
> {code:java}
> if (cnt == msgSize) {
> byte[] data0 = data;
> reset();
> return data0;
> }
> else {
> if (checkHandshake && cnt > 0 && (msgSize >
> ClientListenerNioListener.MAX_HANDSHAKE_MSG_SIZE
> || data[0] != ClientListenerRequest.HANDSHAKE))
> throw new IgniteCheckedException("Invalid handshake message");
> return null;
> }
> {code}
> The reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11875) Thin client is unable to authenticate with long password
[
https://issues.apache.org/jira/browse/IGNITE-11875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851577#comment-16851577
]
Pavel Tupitsyn commented on IGNITE-11875:
-
[~isapego] .NET part looks good to me in general.
One thing: {{TestAuthenticationLongToken}} largely duplicates
{{TestAuthentication}} method, can you please extract common parts to reduce
duplication?
> Thin client is unable to authenticate with long password
>
>
> Key: IGNITE-11875
> URL: https://issues.apache.org/jira/browse/IGNITE-11875
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, odbc, thin client
>Affects Versions: 2.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Token authentication could use long usernames/passwords, that leads to
> "Invalid handshake message"
> ClientListenerNioServerBuffer:
> {code:java}
> if (cnt == msgSize) {
> byte[] data0 = data;
> reset();
> return data0;
> }
> else {
> if (checkHandshake && cnt > 0 && (msgSize >
> ClientListenerNioListener.MAX_HANDSHAKE_MSG_SIZE
> || data[0] != ClientListenerRequest.HANDSHAKE))
> throw new IgniteCheckedException("Invalid handshake message");
> return null;
> }
> {code}
> The reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
