[jira] [Resolved] (IGNITE-14209) Data rebalancing
[ https://issues.apache.org/jira/browse/IGNITE-14209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14209. -- Resolution: Fixed > Data rebalancing > > > Key: IGNITE-14209 > URL: https://issues.apache.org/jira/browse/IGNITE-14209 > Project: Ignite > Issue Type: Epic >Reporter: Vyacheslav Koptilin >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > *Overview* > The lifecycle of the Ignite cluster assumes that new nodes can join this > cluster and the old ones can leave it. In order for the data to remain > distributed equally in the cluster, some replicas have to be moved from one > Ignite node to another. This process is called data rebalancing. > The main goal of this umbrella ticket is an approach that can be implemented > based on Ignite Raft module. > > The first implementation phase has the following constraints in order to > simplify the rebalance process until the table group concept is not defined: > - only "empty" nodes can join the cluster (in other words, node restart with > already exists data is not supported) > - rebalance can be triggered by NODE_JOIN/NODE_FAIL events only in an > automatic way (alternative option is to introduce IgniteCluster interface > which allows triggering rebalance in a manual way) > - reconfiguration of meta-storage nodes is not supported > Phase 1 includes the following sub-tasks: > * IGNITE-15125 > * IGNITE-15491 > * IGNITE-15490 > * IGNITE-15288 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16971) CLI MVP
[ https://issues.apache.org/jira/browse/IGNITE-16971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550625#comment-17550625 ] Andrey N. Gura commented on IGNITE-16971: - [~Mikhail Pochatkin] [~aleksandr.pakhomov] [~kgusakov] Thanks! Merged to the main branch. > CLI MVP > --- > > Key: IGNITE-16971 > URL: https://issues.apache.org/jira/browse/IGNITE-16971 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Fix For: 3.0.0-alpha5 > > Time Spent: 10m > Remaining Estimate: 0h > > The main value of this ticket is to develop the CLI Tool that can be used by > a user. Features that should be included in the MVP: > * bash autocompletion > * static commands autocomplete in REPL mode (not for sql) > * keyword autocomplete in sql > non-REPL commands: > help, init, config show, config update, sql, version, status. > REPL commands: > connect, disconnect, status, help, init, config show, config update, sql, > version. > New CLI should replace the existing one but not break the UIX. Only the > "module" subset of commands is allowed to drop. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17063) .NET: Failed to load libjvm.so in some environments
[ https://issues.apache.org/jira/browse/IGNITE-17063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550618#comment-17550618 ] Igor Sapego commented on IGNITE-17063: -- [~ptupitsyn] looks good to me. > .NET: Failed to load libjvm.so in some environments > --- > > Key: IGNITE-17063 > URL: https://issues.apache.org/jira/browse/IGNITE-17063 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.11 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Trivial > Labels: .NET > Fix For: 2.14 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We rely on "readlink -f /usr/bin/java" to locate the JVM on Linux. > However, in some cases "readlink" is not in PATH and this fails. > # Try full path "/usr/bin/readlink" as well as short path > # Capture stderr when running commands -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] (IGNITE-17063) .NET: Failed to load libjvm.so in some environments
[ https://issues.apache.org/jira/browse/IGNITE-17063 ]
Pavel Tupitsyn deleted comment on IGNITE-17063:
-
was (Author: ignitetcbot):
{panel:title=Branch: [pull/10069/head] Base: [master] : Possible Blockers
(13)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Continuous Query 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6611893]]
* IgniteCacheQuerySelfTestSuite4:
CacheContinuousQueryAsyncFailoverMvccTxSelfTest.testMultiThreaded - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}SPI (Discovery){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6611955]]
* IgniteSpiDiscoverySelfTestSuite: TcpDiscoverySpiMBeanTest.testMBean - Test
has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}JDBC Driver{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6611904]]
{color:#d04437}Platform .NET (Windows){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6611860]]
* exe:
PlatformCacheTopologyChangeTest.TestContinuousTopologyChangeMaintainsCorrectPlatformCacheData(1)
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache (Failover) 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6611870]]
{color:#d04437}Examples (LGPL){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6611899]]
{color:#d04437}Platform .NET (Core Linux){color} [[tests 2 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=6612016]]
* dll: ShellTests.TestExecuteSafeLogsNonZeroExitCodeAndStderr - History for
base branch is absent.
* dll: ShellTests.TestExecuteSafeReturnsStdout - History for base branch is
absent.
{color:#d04437}PDS 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6611918]]
* IgnitePdsTestSuite4:
ResetLostPartitionTest.testReactivateGridBeforeResetLostPartitions - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Open Census{color} [[tests 2 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6611908]]
* IgniteOpenCensusSuite:
OpenCensusMetricExporterSpiTest.testDataRegionOcMetrics - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteOpenCensusSuite: OpenCensusMetricExporterSpiTest.testHistogram - Test
has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Kubernetes{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6611906]]
{panel}
{panel:title=Branch: [pull/10069/head] Base: [master] : New Tests
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=6612016]]
* {color:#013220}dll: ShellTests.TestExecuteSafeLogsException - PASSED{color}
* {color:#8b}dll: ShellTests.TestExecuteSafeLogsNonZeroExitCodeAndStderr -
FAILED{color}
* {color:#8b}dll: ShellTests.TestExecuteSafeReturnsStdout - FAILED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6611964buildTypeId=IgniteTests24Java8_RunAll]
> .NET: Failed to load libjvm.so in some environments
> ---
>
> Key: IGNITE-17063
> URL: https://issues.apache.org/jira/browse/IGNITE-17063
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.11
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Trivial
> Labels: .NET
> Fix For: 2.14
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We rely on "readlink -f /usr/bin/java" to locate the JVM on Linux.
> However, in some cases "readlink" is not in PATH and this fails.
> # Try full path "/usr/bin/readlink" as well as short path
> # Capture stderr when running commands
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17103) SpeedBasedThrottleIntegrationTest is flaky
[
https://issues.apache.org/jira/browse/IGNITE-17103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550607#comment-17550607
]
Ignite TC Bot commented on IGNITE-17103:
{panel:title=Branch: [pull/10068/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10068/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6612709buildTypeId=IgniteTests24Java8_RunAll]
> SpeedBasedThrottleIntegrationTest is flaky
> --
>
> Key: IGNITE-17103
> URL: https://issues.apache.org/jira/browse/IGNITE-17103
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Roman Puchkovskiy
>Assignee: Roman Puchkovskiy
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://ci.ignite.apache.org/viewLog.html?buildId=6609662=buildResultsDiv=IgniteTests24Java8_Pds5#testNameId-6804725593242438487
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17117) Analyze Table SQL Statement not working with Ignite 2.13.0
Sachin Janani created IGNITE-17117:
--
Summary: Analyze Table SQL Statement not working with Ignite 2.13.0
Key: IGNITE-17117
URL: https://issues.apache.org/jira/browse/IGNITE-17117
Project: Ignite
Issue Type: Bug
Affects Versions: 2.13
Reporter: Sachin Janani
Fix For: 2.14
Running ANALYZE table SQL statement is failing with following exception:
{code:java}
0: jdbc:ignite:thin://127.0.0.1/> ANALYZE PRODUCT_TABLE; Error: Failed to parse
query. Syntax error in SQL statement "ANALYZE PRODUCT_TABLE[*]"; SQL statement:
ANALYZE PRODUCT_TABLE [42000-197] (state=42000,code=1001)
java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
"ANALYZE PRODUCT_TABLE[*]"; SQL statement: ANALYZE PRODUCT_TABLE [42000-197] at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
at sqlline.Commands.executeSingleQuery(Commands.java:1054) at
sqlline.Commands.execute(Commands.java:1003) at
sqlline.Commands.sql(Commands.java:967) at
sqlline.SqlLine.dispatch(SqlLine.java:734) at
sqlline.SqlLine.begin(SqlLine.java:541) at
sqlline.SqlLine.start(SqlLine.java:267) at
sqlline.SqlLine.main(SqlLine.java:206) 0: jdbc:ignite:thin://127.0.0.1/> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (IGNITE-17113) Document distributed computing in AI alpha 5
[ https://issues.apache.org/jira/browse/IGNITE-17113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-17113: --- Assignee: Igor Gusev > Document distributed computing in AI alpha 5 > > > Key: IGNITE-17113 > URL: https://issues.apache.org/jira/browse/IGNITE-17113 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16971) CLI MVP
[ https://issues.apache.org/jira/browse/IGNITE-16971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550558#comment-17550558 ] Kirill Gusakov commented on IGNITE-16971: - LGTM, thanks for contribution > CLI MVP > --- > > Key: IGNITE-16971 > URL: https://issues.apache.org/jira/browse/IGNITE-16971 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Fix For: 3.0.0-alpha5 > > Time Spent: 10m > Remaining Estimate: 0h > > The main value of this ticket is to develop the CLI Tool that can be used by > a user. Features that should be included in the MVP: > * bash autocompletion > * static commands autocomplete in REPL mode (not for sql) > * keyword autocomplete in sql > non-REPL commands: > help, init, config show, config update, sql, version, status. > REPL commands: > connect, disconnect, status, help, init, config show, config update, sql, > version. > New CLI should replace the existing one but not break the UIX. Only the > "module" subset of commands is allowed to drop. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17107) [Native Persistence 3.0] End-to-end test for persistent PageMemory
[ https://issues.apache.org/jira/browse/IGNITE-17107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550552#comment-17550552 ] Andrey N. Gura commented on IGNITE-17107: - [~ktkale...@gridgain.com] [~apolovtcev] Thanks! Merged to the main branch. > [Native Persistence 3.0] End-to-end test for persistent PageMemory > -- > > Key: IGNITE-17107 > URL: https://issues.apache.org/jira/browse/IGNITE-17107 > Project: Ignite > Issue Type: Task >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Persistent PageMemory storage was ported and fully integrated into ignite-3, > though only unit tests were written covering this piece of functionality. > We need to write an end-to-end integration test for PageMemory-based > persistent storage. The test should include: > * New storage creation with necessary configuration; > * Simple store/retrieve operations showing that storage actually performs > its tasks. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17073) Document new CLI commands
[ https://issues.apache.org/jira/browse/IGNITE-17073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550538#comment-17550538 ] Aleksandr commented on IGNITE-17073: LGTM, thank you, Igor. > Document new CLI commands > -- > > Key: IGNITE-17073 > URL: https://issues.apache.org/jira/browse/IGNITE-17073 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksandr >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Time Spent: 20m > Remaining Estimate: 0h > > Document commands that are introdused in > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-88%3A+CLI+Tool] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17116) Add architecture documentation for CLI module.
Aleksandr created IGNITE-17116: -- Summary: Add architecture documentation for CLI module. Key: IGNITE-17116 URL: https://issues.apache.org/jira/browse/IGNITE-17116 Project: Ignite Issue Type: Task Reporter: Aleksandr A developer should read the documentation and: * how to create an executable command * how to test an executable command (unit and integration) * how to create an interactive command * how to test an interactive command Also, the ExecutionPepiline concept and the extention mechanismshould be described. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17088) SQL API: Add examples.
[ https://issues.apache.org/jira/browse/IGNITE-17088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-17088: -- Summary: SQL API: Add examples. (was: SQL API: Examples.) > SQL API: Add examples. > -- > > Key: IGNITE-17088 > URL: https://issues.apache.org/jira/browse/IGNITE-17088 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > Add examples of using SQL API. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17115) Add use of IGNITE_GET_METADATA_LOCALLY_ONLY from within SchemaManager
Alexander Lapin created IGNITE-17115: Summary: Add use of IGNITE_GET_METADATA_LOCALLY_ONLY from within SchemaManager Key: IGNITE-17115 URL: https://issues.apache.org/jira/browse/IGNITE-17115 Project: Ignite Issue Type: Task Reporter: Alexander Lapin Assignee: Alexander Lapin -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-14209) Data rebalancing
[ https://issues.apache.org/jira/browse/IGNITE-14209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Gusakov updated IGNITE-14209: Ignite Flags: (was: Docs Required,Release Notes Required) > Data rebalancing > > > Key: IGNITE-14209 > URL: https://issues.apache.org/jira/browse/IGNITE-14209 > Project: Ignite > Issue Type: Epic >Reporter: Vyacheslav Koptilin >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > *Overview* > The lifecycle of the Ignite cluster assumes that new nodes can join this > cluster and the old ones can leave it. In order for the data to remain > distributed equally in the cluster, some replicas have to be moved from one > Ignite node to another. This process is called data rebalancing. > The main goal of this umbrella ticket is an approach that can be implemented > based on Ignite Raft module. > > The first implementation phase has the following constraints in order to > simplify the rebalance process until the table group concept is not defined: > - only "empty" nodes can join the cluster (in other words, node restart with > already exists data is not supported) > - rebalance can be triggered by NODE_JOIN/NODE_FAIL events only in an > automatic way (alternative option is to introduce IgniteCluster interface > which allows triggering rebalance in a manual way) > - reconfiguration of meta-storage nodes is not supported > Phase 1 includes the following sub-tasks: > * IGNITE-15125 > * IGNITE-15491 > * IGNITE-15490 > * IGNITE-15288 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17107) [Native Persistence 3.0] End-to-end test for persistent PageMemory
[ https://issues.apache.org/jira/browse/IGNITE-17107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550515#comment-17550515 ] Aleksandr Polovtcev commented on IGNITE-17107: -- Thank you, looks great! > [Native Persistence 3.0] End-to-end test for persistent PageMemory > -- > > Key: IGNITE-17107 > URL: https://issues.apache.org/jira/browse/IGNITE-17107 > Project: Ignite > Issue Type: Task >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Persistent PageMemory storage was ported and fully integrated into ignite-3, > though only unit tests were written covering this piece of functionality. > We need to write an end-to-end integration test for PageMemory-based > persistent storage. The test should include: > * New storage creation with necessary configuration; > * Simple store/retrieve operations showing that storage actually performs > its tasks. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16973) Add advanced completions to SQL REPL
[
https://issues.apache.org/jira/browse/IGNITE-16973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-16973:
---
Description:
In order to improve the developer experience in SQL REPL mode dynamic
autocompletion can be added. For example, a user types {{select * from ta}} and
gets the suggestion with the list of tables that are fetched from the JDBC.
Also, the current list of SQL keywords for autocomplete is taken from the
default Calcite parser. Use an actual list of Ignite SQL keywords for
auto-complete.
was:In order to improve the developer experience in SQL REPL mode dynamic
autocompletion can be added. For example, a user types {{select * from ta}} and
gets the suggestion with the list of tables that are fetched from the JDBC.
> Add advanced completions to SQL REPL
>
>
> Key: IGNITE-16973
> URL: https://issues.apache.org/jira/browse/IGNITE-16973
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> In order to improve the developer experience in SQL REPL mode dynamic
> autocompletion can be added. For example, a user types {{select * from ta}}
> and gets the suggestion with the list of tables that are fetched from the
> JDBC.
> Also, the current list of SQL keywords for autocomplete is taken from the
> default Calcite parser. Use an actual list of Ignite SQL keywords for
> auto-complete.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17097) Updated micronaut version does not work with shadow plugin
[
https://issues.apache.org/jira/browse/IGNITE-17097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-17097:
---
Fix Version/s: 3.0.0-alpha5
> Updated micronaut version does not work with shadow plugin
> --
>
> Key: IGNITE-17097
> URL: https://issues.apache.org/jira/browse/IGNITE-17097
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr
>Assignee: Aleksandr
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> IGNITE-16943 bumped a version of micronaut in cli to 3.4.1 and it seems the
> regression in the executable file took place. There is a workaround described
> here [https://github.com/micronaut-projects/micronaut-core/issues/7144.]
>
> {code:java}
> ./ignite init
> Picked up _JAVA_OPTIONS: -Djava.net.preferIPv4Stack=true
> Exception in thread "main"
> io.micronaut.context.exceptions.NoSuchBeanException: No bean of type
> [io.micronaut.context.event.ApplicationEventPublisher]
> exists {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17114) Idle_verify must print and compare full partition counter state instead of just LWM
[ https://issues.apache.org/jira/browse/IGNITE-17114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luchnikov Alexander updated IGNITE-17114: - Labels: ise (was: ) > Idle_verify must print and compare full partition counter state instead of > just LWM > --- > > Key: IGNITE-17114 > URL: https://issues.apache.org/jira/browse/IGNITE-17114 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Labels: ise > Fix For: 2.14 > > > Gaps also should be printed/compared. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16971) CLI MVP
[ https://issues.apache.org/jira/browse/IGNITE-16971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550489#comment-17550489 ] Kirill Gusakov commented on IGNITE-16971: - Made some comments in PR, pls check it > CLI MVP > --- > > Key: IGNITE-16971 > URL: https://issues.apache.org/jira/browse/IGNITE-16971 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Fix For: 3.0.0-alpha5 > > Time Spent: 10m > Remaining Estimate: 0h > > The main value of this ticket is to develop the CLI Tool that can be used by > a user. Features that should be included in the MVP: > * bash autocompletion > * static commands autocomplete in REPL mode (not for sql) > * keyword autocomplete in sql > non-REPL commands: > help, init, config show, config update, sql, version, status. > REPL commands: > connect, disconnect, status, help, init, config show, config update, sql, > version. > New CLI should replace the existing one but not break the UIX. Only the > "module" subset of commands is allowed to drop. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17114) Idle_verify must print and compare full partition counter state instead of just LWM
Anton Vinogradov created IGNITE-17114: - Summary: Idle_verify must print and compare full partition counter state instead of just LWM Key: IGNITE-17114 URL: https://issues.apache.org/jira/browse/IGNITE-17114 Project: Ignite Issue Type: Sub-task Reporter: Anton Vinogradov Assignee: Anton Vinogradov Gaps also should be printed/compared. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17114) Idle_verify must print and compare full partition counter state instead of just LWM
[ https://issues.apache.org/jira/browse/IGNITE-17114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-17114: -- Fix Version/s: 2.14 > Idle_verify must print and compare full partition counter state instead of > just LWM > --- > > Key: IGNITE-17114 > URL: https://issues.apache.org/jira/browse/IGNITE-17114 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.14 > > > Gaps also should be printed/compared. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16971) CLI MVP
[ https://issues.apache.org/jira/browse/IGNITE-16971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-16971: --- Fix Version/s: 3.0.0-alpha5 > CLI MVP > --- > > Key: IGNITE-16971 > URL: https://issues.apache.org/jira/browse/IGNITE-16971 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Fix For: 3.0.0-alpha5 > > Time Spent: 10m > Remaining Estimate: 0h > > The main value of this ticket is to develop the CLI Tool that can be used by > a user. Features that should be included in the MVP: > * bash autocompletion > * static commands autocomplete in REPL mode (not for sql) > * keyword autocomplete in sql > non-REPL commands: > help, init, config show, config update, sql, version, status. > REPL commands: > connect, disconnect, status, help, init, config show, config update, sql, > version. > New CLI should replace the existing one but not break the UIX. Only the > "module" subset of commands is allowed to drop. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17112) Consistency check must fix counter after the consistency fix
[
https://issues.apache.org/jira/browse/IGNITE-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-17112:
--
Description:
Consistency repair repairs the consistency for the data committed on at least
single node.
But partition counter may have gaps for prepared, but not committed data, and
such gaps will cause exception on cluster activation:
{noformat}
2022-06-03 22:01:59.695
[ERROR][sys-#322][org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager]
Failed to update partition counter. Most probably a node with most actual data
is out of topology or data streamer is used in preload mode
(allowOverride=false) concurrently with cache transactions [grpName=XXX,
partId=9099]
org.apache.ignite.IgniteCheckedException: Failed to update the counter
[newVal=4854911, curState=Counter [lwm=4854911, holes={4854912=Item
[start=4854912, delta=1]}, maxApplied=4854913, hwm=4854911]]
at
org.apache.ignite.internal.processors.cache.PartitionUpdateCounterTrackingImpl.update(PartitionUpdateCounterTrackingImpl.java:153)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.processors.cache.PartitionUpdateCounterErrorWrapper.update(PartitionUpdateCounterErrorWrapper.java:97)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.updateCounter(IgniteCacheOffheapManagerImpl.java:1687)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.updateCounter(GridCacheOffheapManager.java:2530)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition.updateCounter(GridDhtLocalPartition.java:913)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.update(GridDhtPartitionTopologyImpl.java:1491)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.lambda$updatePartitionFullMap$81bdb8e8$1(GridDhtPartitionsExchangeFuture.java:4817)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.util.IgniteUtils.lambda$null$1(IgniteUtils.java:11358)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[?:1.8.0_322]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[?:1.8.0_322]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[?:1.8.0_322]
at java.lang.Thread.run(Thread.java:750)
{noformat}
Consistency check via cli must close this gaps on successful consistency repair.
was:
Consistency fix still fixes consistency for the data committed on at least
single node.
But partition counter may have gaps for prepared, but not committed data, and
such gaps will cause exception on cluster activation:
{noformat}
2022-06-03 22:01:59.695
[ERROR][sys-#322][org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager]
Failed to update partition counter. Most probably a node with most actual data
is out of topology or data streamer is used in preload mode
(allowOverride=false) concurrently with cache transactions [grpName=XXX,
partId=9099]
org.apache.ignite.IgniteCheckedException: Failed to update the counter
[newVal=4854911, curState=Counter [lwm=4854911, holes={4854912=Item
[start=4854912, delta=1]}, maxApplied=4854913, hwm=4854911]]
at
org.apache.ignite.internal.processors.cache.PartitionUpdateCounterTrackingImpl.update(PartitionUpdateCounterTrackingImpl.java:153)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.processors.cache.PartitionUpdateCounterErrorWrapper.update(PartitionUpdateCounterErrorWrapper.java:97)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.updateCounter(IgniteCacheOffheapManagerImpl.java:1687)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.updateCounter(GridCacheOffheapManager.java:2530)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition.updateCounter(GridDhtLocalPartition.java:913)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
[jira] [Created] (IGNITE-17112) Consistency check must fix counter after the consistency fix
Anton Vinogradov created IGNITE-17112:
-
Summary: Consistency check must fix counter after the consistency
fix
Key: IGNITE-17112
URL: https://issues.apache.org/jira/browse/IGNITE-17112
Project: Ignite
Issue Type: Sub-task
Reporter: Anton Vinogradov
Assignee: Anton Vinogradov
Consistency fix still fixes consistency for the data committed on at least
single node.
But partition counter may have gaps for prepared, but not committed data, and
such gaps will cause exception on cluster activation:
{noformat}
2022-06-03 22:01:59.695
[ERROR][sys-#322][org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager]
Failed to update partition counter. Most probably a node with most actual data
is out of topology or data streamer is used in preload mode
(allowOverride=false) concurrently with cache transactions [grpName=XXX,
partId=9099]
org.apache.ignite.IgniteCheckedException: Failed to update the counter
[newVal=4854911, curState=Counter [lwm=4854911, holes={4854912=Item
[start=4854912, delta=1]}, maxApplied=4854913, hwm=4854911]]
at
org.apache.ignite.internal.processors.cache.PartitionUpdateCounterTrackingImpl.update(PartitionUpdateCounterTrackingImpl.java:153)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.processors.cache.PartitionUpdateCounterErrorWrapper.update(PartitionUpdateCounterErrorWrapper.java:97)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.updateCounter(IgniteCacheOffheapManagerImpl.java:1687)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.updateCounter(GridCacheOffheapManager.java:2530)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition.updateCounter(GridDhtLocalPartition.java:913)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.update(GridDhtPartitionTopologyImpl.java:1491)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.lambda$updatePartitionFullMap$81bdb8e8$1(GridDhtPartitionsExchangeFuture.java:4817)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at
org.apache.ignite.internal.util.IgniteUtils.lambda$null$1(IgniteUtils.java:11358)
~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[?:1.8.0_322]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[?:1.8.0_322]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[?:1.8.0_322]
at java.lang.Thread.run(Thread.java:750)
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17113) Document distributed computing in AI alpha 5
Igor Gusev created IGNITE-17113: --- Summary: Document distributed computing in AI alpha 5 Key: IGNITE-17113 URL: https://issues.apache.org/jira/browse/IGNITE-17113 Project: Ignite Issue Type: Task Components: documentation Reporter: Igor Gusev -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17112) Consistency check must fix counter after the consistency fix
[
https://issues.apache.org/jira/browse/IGNITE-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-17112:
--
Fix Version/s: 2.14
> Consistency check must fix counter after the consistency fix
>
>
> Key: IGNITE-17112
> URL: https://issues.apache.org/jira/browse/IGNITE-17112
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.14
>
>
> Consistency fix still fixes consistency for the data committed on at least
> single node.
> But partition counter may have gaps for prepared, but not committed data, and
> such gaps will cause exception on cluster activation:
> {noformat}
> 2022-06-03 22:01:59.695
> [ERROR][sys-#322][org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager]
> Failed to update partition counter. Most probably a node with most actual
> data is out of topology or data streamer is used in preload mode
> (allowOverride=false) concurrently with cache transactions [grpName=XXX,
> partId=9099]
> org.apache.ignite.IgniteCheckedException: Failed to update the counter
> [newVal=4854911, curState=Counter [lwm=4854911, holes={4854912=Item
> [start=4854912, delta=1]}, maxApplied=4854913, hwm=4854911]]
> at
> org.apache.ignite.internal.processors.cache.PartitionUpdateCounterTrackingImpl.update(PartitionUpdateCounterTrackingImpl.java:153)
> ~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
> at
> org.apache.ignite.internal.processors.cache.PartitionUpdateCounterErrorWrapper.update(PartitionUpdateCounterErrorWrapper.java:97)
> ~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.updateCounter(IgniteCacheOffheapManagerImpl.java:1687)
> ~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.updateCounter(GridCacheOffheapManager.java:2530)
> ~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition.updateCounter(GridDhtLocalPartition.java:913)
> ~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.update(GridDhtPartitionTopologyImpl.java:1491)
> ~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.lambda$updatePartitionFullMap$81bdb8e8$1(GridDhtPartitionsExchangeFuture.java:4817)
> ~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
> at
> org.apache.ignite.internal.util.IgniteUtils.lambda$null$1(IgniteUtils.java:11358)
> ~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [?:1.8.0_322]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [?:1.8.0_322]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [?:1.8.0_322]
> at java.lang.Thread.run(Thread.java:750)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Closed] (IGNITE-17028) Docker image not available for apache ignite(v2.13.0) on s390x architecture.
[ https://issues.apache.org/jira/browse/IGNITE-17028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Ivanov closed IGNITE-17028. > Docker image not available for apache ignite(v2.13.0) on s390x architecture. > > > Key: IGNITE-17028 > URL: https://issues.apache.org/jira/browse/IGNITE-17028 > Project: Ignite > Issue Type: Bug >Reporter: Rishi >Assignee: Petr Ivanov >Priority: Major > > Hi there, > I noticed that 2.13.0 version of Docker image for s390x architecture is not > available on Dockerhub. > Please let me know if there is something I can do at my end to help publish > the images. > We had this issue opened earlier to address similar issue for 2.12.0: > https://issues.apache.org/jira/browse/IGNITE-16481 > FYI: @[~vveider] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-17028) Docker image not available for apache ignite(v2.13.0) on s390x architecture.
[ https://issues.apache.org/jira/browse/IGNITE-17028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Ivanov resolved IGNITE-17028. -- Fix Version/s: (was: 2.14) Assignee: Petr Ivanov Resolution: Done > Docker image not available for apache ignite(v2.13.0) on s390x architecture. > > > Key: IGNITE-17028 > URL: https://issues.apache.org/jira/browse/IGNITE-17028 > Project: Ignite > Issue Type: Bug >Reporter: Rishi >Assignee: Petr Ivanov >Priority: Major > > Hi there, > I noticed that 2.13.0 version of Docker image for s390x architecture is not > available on Dockerhub. > Please let me know if there is something I can do at my end to help publish > the images. > We had this issue opened earlier to address similar issue for 2.12.0: > https://issues.apache.org/jira/browse/IGNITE-16481 > FYI: @[~vveider] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (IGNITE-17028) Docker image not available for apache ignite(v2.13.0) on s390x architecture.
[
https://issues.apache.org/jira/browse/IGNITE-17028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550477#comment-17550477
]
Petr Ivanov edited comment on IGNITE-17028 at 6/6/22 1:42 PM:
--
Uploaded as {{apacheignite/ignite:2.13.0-jdk11-s390x}}
Currently it is not possible to build s390x image on Linux (ERROR:
{{{}standard_init_linux.go:228: exec user process caused: exec format
error{}}}) so I've built it manually and uploaded to Docker Hub.
was (Author: vveider):
Uploaded.
Currently it is not possible to build s390x image on Linux (ERROR:
{{{}standard_init_linux.go:228: exec user process caused: exec format
error{}}}) so I've built it manually and uploaded to Docker Hub.
> Docker image not available for apache ignite(v2.13.0) on s390x architecture.
>
>
> Key: IGNITE-17028
> URL: https://issues.apache.org/jira/browse/IGNITE-17028
> Project: Ignite
> Issue Type: Bug
>Reporter: Rishi
>Assignee: Petr Ivanov
>Priority: Major
>
> Hi there,
> I noticed that 2.13.0 version of Docker image for s390x architecture is not
> available on Dockerhub.
> Please let me know if there is something I can do at my end to help publish
> the images.
> We had this issue opened earlier to address similar issue for 2.12.0:
> https://issues.apache.org/jira/browse/IGNITE-16481
> FYI: @[~vveider]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17028) Docker image not available for apache ignite(v2.13.0) on s390x architecture.
[
https://issues.apache.org/jira/browse/IGNITE-17028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550477#comment-17550477
]
Petr Ivanov commented on IGNITE-17028:
--
Uploaded.
Currently it is not possible to build s390x image on Linux (ERROR:
{{{}standard_init_linux.go:228: exec user process caused: exec format
error{}}}) so I've built it manually and uploaded to Docker Hub.
> Docker image not available for apache ignite(v2.13.0) on s390x architecture.
>
>
> Key: IGNITE-17028
> URL: https://issues.apache.org/jira/browse/IGNITE-17028
> Project: Ignite
> Issue Type: Bug
>Reporter: Rishi
>Priority: Major
> Fix For: 2.14
>
>
> Hi there,
> I noticed that 2.13.0 version of Docker image for s390x architecture is not
> available on Dockerhub.
> Please let me know if there is something I can do at my end to help publish
> the images.
> We had this issue opened earlier to address similar issue for 2.12.0:
> https://issues.apache.org/jira/browse/IGNITE-16481
> FYI: @[~vveider]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17066) [Native Persistence 3.0] Implement a listener for deleting/updating data region's configuration
[
https://issues.apache.org/jira/browse/IGNITE-17066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-17066:
-
Description:
At the moment, we can only add data regions both at the start of the
*org.apache.ignite.internal.storage.pagememory.PageMemoryStorageEngine* and in
the event of adding a data region configuration, see
{*}PageMemoryStorageEngine#start{*}.
We need to add event handling for changing and deleting the data region
configuration, for this we first need to analyze the complexity and feasibility.
was:Currently there is a listener for adding data region configuration, but
no listener for deleting/updating data region configuration.
> [Native Persistence 3.0] Implement a listener for deleting/updating data
> region's configuration
> ---
>
> Key: IGNITE-17066
> URL: https://issues.apache.org/jira/browse/IGNITE-17066
> Project: Ignite
> Issue Type: Task
>Reporter: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
>
> At the moment, we can only add data regions both at the start of the
> *org.apache.ignite.internal.storage.pagememory.PageMemoryStorageEngine* and
> in the event of adding a data region configuration, see
> {*}PageMemoryStorageEngine#start{*}.
> We need to add event handling for changing and deleting the data region
> configuration, for this we first need to analyze the complexity and
> feasibility.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17111) Remove the ability to set the lazy flag in SqlFieldsQuery
[ https://issues.apache.org/jira/browse/IGNITE-17111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luchnikov Alexander updated IGNITE-17111: - Labels: ise (was: ) > Remove the ability to set the lazy flag in SqlFieldsQuery > - > > Key: IGNITE-17111 > URL: https://issues.apache.org/jira/browse/IGNITE-17111 > Project: Ignite > Issue Type: Improvement >Reporter: Luchnikov Alexander >Priority: Minor > Labels: ise > > Remove the ability to set the lazy flag in SqlFieldsQuery. SqlFieldsQuery > must always be executed as lazy=true. > This property > (org.apache.igniteIgniteSystemProperties#IGNITE_SQL_FORCE_LAZY_RESULT_SET) > refers to the same functionality, but is not used in the code. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17111) Remove the ability to set the lazy flag in SqlFieldsQuery
Luchnikov Alexander created IGNITE-17111: Summary: Remove the ability to set the lazy flag in SqlFieldsQuery Key: IGNITE-17111 URL: https://issues.apache.org/jira/browse/IGNITE-17111 Project: Ignite Issue Type: Improvement Reporter: Luchnikov Alexander Remove the ability to set the lazy flag in SqlFieldsQuery. SqlFieldsQuery must always be executed as lazy=true. This property (org.apache.igniteIgniteSystemProperties#IGNITE_SQL_FORCE_LAZY_RESULT_SET) refers to the same functionality, but is not used in the code. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17108) Update Docker deliveries
[ https://issues.apache.org/jira/browse/IGNITE-17108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550460#comment-17550460 ] Petr Ivanov commented on IGNITE-17108: -- Images for 2.13.0: https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_AssembleDockerImages/6612852?buildTab=artifacts# > Update Docker deliveries > > > Key: IGNITE-17108 > URL: https://issues.apache.org/jira/browse/IGNITE-17108 > Project: Ignite > Issue Type: Improvement > Components: build >Affects Versions: 2.13 >Reporter: Petr Ivanov >Assignee: Petr Ivanov >Priority: Major > Fix For: 2.14 > > > # Move to eclipse-temurin docker images (successor of AdoptOpenJDK) > # Add JDK11 Dockerfile > # Add builds for x86-64/jdk8, x86-64/jdk11 and s390/jdk8 on TeamCity. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Closed] (IGNITE-14031) Add Docker images based on Java 11
[ https://issues.apache.org/jira/browse/IGNITE-14031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Ivanov closed IGNITE-14031. Ignite Flags: (was: Docs Required,Release Notes Required) > Add Docker images based on Java 11 > -- > > Key: IGNITE-14031 > URL: https://issues.apache.org/jira/browse/IGNITE-14031 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Kadaner >Assignee: Petr Ivanov >Priority: Major > > Since Java 11 support was added in > https://issues.apache.org/jira/browse/IGNITE-11189 it should be possible to > create Docker images as well. > This will allow usage of TLSv1.3 and make > _‑Djdk.tls.client.protocols=TLSv1.2_ JVM parameter unnecessary on thick > clients. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-14031) Add Docker images based on Java 11
[ https://issues.apache.org/jira/browse/IGNITE-14031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Ivanov resolved IGNITE-14031. -- Resolution: Duplicate Fixed in https://issues.apache.org/jira/browse/IGNITE-17108 > Add Docker images based on Java 11 > -- > > Key: IGNITE-14031 > URL: https://issues.apache.org/jira/browse/IGNITE-14031 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Kadaner >Assignee: Petr Ivanov >Priority: Major > > Since Java 11 support was added in > https://issues.apache.org/jira/browse/IGNITE-11189 it should be possible to > create Docker images as well. > This will allow usage of TLSv1.3 and make > _‑Djdk.tls.client.protocols=TLSv1.2_ JVM parameter unnecessary on thick > clients. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-16967) SQL API: Implement server-side query context.
[ https://issues.apache.org/jira/browse/IGNITE-16967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov reassigned IGNITE-16967: - Assignee: Konstantin Orlov > SQL API: Implement server-side query context. > - > > Key: IGNITE-16967 > URL: https://issues.apache.org/jira/browse/IGNITE-16967 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > > Implement server-side session management. > Avoid session parameters sending on each query start. > Close session on client disconnect. > Close queries when session has been closed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17103) SpeedBasedThrottleIntegrationTest is flaky
[ https://issues.apache.org/jira/browse/IGNITE-17103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550435#comment-17550435 ] Roman Puchkovskiy commented on IGNITE-17103: This test is inherently difficult for making it reliable, and it has low value, so the best thing we can do is probably just to remove it > SpeedBasedThrottleIntegrationTest is flaky > -- > > Key: IGNITE-17103 > URL: https://issues.apache.org/jira/browse/IGNITE-17103 > Project: Ignite > Issue Type: Bug > Components: persistence >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > https://ci.ignite.apache.org/viewLog.html?buildId=6609662=buildResultsDiv=IgniteTests24Java8_Pds5#testNameId-6804725593242438487 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16040) Calcite. Unable to plan query with several correlated sub-queries in select list
[
https://issues.apache.org/jira/browse/IGNITE-16040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550420#comment-17550420
]
Konstantin Orlov commented on IGNITE-16040:
---
The fix has been merged to the Calcite and should be released within 1.31. So,
let's wait until the release and check if the planner could handle the query
from description.
> Calcite. Unable to plan query with several correlated sub-queries in select
> list
>
>
> Key: IGNITE-16040
> URL: https://issues.apache.org/jira/browse/IGNITE-16040
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Konstantin Orlov
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required
>
> Currently the query like below can't be planned by calcite-based sql engine:
> {code:java}
> SELECT a+b*2,
>(a+b+c+d+e)/5,
>(SELECT count(*) FROM t1 AS x WHERE x.c>t1.c AND x.d(SELECT count(*) FROM t1 AS x WHERE x.babs(b-c),
>a-b
> FROM t1
> WHERE EXISTS(SELECT 1 FROM t1 AS x WHERE x.bAND c>d
> ORDER BY 6,5,4,1,3,2
> {code}
> Need to figure it out how to fix this.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17017) [Native Persistence 3.0] Move "pageSize" to the common configuration of PageMemory storage engine
[ https://issues.apache.org/jira/browse/IGNITE-17017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-17017: - Summary: [Native Persistence 3.0] Move "pageSize" to the common configuration of PageMemory storage engine (was: [Native Persistence 3.0] Move "pageSize" to the common configuration) > [Native Persistence 3.0] Move "pageSize" to the common configuration of > PageMemory storage engine > - > > Key: IGNITE-17017 > URL: https://issues.apache.org/jira/browse/IGNITE-17017 > Project: Ignite > Issue Type: Task >Reporter: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha6 > > > Move the *pageSize* into the common configuration for the *page-memory*, but > for this, at the beginning we need to implement a non-internal configuration > extension so that we can make a configuration for the *volatile* and the > *persistent* configuration of the *page-memory*. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16665) [Native Persistence 3.0] Move the group ID to the configuration
[
https://issues.apache.org/jira/browse/IGNITE-16665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-16665:
-
Description:
Now the group id is calculated as {*}TableView.name().hashCode(){*}, need to
move it to the config.
See org.apache.ignite.internal.storage.StorageUtils#groupId
Problem:
Currently, persistent storage engines such as *PageMemory* and *RocksDB* use
the
*org.apache.ignite.configuration.schemas.table.TableConfigurationSchema#name*
(as part or all) as the name for the directory in which the data will be
stored. This does not allow you to rename the table correctly, since the data
will have to be in the new directory so that it is not lost after restarting
the node, but it will be in the directory with the old name.
Possible solution:
Do not use the name of the table as the directory name, instead add the
*org.apache.ignite.configuration.schemas.table.TableConfigurationSchema#id*
which should never change, and must also be unique.
Please see:
* *org.apache.ignite.internal.storage.StorageUtils#groupId*
*
*org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage#start*
* *org.apache.ignite.internal.storage.rocksdb.RocksDbStorageEngine#createTable*
was:
Now the group id is calculated as *TableView.name().hashCode()*, need to move
it to the config.
See org.apache.ignite.internal.storage.StorageUtils#groupId
> [Native Persistence 3.0] Move the group ID to the configuration
> ---
>
> Key: IGNITE-16665
> URL: https://issues.apache.org/jira/browse/IGNITE-16665
> Project: Ignite
> Issue Type: Task
>Reporter: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha6
>
>
> Now the group id is calculated as {*}TableView.name().hashCode(){*}, need to
> move it to the config.
> See org.apache.ignite.internal.storage.StorageUtils#groupId
> Problem:
> Currently, persistent storage engines such as *PageMemory* and *RocksDB* use
> the
> *org.apache.ignite.configuration.schemas.table.TableConfigurationSchema#name*
> (as part or all) as the name for the directory in which the data will be
> stored. This does not allow you to rename the table correctly, since the data
> will have to be in the new directory so that it is not lost after restarting
> the node, but it will be in the directory with the old name.
> Possible solution:
> Do not use the name of the table as the directory name, instead add the
> *org.apache.ignite.configuration.schemas.table.TableConfigurationSchema#id*
> which should never change, and must also be unique.
> Please see:
> * *org.apache.ignite.internal.storage.StorageUtils#groupId*
> *
> *org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage#start*
> *
> *org.apache.ignite.internal.storage.rocksdb.RocksDbStorageEngine#createTable*
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-16665) [Native Persistence 3.0] Move the group ID to the configuration
[
https://issues.apache.org/jira/browse/IGNITE-16665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-16665:
-
Description:
Problem:
Currently, persistent storage engines such as *PageMemory* and *RocksDB* use
the
*org.apache.ignite.configuration.schemas.table.TableConfigurationSchema#name*
(as part or all) as the name for the directory in which the data will be
stored. This does not allow you to rename the table correctly, since the data
will have to be in the new directory so that it is not lost after restarting
the node, but it will be in the directory with the old name.
Possible solution:
Do not use the name of the table as the directory name, instead add the
*org.apache.ignite.configuration.schemas.table.TableConfigurationSchema#id*
which should never change, and must also be unique.
Please see:
* *org.apache.ignite.internal.storage.StorageUtils#groupId*
*
*org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage#start*
* *org.apache.ignite.internal.storage.rocksdb.RocksDbStorageEngine#createTable*
was:
Now the group id is calculated as {*}TableView.name().hashCode(){*}, need to
move it to the config.
See org.apache.ignite.internal.storage.StorageUtils#groupId
Problem:
Currently, persistent storage engines such as *PageMemory* and *RocksDB* use
the
*org.apache.ignite.configuration.schemas.table.TableConfigurationSchema#name*
(as part or all) as the name for the directory in which the data will be
stored. This does not allow you to rename the table correctly, since the data
will have to be in the new directory so that it is not lost after restarting
the node, but it will be in the directory with the old name.
Possible solution:
Do not use the name of the table as the directory name, instead add the
*org.apache.ignite.configuration.schemas.table.TableConfigurationSchema#id*
which should never change, and must also be unique.
Please see:
* *org.apache.ignite.internal.storage.StorageUtils#groupId*
*
*org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage#start*
* *org.apache.ignite.internal.storage.rocksdb.RocksDbStorageEngine#createTable*
> [Native Persistence 3.0] Move the group ID to the configuration
> ---
>
> Key: IGNITE-16665
> URL: https://issues.apache.org/jira/browse/IGNITE-16665
> Project: Ignite
> Issue Type: Task
>Reporter: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha6
>
>
> Problem:
> Currently, persistent storage engines such as *PageMemory* and *RocksDB* use
> the
> *org.apache.ignite.configuration.schemas.table.TableConfigurationSchema#name*
> (as part or all) as the name for the directory in which the data will be
> stored. This does not allow you to rename the table correctly, since the data
> will have to be in the new directory so that it is not lost after restarting
> the node, but it will be in the directory with the old name.
> Possible solution:
> Do not use the name of the table as the directory name, instead add the
> *org.apache.ignite.configuration.schemas.table.TableConfigurationSchema#id*
> which should never change, and must also be unique.
> Please see:
> * *org.apache.ignite.internal.storage.StorageUtils#groupId*
> *
> *org.apache.ignite.internal.storage.pagememory.PersistentPageMemoryTableStorage#start*
> *
> *org.apache.ignite.internal.storage.rocksdb.RocksDbStorageEngine#createTable*
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (IGNITE-8618) Support Java 10
[ https://issues.apache.org/jira/browse/IGNITE-8618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Darlington resolved IGNITE-8618. Resolution: Won't Fix Support for Java 17 was added in 2.13. Java 10 is old and not an LTS version. > Support Java 10 > --- > > Key: IGNITE-8618 > URL: https://issues.apache.org/jira/browse/IGNITE-8618 > Project: Ignite > Issue Type: Task >Affects Versions: 2.4 >Reporter: Anghel Botos >Priority: Major > > Please make required changes so that Ignite runs on Java 10. > The blocking issue I encontered is related to the usage of Unsafe: > Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class > is unavailable. > at > org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1459) > at org.apache.ignite.internal.util.GridUnsafe.(GridUnsafe.java:118) > ... 30 more > Caused by: java.lang.IllegalAccessException: class > org.apache.ignite.internal.util.GridUnsafe cannot access class > jdk.internal.misc.SharedSecrets (in module java.base) because module > java.base does not export jdk.internal.misc to unnamed module @754ba872 > at > java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:360) > at > java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:589) > at java.base/java.lang.reflect.Method.invoke(Method.java:556) > at > org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1456) > ... 31 more > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-16971) CLI MVP
[ https://issues.apache.org/jira/browse/IGNITE-16971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-16971: -- Assignee: Mikhail Pochatkin > CLI MVP > --- > > Key: IGNITE-16971 > URL: https://issues.apache.org/jira/browse/IGNITE-16971 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > The main value of this ticket is to develop the CLI Tool that can be used by > a user. Features that should be included in the MVP: > * bash autocompletion > * static commands autocomplete in REPL mode (not for sql) > * keyword autocomplete in sql > non-REPL commands: > help, init, config show, config update, sql, version, status. > REPL commands: > connect, disconnect, status, help, init, config show, config update, sql, > version. > New CLI should replace the existing one but not break the UIX. Only the > "module" subset of commands is allowed to drop. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17093) Map error codes for cli commands
[ https://issues.apache.org/jira/browse/IGNITE-17093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-17093: --- Description: There should be a mapping between the error and the exit code. * list types of errors that user can get during commands execution * return exit codes from all commands was: There should be a mapping between the error and the exit code. * specify types of errors that user can get during commands execution * return exit codes from all commands > Map error codes for cli commands > > > Key: IGNITE-17093 > URL: https://issues.apache.org/jira/browse/IGNITE-17093 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > There should be a mapping between the error and the exit code. > * list types of errors that user can get during commands execution > * return exit codes from all commands -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17093) Map error codes for cli commands
[ https://issues.apache.org/jira/browse/IGNITE-17093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-17093: --- Summary: Map error codes for cli commands (was: Specify error codes for cli commands) > Map error codes for cli commands > > > Key: IGNITE-17093 > URL: https://issues.apache.org/jira/browse/IGNITE-17093 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > There should be a mapping between the error and the exit code. > * specify types of errors that user can get during commands execution > * return exit codes from all commands -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17110) Auto-connect on the REPL start
[
https://issues.apache.org/jira/browse/IGNITE-17110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-17110:
---
Description:
h2. Description
When a user starts REPL by the {{ignite}} command they get
{{{}[disconnected]{}}}> prompt by default. Even if the user already connected
to the cluster node in the previous session.
h2. To-Do
Implement the auto-connect logic for the case described below. The URL for the
connect command can be taken from the defaults. If the user previously
connected to the URL that differs from the default one then suggest using the
last URL as a default.
{code:bash}
$ ignite
> connect to http://host.from.previous.session:10300 ? # this is asked only if
> the default url is not possible to connect
> yes
[http://host.from.previous.session:10300]> would you like to use
http://host.from.previous.session:10300 as the default URL?
[http://host.from.previous.session:10300]> no
[http://host.from.previous.session:10300]> {code}
was:
h2. Description
When a user starts REPL by the {{ignite}} command they get
{{{}[disconnected]{}}}> prompt by default. Even if the user already connected
to the cluster node in the previous session.
h2. To-Do
Implement the auto-connect logic for the case described below. The URL for the
connect command can be taken from the defaults. If the user previously
connected to the url that differs from the default one suggest to use the last
url as a default everywhere.
{code:bash}
$ ignite
> connect to http://host.from.previous.session:10300 ? # this is asked only if
> the default url is not possible to connect
> yes
[http://host.from.previous.session:10300]> would you like to use
http://host.from.previous.session:10300 as default url?
[http://host.from.previous.session:10300]> no
[http://host.from.previous.session:10300]> {code}
> Auto-connect on the REPL start
> --
>
> Key: IGNITE-17110
> URL: https://issues.apache.org/jira/browse/IGNITE-17110
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Priority: Major
> Labels: ignite-3-cli-tool
>
> h2. Description
> When a user starts REPL by the {{ignite}} command they get
> {{{}[disconnected]{}}}> prompt by default. Even if the user already connected
> to the cluster node in the previous session.
> h2. To-Do
> Implement the auto-connect logic for the case described below. The URL for
> the connect command can be taken from the defaults. If the user previously
> connected to the URL that differs from the default one then suggest using the
> last URL as a default.
> {code:bash}
> $ ignite
> > connect to http://host.from.previous.session:10300 ? # this is asked only
> > if the default url is not possible to connect
> > yes
> [http://host.from.previous.session:10300]> would you like to use
> http://host.from.previous.session:10300 as the default URL?
> [http://host.from.previous.session:10300]> no
> [http://host.from.previous.session:10300]> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17110) Auto-connect on the REPL start
[
https://issues.apache.org/jira/browse/IGNITE-17110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-17110:
---
Description:
h2. Description
When a user starts REPL by the {{ignite}} command they get
{{{}[disconnected]{}}}> prompt by default. Even if the user already connected
to the cluster node in the previous session.
h2. To-Do
Implement the auto-connect logic for the case described below. The URL for the
connect command can be taken from the defaults. If the user previously
connected to the url that differs from the default one suggest to use the last
url as a default everywhere.
{code:bash}
$ ignite
> connect to http://host.from.previous.session:10300 ? # this is asked only if
> the default url is not possible to connect
> yes
[http://host.from.previous.session:10300]> would you like to use
http://host.from.previous.session:10300 as default url?
[http://host.from.previous.session:10300]> no
[http://host.from.previous.session:10300]> {code}
was:
h2. Description
When a user starts REPL by the {{ignite}} command they get
{{{}[disconnected]{}}}> prompt by default. Even if the user already connected
to the cluster node in the previous session.
h2. To-Do
Implement the auto-connect logic for the case described below. The URL for the
connect command can be taken from the defaults. If the user previously
connected to the url that differs from the default one suggest to use the last
url as a default everywhere.
{code:java}
$ ignite
> connect to http://host.from.previous.session:10300 ? # this is asked only if
> the default url is not possible to connect
> yes
[http://host.from.previous.session:10300]> would you like to use
http://host.from.previous.session:10300 as default url?
[http://host.from.previous.session:10300]> no
[http://host.from.previous.session:10300]> {code}
> Auto-connect on the REPL start
> --
>
> Key: IGNITE-17110
> URL: https://issues.apache.org/jira/browse/IGNITE-17110
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Priority: Major
> Labels: ignite-3-cli-tool
>
> h2. Description
> When a user starts REPL by the {{ignite}} command they get
> {{{}[disconnected]{}}}> prompt by default. Even if the user already connected
> to the cluster node in the previous session.
> h2. To-Do
> Implement the auto-connect logic for the case described below. The URL for
> the connect command can be taken from the defaults. If the user previously
> connected to the url that differs from the default one suggest to use the
> last url as a default everywhere.
> {code:bash}
> $ ignite
> > connect to http://host.from.previous.session:10300 ? # this is asked only
> > if the default url is not possible to connect
> > yes
> [http://host.from.previous.session:10300]> would you like to use
> http://host.from.previous.session:10300 as default url?
> [http://host.from.previous.session:10300]> no
> [http://host.from.previous.session:10300]> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17110) Auto-connect on the REPL start
[
https://issues.apache.org/jira/browse/IGNITE-17110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-17110:
---
Description:
h2. Description
When a user starts REPL by the {{ignite}} command they get
{{{}[disconnected]{}}}> prompt by default. Even if the user already connected
to the cluster node in the previous session.
h2. To-Do
Implement the auto-connect logic for the case described below. The URL for the
connect command can be taken from the defaults. If the user previously
connected to the url that differs from the default one suggest to use the last
url as a default everywhere.
{code:java}
$ ignite
> connect to http://host.from.previous.session:10300 ? # this is asked only if
> the default url is not possible to connect
> yes
[http://host.from.previous.session:10300]> would you like to use
http://host.from.previous.session:10300 as default url?
[http://host.from.previous.session:10300]> no
[http://host.from.previous.session:10300]> {code}
was:
h2. Description
When a user starts REPL by the {{ignite}} command they get
{{{}[disconnected]{}}}> prompt by default. Even if the user already connected
to the cluster node in the previous session.
h2. To-Do
Implement the auto-connect logic for the case descibed below. The url for the
connect command can be taken from defaults
> Auto-connect on the REPL start
> --
>
> Key: IGNITE-17110
> URL: https://issues.apache.org/jira/browse/IGNITE-17110
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Priority: Major
> Labels: ignite-3-cli-tool
>
> h2. Description
> When a user starts REPL by the {{ignite}} command they get
> {{{}[disconnected]{}}}> prompt by default. Even if the user already connected
> to the cluster node in the previous session.
> h2. To-Do
> Implement the auto-connect logic for the case described below. The URL for
> the connect command can be taken from the defaults. If the user previously
> connected to the url that differs from the default one suggest to use the
> last url as a default everywhere.
> {code:java}
> $ ignite
> > connect to http://host.from.previous.session:10300 ? # this is asked only
> > if the default url is not possible to connect
> > yes
> [http://host.from.previous.session:10300]> would you like to use
> http://host.from.previous.session:10300 as default url?
> [http://host.from.previous.session:10300]> no
> [http://host.from.previous.session:10300]> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (IGNITE-17108) Update Docker deliveries
[ https://issues.apache.org/jira/browse/IGNITE-17108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Ivanov reassigned IGNITE-17108: Assignee: Petr Ivanov > Update Docker deliveries > > > Key: IGNITE-17108 > URL: https://issues.apache.org/jira/browse/IGNITE-17108 > Project: Ignite > Issue Type: Improvement > Components: build >Affects Versions: 2.13 >Reporter: Petr Ivanov >Assignee: Petr Ivanov >Priority: Major > Fix For: 2.14 > > > # Move to eclipse-temurin docker images (successor of AdoptOpenJDK) > # Add JDK11 Dockerfile > # Add builds for x86-64/jdk8, x86-64/jdk11 and s390/jdk8 on TeamCity. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17110) Auto-connect on the REPL start
[
https://issues.apache.org/jira/browse/IGNITE-17110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-17110:
---
Summary: Auto-connect on the REPL start (was: Autoconnect on the REPL
start)
> Auto-connect on the REPL start
> --
>
> Key: IGNITE-17110
> URL: https://issues.apache.org/jira/browse/IGNITE-17110
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Priority: Major
> Labels: ignite-3-cli-tool
>
> h2. Description
> When a user starts REPL by the {{ignite}} command they get
> {{{}[disconnected]{}}}> prompt by default. Even if the user already connected
> to the cluster node in the previous session.
> h2. To-Do
> Implement the auto-connect logic for the case descibed below. The url for the
> connect command can be taken from defaults
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17110) Autoconnect on the REPL start
[
https://issues.apache.org/jira/browse/IGNITE-17110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-17110:
---
Description:
h2. Description
When a user starts REPL by the {{ignite}} command they get
{{{}[disconnected]{}}}> prompt by default. Even if the user already connected
to the cluster node in the previous session.
h2. To-Do
Implement the auto-connect logic for the case descibed below. The url for the
connect command can be taken from defaults
> Autoconnect on the REPL start
> -
>
> Key: IGNITE-17110
> URL: https://issues.apache.org/jira/browse/IGNITE-17110
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Priority: Major
> Labels: ignite-3-cli-tool
>
> h2. Description
> When a user starts REPL by the {{ignite}} command they get
> {{{}[disconnected]{}}}> prompt by default. Even if the user already connected
> to the cluster node in the previous session.
> h2. To-Do
> Implement the auto-connect logic for the case descibed below. The url for the
> connect command can be taken from defaults
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17110) Autoconnect on the REPL start
Aleksandr created IGNITE-17110: -- Summary: Autoconnect on the REPL start Key: IGNITE-17110 URL: https://issues.apache.org/jira/browse/IGNITE-17110 Project: Ignite Issue Type: Task Reporter: Aleksandr -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17101) Move ignite-mesos to the Ignite Extensions project
[ https://issues.apache.org/jira/browse/IGNITE-17101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550396#comment-17550396 ] Maxim Muzafarov commented on IGNITE-17101: -- Merged to the master branch. A new test suite created: https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Mesos_IgniteExtensions_Tests=%3Cdefault%3E=buildTypeStatusDiv > Move ignite-mesos to the Ignite Extensions project > -- > > Key: IGNITE-17101 > URL: https://issues.apache.org/jira/browse/IGNITE-17101 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > The ignite-mesos module must be moved to the Ignite extensions project since > it has not been updated for a few years. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-16731) Update ignite-extensions: dependency zookeeper
[ https://issues.apache.org/jira/browse/IGNITE-16731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr resolved IGNITE-16731. Resolution: Duplicate fix https://issues.apache.org/jira/browse/IGNITE-16673 > Update ignite-extensions: dependency zookeeper > --- > > Key: IGNITE-16731 > URL: https://issues.apache.org/jira/browse/IGNITE-16731 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > > Update Ignite dependency: Zookeeper 3.5.5 to 3.8.0 and curator 4.2.0 to 5.2.1 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17101) Move ignite-mesos to the Ignite Extensions project
[
https://issues.apache.org/jira/browse/IGNITE-17101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550375#comment-17550375
]
Ignite TC Bot commented on IGNITE-17101:
{panel:title=Branch: [pull/10067/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10067/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6610079buildTypeId=IgniteTests24Java8_RunAll]
> Move ignite-mesos to the Ignite Extensions project
> --
>
> Key: IGNITE-17101
> URL: https://issues.apache.org/jira/browse/IGNITE-17101
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The ignite-mesos module must be moved to the Ignite extensions project since
> it has not been updated for a few years.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17109) Error handling for invalid url passed to any command
[
https://issues.apache.org/jira/browse/IGNITE-17109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-17109:
---
Description:
h2. Description
Different commands given the wrong URL display different messages. For example
{code:java}
disconnected]> connect lkhjasdflkjhhasdf
2022-06-06 10:41:04:665 +0100 [ERROR][main][ExceptionHandler] Unhandled
exception
java.lang.IllegalArgumentException: Expected URL scheme 'http' or 'https' but
no colon was found
at okhttp3.HttpUrl$Builder.parse$okhttp(HttpUrl.kt:1260)
at okhttp3.HttpUrl$Companion.get(HttpUrl.kt:1633)
at okhttp3.Request$Builder.url(Request.kt:184)
...
Internal error! {code}
{code:java}
[disconnected]> connect http://kjhasdflkjhhasdf:10300/
Api error: null
{code}
{code:java}
[disconnected]> sql -u=hdbkljghhgasdflkjhasdf
Connection failed. {code}
h2. To-Do
* Test all possible variations of incorrect URLs with integration/interface
tests
* Define a single error handler for the wrong URL, port, etc.
As a result, all variations of wrong data passed should be handled on a
consistent way. The user has to see the same messages for the same mistakes
regardless of the command is used.
was:
Different commands given the wrong URL display different messages. For example
{code:java}
disconnected]> connect lkhjasdflkjhhasdf
2022-06-06 10:41:04:665 +0100 [ERROR][main][ExceptionHandler] Unhandled
exception
java.lang.IllegalArgumentException: Expected URL scheme 'http' or 'https' but
no colon was found
at okhttp3.HttpUrl$Builder.parse$okhttp(HttpUrl.kt:1260)
at okhttp3.HttpUrl$Companion.get(HttpUrl.kt:1633)
at okhttp3.Request$Builder.url(Request.kt:184)
...
Internal error! {code}
{code:java}
[disconnected]> connect http://kjhasdflkjhhasdf:10300/
Api error: null
{code}
{code:java}
[disconnected]> sql -u=hdbkljghhgasdflkjhasdf
Connection failed. {code}
Test all possible variations of incorrect urls and display
> Error handling for invalid url passed to any command
>
>
> Key: IGNITE-17109
> URL: https://issues.apache.org/jira/browse/IGNITE-17109
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Priority: Major
>
> h2. Description
> Different commands given the wrong URL display different messages. For example
>
> {code:java}
> disconnected]> connect lkhjasdflkjhhasdf
> 2022-06-06 10:41:04:665 +0100 [ERROR][main][ExceptionHandler] Unhandled
> exception
> java.lang.IllegalArgumentException: Expected URL scheme 'http' or 'https' but
> no colon was found
> at okhttp3.HttpUrl$Builder.parse$okhttp(HttpUrl.kt:1260)
> at okhttp3.HttpUrl$Companion.get(HttpUrl.kt:1633)
> at okhttp3.Request$Builder.url(Request.kt:184)
> ...
> Internal error! {code}
>
> {code:java}
> [disconnected]> connect http://kjhasdflkjhhasdf:10300/
> Api error: null
> {code}
>
> {code:java}
> [disconnected]> sql -u=hdbkljghhgasdflkjhasdf
> Connection failed. {code}
> h2. To-Do
> * Test all possible variations of incorrect URLs with integration/interface
> tests
> * Define a single error handler for the wrong URL, port, etc.
> As a result, all variations of wrong data passed should be handled on a
> consistent way. The user has to see the same messages for the same mistakes
> regardless of the command is used.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (IGNITE-16956) Tracing for rebalance logs
[ https://issues.apache.org/jira/browse/IGNITE-16956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-16956. -- Resolution: Won't Fix The approach based on unique tags (light weight tracing) does not cover all cases. I think we need to introduce common tracing framework instead. > Tracing for rebalance logs > -- > > Key: IGNITE-16956 > URL: https://issues.apache.org/jira/browse/IGNITE-16956 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Priority: Major > Labels: ignite-3 > > We need to implement a tracing of the rebalance process by the one trace id > to simplify issues' debugging in future. For this purposes we need to: > * create unique trace id, when rebalance triggered (update of replicas' > number, baseline changes) > * attach this trace id to all logs, connected with rebalance process > (https://issues.apache.org/jira/browse/IGNITE-16955). > The spreading of this trace id to the raft logs can be the most complex part > of the implementation. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17109) Error handling for invalid url passed to any command
[
https://issues.apache.org/jira/browse/IGNITE-17109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-17109:
---
Description:
Different commands given the wrong URL display different messages. For example
{code:java}
disconnected]> connect lkhjasdflkjhhasdf
2022-06-06 10:41:04:665 +0100 [ERROR][main][ExceptionHandler] Unhandled
exception
java.lang.IllegalArgumentException: Expected URL scheme 'http' or 'https' but
no colon was found
at okhttp3.HttpUrl$Builder.parse$okhttp(HttpUrl.kt:1260)
at okhttp3.HttpUrl$Companion.get(HttpUrl.kt:1633)
at okhttp3.Request$Builder.url(Request.kt:184)
...
Internal error! {code}
{code:java}
[disconnected]> connect http://kjhasdflkjhhasdf:10300/
Api error: null
{code}
{code:java}
[disconnected]> sql -u=hdbkljghhgasdflkjhasdf
Connection failed. {code}
Test all possible variations of incorrect urls and display
> Error handling for invalid url passed to any command
>
>
> Key: IGNITE-17109
> URL: https://issues.apache.org/jira/browse/IGNITE-17109
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Priority: Major
>
> Different commands given the wrong URL display different messages. For example
>
> {code:java}
> disconnected]> connect lkhjasdflkjhhasdf
> 2022-06-06 10:41:04:665 +0100 [ERROR][main][ExceptionHandler] Unhandled
> exception
> java.lang.IllegalArgumentException: Expected URL scheme 'http' or 'https' but
> no colon was found
> at okhttp3.HttpUrl$Builder.parse$okhttp(HttpUrl.kt:1260)
> at okhttp3.HttpUrl$Companion.get(HttpUrl.kt:1633)
> at okhttp3.Request$Builder.url(Request.kt:184)
> ...
> Internal error! {code}
>
> {code:java}
> [disconnected]> connect http://kjhasdflkjhhasdf:10300/
> Api error: null
> {code}
>
> {code:java}
> [disconnected]> sql -u=hdbkljghhgasdflkjhasdf
> Connection failed. {code}
>
> Test all possible variations of incorrect urls and display
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17109) Error handling for invalid url passed to any command
Aleksandr created IGNITE-17109: -- Summary: Error handling for invalid url passed to any command Key: IGNITE-17109 URL: https://issues.apache.org/jira/browse/IGNITE-17109 Project: Ignite Issue Type: Task Reporter: Aleksandr -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17108) Update Docker deliveries
[ https://issues.apache.org/jira/browse/IGNITE-17108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Ivanov updated IGNITE-17108: - Ignite Flags: (was: Docs Required,Release Notes Required) > Update Docker deliveries > > > Key: IGNITE-17108 > URL: https://issues.apache.org/jira/browse/IGNITE-17108 > Project: Ignite > Issue Type: Improvement > Components: build >Affects Versions: 2.13 >Reporter: Petr Ivanov >Priority: Major > Fix For: 2.14 > > > # Move to eclipse-temurin docker images (successor of AdoptOpenJDK) > # Add JDK11 Dockerfile > # Add builds for x86-64/jdk8, x86-64/jdk11 and s390/jdk8 on TeamCity. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17108) Update Docker deliveries
Petr Ivanov created IGNITE-17108: Summary: Update Docker deliveries Key: IGNITE-17108 URL: https://issues.apache.org/jira/browse/IGNITE-17108 Project: Ignite Issue Type: Improvement Reporter: Petr Ivanov # Move to eclipse-temurin docker images (successor of AdoptOpenJDK) # Add JDK11 Dockerfile # Add builds for x86-64/jdk8, x86-64/jdk11 and s390/jdk8 on TeamCity. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17108) Update Docker deliveries
[ https://issues.apache.org/jira/browse/IGNITE-17108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Ivanov updated IGNITE-17108: - Component/s: build > Update Docker deliveries > > > Key: IGNITE-17108 > URL: https://issues.apache.org/jira/browse/IGNITE-17108 > Project: Ignite > Issue Type: Improvement > Components: build >Affects Versions: 2.13 >Reporter: Petr Ivanov >Priority: Major > Fix For: 2.14 > > > # Move to eclipse-temurin docker images (successor of AdoptOpenJDK) > # Add JDK11 Dockerfile > # Add builds for x86-64/jdk8, x86-64/jdk11 and s390/jdk8 on TeamCity. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17108) Update Docker deliveries
[ https://issues.apache.org/jira/browse/IGNITE-17108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Ivanov updated IGNITE-17108: - Affects Version/s: 2.13 > Update Docker deliveries > > > Key: IGNITE-17108 > URL: https://issues.apache.org/jira/browse/IGNITE-17108 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.13 >Reporter: Petr Ivanov >Priority: Major > Fix For: 2.14 > > > # Move to eclipse-temurin docker images (successor of AdoptOpenJDK) > # Add JDK11 Dockerfile > # Add builds for x86-64/jdk8, x86-64/jdk11 and s390/jdk8 on TeamCity. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17108) Update Docker deliveries
[ https://issues.apache.org/jira/browse/IGNITE-17108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Ivanov updated IGNITE-17108: - Fix Version/s: 2.14 > Update Docker deliveries > > > Key: IGNITE-17108 > URL: https://issues.apache.org/jira/browse/IGNITE-17108 > Project: Ignite > Issue Type: Improvement >Reporter: Petr Ivanov >Priority: Major > Fix For: 2.14 > > > # Move to eclipse-temurin docker images (successor of AdoptOpenJDK) > # Add JDK11 Dockerfile > # Add builds for x86-64/jdk8, x86-64/jdk11 and s390/jdk8 on TeamCity. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17107) [Native Persistence 3.0] End-to-end test for persistent PageMemory
Kirill Tkalenko created IGNITE-17107: Summary: [Native Persistence 3.0] End-to-end test for persistent PageMemory Key: IGNITE-17107 URL: https://issues.apache.org/jira/browse/IGNITE-17107 Project: Ignite Issue Type: Task Reporter: Kirill Tkalenko Assignee: Kirill Tkalenko Fix For: 3.0.0-alpha5 Persistent PageMemory storage was ported and fully integrated into ignite-3, though only unit tests were written covering this piece of functionality. We need to write an end-to-end integration test for PageMemory-based persistent storage. The test should include: * New storage creation with necessary configuration; * Simple store/retrieve operations showing that storage actually performs its tasks. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17063) .NET: Failed to load libjvm.so in some environments
[
https://issues.apache.org/jira/browse/IGNITE-17063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550367#comment-17550367
]
Ignite TC Bot commented on IGNITE-17063:
{panel:title=Branch: [pull/10069/head] Base: [master] : Possible Blockers
(13)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Continuous Query 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6611893]]
* IgniteCacheQuerySelfTestSuite4:
CacheContinuousQueryAsyncFailoverMvccTxSelfTest.testMultiThreaded - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}SPI (Discovery){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6611955]]
* IgniteSpiDiscoverySelfTestSuite: TcpDiscoverySpiMBeanTest.testMBean - Test
has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}JDBC Driver{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6611904]]
{color:#d04437}Platform .NET (Windows){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6611860]]
* exe:
PlatformCacheTopologyChangeTest.TestContinuousTopologyChangeMaintainsCorrectPlatformCacheData(1)
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache (Failover) 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6611870]]
{color:#d04437}Examples (LGPL){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6611899]]
{color:#d04437}Platform .NET (Core Linux){color} [[tests 2 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=6612016]]
* dll: ShellTests.TestExecuteSafeLogsNonZeroExitCodeAndStderr - History for
base branch is absent.
* dll: ShellTests.TestExecuteSafeReturnsStdout - History for base branch is
absent.
{color:#d04437}PDS 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6611918]]
* IgnitePdsTestSuite4:
ResetLostPartitionTest.testReactivateGridBeforeResetLostPartitions - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Open Census{color} [[tests 2 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6611908]]
* IgniteOpenCensusSuite:
OpenCensusMetricExporterSpiTest.testDataRegionOcMetrics - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteOpenCensusSuite: OpenCensusMetricExporterSpiTest.testHistogram - Test
has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Kubernetes{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6611906]]
{panel}
{panel:title=Branch: [pull/10069/head] Base: [master] : New Tests
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=6612016]]
* {color:#013220}dll: ShellTests.TestExecuteSafeLogsException - PASSED{color}
* {color:#8b}dll: ShellTests.TestExecuteSafeLogsNonZeroExitCodeAndStderr -
FAILED{color}
* {color:#8b}dll: ShellTests.TestExecuteSafeReturnsStdout - FAILED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6611964buildTypeId=IgniteTests24Java8_RunAll]
> .NET: Failed to load libjvm.so in some environments
> ---
>
> Key: IGNITE-17063
> URL: https://issues.apache.org/jira/browse/IGNITE-17063
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.11
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Trivial
> Labels: .NET
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We rely on "readlink -f /usr/bin/java" to locate the JVM on Linux.
> However, in some cases "readlink" is not in PATH and this fails.
> # Try full path "/usr/bin/readlink" as well as short path
> # Capture stderr when running commands
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-16641) [Native Persistence 3.0] Support persistent B+Tree-based storage
[ https://issues.apache.org/jira/browse/IGNITE-16641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-16641: - Reviewer: Semyon Danilov > [Native Persistence 3.0] Support persistent B+Tree-based storage > > > Key: IGNITE-16641 > URL: https://issues.apache.org/jira/browse/IGNITE-16641 > Project: Ignite > Issue Type: Task >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Need to support the persistent B+Tree-based storage case: > * Add checkpoint configuration to > *PageMemoryStorageEngineConfigurationSchema*; > * Add *AbstractPageMemoryDataRegion* implementation for persistent case; > * Add *PageMemoryTableStorage* implementation for persistent case; > * Fix all *TODO: IGNITE-16641*. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17104) Organize the prevention of crossing the field PageIo#type
[
https://issues.apache.org/jira/browse/IGNITE-17104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-17104:
-
Description:
Problem:
When adding a new heir to the
{*}org.apache.ignite.internal.pagememory.io.PageIo{*}, we need to determine its
{*}PageIo#type{*}, and at first glance it is not clear how to do this, and when
testing, it turns out that this type is already taken, which is not convenient.
It is necessary to organize a mechanism / methodology for how to do this, since
at the moment the next one from all known ones is simply taken. Also, don't
forget that these types can be added via modules/plugins.
Implementation thoughts:
* For each structure, we reserve a range of 50 types, and then we get about
1310 (65535 / 50) possible structures, which should be enough;
* Somewhere to keep a register of structures to minimize their intersection,
for example, make it look like [Community edition features
list|https://ggsystems.atlassian.net/wiki/spaces/GG/pages/1192198276/Community+edition+features+list].
was:
Problem:
When adding a new heir to the
{*}org.apache.ignite.internal.pagememory.io.PageIo{*}, we need to determine its
{*}PageIo#type{*}, and at first glance it is not clear how to do this, and when
testing, it turns out that this type is already taken, which is not convenient.
It is necessary to organize a mechanism / methodology for how to do this, since
at the moment the next one from all known ones is simply taken. Also, don't
forget that these types can be added via modules/plugins.
> Organize the prevention of crossing the field PageIo#type
> -
>
> Key: IGNITE-17104
> URL: https://issues.apache.org/jira/browse/IGNITE-17104
> Project: Ignite
> Issue Type: Task
>Reporter: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha6
>
>
> Problem:
> When adding a new heir to the
> {*}org.apache.ignite.internal.pagememory.io.PageIo{*}, we need to determine
> its {*}PageIo#type{*}, and at first glance it is not clear how to do this,
> and when testing, it turns out that this type is already taken, which is not
> convenient. It is necessary to organize a mechanism / methodology for how to
> do this, since at the moment the next one from all known ones is simply
> taken. Also, don't forget that these types can be added via modules/plugins.
>
> Implementation thoughts:
> * For each structure, we reserve a range of 50 types, and then we get about
> 1310 (65535 / 50) possible structures, which should be enough;
> * Somewhere to keep a register of structures to minimize their intersection,
> for example, make it look like [Community edition features
> list|https://ggsystems.atlassian.net/wiki/spaces/GG/pages/1192198276/Community+edition+features+list].
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17090) Map sql errors to messages that user see
[
https://issues.apache.org/jira/browse/IGNITE-17090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-17090:
---
Description:
There is a number of errors that user can get during sql command execution. Map
all types of errors and map them to exit error codes and user messages. Also, a
user has to understand what is wrong with the query. Now it displays jusn an
abstract message.
How it works now:
{code:java}
sql-cli> create table myta
SQL query parsing error: Sql query execution failed.
sql-cli> {code}
{code:java}
sql-cli> create table mytable(i int, j int);
Unrecognized error while process SQL query.
sql-cli> {code}
"SQL query parsing error: Sql query execution failed.", "Unrecognized error
while process SQL query." say nothing about {*}what exactly is wrong{*}.
was:There is a number of errors that user can get during sql command
execution. Map all types of errors and map them to exit error codes and user
messages. Also, a user has to understand what is wrong with the query. Now it
displays jusn an abstract message.
> Map sql errors to messages that user see
>
>
> Key: IGNITE-17090
> URL: https://issues.apache.org/jira/browse/IGNITE-17090
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> There is a number of errors that user can get during sql command execution.
> Map all types of errors and map them to exit error codes and user messages.
> Also, a user has to understand what is wrong with the query. Now it displays
> jusn an abstract message.
>
> How it works now:
> {code:java}
> sql-cli> create table myta
> SQL query parsing error: Sql query execution failed.
> sql-cli> {code}
> {code:java}
> sql-cli> create table mytable(i int, j int);
> Unrecognized error while process SQL query.
> sql-cli> {code}
> "SQL query parsing error: Sql query execution failed.", "Unrecognized error
> while process SQL query." say nothing about {*}what exactly is wrong{*}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17106) Create documentation for Java SQL API
Igor Gusev created IGNITE-17106: --- Summary: Create documentation for Java SQL API Key: IGNITE-17106 URL: https://issues.apache.org/jira/browse/IGNITE-17106 Project: Ignite Issue Type: Task Components: documentation Reporter: Igor Gusev -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17105) Maven unused dependencies check false positive
Vadim Pakhnushev created IGNITE-17105: - Summary: Maven unused dependencies check false positive Key: IGNITE-17105 URL: https://issues.apache.org/jira/browse/IGNITE-17105 Project: Ignite Issue Type: Bug Reporter: Vadim Pakhnushev CheckUnusedDependenciesAndPluginsInParent.sh greps dependencies without whole words only switch, so for example unused dependency "jline" is falsely found to be used in "picocli-shell-jline3" -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17104) Organize the prevention of crossing the field PageIo#type
[
https://issues.apache.org/jira/browse/IGNITE-17104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-17104:
-
Description:
Problem:
When adding a new heir to the
{*}org.apache.ignite.internal.pagememory.io.PageIo{*}, we need to determine its
{*}PageIo#type{*}, and at first glance it is not clear how to do this, and when
testing, it turns out that this type is already taken, which is not convenient.
It is necessary to organize a mechanism / methodology for how to do this, since
at the moment the next one from all known ones is simply taken. Also, don't
forget that these types can be added via modules/plugins.
was:
Problem:
When adding a new heir to the "123" class, we need to determine its type, and
at first glance it is not clear how to do this, and when testing, it turns out
that this type is already taken, which is not convenient. It is necessary to
organize a mechanism / methodology for how to do this, since at the moment the
next one from all known ones is simply taken. Also, don't forget that these
types can be added via modules/plugins.
> Organize the prevention of crossing the field PageIo#type
> -
>
> Key: IGNITE-17104
> URL: https://issues.apache.org/jira/browse/IGNITE-17104
> Project: Ignite
> Issue Type: Task
>Reporter: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha6
>
>
> Problem:
> When adding a new heir to the
> {*}org.apache.ignite.internal.pagememory.io.PageIo{*}, we need to determine
> its {*}PageIo#type{*}, and at first glance it is not clear how to do this,
> and when testing, it turns out that this type is already taken, which is not
> convenient. It is necessary to organize a mechanism / methodology for how to
> do this, since at the moment the next one from all known ones is simply
> taken. Also, don't forget that these types can be added via modules/plugins.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17104) Organize the prevention of crossing the field PageIo#type
[ https://issues.apache.org/jira/browse/IGNITE-17104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-17104: - Description: Problem: When adding a new heir to the "123" class, we need to determine its type, and at first glance it is not clear how to do this, and when testing, it turns out that this type is already taken, which is not convenient. It is necessary to organize a mechanism / methodology for how to do this, since at the moment the next one from all known ones is simply taken. Also, don't forget that these types can be added via modules/plugins. was:Organization of the PageIo#type to prevent crossing. > Organize the prevention of crossing the field PageIo#type > - > > Key: IGNITE-17104 > URL: https://issues.apache.org/jira/browse/IGNITE-17104 > Project: Ignite > Issue Type: Task >Reporter: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha6 > > > Problem: > When adding a new heir to the "123" class, we need to determine its type, and > at first glance it is not clear how to do this, and when testing, it turns > out that this type is already taken, which is not convenient. It is necessary > to organize a mechanism / methodology for how to do this, since at the moment > the next one from all known ones is simply taken. Also, don't forget that > these types can be added via modules/plugins. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17090) Map sql errors to messages that user see
[ https://issues.apache.org/jira/browse/IGNITE-17090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-17090: --- Description: There is a number of errors that user can get during sql command execution. Map all types of errors and map them to exit error codes and user messages. Also, a user has to understand what is wrong with the query. Now it displays jusn an abstract message. (was: There is a number of errors that user can get during sql command execution. Map all types of errors and map them to exit error codes and user messages. Also, a user has to understand what is wrong with the query. Now it displays jusn an abstrac message.) > Map sql errors to messages that user see > > > Key: IGNITE-17090 > URL: https://issues.apache.org/jira/browse/IGNITE-17090 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > There is a number of errors that user can get during sql command execution. > Map all types of errors and map them to exit error codes and user messages. > Also, a user has to understand what is wrong with the query. Now it displays > jusn an abstract message. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17090) Map sql errors to messages that user see
[ https://issues.apache.org/jira/browse/IGNITE-17090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-17090: --- Description: There is a number of errors that user can get during sql command execution. Map all types of errors and map them to exit error codes and user messages. Also, a user has to understand what is wrong with the query. Now it displays jusn an abstrac message. (was: There is a number of errors that user can get during sql command execution. Specify all types of errors and map them to exit error codes and user messages.) > Map sql errors to messages that user see > > > Key: IGNITE-17090 > URL: https://issues.apache.org/jira/browse/IGNITE-17090 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > There is a number of errors that user can get during sql command execution. > Map all types of errors and map them to exit error codes and user messages. > Also, a user has to understand what is wrong with the query. Now it displays > jusn an abstrac message. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17090) Map sql errors to messages that user see
[ https://issues.apache.org/jira/browse/IGNITE-17090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-17090: --- Summary: Map sql errors to messages that user see (was: Specify sql errors to messages that user see) > Map sql errors to messages that user see > > > Key: IGNITE-17090 > URL: https://issues.apache.org/jira/browse/IGNITE-17090 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > There is a number of errors that user can get during sql command execution. > Specify all types of errors and map them to exit error codes and user > messages. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17104) Organize the prevention of crossing the field PageIo#type
[ https://issues.apache.org/jira/browse/IGNITE-17104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-17104: - Summary: Organize the prevention of crossing the field PageIo#type (was: Organization of the PageIo#type to prevent crossing) > Organize the prevention of crossing the field PageIo#type > - > > Key: IGNITE-17104 > URL: https://issues.apache.org/jira/browse/IGNITE-17104 > Project: Ignite > Issue Type: Task >Reporter: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha6 > > > Organization of the PageIo#type to prevent crossing. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17089) Validate "node" option in "node config show" cmd
[
https://issues.apache.org/jira/browse/IGNITE-17089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-17089:
---
Description: Now {{ignite config show does not validate the passed node}}
option. Add tests for this and impement the validation. (was: Now {{ignite
config show }}does not validate the passed {{node}} option. Add tests for this
and impement the validation.)
> Validate "node" option in "node config show" cmd
>
>
> Key: IGNITE-17089
> URL: https://issues.apache.org/jira/browse/IGNITE-17089
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> Now {{ignite config show does not validate the passed node}} option. Add
> tests for this and impement the validation.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17100) JoinReady Raft command must be idempotent
[
https://issues.apache.org/jira/browse/IGNITE-17100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semyon Danilov updated IGNITE-17100:
Fix Version/s: 3.0.0-alpha5
> JoinReady Raft command must be idempotent
> -
>
> Key: IGNITE-17100
> URL: https://issues.apache.org/jira/browse/IGNITE-17100
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Looks like because {{JoinReadyCommand}} is not idempotent, it can sometimes
> lead to test failures when it gets re-applied due to a retry.
> For example, see
> https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_IntegrationTests_ModuleRunner/6605739?buildTab=overview
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17104) Organization of the PageIo#type to prevent crossing
Kirill Tkalenko created IGNITE-17104: Summary: Organization of the PageIo#type to prevent crossing Key: IGNITE-17104 URL: https://issues.apache.org/jira/browse/IGNITE-17104 Project: Ignite Issue Type: Task Reporter: Kirill Tkalenko Fix For: 3.0.0-alpha6 Organization of the PageIo#type to prevent crossing. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17096) Update Ignite dependency: jsonpath
[ https://issues.apache.org/jira/browse/IGNITE-17096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17096: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Update Ignite dependency: jsonpath > -- > > Key: IGNITE-17096 > URL: https://issues.apache.org/jira/browse/IGNITE-17096 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Minor > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Update jsonpath dependency 2.4.0 to 2.7.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
