[jira] [Updated] (IGNITE-21899) Fix for TC Bot with Ignite version 2.16
[ https://issues.apache.org/jira/browse/IGNITE-21899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Valuyskiy updated IGNITE-21899: Description: It's impossible to build the project with Apache Ignite 2.16, as GridIntList#clear(), which was removed in the 2.16 version (https://issues.apache.org/jira/browse/IGNITE-20143), is used in TC Bot. All in all, GridIntList is a private API and should not be used in TC Bot. (was: It's impossible to build the project with Apache Ignite 2.16, as GridIntList#clear(), which was removed in the 2.16 version (), is used in TC Bot. ) > Fix for TC Bot with Ignite version 2.16 > --- > > Key: IGNITE-21899 > URL: https://issues.apache.org/jira/browse/IGNITE-21899 > Project: Ignite > Issue Type: Task >Reporter: Oleg Valuyskiy >Assignee: Oleg Valuyskiy >Priority: Major > Labels: ise > > It's impossible to build the project with Apache Ignite 2.16, as > GridIntList#clear(), which was removed in the 2.16 version > (https://issues.apache.org/jira/browse/IGNITE-20143), is used in TC Bot. All > in all, GridIntList is a private API and should not be used in TC Bot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21899) Fix for TC Bot with Ignite version 2.16
[ https://issues.apache.org/jira/browse/IGNITE-21899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Valuyskiy updated IGNITE-21899: Description: It's impossible to build the project with Apache Ignite 2.16, as GridIntList#clear(), which was removed in the 2.16 version (), is used in TC Bot. > Fix for TC Bot with Ignite version 2.16 > --- > > Key: IGNITE-21899 > URL: https://issues.apache.org/jira/browse/IGNITE-21899 > Project: Ignite > Issue Type: Task >Reporter: Oleg Valuyskiy >Assignee: Oleg Valuyskiy >Priority: Major > Labels: ise > > It's impossible to build the project with Apache Ignite 2.16, as > GridIntList#clear(), which was removed in the 2.16 version (), is used in TC > Bot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22216) Remove the GridCacheQueryInfo#all and GridCacheQueryRequest#all properties
[ https://issues.apache.org/jira/browse/IGNITE-22216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Valuyskiy updated IGNITE-22216: Description: The GridCacheQueryInfo#all and GridCacheQueryRequest#all properties don't serve any real purpose but make some of the code where they are used rather confusing. Therefore it is advised to remove the 'all' property from both GridCacheQueryInfo and GridCacheQueryRequest classes. (was: The GridCacheQueryInfo#all property doesn't serve any real purpose but makes some of the code where it is used rather confusing. Therefore it is advised to remove the 'all' property from the GridCacheQueryInfo class.) > Remove the GridCacheQueryInfo#all and GridCacheQueryRequest#all properties > -- > > Key: IGNITE-22216 > URL: https://issues.apache.org/jira/browse/IGNITE-22216 > Project: Ignite > Issue Type: Task >Reporter: Oleg Valuyskiy >Assignee: Oleg Valuyskiy >Priority: Minor > Labels: ise > > The GridCacheQueryInfo#all and GridCacheQueryRequest#all properties don't > serve any real purpose but make some of the code where they are used rather > confusing. Therefore it is advised to remove the 'all' property from both > GridCacheQueryInfo and GridCacheQueryRequest classes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22216) Remove the GridCacheQueryInfo#all and GridCacheQueryRequest#all properties
[ https://issues.apache.org/jira/browse/IGNITE-22216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Valuyskiy updated IGNITE-22216: Summary: Remove the GridCacheQueryInfo#all and GridCacheQueryRequest#all properties (was: Remove the GridCacheQueryInfo#all property) > Remove the GridCacheQueryInfo#all and GridCacheQueryRequest#all properties > -- > > Key: IGNITE-22216 > URL: https://issues.apache.org/jira/browse/IGNITE-22216 > Project: Ignite > Issue Type: Task >Reporter: Oleg Valuyskiy >Assignee: Oleg Valuyskiy >Priority: Minor > Labels: ise > > The GridCacheQueryInfo#all property doesn't serve any real purpose but makes > some of the code where it is used rather confusing. Therefore it is advised > to remove the 'all' property from the GridCacheQueryInfo class. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22140) Possible pagination bug in GridCacheQueryManager#runQuery()
[ https://issues.apache.org/jira/browse/IGNITE-22140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Valuyskiy updated IGNITE-22140: Description: It looks like there is a pagination bug in the GridCacheQueryManager#runQuery() method caused by fact that the ‘cnt’ counter doesn’t get reset after sending the first page with query results. It is advised to find out whether the bug really exists and fix it if that’s the case. was: It looks like there is a pagination bug in the GridCacheQueryManager#runQuery() method caused by fact that the ‘cnt’ counter doesn’t get reset after sending the first page with query results. It is advised to find out whether the bug really exists and fix it of that’s the case. > Possible pagination bug in GridCacheQueryManager#runQuery() > --- > > Key: IGNITE-22140 > URL: https://issues.apache.org/jira/browse/IGNITE-22140 > Project: Ignite > Issue Type: Task >Reporter: Oleg Valuyskiy >Assignee: Oleg Valuyskiy >Priority: Major > Labels: ise > > It looks like there is a pagination bug in the > GridCacheQueryManager#runQuery() method caused by fact that the ‘cnt’ counter > doesn’t get reset after sending the first page with query results. > It is advised to find out whether the bug really exists and fix it if that’s > the case. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22215) Fix for ThinClientIndexQueryTest#testPageSize
[ https://issues.apache.org/jira/browse/IGNITE-22215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Valuyskiy updated IGNITE-22215: Description: There is a bug in ThinClientIndexQueryTest#testPageSize where the 'reqs' collection is always empty as a wrong class is used for recording next page requests (GridQueryNextPageRequest instead of GridCacheQueryRequest). (was: There is a bug in ThinClientIndexQueryTest#testPageSize where the 'reqs' collection is always as a wrong class is used for recording next page requests (GridQueryNextPageRequest instead of GridCacheQueryRequest).) > Fix for ThinClientIndexQueryTest#testPageSize > - > > Key: IGNITE-22215 > URL: https://issues.apache.org/jira/browse/IGNITE-22215 > Project: Ignite > Issue Type: Task >Reporter: Oleg Valuyskiy >Assignee: Oleg Valuyskiy >Priority: Minor > Labels: ise > > There is a bug in ThinClientIndexQueryTest#testPageSize where the 'reqs' > collection is always empty as a wrong class is used for recording next page > requests (GridQueryNextPageRequest instead of GridCacheQueryRequest). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22216) Remove the GridCacheQueryInfo#all property
Oleg Valuyskiy created IGNITE-22216: --- Summary: Remove the GridCacheQueryInfo#all property Key: IGNITE-22216 URL: https://issues.apache.org/jira/browse/IGNITE-22216 Project: Ignite Issue Type: Task Reporter: Oleg Valuyskiy Assignee: Oleg Valuyskiy The GridCacheQueryInfo#all property doesn't serve any real purpose but makes some of the code where it is used rather confusing. Therefore it is advised to remove the 'all' property from the GridCacheQueryInfo class. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22215) Fox for ThinClientIndexQueryTest#testPageSize
Oleg Valuyskiy created IGNITE-22215: --- Summary: Fox for ThinClientIndexQueryTest#testPageSize Key: IGNITE-22215 URL: https://issues.apache.org/jira/browse/IGNITE-22215 Project: Ignite Issue Type: Task Reporter: Oleg Valuyskiy Assignee: Oleg Valuyskiy There is a bug in ThinClientIndexQueryTest#testPageSize where the 'reqs' collection is always as a wrong class is used for recording next page requests (GridQueryNextPageRequest instead of GridCacheQueryRequest). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22183) Adding events recording for Index Queries
Oleg Valuyskiy created IGNITE-22183: --- Summary: Adding events recording for Index Queries Key: IGNITE-22183 URL: https://issues.apache.org/jira/browse/IGNITE-22183 Project: Ignite Issue Type: Task Reporter: Oleg Valuyskiy Assignee: Oleg Valuyskiy Recording of Cache Query Read Object events and Cache Query Execution events need to be added for Index Queries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22140) Possible pagination bug in GridCacheQueryManager#runQuery()
Oleg Valuyskiy created IGNITE-22140: --- Summary: Possible pagination bug in GridCacheQueryManager#runQuery() Key: IGNITE-22140 URL: https://issues.apache.org/jira/browse/IGNITE-22140 Project: Ignite Issue Type: Task Reporter: Oleg Valuyskiy Assignee: Oleg Valuyskiy It looks like there is a pagination bug in the GridCacheQueryManager#runQuery() method caused by fact that the ‘cnt’ counter doesn’t get reset after sending the first page with query results. It is advised to find out whether the bug really exists and fix it of that’s the case. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21826) MvccCoordinator removal
[ https://issues.apache.org/jira/browse/IGNITE-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Valuyskiy reassigned IGNITE-21826: --- Assignee: Julia Bakulina (was: Oleg Valuyskiy) > MvccCoordinator removal > --- > > Key: IGNITE-21826 > URL: https://issues.apache.org/jira/browse/IGNITE-21826 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Julia Bakulina >Priority: Minor > Labels: ise > > MvccCoordinator class and corresponding code have to be removed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21826) MvccCoordinator removal
[ https://issues.apache.org/jira/browse/IGNITE-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836873#comment-17836873 ] Oleg Valuyskiy commented on IGNITE-21826: - [~julia_bakulina] Yes, you may proceed with this ticket. > MvccCoordinator removal > --- > > Key: IGNITE-21826 > URL: https://issues.apache.org/jira/browse/IGNITE-21826 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Oleg Valuyskiy >Priority: Minor > Labels: ise > > MvccCoordinator class and corresponding code have to be removed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21901) Temporarily change Ignite version back to 2.14 in TC Bot
Oleg Valuyskiy created IGNITE-21901: --- Summary: Temporarily change Ignite version back to 2.14 in TC Bot Key: IGNITE-21901 URL: https://issues.apache.org/jira/browse/IGNITE-21901 Project: Ignite Issue Type: Task Reporter: Oleg Valuyskiy Assignee: Oleg Valuyskiy It is advised to change Ignite version in TC Bot back to 2.14 as 2.16 requires a number of other changes in the project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21899) Fix for TC Bot with Ignite version 2.16
Oleg Valuyskiy created IGNITE-21899: --- Summary: Fix for TC Bot with Ignite version 2.16 Key: IGNITE-21899 URL: https://issues.apache.org/jira/browse/IGNITE-21899 Project: Ignite Issue Type: Task Reporter: Oleg Valuyskiy Assignee: Oleg Valuyskiy -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21445) IndexQuery ignores pageSize if setLocal=true is set
[ https://issues.apache.org/jira/browse/IGNITE-21445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Valuyskiy reassigned IGNITE-21445: --- Assignee: Oleg Valuyskiy > IndexQuery ignores pageSize if setLocal=true is set > --- > > Key: IGNITE-21445 > URL: https://issues.apache.org/jira/browse/IGNITE-21445 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.14 >Reporter: Maksim Timonin >Assignee: Oleg Valuyskiy >Priority: Major > Labels: ise > > In 2.14, see GridCacheQueryManager#runQuery:L1323 > If query is local it just collects all possible data. > For ScanQuery this code doesn't work, as it directly uses local > scanQueryIterator that returns entry one by one. > Solution: > # Prepare page for iterating > # Use the same logic as ScanQuery for local queries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21826) MvccCoordinator removal
[ https://issues.apache.org/jira/browse/IGNITE-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Valuyskiy reassigned IGNITE-21826: --- Assignee: Oleg Valuyskiy > MvccCoordinator removal > --- > > Key: IGNITE-21826 > URL: https://issues.apache.org/jira/browse/IGNITE-21826 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Oleg Valuyskiy >Priority: Minor > Labels: ise > > MvccCoordinator class and corresponding code have to be removed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21770) Improve logging for the ‘Probably disk is too busy, please check your device’ event (when reading from disk)
Oleg Valuyskiy created IGNITE-21770:
---
Summary: Improve logging for the ‘Probably disk is too busy,
please check your device’ event (when reading from disk)
Key: IGNITE-21770
URL: https://issues.apache.org/jira/browse/IGNITE-21770
Project: Ignite
Issue Type: Improvement
Reporter: Oleg Valuyskiy
Assignee: Oleg Valuyskiy
Make logging messages more specific and include more information that could be
necessary for analysis.
Stack trace example:
{code:java}
2024-03-15 04:23:25.395 [ERROR][ForkJoinPool.commonPool-worker-41][] Critical
system error detected. Will be handled accordingly to configured handler
[hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
o.a.i.i.processors.cache.persistence.StorageException: Failed to read page
[file=/opt/ignite/ssd/data/cell_6_node_4/cacheGroup-part/part-15909.bin,
pageId=349803611487542]]]
org.apache.ignite.internal.processors.cache.persistence.StorageException:
Failed to read page
[file=/opt/ignite/ssd/data/cell_6_node_4/cacheGroup-part/part-15909.bin,
pageId=349803611487542]
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore.read(FilePageStore.java:547)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore.read(FilePageStore.java:487)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageReadWriteManagerImpl.read(PageReadWriteManagerImpl.java:69)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:522)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:930)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:741)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:730)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.doInitFromLink(CacheDataRowAdapter.java:304)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:165)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:136)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.tree.DataRow.(DataRow.java:55)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.tree.CacheDataRowStore.dataRow(CacheDataRowStore.java:129)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.tree.CacheDataTree.getRow(CacheDataTree.java:424)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.tree.CacheDataTree.getRow(CacheDataTree.java:63)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.fillFromBuffer0(BPlusTree.java:6168)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.fillFromBuffer(BPlusTree.java:5917)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.nextPage(BPlusTree.java:5971)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.next(BPlusTree.java:6221)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$3.onHasNext(IgniteCacheOffheapManagerImpl.java:913)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:56)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.verify.IdleVerifyUtility.calculatePartitionHash(IdleVerifyUtility.java:269)
~[ignite-core-14.1.2.jar:14.1.2]
at
org.apache.ignite.internal.processors.cache.verify.VerifyBackupPartitionsTaskV2$VerifyBackupPartitionsJobV2.lambda$calculatePartitionHashAsync$3(VerifyBackupPartitionsTaskV2.java:478)
~[ignite-core-14.1.2.jar:14.1.2]
at
java.util.concurrent.ForkJoinTask$AdaptedCallable.exec(ForkJoinTask.java:1448)
~[?:?]
at
[jira] [Updated] (IGNITE-21542) Documentation for Ignite security model
[ https://issues.apache.org/jira/browse/IGNITE-21542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Valuyskiy updated IGNITE-21542: Component/s: documentation > Documentation for Ignite security model > --- > > Key: IGNITE-21542 > URL: https://issues.apache.org/jira/browse/IGNITE-21542 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Oleg Valuyskiy >Assignee: Oleg Valuyskiy >Priority: Minor > Labels: ise > Fix For: 2.17 > > Time Spent: 10m > Remaining Estimate: 0h > > It might be helpful to introduce documentation regarding what could be > expected from Ignite installations in terms of security. More specifically, > what Ignite users can expect when it comes to Discovery and Communication > ports inside and outside of the Ignite DMZ. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21542) Documentation for Ignite security model
[ https://issues.apache.org/jira/browse/IGNITE-21542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Valuyskiy updated IGNITE-21542: Summary: Documentation for Ignite security model (was: Documentation on the Ignite DMZ security model) > Documentation for Ignite security model > --- > > Key: IGNITE-21542 > URL: https://issues.apache.org/jira/browse/IGNITE-21542 > Project: Ignite > Issue Type: Task >Reporter: Oleg Valuyskiy >Assignee: Oleg Valuyskiy >Priority: Minor > Labels: ise > Fix For: 2.17 > > > It might be helpful to introduce documentation regarding what could be > expected from Ignite installations in terms of security. More specifically, > what Ignite users can expect when it comes to Discovery and Communication > ports inside and outside of the Ignite DMZ. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21542) Documentation on the Ignite DMZ security model
Oleg Valuyskiy created IGNITE-21542: --- Summary: Documentation on the Ignite DMZ security model Key: IGNITE-21542 URL: https://issues.apache.org/jira/browse/IGNITE-21542 Project: Ignite Issue Type: Task Reporter: Oleg Valuyskiy Assignee: Oleg Valuyskiy It might be helpful to introduce documentation regarding what could be expected from Ignite installations in terms of security. More specifically, what Ignite users can expect when it comes to Discovery and Communication ports inside and outside of the Ignite DMZ. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20913) Previous value, version, their combination or parts should be written as a part of the DataEntry to allow CacheVersionConflictResolver use them on resolve
[ https://issues.apache.org/jira/browse/IGNITE-20913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Valuyskiy updated IGNITE-20913: Labels: ise (was: ) > Previous value, version, their combination or parts should be written as a > part of the DataEntry to allow CacheVersionConflictResolver use them on > resolve > -- > > Key: IGNITE-20913 > URL: https://issues.apache.org/jira/browse/IGNITE-20913 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Labels: ise > Fix For: 2.17 > > Time Spent: 10m > Remaining Estimate: 0h > > Just allowing CacheVersionConflictResolver to resolve -more- complex cases. > Main goal is to allow any changes from other cluster when both clusters are > synchronized (have the same value/version). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (IGNITE-21520) Update Ignite version in TeamCity bot
[ https://issues.apache.org/jira/browse/IGNITE-21520 ] Oleg Valuyskiy deleted comment on IGNITE-21520: - was (Author: JIRAUSER303481): PR: https://github.com/apache/ignite-teamcity-bot/pull/195 > Update Ignite version in TeamCity bot > - > > Key: IGNITE-21520 > URL: https://issues.apache.org/jira/browse/IGNITE-21520 > Project: Ignite > Issue Type: Task >Reporter: Oleg Valuyskiy >Assignee: Oleg Valuyskiy >Priority: Minor > Labels: ise > > With the availability of the 2.16 Ignite version, it is advisable to update > the version of Ignite from 2.14 to 2.16 in TeamCity bot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21520) Update Ignite version in TeamCity bot
[ https://issues.apache.org/jira/browse/IGNITE-21520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816829#comment-17816829 ] Oleg Valuyskiy commented on IGNITE-21520: - PR: https://github.com/apache/ignite-teamcity-bot/pull/195 > Update Ignite version in TeamCity bot > - > > Key: IGNITE-21520 > URL: https://issues.apache.org/jira/browse/IGNITE-21520 > Project: Ignite > Issue Type: Task >Reporter: Oleg Valuyskiy >Assignee: Oleg Valuyskiy >Priority: Minor > Labels: ise > > With the availability of the 2.16 Ignite version, it is advisable to update > the version of Ignite from 2.14 to 2.16 in TeamCity bot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21520) Update Ignite version in TeamCity bot
Oleg Valuyskiy created IGNITE-21520: --- Summary: Update Ignite version in TeamCity bot Key: IGNITE-21520 URL: https://issues.apache.org/jira/browse/IGNITE-21520 Project: Ignite Issue Type: Task Reporter: Oleg Valuyskiy Assignee: Oleg Valuyskiy With the availability of the 2.16 Ignite version, it is advisable to update the version of Ignite from 2.14 to 2.16 in TeamCity bot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21475) Replacing currentTimeMillis() with nanoTime() in LongJVMPauseDetector
Oleg Valuyskiy created IGNITE-21475: --- Summary: Replacing currentTimeMillis() with nanoTime() in LongJVMPauseDetector Key: IGNITE-21475 URL: https://issues.apache.org/jira/browse/IGNITE-21475 Project: Ignite Issue Type: Improvement Reporter: Oleg Valuyskiy Assignee: Oleg Valuyskiy To improve the mechanism of JVM pause detection, it’s recommended to replace System.System.currentTimeMillis() with System.nanoTime() in the ‘LongJVMPauseDetector’ class, since currentTimeMillis() is not monotonic. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-21102) Incorrect cluster state output for ACTIVE_READ_ONLY in --baseline
[
https://issues.apache.org/jira/browse/IGNITE-21102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17800481#comment-17800481
]
Oleg Valuyskiy edited comment on IGNITE-21102 at 12/26/23 1:01 PM:
---
[~yuri.naryshkin], please review my changes.
The ‘ClusterState’ property has been added to the ‘BaseLineTaskResult’ class;
this property is now used to indicate the state of a cluster in the
‘AbstractBaselineCommand#printResult’ method – instead of the ‘active/inactive’
flag.
was (Author: JIRAUSER303481):
[~nizhikov], please review my changes.
The ‘ClusterState’ property has been added to the ‘BaseLineTaskResult’ class;
this property is now used to indicate the state of a cluster in the
‘AbstractBaselineCommand#printResult’ method – instead of the ‘active/inactive’
flag.
> Incorrect cluster state output for ACTIVE_READ_ONLY in --baseline
> -
>
> Key: IGNITE-21102
> URL: https://issues.apache.org/jira/browse/IGNITE-21102
> Project: Ignite
> Issue Type: Bug
>Reporter: Julia Bakulina
>Assignee: Oleg Valuyskiy
>Priority: Major
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Incorrect cluster state output for ACTIVE_READ_ONLY in --baseline.
> org.apache.ignite.internal.commandline.BaselineCommand#baselinePrint0
> {code:java}
> logger.info("Cluster state: " + (res.isActive() ? "active" :
> "inactive"));
> {code}
> org.apache.ignite.cluster.ClusterState#ACTIVE_READ_ONLY
>
> An example of changing the cluster state:
> {code:java}
> Command [SET-STATE] started
> Arguments: ... --set-state ACTIVE_READ_ONLY
>
> Cluster state changed to ACTIVE_READ_ONLY
> Command [SET-STATE] finished with code: 0 {code}
> Cluster state in control.sh --baseline
> {code:java}
> Command [BASELINE] started
> Arguments: ... --baseline
>
> Cluster state: active
> Current topology version: 1
> Baseline auto adjustment disabled:...
> Current topology version: 1 (...)
> Baseline nodes:
> ...
>
> Number of baseline nodes: 1
> Other nodes not found.
> Command [BASELINE] finished with code: 0 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21102) Incorrect cluster state output for ACTIVE_READ_ONLY in --baseline
[
https://issues.apache.org/jira/browse/IGNITE-21102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17800481#comment-17800481
]
Oleg Valuyskiy commented on IGNITE-21102:
-
[~nizhikov], please review my changes.
The ‘ClusterState’ property has been added to the ‘BaseLineTaskResult’ class;
this property is now used to indicate the state of a cluster in the
‘AbstractBaselineCommand#printResult’ method – instead of the ‘active/inactive’
flag.
> Incorrect cluster state output for ACTIVE_READ_ONLY in --baseline
> -
>
> Key: IGNITE-21102
> URL: https://issues.apache.org/jira/browse/IGNITE-21102
> Project: Ignite
> Issue Type: Bug
>Reporter: Julia Bakulina
>Assignee: Oleg Valuyskiy
>Priority: Major
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Incorrect cluster state output for ACTIVE_READ_ONLY in --baseline.
> org.apache.ignite.internal.commandline.BaselineCommand#baselinePrint0
> {code:java}
> logger.info("Cluster state: " + (res.isActive() ? "active" :
> "inactive"));
> {code}
> org.apache.ignite.cluster.ClusterState#ACTIVE_READ_ONLY
>
> An example of changing the cluster state:
> {code:java}
> Command [SET-STATE] started
> Arguments: ... --set-state ACTIVE_READ_ONLY
>
> Cluster state changed to ACTIVE_READ_ONLY
> Command [SET-STATE] finished with code: 0 {code}
> Cluster state in control.sh --baseline
> {code:java}
> Command [BASELINE] started
> Arguments: ... --baseline
>
> Cluster state: active
> Current topology version: 1
> Baseline auto adjustment disabled:...
> Current topology version: 1 (...)
> Baseline nodes:
> ...
>
> Number of baseline nodes: 1
> Other nodes not found.
> Command [BASELINE] finished with code: 0 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-21102) Incorrect cluster state output for ACTIVE_READ_ONLY in --baseline
[
https://issues.apache.org/jira/browse/IGNITE-21102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Valuyskiy reassigned IGNITE-21102:
---
Assignee: Oleg Valuyskiy (was: Julia Bakulina)
> Incorrect cluster state output for ACTIVE_READ_ONLY in --baseline
> -
>
> Key: IGNITE-21102
> URL: https://issues.apache.org/jira/browse/IGNITE-21102
> Project: Ignite
> Issue Type: Bug
>Reporter: Julia Bakulina
>Assignee: Oleg Valuyskiy
>Priority: Major
> Labels: ise
>
> Incorrect cluster state output for ACTIVE_READ_ONLY in --baseline.
> org.apache.ignite.internal.commandline.BaselineCommand#baselinePrint0
> {code:java}
> logger.info("Cluster state: " + (res.isActive() ? "active" :
> "inactive"));
> {code}
> org.apache.ignite.cluster.ClusterState#ACTIVE_READ_ONLY
>
> An example of changing the cluster state:
> {code:java}
> Command [SET-STATE] started
> Arguments: ... --set-state ACTIVE_READ_ONLY
>
> Cluster state changed to ACTIVE_READ_ONLY
> Command [SET-STATE] finished with code: 0 {code}
> Cluster state in control.sh --baseline
> {code:java}
> Command [BASELINE] started
> Arguments: ... --baseline
>
> Cluster state: active
> Current topology version: 1
> Baseline auto adjustment disabled:...
> Current topology version: 1 (...)
> Baseline nodes:
> ...
>
> Number of baseline nodes: 1
> Other nodes not found.
> Command [BASELINE] finished with code: 0 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21051) Fix javadocs for IndexQuery
[ https://issues.apache.org/jira/browse/IGNITE-21051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17797091#comment-17797091 ] Oleg Valuyskiy commented on IGNITE-21051: - [~timonin.maksim], please review my changes. Bulletpoints for index discovering algorithms and paragraph separators have been added to Javadoc in the IndexQuery class. > Fix javadocs for IndexQuery > --- > > Key: IGNITE-21051 > URL: https://issues.apache.org/jira/browse/IGNITE-21051 > Project: Ignite > Issue Type: Improvement >Reporter: Maksim Timonin >Assignee: Oleg Valuyskiy >Priority: Major > Labels: ise, newbie > Time Spent: 1h > Remaining Estimate: 0h > > It's required to fix javadoc formatting in the `IndexQuery` class. Now it > renders the algorithm list in single line. Should use "ul", "li" tags for > correct rendering. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21051) Fix javadocs for IndexQuery
[ https://issues.apache.org/jira/browse/IGNITE-21051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Valuyskiy reassigned IGNITE-21051: --- Assignee: Oleg Valuyskiy > Fix javadocs for IndexQuery > --- > > Key: IGNITE-21051 > URL: https://issues.apache.org/jira/browse/IGNITE-21051 > Project: Ignite > Issue Type: Improvement >Reporter: Maksim Timonin >Assignee: Oleg Valuyskiy >Priority: Major > Labels: ise, newbie > > It's required to fix javadoc formatting in the `IndexQuery` class. Now it > renders the algorithm list in single line. Should use "ul", "li" tags for > correct rendering. -- This message was sent by Atlassian Jira (v8.20.10#820010)
