[jira] [Updated] (IGNITE-13940) Ignite configuration annotation processor wrong test sources output
[ https://issues.apache.org/jira/browse/IGNITE-13940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-13940: - Fix Version/s: 3.0.0-alpha1 > Ignite configuration annotation processor wrong test sources output > --- > > Key: IGNITE-13940 > URL: https://issues.apache.org/jira/browse/IGNITE-13940 > Project: Ignite > Issue Type: Bug >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha1 > > Time Spent: 10m > Remaining Estimate: 0h > > In ignite3, after a new maven structure was introduced, maven-compiler-plugin > generated test sources in "target/test-classes" folder instead of > "generated-test-source/test-annotations" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13940) Ignite configuration annotation processor wrong test sources output
[ https://issues.apache.org/jira/browse/IGNITE-13940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-13940: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Ignite configuration annotation processor wrong test sources output > --- > > Key: IGNITE-13940 > URL: https://issues.apache.org/jira/browse/IGNITE-13940 > Project: Ignite > Issue Type: Bug >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha1 > > Time Spent: 10m > Remaining Estimate: 0h > > In ignite3, after a new maven structure was introduced, maven-compiler-plugin > generated test sources in "target/test-classes" folder instead of > "generated-test-source/test-annotations" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13940) Ignite configuration annotation processor wrong test sources output
[ https://issues.apache.org/jira/browse/IGNITE-13940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semyon Danilov updated IGNITE-13940: Labels: ignite-3 (was: ) > Ignite configuration annotation processor wrong test sources output > --- > > Key: IGNITE-13940 > URL: https://issues.apache.org/jira/browse/IGNITE-13940 > Project: Ignite > Issue Type: Bug >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > In ignite3, after a new maven structure was introduced, maven-compiler-plugin > generated test sources in "target/test-classes" folder instead of > "generated-test-source/test-annotations" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13740) Create a "Getting Started" documentation page for Ignite 3.0
[ https://issues.apache.org/jira/browse/IGNITE-13740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256842#comment-17256842 ] Valentin Kulichenko commented on IGNITE-13740: -- Create a ticket for the port change: https://issues.apache.org/jira/browse/IGNITE-13943 > Create a "Getting Started" documentation page for Ignite 3.0 > > > Key: IGNITE-13740 > URL: https://issues.apache.org/jira/browse/IGNITE-13740 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Valentin Kulichenko >Assignee: Nikita Safonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Need to create a starting page that describes: > # Installation and upgrade process for manual download and RPM/DEB options. > # How to add optional modules (both Ignite and user-provided). > # How to start a node. > # Any other basic ops appropriate for the "Getting Started" page. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13943) Change the default port for REST
Valentin Kulichenko created IGNITE-13943: Summary: Change the default port for REST Key: IGNITE-13943 URL: https://issues.apache.org/jira/browse/IGNITE-13943 Project: Ignite Issue Type: Improvement Reporter: Valentin Kulichenko Assignee: Valentin Kulichenko Fix For: 3.0.0-alpha1 Port 8080 is often consumed by other apps, so it doesn't seem to be a good choice for the default REST port. Let's choose something more Ignite-specific. Otherwise, there is a big chance a user will not be able to go through the Getting Started guide (all the management commands will require explicit endpoint). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13939) [windows][usability] cmd/powershell there is no command highlighting in the help strings.
[ https://issues.apache.org/jira/browse/IGNITE-13939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256838#comment-17256838 ] Valentin Kulichenko commented on IGNITE-13939: -- Fixed the main issue - highlighting now works in CMD and PowerShell. However, color and other styles are inconsistent across different terminals - created https://issues.apache.org/jira/browse/IGNITE-13942. > [windows][usability] cmd/powershell there is no command highlighting in the > help strings. > - > > Key: IGNITE-13939 > URL: https://issues.apache.org/jira/browse/IGNITE-13939 > Project: Ignite > Issue Type: Bug >Reporter: Fedor Malchikov >Assignee: Valentin Kulichenko >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Fix For: 3.0.0-alpha1 > > Attachments: image-2020-12-30-16-26-04-865.png > > > windows: > !image-2020-12-30-16-26-04-865.png! > > This makes reading doc strings more difficult than in nix\macos. > I would like to have additional quotation marks for commands. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13939) [windows][usability] cmd/powershell there is no command highlighting in the help strings.
[
https://issues.apache.org/jira/browse/IGNITE-13939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko resolved IGNITE-13939.
--
Resolution: Fixed
Fixed in {{main}}.
> [windows][usability] cmd/powershell there is no command highlighting in the
> help strings.
> -
>
> Key: IGNITE-13939
> URL: https://issues.apache.org/jira/browse/IGNITE-13939
> Project: Ignite
> Issue Type: Bug
>Reporter: Fedor Malchikov
>Assignee: Valentin Kulichenko
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha1
>
> Attachments: image-2020-12-30-16-26-04-865.png
>
>
> windows:
> !image-2020-12-30-16-26-04-865.png!
>
> This makes reading doc strings more difficult than in nix\macos.
> I would like to have additional quotation marks for commands.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-9109) CPP Thin: Implement SQL API
[ https://issues.apache.org/jira/browse/IGNITE-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-9109: Ignite Flags: Docs Required,Release Notes Required (was: Docs Required) Release Note: C++ thin client: Added SQL API > CPP Thin: Implement SQL API > --- > > Key: IGNITE-9109 > URL: https://issues.apache.org/jira/browse/IGNITE-9109 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 2.6 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: 2.10 > > Time Spent: 40m > Remaining Estimate: 0h > > Need to implement SQL API for C++ thin client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13942) [CLI] Highlighting is inconsistent across different terminals
Valentin Kulichenko created IGNITE-13942: Summary: [CLI] Highlighting is inconsistent across different terminals Key: IGNITE-13942 URL: https://issues.apache.org/jira/browse/IGNITE-13942 Project: Ignite Issue Type: Bug Reporter: Valentin Kulichenko Colors and the highlighting used by the CLI tool differ from terminal to terminal. Need to investigate and see how this can be fixed/improved. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13937) [windows] Invalid ignite icon in ascii graphics (cmd, powershell)
[ https://issues.apache.org/jira/browse/IGNITE-13937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256835#comment-17256835 ] Valentin Kulichenko edited comment on IGNITE-13937 at 12/31/20, 5:13 AM: - Changed the banner so that uses only ASCII symbols and therefore compatible with all terminals. was (Author: vkulichenko): Changed that banner so that uses only ASCII symbols and therefore compatible with all terminals. > [windows] Invalid ignite icon in ascii graphics (cmd, powershell) > - > > Key: IGNITE-13937 > URL: https://issues.apache.org/jira/browse/IGNITE-13937 > Project: Ignite > Issue Type: Bug >Reporter: Fedor Malchikov >Assignee: Valentin Kulichenko >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Fix For: 3.0.0-alpha1 > > Attachments: image-2020-12-30-15-53-47-187.png > > > !image-2020-12-30-15-53-47-187.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13937) [windows] Invalid ignite icon in ascii graphics (cmd, powershell)
[
https://issues.apache.org/jira/browse/IGNITE-13937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko resolved IGNITE-13937.
--
Resolution: Fixed
Fixed in {{main}}.
> [windows] Invalid ignite icon in ascii graphics (cmd, powershell)
> -
>
> Key: IGNITE-13937
> URL: https://issues.apache.org/jira/browse/IGNITE-13937
> Project: Ignite
> Issue Type: Bug
>Reporter: Fedor Malchikov
>Assignee: Valentin Kulichenko
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha1
>
> Attachments: image-2020-12-30-15-53-47-187.png
>
>
> !image-2020-12-30-15-53-47-187.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13937) [windows] Invalid ignite icon in ascii graphics (cmd, powershell)
[ https://issues.apache.org/jira/browse/IGNITE-13937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256835#comment-17256835 ] Valentin Kulichenko commented on IGNITE-13937: -- Changed that banner so that uses only ASCII symbols and therefore compatible with all terminals. > [windows] Invalid ignite icon in ascii graphics (cmd, powershell) > - > > Key: IGNITE-13937 > URL: https://issues.apache.org/jira/browse/IGNITE-13937 > Project: Ignite > Issue Type: Bug >Reporter: Fedor Malchikov >Assignee: Valentin Kulichenko >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Fix For: 3.0.0-alpha1 > > Attachments: image-2020-12-30-15-53-47-187.png > > > !image-2020-12-30-15-53-47-187.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13936) [windows] Error: Could not find or load main class org.apache.ignite.app.IgniteRunner
[
https://issues.apache.org/jira/browse/IGNITE-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256832#comment-17256832
]
Valentin Kulichenko commented on IGNITE-13936:
--
[~prom1se], never mind. I was able to reproduce and find the root cause.
> [windows] Error: Could not find or load main class
> org.apache.ignite.app.IgniteRunner
> -
>
> Key: IGNITE-13936
> URL: https://issues.apache.org/jira/browse/IGNITE-13936
> Project: Ignite
> Issue Type: Bug
>Reporter: Fedor Malchikov
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha1
>
>
> {code:java}
> PS C:\pub_share> .\ignite.exe init
> --repo=https://repository.apache.org/content/repositories/orgapacheignite-1499
> >>
> Creating directories... Done!
> +++
> | Binaries Directory | C:\Users\user\ignite\bin |
> +++
> | Work Directory | C:\Users\user\ignite\work |
> +++
> Installing org.apache.ignite:ignite-runner:3.0.0-alpha1...
> |===>|
> 99%
> ||
> Done!
> Apache Ignite is successfully initialized. Use the ignite node start command
> to start a new local node.
> PS C:\pub_share> .\ignite.exe node start 1
> Starting a new Ignite node...
> ||
> Done!
> ||
> Done!
> Can't start the node. Read logs for details: C:\Users\justp\ignite\work\1.log
>
> {code}
>
> info in log:
> Error: Could not find or load main class org.apache.ignite.app.IgniteRunner
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.app.IgniteRunner
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-13936) [windows] Error: Could not find or load main class org.apache.ignite.app.IgniteRunner
[
https://issues.apache.org/jira/browse/IGNITE-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko resolved IGNITE-13936.
--
Resolution: Fixed
Fixed in {{main}}.
> [windows] Error: Could not find or load main class
> org.apache.ignite.app.IgniteRunner
> -
>
> Key: IGNITE-13936
> URL: https://issues.apache.org/jira/browse/IGNITE-13936
> Project: Ignite
> Issue Type: Bug
>Reporter: Fedor Malchikov
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha1
>
>
> {code:java}
> PS C:\pub_share> .\ignite.exe init
> --repo=https://repository.apache.org/content/repositories/orgapacheignite-1499
> >>
> Creating directories... Done!
> +++
> | Binaries Directory | C:\Users\user\ignite\bin |
> +++
> | Work Directory | C:\Users\user\ignite\work |
> +++
> Installing org.apache.ignite:ignite-runner:3.0.0-alpha1...
> |===>|
> 99%
> ||
> Done!
> Apache Ignite is successfully initialized. Use the ignite node start command
> to start a new local node.
> PS C:\pub_share> .\ignite.exe node start 1
> Starting a new Ignite node...
> ||
> Done!
> ||
> Done!
> Can't start the node. Read logs for details: C:\Users\justp\ignite\work\1.log
>
> {code}
>
> info in log:
> Error: Could not find or load main class org.apache.ignite.app.IgniteRunner
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.app.IgniteRunner
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-9109) CPP Thin: Implement SQL API
[
https://issues.apache.org/jira/browse/IGNITE-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256830#comment-17256830
]
Ignite TC Bot commented on IGNITE-9109:
---
{panel:title=Branch: [pull/8628/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8628/head] Base: [master] : New Tests
(2048)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform C++ CMake (Win x64 / Debug){color} [[tests
993|https://ci.ignite.apache.org/viewLog.html?buildId=5813702]]
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectTwoValues
- PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionFloor - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectSingleValue - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionLog - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
CreateTableInsertSelect - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlDateTimeFunctionTestSuite: TestCurrentDate
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectTwoValuesInDifferentOrder - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForCacheNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForClientNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: CacheQueryTestSuite:
TestFieldsQueryByteArrayInsertSelect - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForDaemons -
PASSED{color}
... and 982 new tests
{color:#8b}Platform C++ (Win x64 / Debug){color} [[tests
993|https://ci.ignite.apache.org/viewLog.html?buildId=5813689]]
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectTwoValues
- PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionFloor - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectSingleValue - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionLog - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
CreateTableInsertSelect - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlDateTimeFunctionTestSuite: TestCurrentDate
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectTwoValuesInDifferentOrder - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForCacheNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: CacheQueryTestSuite:
TestFieldsQueryByteArrayInsertSelect - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForClientNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForDaemons -
PASSED{color}
... and 982 new tests
{color:#8b}Platform C++ (Win x64 / Release){color} [[tests
32|https://ci.ignite.apache.org/viewLog.html?buildId=5813690]]
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectTwoValues
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectSingleValue - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
CreateTableInsertSelect - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectTwoValuesInDifferentOrder - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForCacheNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForClientNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForDaemons -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForHost - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForOldest -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForRandom -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForRemotes -
PASSED{color}
... and 21 new tests
{color:#8b}Platform C++ CMake (Linux Clang){color} [[tests
10|https://ci.ignite.apache.org/viewLog.html?buildId=5813694]]
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectTwoValues
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectSingleValue - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
CreateTableInsertSelect - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectTwoValuesInDifferentOrder - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryBasicTestSuite:
SqlFieldsQueryDefaults - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectEmpty -
PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryBasicTestSuite:
SqlFieldsQuerySetGet - PASSED{color}
*
[jira] [Commented] (IGNITE-12892) Clarify WAL archive size configuration
[ https://issues.apache.org/jira/browse/IGNITE-12892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256828#comment-17256828 ] shivakumar commented on IGNITE-12892: - Hi [~sdanilov] could you please provide this change as patch on 2.9.1 ? > Clarify WAL archive size configuration > -- > > Key: IGNITE-12892 > URL: https://issues.apache.org/jira/browse/IGNITE-12892 > Project: Ignite > Issue Type: Sub-task >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Fix For: 2.10 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Actual maximum size of WAL archive that can be reserved for historical > rebalance is calculated as minimum of three properties: > # DataStorageConfiguration#walHistSize (units: number of checkpoints) > # DataStorageConfiguration#maxWalArchiveSize (units: bytes) > # IgniteSystemProperties#IGNITE_PDS_MAX_CHECKPOINT_MEMORY_HISTORY_SIZE > (units: number of checkpoints) > The logic is a little unclear, so I propose following changes: > # Stop using walHistSize at all (it's already deprecated) for WAL truncation > # Use IGNITE_PDS_MAX_CHECKPOINT_MEMORY_HISTORY_SIZE only in case WAL archive > is managed externally (so we limit the quantity of checkpoints stored in > memory, but don't remove WAL files) > # Use -1 for maxWalArchiveSize (instead of Long.MAX_VALUE) to disable WAL > truncation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13373) WAL segmentns do not released on releaseHistoryForPreloading()
[ https://issues.apache.org/jira/browse/IGNITE-13373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256827#comment-17256827 ] shivakumar commented on IGNITE-13373: - Hi [~alapin] could you please provide this change as patch on 2.9.1 ? > WAL segmentns do not released on releaseHistoryForPreloading() > -- > > Key: IGNITE-13373 > URL: https://issues.apache.org/jira/browse/IGNITE-13373 > Project: Ignite > Issue Type: Bug >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Labels: 2.9.1-rc > Fix For: 2.10 > > Time Spent: 20m > Remaining Estimate: 0h > > * Reserve/releaseHistoryForPreloading() was reworked, now we store oldest > WALPointer that was reserved during reserveHistoryForPreloading in > reservedForPreloading field. As a result it's possible to release wall > reservation on releaseHIstoryForPreloading(). > * searchAndReserveCheckpoints() was slightly refactored: now it returns not > only an earliestValidCheckpoints but also an oldest reservedCheckpoint, so > that there’s no need to recalculate it within reserveHistoryForExchange(). > * -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13738) Document the new configuration format
[ https://issues.apache.org/jira/browse/IGNITE-13738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-13738: - Fix Version/s: (was: 3.0.0-alpha1) > Document the new configuration format > - > > Key: IGNITE-13738 > URL: https://issues.apache.org/jira/browse/IGNITE-13738 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Reporter: Valentin Kulichenko >Assignee: Nikita Safonov >Priority: Major > Labels: ignite-3 > > IEP: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-55+Unified+Configuration] > Need to create a documentation page describing formats supported by the new > configuration engine (HOCON, Properties, JSON) and the currently available > parameters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13739) Document the new CLI tool
[ https://issues.apache.org/jira/browse/IGNITE-13739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-13739: - Fix Version/s: (was: 3.0.0-alpha1) > Document the new CLI tool > - > > Key: IGNITE-13739 > URL: https://issues.apache.org/jira/browse/IGNITE-13739 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Reporter: Valentin Kulichenko >Assignee: Nikita Safonov >Priority: Major > Labels: ignite-3 > > Need to create a documentation page describing how to use the command-line > tool. We should provide detailed explanations on all the supported commands, > as well as their parameters. > Some more information in the parent ticket: > https://issues.apache.org/jira/browse/IGNITE-13609 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13937) [windows] Invalid ignite icon in ascii graphics (cmd, powershell)
[ https://issues.apache.org/jira/browse/IGNITE-13937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko reassigned IGNITE-13937: Assignee: Valentin Kulichenko > [windows] Invalid ignite icon in ascii graphics (cmd, powershell) > - > > Key: IGNITE-13937 > URL: https://issues.apache.org/jira/browse/IGNITE-13937 > Project: Ignite > Issue Type: Bug >Reporter: Fedor Malchikov >Assignee: Valentin Kulichenko >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Fix For: 3.0.0-alpha1 > > Attachments: image-2020-12-30-15-53-47-187.png > > > !image-2020-12-30-15-53-47-187.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13939) [windows][usability] cmd/powershell there is no command highlighting in the help strings.
[ https://issues.apache.org/jira/browse/IGNITE-13939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-13939: - Fix Version/s: 3.0.0-alpha1 > [windows][usability] cmd/powershell there is no command highlighting in the > help strings. > - > > Key: IGNITE-13939 > URL: https://issues.apache.org/jira/browse/IGNITE-13939 > Project: Ignite > Issue Type: Bug >Reporter: Fedor Malchikov >Assignee: Valentin Kulichenko >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Fix For: 3.0.0-alpha1 > > Attachments: image-2020-12-30-16-26-04-865.png > > > windows: > !image-2020-12-30-16-26-04-865.png! > > This makes reading doc strings more difficult than in nix\macos. > I would like to have additional quotation marks for commands. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13939) [windows][usability] cmd/powershell there is no command highlighting in the help strings.
[ https://issues.apache.org/jira/browse/IGNITE-13939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-13939: - Priority: Major (was: Minor) > [windows][usability] cmd/powershell there is no command highlighting in the > help strings. > - > > Key: IGNITE-13939 > URL: https://issues.apache.org/jira/browse/IGNITE-13939 > Project: Ignite > Issue Type: Bug >Reporter: Fedor Malchikov >Assignee: Valentin Kulichenko >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Attachments: image-2020-12-30-16-26-04-865.png > > > windows: > !image-2020-12-30-16-26-04-865.png! > > This makes reading doc strings more difficult than in nix\macos. > I would like to have additional quotation marks for commands. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13938) [windows] double progress bar for 100% operations
[
https://issues.apache.org/jira/browse/IGNITE-13938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-13938:
-
Fix Version/s: 3.0.0-alpha1
> [windows] double progress bar for 100% operations
> -
>
> Key: IGNITE-13938
> URL: https://issues.apache.org/jira/browse/IGNITE-13938
> Project: Ignite
> Issue Type: Bug
>Reporter: Fedor Malchikov
>Assignee: Valentin Kulichenko
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha1
>
>
> {code:java}
> PS C:\pub_share> .\ignite.exe init
> --repo=https://repository.apache.org/content/repositories/orgapacheignite-1499
> >>
> Creating directories... Done!
> +++
> | Binaries Directory | C:\Users\user\ignite\bin |
> +++
> | Work Directory | C:\Users\user\ignite\work |
> +++Installing
> org.apache.ignite:ignite-runner:3.0.0-alpha1...
> |===>|
>99%
> ||
> Done!Apache Ignite is successfully initialized. Use the ignite node start
> command to start a new local node.
> PS C:\pub_share> .\ignite.exe node start 1
> Starting a new Ignite node...
> ||
> Done!
> ||
> Done!
> Can't start the node. Read logs for details: C:\Users\justp\ignite\work\1.log
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13937) [windows] Invalid ignite icon in ascii graphics (cmd, powershell)
[ https://issues.apache.org/jira/browse/IGNITE-13937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-13937: - Fix Version/s: 3.0.0-alpha1 > [windows] Invalid ignite icon in ascii graphics (cmd, powershell) > - > > Key: IGNITE-13937 > URL: https://issues.apache.org/jira/browse/IGNITE-13937 > Project: Ignite > Issue Type: Bug >Reporter: Fedor Malchikov >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Fix For: 3.0.0-alpha1 > > Attachments: image-2020-12-30-15-53-47-187.png > > > !image-2020-12-30-15-53-47-187.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13933) Add an ability to customize documentation source repo
[ https://issues.apache.org/jira/browse/IGNITE-13933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-13933. -- Resolution: Fixed > Add an ability to customize documentation source repo > - > > Key: IGNITE-13933 > URL: https://issues.apache.org/jira/browse/IGNITE-13933 > Project: Ignite > Issue Type: Improvement > Components: website >Reporter: Valentin Kulichenko >Assignee: Mauricio Stekl >Priority: Critical > Fix For: 3.0.0-alpha1 > > > Documentation deployment script current has the original Ignite repo > hardcoded: > https://github.com/apache/ignite-website/blob/master/_docs/build.sh#L42 > Ignite 3.x is located in a different repo: https://github.com/apache/ignite-3 > Suggestion: add a parameter that would allow specifying the version (2.x or > 3.x). The script should then pick the corresponding repo URL and fetch the > sources from there. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13939) [windows][usability] cmd/powershell there is no command highlighting in the help strings.
[ https://issues.apache.org/jira/browse/IGNITE-13939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko reassigned IGNITE-13939: Assignee: Valentin Kulichenko > [windows][usability] cmd/powershell there is no command highlighting in the > help strings. > - > > Key: IGNITE-13939 > URL: https://issues.apache.org/jira/browse/IGNITE-13939 > Project: Ignite > Issue Type: Bug >Reporter: Fedor Malchikov >Assignee: Valentin Kulichenko >Priority: Minor > Labels: ignite-3, ignite-3-cli-tool > Attachments: image-2020-12-30-16-26-04-865.png > > > windows: > !image-2020-12-30-16-26-04-865.png! > > This makes reading doc strings more difficult than in nix\macos. > I would like to have additional quotation marks for commands. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9109) CPP Thin: Implement SQL API
[ https://issues.apache.org/jira/browse/IGNITE-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-9109: Fix Version/s: 2.10 > CPP Thin: Implement SQL API > --- > > Key: IGNITE-9109 > URL: https://issues.apache.org/jira/browse/IGNITE-9109 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 2.6 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: 2.10 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Need to implement SQL API for C++ thin client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-9109) CPP Thin: Implement SQL API
[
https://issues.apache.org/jira/browse/IGNITE-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256756#comment-17256756
]
Ignite TC Bot commented on IGNITE-9109:
---
{panel:title=Branch: [pull/8628/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8628/head] Base: [master] : New Tests
(1900)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform C++ CMake (Win x64 / Debug){color} [[tests
899|https://ci.ignite.apache.org/viewLog.html?buildId=5813412]]
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionFloor - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionLog - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlDateTimeFunctionTestSuite: TestCurrentDate
- PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForCacheNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForClientNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: CacheQueryTestSuite:
TestFieldsQueryByteArrayInsertSelect - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForDaemons -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForHost - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForOldest -
PASSED{color}
* {color:#013220}IgniteCoreTest: ContinuousQueryTestSuite: TestBasic -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForRandom -
PASSED{color}
... and 888 new tests
{color:#8b}Platform C++ (Win x64 / Debug){color} [[tests
971|https://ci.ignite.apache.org/viewLog.html?buildId=5813405]]
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectTwoValues
- PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionFloor - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectSingleValue - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionLog - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
CreateTableInsertSelect - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlDateTimeFunctionTestSuite: TestCurrentDate
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectTwoValuesInDifferentOrder - PASSED{color}
* {color:#013220}IgniteCoreTest: CacheQueryTestSuite:
TestFieldsQueryByteArrayInsertSelect - PASSED{color}
* {color:#013220}IgniteCoreTest: ContinuousQueryTestSuite: TestBasic -
PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryBasicTestSuite:
SqlFieldsQueryDefaults - PASSED{color}
* {color:#013220}IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQueryScan
- PASSED{color}
... and 960 new tests
{color:#8b}Platform C++ (Win x64 / Release){color} [[tests
10|https://ci.ignite.apache.org/viewLog.html?buildId=5813406]]
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectTwoValues
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectSingleValue - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
CreateTableInsertSelect - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectTwoValuesInDifferentOrder - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryBasicTestSuite:
SqlFieldsQueryDefaults - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectEmpty -
PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryBasicTestSuite:
SqlFieldsQuerySetGet - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
Select1Values - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectKeyValue
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
Select10ValuesPageSize1 - PASSED{color}
{color:#8b}Platform C++ CMake (Linux Clang){color} [[tests
10|https://ci.ignite.apache.org/viewLog.html?buildId=5813410]]
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectTwoValues
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectSingleValue - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
CreateTableInsertSelect - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectTwoValuesInDifferentOrder - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryBasicTestSuite:
SqlFieldsQueryDefaults - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectEmpty -
PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryBasicTestSuite:
SqlFieldsQuerySetGet - PASSED{color}
* {color:#013220}IgniteThinClientTest:
[jira] [Commented] (IGNITE-13740) Create a "Getting Started" documentation page for Ignite 3.0
[ https://issues.apache.org/jira/browse/IGNITE-13740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256742#comment-17256742 ] Denis A. Magda commented on IGNITE-13740: - *The Documentation Overview page* * Provide references to all the mentioned IEP *The Getting Started* * Add "Windows" tabs for the OS-specific instructions such as a dir creation and curl-like-download. In all the relevant places. * The CLI reference is hard-coded to the staging. This parameter needs to be set in the _config.yaml file. Use the reference to the binary location and the "version" tag in the sources instead of the hard-coded text. * the export command - calculate the local path automatically and add it to the PATH env variable. Unit + Windows. * Extend the Starting a Node section by showing how to start a two-node cluster. * [~vkulichenko] consider changing the default REST port from 8080 to smth less frequently used. * Next steps - the Ignite CLI commands' table and the HOCON config need to be moved to separate pages and documented thoroughly. > Create a "Getting Started" documentation page for Ignite 3.0 > > > Key: IGNITE-13740 > URL: https://issues.apache.org/jira/browse/IGNITE-13740 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Valentin Kulichenko >Assignee: Nikita Safonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Need to create a starting page that describes: > # Installation and upgrade process for manual download and RPM/DEB options. > # How to add optional modules (both Ignite and user-provided). > # How to start a node. > # Any other basic ops appropriate for the "Getting Started" page. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13938) [windows] double progress bar for 100% operations
[
https://issues.apache.org/jira/browse/IGNITE-13938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko reassigned IGNITE-13938:
Assignee: Valentin Kulichenko
> [windows] double progress bar for 100% operations
> -
>
> Key: IGNITE-13938
> URL: https://issues.apache.org/jira/browse/IGNITE-13938
> Project: Ignite
> Issue Type: Bug
>Reporter: Fedor Malchikov
>Assignee: Valentin Kulichenko
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> {code:java}
> PS C:\pub_share> .\ignite.exe init
> --repo=https://repository.apache.org/content/repositories/orgapacheignite-1499
> >>
> Creating directories... Done!
> +++
> | Binaries Directory | C:\Users\user\ignite\bin |
> +++
> | Work Directory | C:\Users\user\ignite\work |
> +++Installing
> org.apache.ignite:ignite-runner:3.0.0-alpha1...
> |===>|
>99%
> ||
> Done!Apache Ignite is successfully initialized. Use the ignite node start
> command to start a new local node.
> PS C:\pub_share> .\ignite.exe node start 1
> Starting a new Ignite node...
> ||
> Done!
> ||
> Done!
> Can't start the node. Read logs for details: C:\Users\justp\ignite\work\1.log
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13928) Index defragmentation: only one index defragmented
[
https://issues.apache.org/jira/browse/IGNITE-13928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256708#comment-17256708
]
Ignite TC Bot commented on IGNITE-13928:
{panel:title=Branch: [pull/8622/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8622/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS 4{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5812924]]
* {color:#013220}IgnitePdsTestSuite4:
DefragmentationMXBeanTest.testDefragmentationStatus - PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
DefragmentationMXBeanTest.testDefragmentationCancel - PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
DefragmentationMXBeanTest.testDefragmentationSchedule - PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
DefragmentationMXBeanTest.testDefragmentationCancelInProgress - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5812950buildTypeId=IgniteTests24Java8_RunAll]
> Index defragmentation: only one index defragmented
> --
>
> Key: IGNITE-13928
> URL: https://issues.apache.org/jira/browse/IGNITE-13928
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Semyon Danilov
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In IndexingDefragmentation.java:
> {code:java}
> // code placeholder
> H2TreeIndex oldH2Idx = (H2TreeIndex)indexes.get(2);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-13936) [windows] Error: Could not find or load main class org.apache.ignite.app.IgniteRunner
[
https://issues.apache.org/jira/browse/IGNITE-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko reassigned IGNITE-13936:
Assignee: Valentin Kulichenko
> [windows] Error: Could not find or load main class
> org.apache.ignite.app.IgniteRunner
> -
>
> Key: IGNITE-13936
> URL: https://issues.apache.org/jira/browse/IGNITE-13936
> Project: Ignite
> Issue Type: Bug
>Reporter: Fedor Malchikov
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha1
>
>
> {code:java}
> PS C:\pub_share> .\ignite.exe init
> --repo=https://repository.apache.org/content/repositories/orgapacheignite-1499
> >>
> Creating directories... Done!
> +++
> | Binaries Directory | C:\Users\user\ignite\bin |
> +++
> | Work Directory | C:\Users\user\ignite\work |
> +++
> Installing org.apache.ignite:ignite-runner:3.0.0-alpha1...
> |===>|
> 99%
> ||
> Done!
> Apache Ignite is successfully initialized. Use the ignite node start command
> to start a new local node.
> PS C:\pub_share> .\ignite.exe node start 1
> Starting a new Ignite node...
> ||
> Done!
> ||
> Done!
> Can't start the node. Read logs for details: C:\Users\justp\ignite\work\1.log
>
> {code}
>
> info in log:
> Error: Could not find or load main class org.apache.ignite.app.IgniteRunner
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.app.IgniteRunner
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13936) [windows] Error: Could not find or load main class org.apache.ignite.app.IgniteRunner
[
https://issues.apache.org/jira/browse/IGNITE-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-13936:
-
Fix Version/s: 3.0.0-alpha1
> [windows] Error: Could not find or load main class
> org.apache.ignite.app.IgniteRunner
> -
>
> Key: IGNITE-13936
> URL: https://issues.apache.org/jira/browse/IGNITE-13936
> Project: Ignite
> Issue Type: Bug
>Reporter: Fedor Malchikov
>Priority: Blocker
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha1
>
>
> {code:java}
> PS C:\pub_share> .\ignite.exe init
> --repo=https://repository.apache.org/content/repositories/orgapacheignite-1499
> >>
> Creating directories... Done!
> +++
> | Binaries Directory | C:\Users\user\ignite\bin |
> +++
> | Work Directory | C:\Users\user\ignite\work |
> +++
> Installing org.apache.ignite:ignite-runner:3.0.0-alpha1...
> |===>|
> 99%
> ||
> Done!
> Apache Ignite is successfully initialized. Use the ignite node start command
> to start a new local node.
> PS C:\pub_share> .\ignite.exe node start 1
> Starting a new Ignite node...
> ||
> Done!
> ||
> Done!
> Can't start the node. Read logs for details: C:\Users\justp\ignite\work\1.log
>
> {code}
>
> info in log:
> Error: Could not find or load main class org.apache.ignite.app.IgniteRunner
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.app.IgniteRunner
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13941) Poor CLS reported for multiple website pages
Denis A. Magda created IGNITE-13941: --- Summary: Poor CLS reported for multiple website pages Key: IGNITE-13941 URL: https://issues.apache.org/jira/browse/IGNITE-13941 Project: Ignite Issue Type: Bug Components: website Reporter: Denis A. Magda Assignee: Mauricio Stekl Google reported a poor CLS index for multiple pages: [https://search.google.com/search-console/core-web-vitals?resource_id=https%3A%2F%2Fignite.apache.org%2F] The mobile traffic is affected even more severely. Need to address the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13933) Add an ability to customize documentation source repo
[
https://issues.apache.org/jira/browse/IGNITE-13933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256659#comment-17256659
]
Mauricio Stekl commented on IGNITE-13933:
-
[~vkulichenko], I sent a patch to fix the issue:
[https://github.com/apache/ignite-website/pull/66]
I didn't add another parameter to the script, but I'm picking the first char of
the --version parameter. The doc can still be built using the same syntax,
like:
{{./build.sh --version=3.0.0-alpha1 --github-branch=ignite-3.0.0-alpha1}}
> Add an ability to customize documentation source repo
> -
>
> Key: IGNITE-13933
> URL: https://issues.apache.org/jira/browse/IGNITE-13933
> Project: Ignite
> Issue Type: Improvement
> Components: website
>Reporter: Valentin Kulichenko
>Assignee: Mauricio Stekl
>Priority: Critical
> Fix For: 3.0.0-alpha1
>
>
> Documentation deployment script current has the original Ignite repo
> hardcoded:
> https://github.com/apache/ignite-website/blob/master/_docs/build.sh#L42
> Ignite 3.x is located in a different repo: https://github.com/apache/ignite-3
> Suggestion: add a parameter that would allow specifying the version (2.x or
> 3.x). The script should then pick the corresponding repo URL and fetch the
> sources from there.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13936) [windows] Error: Could not find or load main class org.apache.ignite.app.IgniteRunner
[
https://issues.apache.org/jira/browse/IGNITE-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256624#comment-17256624
]
Valentin Kulichenko commented on IGNITE-13936:
--
[~prom1se], can you please show:
# The full log.
# The output of the {{ignite node classpath}} command.
# The contents of the {{C:\Users\user\ignite\bin}} folder.
> [windows] Error: Could not find or load main class
> org.apache.ignite.app.IgniteRunner
> -
>
> Key: IGNITE-13936
> URL: https://issues.apache.org/jira/browse/IGNITE-13936
> Project: Ignite
> Issue Type: Bug
>Reporter: Fedor Malchikov
>Priority: Blocker
> Labels: ignite-3, ignite-3-cli-tool
>
> {code:java}
> PS C:\pub_share> .\ignite.exe init
> --repo=https://repository.apache.org/content/repositories/orgapacheignite-1499
> >>
> Creating directories... Done!
> +++
> | Binaries Directory | C:\Users\user\ignite\bin |
> +++
> | Work Directory | C:\Users\user\ignite\work |
> +++
> Installing org.apache.ignite:ignite-runner:3.0.0-alpha1...
> |===>|
> 99%
> ||
> Done!
> Apache Ignite is successfully initialized. Use the ignite node start command
> to start a new local node.
> PS C:\pub_share> .\ignite.exe node start 1
> Starting a new Ignite node...
> ||
> Done!
> ||
> Done!
> Can't start the node. Read logs for details: C:\Users\justp\ignite\work\1.log
>
> {code}
>
> info in log:
> Error: Could not find or load main class org.apache.ignite.app.IgniteRunner
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.app.IgniteRunner
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-13933) Add an ability to customize documentation source repo
[ https://issues.apache.org/jira/browse/IGNITE-13933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-13933: --- Assignee: Mauricio Stekl > Add an ability to customize documentation source repo > - > > Key: IGNITE-13933 > URL: https://issues.apache.org/jira/browse/IGNITE-13933 > Project: Ignite > Issue Type: Improvement > Components: website >Reporter: Valentin Kulichenko >Assignee: Mauricio Stekl >Priority: Critical > Fix For: 3.0.0-alpha1 > > > Documentation deployment script current has the original Ignite repo > hardcoded: > https://github.com/apache/ignite-website/blob/master/_docs/build.sh#L42 > Ignite 3.x is located in a different repo: https://github.com/apache/ignite-3 > Suggestion: add a parameter that would allow specifying the version (2.x or > 3.x). The script should then pick the corresponding repo URL and fetch the > sources from there. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13940) Ignite configuration annotation processor wrong test sources output
[ https://issues.apache.org/jira/browse/IGNITE-13940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semyon Danilov updated IGNITE-13940: Description: In ignite3, after a new maven structure was introduced, maven-compiler-plugin generated test sources in "target/test-classes" folder instead of "generated-test-source/test-annotations" > Ignite configuration annotation processor wrong test sources output > --- > > Key: IGNITE-13940 > URL: https://issues.apache.org/jira/browse/IGNITE-13940 > Project: Ignite > Issue Type: Bug >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > > In ignite3, after a new maven structure was introduced, maven-compiler-plugin > generated test sources in "target/test-classes" folder instead of > "generated-test-source/test-annotations" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13940) Ignite configuration annotation processor wrong test sources output
Semyon Danilov created IGNITE-13940: --- Summary: Ignite configuration annotation processor wrong test sources output Key: IGNITE-13940 URL: https://issues.apache.org/jira/browse/IGNITE-13940 Project: Ignite Issue Type: Bug Reporter: Semyon Danilov Assignee: Semyon Danilov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11110) UnsupportedOperationException: null when stopping grid
[
https://issues.apache.org/jira/browse/IGNITE-0?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-0:
-
Ignite Flags: Release Notes Required
> UnsupportedOperationException: null when stopping grid
> --
>
> Key: IGNITE-0
> URL: https://issues.apache.org/jira/browse/IGNITE-0
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Jens Borgland
>Assignee: Anton Kurbanov
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> After upgrading to 2.7 we've started getting these errors when stopping grids:
> {noformat}
> java.lang.UnsupportedOperationException: null
> at
> org.jsr166.ConcurrentLinkedHashMap.clear(ConcurrentLinkedHashMap.java:1551)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.stop(GridJobProcessor.java:264)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2356)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2228)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2612)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2575)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:379)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at org.apache.ignite.Ignition.stop(Ignition.java:225)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3568)
> ~[ignite-core-2.7.0.jar:2.7.0]
> {noformat}
> At first glance it looks likely that it was introduced with commit
> [d04d764|https://github.com/apache/ignite/commit/d04d76440ce86873de7aebc8c03d39484cd1e3e5]
> (the {{GridJobProcessor}} still calls {{clear()}} on maps).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13837) Configuration initialization
[ https://issues.apache.org/jira/browse/IGNITE-13837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256558#comment-17256558 ] Sergey Chugunov commented on IGNITE-13837: -- There are several points that are great to clarify in this ticket. First, how do we want to do an actual update of configuration tree that we have in memory? One of possible ways to simplify flow is to update it only by a callback from storage (when the update is already accepted by storage). That approach simplifies compare-and-set flow by making storage responsible to do an actual cas operation. Second, as we have storage involved into the update we need to clarify a hierarchy of exceptions declared by API to let user code to decide how to handle different situation. > Configuration initialization > > > Key: IGNITE-13837 > URL: https://issues.apache.org/jira/browse/IGNITE-13837 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Kalashnikov >Priority: Major > > It needs to think how the first initialization of node/cluster should look > like. What is the format of initial properties(json/hocon etc.)? How should > they be handled? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13509) Support encrypted caches in ducktape tests
[ https://issues.apache.org/jira/browse/IGNITE-13509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-13509: -- Description: Add support for encrypted caches in ignite ducktape tests. Add PDS compatibility test for encrypted caches. was:Add support for encrypted caches in ignite ducktape tests. > Support encrypted caches in ducktape tests > -- > > Key: IGNITE-13509 > URL: https://issues.apache.org/jira/browse/IGNITE-13509 > Project: Ignite > Issue Type: Task >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Minor > Labels: IEP-56, ducktape > Time Spent: 0.5h > Remaining Estimate: 0h > > Add support for encrypted caches in ignite ducktape tests. > Add PDS compatibility test for encrypted caches. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-9109) CPP Thin: Implement SQL API
[ https://issues.apache.org/jira/browse/IGNITE-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256539#comment-17256539 ] Pavel Tupitsyn commented on IGNITE-9109: [~isapego] Looks good, thanks! > CPP Thin: Implement SQL API > --- > > Key: IGNITE-9109 > URL: https://issues.apache.org/jira/browse/IGNITE-9109 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 2.6 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Need to implement SQL API for C++ thin client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13939) [windows][usability] cmd/powershell there is no command highlighting in the help strings.
Fedor Malchikov created IGNITE-13939: - Summary: [windows][usability] cmd/powershell there is no command highlighting in the help strings. Key: IGNITE-13939 URL: https://issues.apache.org/jira/browse/IGNITE-13939 Project: Ignite Issue Type: Bug Reporter: Fedor Malchikov Attachments: image-2020-12-30-16-26-04-865.png windows: !image-2020-12-30-16-26-04-865.png! This makes reading doc strings more difficult than in nix\macos. I would like to have additional quotation marks for commands. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13937) [windows] Invalid ignite icon in ascii graphics (cmd, powershell)
[ https://issues.apache.org/jira/browse/IGNITE-13937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fedor Malchikov updated IGNITE-13937: -- Labels: ignite-3 ignite-3-cli-tool (was: ) > [windows] Invalid ignite icon in ascii graphics (cmd, powershell) > - > > Key: IGNITE-13937 > URL: https://issues.apache.org/jira/browse/IGNITE-13937 > Project: Ignite > Issue Type: Bug >Reporter: Fedor Malchikov >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Attachments: image-2020-12-30-15-53-47-187.png > > > !image-2020-12-30-15-53-47-187.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13938) [windows] double progress bar for 100% operations
Fedor Malchikov created IGNITE-13938:
-
Summary: [windows] double progress bar for 100% operations
Key: IGNITE-13938
URL: https://issues.apache.org/jira/browse/IGNITE-13938
Project: Ignite
Issue Type: Bug
Reporter: Fedor Malchikov
{code:java}
PS C:\pub_share> .\ignite.exe init
--repo=https://repository.apache.org/content/repositories/orgapacheignite-1499
>>
Creating directories... Done!
+++
| Binaries Directory | C:\Users\user\ignite\bin |
+++
| Work Directory | C:\Users\user\ignite\work |
+++Installing
org.apache.ignite:ignite-runner:3.0.0-alpha1...
|===>|
99%
||
Done!Apache Ignite is successfully initialized. Use the ignite node start
command to start a new local node.
PS C:\pub_share> .\ignite.exe node start 1
Starting a new Ignite node...
||
Done!
||
Done!
Can't start the node. Read logs for details: C:\Users\justp\ignite\work\1.log
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13937) [windows] Invalid ignite icon in ascii graphics (cmd, powershell)
Fedor Malchikov created IGNITE-13937: - Summary: [windows] Invalid ignite icon in ascii graphics (cmd, powershell) Key: IGNITE-13937 URL: https://issues.apache.org/jira/browse/IGNITE-13937 Project: Ignite Issue Type: Bug Reporter: Fedor Malchikov Attachments: image-2020-12-30-15-53-47-187.png !image-2020-12-30-15-53-47-187.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13936) [windows] Error: Could not find or load main class org.apache.ignite.app.IgniteRunner
Fedor Malchikov created IGNITE-13936:
-
Summary: [windows] Error: Could not find or load main class
org.apache.ignite.app.IgniteRunner
Key: IGNITE-13936
URL: https://issues.apache.org/jira/browse/IGNITE-13936
Project: Ignite
Issue Type: Bug
Reporter: Fedor Malchikov
{code:java}
PS C:\pub_share> .\ignite.exe init
--repo=https://repository.apache.org/content/repositories/orgapacheignite-1499
>>
Creating directories... Done!
+++
| Binaries Directory | C:\Users\user\ignite\bin |
+++
| Work Directory | C:\Users\user\ignite\work |
+++
Installing org.apache.ignite:ignite-runner:3.0.0-alpha1...
|===>|
99%
||
Done!
Apache Ignite is successfully initialized. Use the ignite node start command to
start a new local node.
PS C:\pub_share> .\ignite.exe node start 1
Starting a new Ignite node...
||
Done!
||
Done!
Can't start the node. Read logs for details: C:\Users\justp\ignite\work\1.log
{code}
info in log:
Error: Could not find or load main class org.apache.ignite.app.IgniteRunner
Caused by: java.lang.ClassNotFoundException: org.apache.ignite.app.IgniteRunner
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13624) Extend tracing of communication socket write with number of sent bytes.
[ https://issues.apache.org/jira/browse/IGNITE-13624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256480#comment-17256480 ] Vyacheslav Koptilin commented on IGNITE-13624: -- Hello [~mmuzaf], I have no objection. > Extend tracing of communication socket write with number of sent bytes. > --- > > Key: IGNITE-13624 > URL: https://issues.apache.org/jira/browse/IGNITE-13624 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Labels: iep-48 > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > It's needed to extend tracing of communication socket write with number of > sent bytes for each message. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-9109) CPP Thin: Implement SQL API
[ https://issues.apache.org/jira/browse/IGNITE-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256473#comment-17256473 ] Igor Sapego commented on IGNITE-9109: - [~ptupitsyn] fixed. Please, take another look. > CPP Thin: Implement SQL API > --- > > Key: IGNITE-9109 > URL: https://issues.apache.org/jira/browse/IGNITE-9109 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 2.6 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Need to implement SQL API for C++ thin client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12273) Slow TX recovery
[ https://issues.apache.org/jira/browse/IGNITE-12273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov (Obsolete, actual is "av") reassigned IGNITE-12273: Assignee: Anton Vinogradov (was: Anton Vinogradov (Obsolete, actual is "av")) > Slow TX recovery > > > Key: IGNITE-12273 > URL: https://issues.apache.org/jira/browse/IGNITE-12273 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov (Obsolete, actual is "av") >Assignee: Anton Vinogradov >Priority: Major > Labels: iep-45 > > TX recovery cause B*B*N*2 GridCacheTxRecoveryRequest messages sending (B - > backups, N - prepared txs amount). > Seems, we able to perform recovery more efficiently. > For example, we may send only B*B*2 messages, accumulates txs together. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12956) Fully prepared TX rolled back on recovery if TX coordinator failed and some primary has only reads
[
https://issues.apache.org/jira/browse/IGNITE-12956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov (Obsolete, actual is "av") reassigned IGNITE-12956:
Assignee: Anton Vinogradov
> Fully prepared TX rolled back on recovery if TX coordinator failed and some
> primary has only reads
> --
>
> Key: IGNITE-12956
> URL: https://issues.apache.org/jira/browse/IGNITE-12956
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov (Obsolete, actual is "av")
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We have 3 nodes with partitioned cache with 2 backups.
> A - tx coordinator.
> B and C - other nodes.
> Let's start tx from A and perform
> {noformat}
> cache.put(primaryKeyA, someVal);
> cache.get(primaryKeyB;
> tx.prepare();
> {noformat}
> then kill A.
> Expected: tx recovered and
> {noformat}
> cache.get(primaryKeyA)!=null
> {noformat}
> Actual: tx rolled back and
> and
> {noformat}
> cache.get(primaryKeyA)==null
> {noformat}
> Reason: Node C has only 1 active transaction (because reads not propagated to
> backup), but expect to have 2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12956) Fully prepared TX rolled back on recovery if TX coordinator failed and some primary has only reads
[
https://issues.apache.org/jira/browse/IGNITE-12956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov (Obsolete, actual is "av") reassigned IGNITE-12956:
Assignee: (was: Anton Vinogradov (Obsolete, actual is "av"))
> Fully prepared TX rolled back on recovery if TX coordinator failed and some
> primary has only reads
> --
>
> Key: IGNITE-12956
> URL: https://issues.apache.org/jira/browse/IGNITE-12956
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov (Obsolete, actual is "av")
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We have 3 nodes with partitioned cache with 2 backups.
> A - tx coordinator.
> B and C - other nodes.
> Let's start tx from A and perform
> {noformat}
> cache.put(primaryKeyA, someVal);
> cache.get(primaryKeyB;
> tx.prepare();
> {noformat}
> then kill A.
> Expected: tx recovered and
> {noformat}
> cache.get(primaryKeyA)!=null
> {noformat}
> Actual: tx rolled back and
> and
> {noformat}
> cache.get(primaryKeyA)==null
> {noformat}
> Reason: Node C has only 1 active transaction (because reads not propagated to
> backup), but expect to have 2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-13873) Milti-cell transaction changes may be not visible (during some time) after the Cellular switch
[
https://issues.apache.org/jira/browse/IGNITE-13873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov (Obsolete, actual is "av") reassigned IGNITE-13873:
Assignee: Anton Vinogradov (was: Anton Vinogradov (Obsolete, actual is
"av"))
> Milti-cell transaction changes may be not visible (during some time) after
> the Cellular switch
> --
>
> Key: IGNITE-13873
> URL: https://issues.apache.org/jira/browse/IGNITE-13873
> Project: Ignite
> Issue Type: Improvement
>Reporter: Anton Vinogradov (Obsolete, actual is "av")
>Assignee: Anton Vinogradov
>Priority: Critical
> Labels: iep-45
> Fix For: 2.10, 2.9.2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Transactions over some cells may be recovered after the stale data read.
> For example:
> We have 2 cells, the first contains partitions for k1, second for k2.
> Tx with put(k1,v1) and put(k2,v2) started and prepared.
> Then node from the first cell, which is the primary for k1, failed.
> Currently, the second cell (with key2) may finish the cellular switch before
> tx recovered and stale data read is possible.
> Primaries from the {{tx.transactionNodes()}} should be taken into account
> instead of the current logic that awaits for all transactions located on
> nodes who are backups to the failed primary.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13428) Ignite Distributed Environment Tests [Umbrella]
[ https://issues.apache.org/jira/browse/IGNITE-13428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13428: -- Summary: Ignite Distributed Environment Tests [Umbrella] (was: Ignite Distributed Environment Tests) > Ignite Distributed Environment Tests [Umbrella] > --- > > Key: IGNITE-13428 > URL: https://issues.apache.org/jira/browse/IGNITE-13428 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Priority: Major > Labels: IEP-56, ducktape > > Currently Ignite doesn’t have a solution for automated testing in real-world > distributed environment. > This ticket aims to provide such solution. The proposed test framework is > based on [ducktape|https://github.com/confluentinc/ducktape]. Requirements to > integration tests includes: easy start of fair distributed environment > locally, run compatibility tests, provide comparison benchmarks between > different Ignite versions, integration tests with 3rd party services, > parametrize tests and provide clear reports. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13448) Ducktests selftest: time is synchronized on nodes
[ https://issues.apache.org/jira/browse/IGNITE-13448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256436#comment-17256436 ] Anton Vinogradov commented on IGNITE-13448: --- [~andrey-kuznetsov], do you have plans to continue this task? > Ducktests selftest: time is synchronized on nodes > - > > Key: IGNITE-13448 > URL: https://issues.apache.org/jira/browse/IGNITE-13448 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Priority: Major > Labels: IEP-56, ducktape > Time Spent: 1h 50m > Remaining Estimate: 0h > > Selftests are tests that check ducktests environment is correct and test are > reliable, and we can rely on their timings and results. > It's required to add test that check that time on all nodes is synchronized > (the same). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13448) Ducktests selftest: time is synchronized on nodes
[ https://issues.apache.org/jira/browse/IGNITE-13448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov reassigned IGNITE-13448: - Assignee: (was: Andrey Kuznetsov) > Ducktests selftest: time is synchronized on nodes > - > > Key: IGNITE-13448 > URL: https://issues.apache.org/jira/browse/IGNITE-13448 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Priority: Major > Labels: IEP-56, ducktape > Time Spent: 1h 50m > Remaining Estimate: 0h > > Selftests are tests that check ducktests environment is correct and test are > reliable, and we can rely on their timings and results. > It's required to add test that check that time on all nodes is synchronized > (the same). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-9109) CPP Thin: Implement SQL API
[ https://issues.apache.org/jira/browse/IGNITE-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256391#comment-17256391 ] Pavel Tupitsyn commented on IGNITE-9109: [~isapego] looks good to me in general; please see a few comments on GitHub. > CPP Thin: Implement SQL API > --- > > Key: IGNITE-9109 > URL: https://issues.apache.org/jira/browse/IGNITE-9109 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 2.6 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Need to implement SQL API for C++ thin client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13845) Add checkpoint metrics
[ https://issues.apache.org/jira/browse/IGNITE-13845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256375#comment-17256375 ] Nikolay Izhikov commented on IGNITE-13845: -- Hello, [~NSAmelchev]. Please, don't forget to document those new metrics. > Add checkpoint metrics > -- > > Key: IGNITE-13845 > URL: https://issues.apache.org/jira/browse/IGNITE-13845 > Project: Ignite > Issue Type: New Feature >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.10 > > Time Spent: 40m > Remaining Estimate: 0h > > Add last checkpoint duration metrics: > * beforeLockDuration > * listenersExecuteDuration > * lockHoldDuration > * walCpRecordFsyncDuration > * writeCheckpointEntryDuration > * splitAndSortCpPagesDuration > Add durations histograms: > * CheckpointBeforeLockHistogram > * CheckpointLockWaitHistogram > * CheckpointListenersExecuteHistogram > * CheckpointMarkHistogram > * CheckpointLockHoldHistogram > * CheckpointPagesWriteHistogram > * CheckpointFsyncHistogram > * CheckpointWalRecordFsyncHistogram > * CheckpointWriteEntryHistogram > * CheckpointSplitAndSortPagesHistogram > * CheckpointHistogram -- This message was sent by Atlassian Jira (v8.3.4#803005)
