[jira] [Updated] (IGNITE-14120) select count * returns multiple rows
[ https://issues.apache.org/jira/browse/IGNITE-14120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isaac Zhu updated IGNITE-14120: --- Description: I have a partitioned table which has 1 backup, the *queryParallelism* is set to 4. The table primary key is column "ID", If I do this query: select count( * ) from my_table where ID = 1000; It will return 4 rows: 1 0 0 0 If I query by other not primary-key columns of this table, the result is good, like: select count( *) from my_table where name = 'abcd' result is: 0 was: I have a partitioned table which has 1 backup, the *queryParallelism* is set to 4. The table primary key is column "ID", If I do this query: select count(*) from my_table where ID = 1000; It will return 4 rows: 1 0 0 0 If I query by other not primary-key columns of this table, the result is good, like: select count(*) from my_table where name = 'abcd' result is: 0 > select count * returns multiple rows > > > Key: IGNITE-14120 > URL: https://issues.apache.org/jira/browse/IGNITE-14120 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8.1 >Reporter: Isaac Zhu >Priority: Major > > I have a partitioned table which has 1 backup, the *queryParallelism* is set > to 4. > The table primary key is column "ID", > If I do this query: > select count( * ) from my_table where ID = 1000; > It will return 4 rows: > 1 > 0 > 0 > 0 > > If I query by other not primary-key columns of this table, the result is > good, like: > select count( *) from my_table where name = 'abcd' > result is: > 0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12975) pyignte sql query should not try to create a cache
[ https://issues.apache.org/jira/browse/IGNITE-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278434#comment-17278434 ] Igor Sapego commented on IGNITE-12975: -- Tests pass: https://ci.ignite.apache.org/buildConfiguration/IgniteThinClients_Tests_ThinClientPython/5856331 [~Melnichuk], [~ivandasch], can you guys take a look? > pyignte sql query should not try to create a cache > -- > > Key: IGNITE-12975 > URL: https://issues.apache.org/jira/browse/IGNITE-12975 > Project: Ignite > Issue Type: Bug > Components: python >Affects Versions: 2.7.6 >Reporter: Isaac Zhu >Assignee: Igor Sapego >Priority: Major > Attachments: IGNITE-12975_Fix_cache_obtaining_method.patch > > Time Spent: 10m > Remaining Estimate: 0h > > I find in this line: > [https://github.com/apache/ignite/blob/master/modules/platforms/python/pyignite/client.py#L395] > When doing an SQL query through the pyignite thin client, it is trying to get > the cache by calling "get_or_create_cache". This caused my ignite instance > returns an "Authorization error" because I was using an account that only can > read cache and does not have permission to create a cache - we implemented a > Security Processor in our ignite cluster to handle the authorization. > I think here call the "self.get_cache" is enough to perform a SQL query -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14127) Python Thin: increase default query page size
[ https://issues.apache.org/jira/browse/IGNITE-14127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-14127: - Release Note: Python thin: increased default SQL page size from 1 to 1024 > Python Thin: increase default query page size > - > > Key: IGNITE-14127 > URL: https://issues.apache.org/jira/browse/IGNITE-14127 > Project: Ignite > Issue Type: Improvement > Components: python, thin client >Affects Versions: python-0.3.4 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: python-0.4.0 > > > Python has query cursor page size set to 1 by default, which is inefficient. > Other clients use 1024. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14127) Python Thin: increase default query page size
Igor Sapego created IGNITE-14127: Summary: Python Thin: increase default query page size Key: IGNITE-14127 URL: https://issues.apache.org/jira/browse/IGNITE-14127 Project: Ignite Issue Type: Improvement Components: python, thin client Affects Versions: python-0.3.4 Reporter: Igor Sapego Assignee: Igor Sapego Fix For: python-0.4.0 Python has query cursor page size set to 1 by default, which is inefficient. Other clients use 1024. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13767) Remove Python PHP and Node.js thin clients from main repository
[
https://issues.apache.org/jira/browse/IGNITE-13767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278400#comment-17278400
]
Ignite TC Bot commented on IGNITE-13767:
{panel:title=Branch: [pull/8512/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8512/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=5855462&buildTypeId=IgniteTests24Java8_RunAll]
> Remove Python PHP and Node.js thin clients from main repository
> ---
>
> Key: IGNITE-13767
> URL: https://issues.apache.org/jira/browse/IGNITE-13767
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 2.9
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Need to remove the following directories, as we now have separate repos for
> Python, Node.js and PHP thin clients:
> modules/platforms/python
> modules/platforms/nodejs
> modules/platforms/php
>
> Also, need to check all the places in code where those directories are
> referenced.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-11528) SQL: Deprecate SqlQuery for Python thin client
[ https://issues.apache.org/jira/browse/IGNITE-11528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-11528: Assignee: Igor Sapego > SQL: Deprecate SqlQuery for Python thin client > -- > > Key: IGNITE-11528 > URL: https://issues.apache.org/jira/browse/IGNITE-11528 > Project: Ignite > Issue Type: Task > Components: thin client >Affects Versions: 2.7 >Reporter: Taras Ledkov >Assignee: Igor Sapego >Priority: Major > > This API is very limited comparing to SqlFieldsQuery. Let's deprecate it with > proper links to SqlFieldsQuery. This should be not only deprecation on public > API, but removal from examples as well. > Parent ticket: IGNITE-11334 > Ticket for documentation: IGNITE-11370 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14126) Annoying warning messages in test logs from cli module
Kirill Gusakov created IGNITE-14126:
---
Summary: Annoying warning messages in test logs from cli module
Key: IGNITE-14126
URL: https://issues.apache.org/jira/browse/IGNITE-14126
Project: Ignite
Issue Type: Task
Reporter: Kirill Gusakov
Assignee: Kirill Gusakov
{noformat}
[INFO] Running org.apache.ignite.cli.IgniteCliInterfaceTest
Feb 03, 2021 11:40:56 PM org.jline.utils.Log logr
WARNING: Unable to create a system terminal, creating a dumb terminal (enable
debug logging for more information)
Feb 03, 2021 11:40:56 PM org.jline.utils.Log logr
WARNING: Unable to create a system terminal, creating a dumb terminal (enable
debug logging for more information)
Feb 03, 2021 11:40:56 PM org.jline.utils.Log logr
WARNING: Unable to create a system terminal, creating a dumb terminal (enable
debug logging for more information){noformat}
JLine spams test logs with messages about the dumb terminal. While this warning
can be helpful during app runs, it should be suppressed for test runs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14125) GridClusterStateProcessor: Logging at INFO level without checking if INFO level is enabled
Paolo Bazzi created IGNITE-14125: Summary: GridClusterStateProcessor: Logging at INFO level without checking if INFO level is enabled Key: IGNITE-14125 URL: https://issues.apache.org/jira/browse/IGNITE-14125 Project: Ignite Issue Type: Bug Affects Versions: 2.9.1 Reporter: Paolo Bazzi The following WARN log is printed to logfile when starting up the ignite instance: Log: 2021-02-01 18:57:03,068 WARN [] org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.warning(Slf4jLogger.java:127) - Logging at INFO level without checking if INFO level is enabled: Cluster state was changed from ACTIVE to ACTIVE - MDC[] Origin: org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor#onStateFinishMessage -> Needs a check for log level before logging to info logger. See http://apache-ignite-users.70518.x6.nabble.com/Ignite-Startup-Warnings-td35344.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14069) Add RELEASE_NOTES for 2.10
[ https://issues.apache.org/jira/browse/IGNITE-14069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-14069: - Fix Version/s: 2.10 > Add RELEASE_NOTES for 2.10 > -- > > Key: IGNITE-14069 > URL: https://issues.apache.org/jira/browse/IGNITE-14069 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > The RELEASE_NOTES must be updated for the 2.10 release. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14114) Replace progress bar in NodeManager by spinner
[ https://issues.apache.org/jira/browse/IGNITE-14114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Gusakov reassigned IGNITE-14114: --- Assignee: Kirill Gusakov > Replace progress bar in NodeManager by spinner > -- > > Key: IGNITE-14114 > URL: https://issues.apache.org/jira/browse/IGNITE-14114 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > At the moment we have no information about the duration of the node start > process. So, instead of a fake progress bar, we should implement "spinner" > approach for this type of process. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14064) .NET: Incorrect table name when query type is generic
[
https://issues.apache.org/jira/browse/IGNITE-14064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14064:
Release Note: .NET: Fix inferred SQL table name when query entity value
type is generic
> .NET: Incorrect table name when query type is generic
> -
>
> Key: IGNITE-14064
> URL: https://issues.apache.org/jira/browse/IGNITE-14064
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
> Fix For: 2.11
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Using a generic type as a QueryEntity value type results in a broken SQL
> table name:
> {code}
> var ignite = Ignition.Start(TestUtils.GetTestConfiguration());
> var cfg = new CacheConfiguration(
> TestUtils.TestName,
> new QueryEntity(typeof(int), typeof(GenericTest)));
> var cache = ignite.GetOrCreateCache GenericTest>(cfg);
> cache[1] = new GenericTest {Prop = "1"};
> var tables = cache.Query(new SqlFieldsQuery("SELECT TABLE_NAME
> FROM INFORMATION_SCHEMA.TABLES"))
> .Select(x => (string) x.Single()).ToArray();
> {code}
> Resulting table name is *0, CULTURE=NEUTRAL,
> PUBLICKEYTOKEN=7CEC85D7BEA7798E]]*.
> We should add .NET generics support to
> {{org.apache.ignite.internal.processors.query.QueryUtils.typeName}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14124) Fix project's Maven settings
Peter Ivanov created IGNITE-14124: - Summary: Fix project's Maven settings Key: IGNITE-14124 URL: https://issues.apache.org/jira/browse/IGNITE-14124 Project: Ignite Issue Type: Bug Affects Versions: 3.0.0-alpha2 Reporter: Peter Ivanov Assignee: Peter Ivanov Fix For: 3.0.0-alpha2 https://ci.ignite.apache.org/buildConfiguration/ignite3_Tests_RunSanityCheck/5855660?buildTab=dependencies&mode=list -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14122) Fix NPE in ProgressBarTest
[
https://issues.apache.org/jira/browse/IGNITE-14122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-14122:
-
Fix Version/s: 3.0.0-alpha2
> Fix NPE in ProgressBarTest
> --
>
> Key: IGNITE-14122
> URL: https://issues.apache.org/jira/browse/IGNITE-14122
> Project: Ignite
> Issue Type: Task
>Reporter: Kirill Gusakov
>Assignee: Kirill Gusakov
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> [ERROR] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.137
> s <<< FAILURE! - in org.apache.ignite.cli.ui.ProgressBarTest
> [ERROR] org.apache.ignite.cli.ui.ProgressBarTest.testScaledToTerminalWidth()
> Time elapsed: 0.134 s <<< FAILURE!
> java.lang.NullPointerException
> at org.apache.ignite.cli.ui.ProgressBar.step(ProgressBar.java:87)
> at
> org.apache.ignite.cli.ui.ProgressBarTest.testScaledToTerminalWidth(ProgressBarTest.java:55)[ERROR]
> org.apache.ignite.cli.ui.ProgressBarTest.testRedundantStepsProgressBar()
> Time elapsed: 0 s <<< FAILURE!
> java.lang.NullPointerException
> at org.apache.ignite.cli.ui.ProgressBar.step(ProgressBar.java:87)
> at
> org.apache.ignite.cli.ui.ProgressBarTest.testRedundantStepsProgressBar(ProgressBarTest.java:67){noformat}
> The root cause of problem in tests itself. Looks like \{{BeforeEach}}
> annotations are not working at all
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14123) Separate unit tests from integration tests
Semyon Danilov created IGNITE-14123: --- Summary: Separate unit tests from integration tests Key: IGNITE-14123 URL: https://issues.apache.org/jira/browse/IGNITE-14123 Project: Ignite Issue Type: Bug Components: build Reporter: Semyon Danilov Assignee: Semyon Danilov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14122) Fix NPE in ProgressBarTest
[
https://issues.apache.org/jira/browse/IGNITE-14122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Gusakov updated IGNITE-14122:
Description:
{noformat}
[ERROR] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.137 s
<<< FAILURE! - in org.apache.ignite.cli.ui.ProgressBarTest
[ERROR] org.apache.ignite.cli.ui.ProgressBarTest.testScaledToTerminalWidth()
Time elapsed: 0.134 s <<< FAILURE!
java.lang.NullPointerException
at org.apache.ignite.cli.ui.ProgressBar.step(ProgressBar.java:87)
at
org.apache.ignite.cli.ui.ProgressBarTest.testScaledToTerminalWidth(ProgressBarTest.java:55)[ERROR]
org.apache.ignite.cli.ui.ProgressBarTest.testRedundantStepsProgressBar() Time
elapsed: 0 s <<< FAILURE!
java.lang.NullPointerException
at org.apache.ignite.cli.ui.ProgressBar.step(ProgressBar.java:87)
at
org.apache.ignite.cli.ui.ProgressBarTest.testRedundantStepsProgressBar(ProgressBarTest.java:67){noformat}
The root cause of problem in tests itself. Looks like \{{BeforeEach}}
annotations are not working at all
was:
{noformat}
[ERROR] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.137 s
<<< FAILURE! - in org.apache.ignite.cli.ui.ProgressBarTest
[ERROR] org.apache.ignite.cli.ui.ProgressBarTest.testScaledToTerminalWidth()
Time elapsed: 0.134 s <<< FAILURE!
java.lang.NullPointerException
at org.apache.ignite.cli.ui.ProgressBar.step(ProgressBar.java:87)
at
org.apache.ignite.cli.ui.ProgressBarTest.testScaledToTerminalWidth(ProgressBarTest.java:55)[ERROR]
org.apache.ignite.cli.ui.ProgressBarTest.testRedundantStepsProgressBar() Time
elapsed: 0 s <<< FAILURE!
java.lang.NullPointerException
at org.apache.ignite.cli.ui.ProgressBar.step(ProgressBar.java:87)
at
org.apache.ignite.cli.ui.ProgressBarTest.testRedundantStepsProgressBar(ProgressBarTest.java:67){noformat}
> Fix NPE in ProgressBarTest
> --
>
> Key: IGNITE-14122
> URL: https://issues.apache.org/jira/browse/IGNITE-14122
> Project: Ignite
> Issue Type: Task
>Reporter: Kirill Gusakov
>Assignee: Kirill Gusakov
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> [ERROR] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.137
> s <<< FAILURE! - in org.apache.ignite.cli.ui.ProgressBarTest
> [ERROR] org.apache.ignite.cli.ui.ProgressBarTest.testScaledToTerminalWidth()
> Time elapsed: 0.134 s <<< FAILURE!
> java.lang.NullPointerException
> at org.apache.ignite.cli.ui.ProgressBar.step(ProgressBar.java:87)
> at
> org.apache.ignite.cli.ui.ProgressBarTest.testScaledToTerminalWidth(ProgressBarTest.java:55)[ERROR]
> org.apache.ignite.cli.ui.ProgressBarTest.testRedundantStepsProgressBar()
> Time elapsed: 0 s <<< FAILURE!
> java.lang.NullPointerException
> at org.apache.ignite.cli.ui.ProgressBar.step(ProgressBar.java:87)
> at
> org.apache.ignite.cli.ui.ProgressBarTest.testRedundantStepsProgressBar(ProgressBarTest.java:67){noformat}
> The root cause of problem in tests itself. Looks like \{{BeforeEach}}
> annotations are not working at all
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14020) .NET: Exceptions interoperability
[
https://issues.apache.org/jira/browse/IGNITE-14020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278014#comment-17278014
]
Ignite TC Bot commented on IGNITE-14020:
{panel:title=Branch: [pull/8746/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8746/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=5854474&buildTypeId=IgniteTests24Java8_RunAll]
> .NET: Exceptions interoperability
> ---
>
> Key: IGNITE-14020
> URL: https://issues.apache.org/jira/browse/IGNITE-14020
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.9.1
>Reporter: Yaroslav Molochkov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: .NET, .net-core
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently it's cumbersome to make use of .net exceptions because an exception
> is propagated from java-side reflection or local call hence we will see lots
> of unrelated and, more often than not, useless frames. To avoid that the
> exception from the .net side needs to have registered java counterpart so we
> can see the exact problem clearly.
> I propose to make exceptions interoperable just like types. We can resolve
> types between environments up to a namespace. It would be very useful to do
> the same with exceptions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14122) Fix NPE in ProgressBarTest
Kirill Gusakov created IGNITE-14122:
---
Summary: Fix NPE in ProgressBarTest
Key: IGNITE-14122
URL: https://issues.apache.org/jira/browse/IGNITE-14122
Project: Ignite
Issue Type: Task
Reporter: Kirill Gusakov
Assignee: Kirill Gusakov
{noformat}
[ERROR] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.137 s
<<< FAILURE! - in org.apache.ignite.cli.ui.ProgressBarTest
[ERROR] org.apache.ignite.cli.ui.ProgressBarTest.testScaledToTerminalWidth()
Time elapsed: 0.134 s <<< FAILURE!
java.lang.NullPointerException
at org.apache.ignite.cli.ui.ProgressBar.step(ProgressBar.java:87)
at
org.apache.ignite.cli.ui.ProgressBarTest.testScaledToTerminalWidth(ProgressBarTest.java:55)[ERROR]
org.apache.ignite.cli.ui.ProgressBarTest.testRedundantStepsProgressBar() Time
elapsed: 0 s <<< FAILURE!
java.lang.NullPointerException
at org.apache.ignite.cli.ui.ProgressBar.step(ProgressBar.java:87)
at
org.apache.ignite.cli.ui.ProgressBarTest.testRedundantStepsProgressBar(ProgressBarTest.java:67){noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14112) Revisit GridClosureProcessor#runLocalSafe(Runnable, byte) usages
[
https://issues.apache.org/jira/browse/IGNITE-14112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17277995#comment-17277995
]
Ignite TC Bot commented on IGNITE-14112:
{panel:title=Branch: [pull/8743/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8743/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=5854246&buildTypeId=IgniteTests24Java8_RunAll]
> Revisit GridClosureProcessor#runLocalSafe(Runnable, byte) usages
>
>
> Key: IGNITE-14112
> URL: https://issues.apache.org/jira/browse/IGNITE-14112
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If a simple {{Runnable}} is passed to the {{runLocalSafe}} method, not only
> will Ignite attempt to inject resources to the runnable, but it will also
> make a call to deployment, which may have various side effects.
> Need to walk through the code and replace {{Runnable}} with
> {{GridPlainRunnable}} in all places where injection is not needed/expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14094) Configuration storage interface
[ https://issues.apache.org/jira/browse/IGNITE-14094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17277971#comment-17277971 ] Ivan Bessonov commented on IGNITE-14094: [~sdanilov] looks good to me, thank you! Let's proceed with other improvements in other issues. > Configuration storage interface > --- > > Key: IGNITE-14094 > URL: https://issues.apache.org/jira/browse/IGNITE-14094 > Project: Ignite > Issue Type: Sub-task >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > Create configuration storage interface with its probable "metastorage" > implementation in mind (meaning string keys and primitive values). Support > write retries (based on versioning). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14080) binary-metadata-writer hung with no ignite instance
[
https://issues.apache.org/jira/browse/IGNITE-14080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-14080:
-
Fix Version/s: 2.11
> binary-metadata-writer hung with no ignite instance
> ---
>
> Key: IGNITE-14080
> URL: https://issues.apache.org/jira/browse/IGNITE-14080
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9.1
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If you start with no ignite instance, {{IgniteWalIteratorFactory}} creates
> {{BinaryMetadataFileStore}} which never stops by itself and hung on
> {{queue.take()}}.
> stacktrace:
> {code:java}
> "binary-metadata-writer-#1" #22 prio=5 os_prio=0 tid=0x7f2c0885b800
> nid=0x2a3ac9 waiting on condition [0x7f2afc55b000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x000580ad7130> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
> at
> java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
> at
> org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore$BinaryMetadataAsyncWriter.body0(BinaryMetadataFileStore.java:362)
> at
> org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore$BinaryMetadataAsyncWriter.body(BinaryMetadataFileStore.java:343)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14113) Fix licenses in cli module
[ https://issues.apache.org/jira/browse/IGNITE-14113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-14113: - Fix Version/s: 3.0.0-alpha2 > Fix licenses in cli module > -- > > Key: IGNITE-14113 > URL: https://issues.apache.org/jira/browse/IGNITE-14113 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Fix For: 3.0.0-alpha2 > > Time Spent: 20m > Remaining Estimate: 0h > > The following files do not contain license header: > - TerminalFactory > - ProgressBarTest > - builtin_modules.conf > Need to be fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14113) Fix licenses in cli module
[ https://issues.apache.org/jira/browse/IGNITE-14113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-14113: - Description: The following files do not contain license header: - TerminalFactory - ProgressBarTest - builtin_modules.conf Need to be fixed. > Fix licenses in cli module > -- > > Key: IGNITE-14113 > URL: https://issues.apache.org/jira/browse/IGNITE-14113 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > Time Spent: 20m > Remaining Estimate: 0h > > The following files do not contain license header: > - TerminalFactory > - ProgressBarTest > - builtin_modules.conf > Need to be fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13907) CPP thin: allow user to limit number of max active connections per client
[ https://issues.apache.org/jira/browse/IGNITE-13907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego resolved IGNITE-13907. -- Resolution: Duplicate Resolved by IGNITE-13763 > CPP thin: allow user to limit number of max active connections per client > - > > Key: IGNITE-13907 > URL: https://issues.apache.org/jira/browse/IGNITE-13907 > Project: Ignite > Issue Type: New Feature > Components: thin client >Affects Versions: 2.9 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > > Thin clients now can establish connections with multiple servers > simultaneously. It is implemented this way to make partition awareness [1] > work or for fast failover if partition awareness is not used. However, > sometimes it can create excessive load for cluster in use cases when there > are a lot of thin clients. We should give user a possibility to limit maximum > number of active connections established by a client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14121) Implement ability to generate configuration trees from arbitrary sources
Ivan Bessonov created IGNITE-14121: -- Summary: Implement ability to generate configuration trees from arbitrary sources Key: IGNITE-14121 URL: https://issues.apache.org/jira/browse/IGNITE-14121 Project: Ignite Issue Type: Sub-task Reporter: Ivan Bessonov Assignee: Ivan Bessonov Prototype is already present here: [https://github.com/apache/ignite-3/pull/34/files] Now we need to adapt it to current configuration code and implement automatic generation of construction method's implementations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13877) Error restarting the node with switching from disabled WAL archiving to enabled
[
https://issues.apache.org/jira/browse/IGNITE-13877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17277837#comment-17277837
]
Ignite TC Bot commented on IGNITE-13877:
{panel:title=Branch: [pull/8681/head] Base: [master] : Possible Blockers
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS 1{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=5854816]]
* IgnitePdsTestSuite:
WalArchiveConsistencyTest.testDecreaseWalSegmentsWitTruncate1[walMode=FSYNC] -
New test duration 91s is more that 1 minute
* IgnitePdsTestSuite:
WalArchiveConsistencyTest.testDecreaseWalSegmentsWitTruncate0[walMode=FSYNC] -
New test duration 86s is more that 1 minute
* IgnitePdsTestSuite:
WalArchiveConsistencyTest.testNotChangeWalSegmentsWitTruncate[walMode=FSYNC] -
New test duration 76s is more that 1 minute
{panel}
{panel:title=Branch: [pull/8681/head] Base: [master] : New Tests
(10)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS 1{color} [[tests
10|https://ci.ignite.apache.org/viewLog.html?buildId=5854816]]
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testDecreaseWalSegmentsWithoutTruncate[walMode=LOG_ONLY]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testNotChangeWalSegmentsWitTruncate[walMode=LOG_ONLY]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testDecreaseWalSegmentsWitTruncate1[walMode=LOG_ONLY]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testDecreaseWalSegmentsWitTruncate1[walMode=FSYNC] -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testDecreaseWalSegmentsWithoutTruncate[walMode=FSYNC]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testIncreaseWalSegmentsWithoutTruncate[walMode=LOG_ONLY]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testDecreaseWalSegmentsWitTruncate0[walMode=FSYNC] -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testDecreaseWalSegmentsWitTruncate0[walMode=LOG_ONLY]
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testNotChangeWalSegmentsWitTruncate[walMode=FSYNC] -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
WalArchiveConsistencyTest.testIncreaseWalSegmentsWithoutTruncate[walMode=FSYNC]
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5854845&buildTypeId=IgniteTests24Java8_RunAll]
> Error restarting the node with switching from disabled WAL archiving to
> enabled
> ---
>
> Key: IGNITE-13877
> URL: https://issues.apache.org/jira/browse/IGNITE-13877
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.11
>
> Attachments: Ignite13877Test.java
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> If a user starts a node with WAL archiving disabled, and then poured data
> there and there were more than *DataStorageConfiguration#walSegments* and
> then wants to restart a node with WAL archiving enabled, they will fail due
> to the following error:
> {noformat}
> SEVERE: Critical system error detected. Will be handled accordingly to
> configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false,
> timeout=0, super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.StorageException: Failed to read
> checkpoint record from WAL, persistence consistency cannot be guaranteed.
> Make sure configuration points to correct WAL folders and WAL folder is
> properly mounted [ptr=FileWALPointer [idx=11, fileOff=15864934, len=21409],
> walPath=db/wal, walArchive=db/wal/archive]]]
> class
> org.apache.ignite.internal.processors.cache.persistence.StorageException:
> Failed to read checkpoint record from WAL, persistence consistency cannot be
> guaranteed. Make sure configuration points to correct WAL folders and WAL
> folder is properly mounted [ptr=FileWALPointer [idx=11, fileOff=15864934,
> len=21409], walPath=db/wal, walArchive=db/wal/archive]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.performBinaryMemoryRestore(GridCacheDatabaseSharedManager.java:2324)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:799)
> at
> org.apache.ignite.internal.process
[jira] [Commented] (IGNITE-14102) Create escaping and searching util methods for configuration framework
[ https://issues.apache.org/jira/browse/IGNITE-14102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17277826#comment-17277826 ] Semyon Danilov commented on IGNITE-14102: - LGTM! > Create escaping and searching util methods for configuration framework > -- > > Key: IGNITE-14102 > URL: https://issues.apache.org/jira/browse/IGNITE-14102 > Project: Ignite > Issue Type: Sub-task >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Right of the bat, I can think of two useful things to do: > * escaping / unescaping; > * replace for BaseSelectors#find that'll work on new trees. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13623) Scaladoc not created during release process
[ https://issues.apache.org/jira/browse/IGNITE-13623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17277810#comment-17277810 ] Aleksey Plekhanov commented on IGNITE-13623: [~timonin.maksim], sure, I'll have a look tomorrow. > Scaladoc not created during release process > --- > > Key: IGNITE-13623 > URL: https://issues.apache.org/jira/browse/IGNITE-13623 > Project: Ignite > Issue Type: Bug > Components: build >Affects Versions: 2.8, 2.9, 2.8.1 >Reporter: Aleksey Plekhanov >Assignee: Maksim Timonin >Priority: Blocker > Time Spent: 10m > Remaining Estimate: 0h > > Scaladoc creation is broken (probably by IGNITE-11933). We have 3 release > assemblies without scaladoc now (2.8, 2.8.1, 2.9). -- This message was sent by Atlassian Jira (v8.3.4#803005)
