[jira] [Assigned] (IGNITE-8140) Web console: "integer number too large" in generated project
[
https://issues.apache.org/jira/browse/IGNITE-8140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov reassigned IGNITE-8140:
--
Assignee: Vasiliy Sisko (was: Pavel Konstantinov)
> Web console: "integer number too large" in generated project
>
>
> Key: IGNITE-8140
> URL: https://issues.apache.org/jira/browse/IGNITE-8140
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Major
> Fix For: 2.5
>
>
> Some methods expected Long type but we set Integer, please fix
> {code}
> dataStorageCfg.setSystemRegionMaxSize(2147483648);
> eventStorage.setExpireAgeMs(2323232323232323);
> cfg.setMetricsExpireTime(2323232323);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8141) Improve OS config suggestions: SWAPPINESS
[
https://issues.apache.org/jira/browse/IGNITE-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433508#comment-16433508
]
Vyacheslav Daradur commented on IGNITE-8141:
[~rsandberg], why you think so?
{quote} you still might like to set this param <= 10, which is still within the
recommendations.
{quote}
Where you read such recommendation?
Here are documents, which recommend setting the value to 10 strictly (not less):
[https://apacheignite.readme.io/docs/durable-memory-tuning#section-adjust-swappiness-settings]
[https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-memory-issues]
Same in official RHEL recommendation for databases:
[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/performance_tuning_guide/s-memory-tunables]
> Improve OS config suggestions: SWAPPINESS
> -
>
> Key: IGNITE-8141
> URL: https://issues.apache.org/jira/browse/IGNITE-8141
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 2.4
>Reporter: Reed Sandberg
>Assignee: Reed Sandberg
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.6
>
>
> Acknowledge suggested SWAPPINESS OS param adjustment using a range (<= 10).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8141) Improve OS config suggestions: SWAPPINESS
[
https://issues.apache.org/jira/browse/IGNITE-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433508#comment-16433508
]
Vyacheslav Daradur edited comment on IGNITE-8141 at 4/11/18 7:17 AM:
-
[~rsandberg], why do you think so?
{quote} you still might like to set this param <= 10, which is still within the
recommendations.
{quote}
Where do you read such recommendation?
Here are documents, which recommend setting the value to 10 strictly (not less):
[https://apacheignite.readme.io/docs/durable-memory-tuning#section-adjust-swappiness-settings]
[https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-memory-issues]
Same in official RHEL recommendation for databases:
[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/performance_tuning_guide/s-memory-tunables]
was (Author: daradurvs):
[~rsandberg], why you think so?
{quote} you still might like to set this param <= 10, which is still within the
recommendations.
{quote}
Where you read such recommendation?
Here are documents, which recommend setting the value to 10 strictly (not less):
[https://apacheignite.readme.io/docs/durable-memory-tuning#section-adjust-swappiness-settings]
[https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-memory-issues]
Same in official RHEL recommendation for databases:
[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/performance_tuning_guide/s-memory-tunables]
> Improve OS config suggestions: SWAPPINESS
> -
>
> Key: IGNITE-8141
> URL: https://issues.apache.org/jira/browse/IGNITE-8141
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 2.4
>Reporter: Reed Sandberg
>Assignee: Reed Sandberg
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.6
>
>
> Acknowledge suggested SWAPPINESS OS param adjustment using a range (<= 10).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8141) Improve OS config suggestions: SWAPPINESS
[ https://issues.apache.org/jira/browse/IGNITE-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433523#comment-16433523 ] Dmitriy Pavlov commented on IGNITE-8141: I also think interval check (0,10) is better than previous validation = 10. User can select value 9 and from point of view of performance it is still good. But previous suggestions logic will begin to warn. So +1 from me to initial proposal, probably modified with periststence/in-memory variations. > Improve OS config suggestions: SWAPPINESS > - > > Key: IGNITE-8141 > URL: https://issues.apache.org/jira/browse/IGNITE-8141 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.4 >Reporter: Reed Sandberg >Assignee: Reed Sandberg >Priority: Minor > Labels: pull-request-available > Fix For: 2.6 > > > Acknowledge suggested SWAPPINESS OS param adjustment using a range (<= 10). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8174) Web console: Skip saving of cluster data
[
https://issues.apache.org/jira/browse/IGNITE-8174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Borisov updated IGNITE-8174:
-
Description:
*Steps to reproduce:*
1. Open advanced cluster creation form (/configuration/new/advanced/cluster)
2. Go to caches tab, add a cache and press "Save" button
3. Go back to cluster tab
*What happens:*
The cluster is saved with no name, the "Name" field is empty.
*What should happen:*
Cluster name should be "Cluster${N}".
was:
# Create new cluster
# Add cache
# Open advanced tab without saving of cluster.
# Change tab from cluster
Tab opened without check of changes and cluster saving.
# Make some changes and save
Cluster is saved with empty name.
> Web console: Skip saving of cluster data
>
>
> Key: IGNITE-8174
> URL: https://issues.apache.org/jira/browse/IGNITE-8174
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Affects Versions: 2.5
>Reporter: Vasiliy Sisko
>Assignee: Ilya Borisov
>Priority: Major
>
> *Steps to reproduce:*
> 1. Open advanced cluster creation form (/configuration/new/advanced/cluster)
> 2. Go to caches tab, add a cache and press "Save" button
> 3. Go back to cluster tab
> *What happens:*
> The cluster is saved with no name, the "Name" field is empty.
> *What should happen:*
> Cluster name should be "Cluster${N}".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8111) Add extra validation for WAL segment size
[ https://issues.apache.org/jira/browse/IGNITE-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433526#comment-16433526 ] Denis Garus commented on IGNITE-8111: - [~dpavlov], I've changed value of walBufferSize because before my changes walSegmentSize was equal walBufferSize and I saved this condition. But this change doesn't impact to test result. > Add extra validation for WAL segment size > - > > Key: IGNITE-8111 > URL: https://issues.apache.org/jira/browse/IGNITE-8111 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Ivan Rakov >Assignee: Denis Garus >Priority: Major > Labels: newbie > Fix For: 2.6 > > > Currently we can set extra small DataStorageConfiguration#walSegmentSize (10 > pages or even less than one page), which will trigger multiple assertion > errors in code. > We have to implement validation on node start that WAL segment size has > reasonable value (512KB or more). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8042) .NET thin client: Add username/password to handshake
[ https://issues.apache.org/jira/browse/IGNITE-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433533#comment-16433533 ] Vladimir Ozerov commented on IGNITE-8042: - [~ptupitsyn], [~kukushal], Guys, I implemented auth supoprt in .NET. Had to introduce new proto version in .NET and change the protocol a bit (status code is not passed backwards). Could you please conduct a review? > .NET thin client: Add username/password to handshake > > > Key: IGNITE-8042 > URL: https://issues.apache.org/jira/browse/IGNITE-8042 > Project: Ignite > Issue Type: Task > Components: platforms, thin client >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.5 > > > We added username/password authentication recently (IGNITE-7860). Need to > optionally pass username and password in .NET thin client handshake. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8174) Web console: new cluster name missing
[
https://issues.apache.org/jira/browse/IGNITE-8174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Borisov updated IGNITE-8174:
-
Summary: Web console: new cluster name missing (was: Web console: Skip
saving of cluster data)
> Web console: new cluster name missing
> -
>
> Key: IGNITE-8174
> URL: https://issues.apache.org/jira/browse/IGNITE-8174
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Affects Versions: 2.5
>Reporter: Vasiliy Sisko
>Assignee: Ilya Borisov
>Priority: Major
>
> *Steps to reproduce:*
> 1. Open advanced cluster creation form (/configuration/new/advanced/cluster)
> 2. Go to caches tab, add a cache and press "Save" button
> 3. Go back to cluster tab
> *What happens:*
> The cluster is saved with no name, the "Name" field is empty.
> *What should happen:*
> Cluster name should be "Cluster${N}".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8216) Zookeeper test-jar artifact building and minor javadoc improvement
Sergey Chugunov created IGNITE-8216: --- Summary: Zookeeper test-jar artifact building and minor javadoc improvement Key: IGNITE-8216 URL: https://issues.apache.org/jira/browse/IGNITE-8216 Project: Ignite Issue Type: Improvement Components: zookeeper Reporter: Sergey Chugunov Assignee: Sergey Chugunov Fix For: 2.5 Zookeeper test-jar artifact should be built like core module test-jar. Javadoc title should be provided to *org.apache.ignite.failure* package. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-4091) Refactor direct usage of Angular API
[ https://issues.apache.org/jira/browse/IGNITE-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-4091: Assignee: Ilya Borisov (was: Alexey Kuznetsov) Looks good for me. But just in case, [~Klaster_1], please review one more time (compare vs master). > Refactor direct usage of Angular API > > > Key: IGNITE-4091 > URL: https://issues.apache.org/jira/browse/IGNITE-4091 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.7 >Reporter: Alexey Kuznetsov >Assignee: Ilya Borisov >Priority: Major > > It is not recommended to use Angular API in user code (because it may be > changed by Angular developers). > All usage of angular.XXX should be replaced with appropriate functions from > lodash library. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-4091) Refactor direct usage of Angular API
[ https://issues.apache.org/jira/browse/IGNITE-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-4091: Assignee: Alexander Kalinin (was: Ilya Borisov) > Refactor direct usage of Angular API > > > Key: IGNITE-4091 > URL: https://issues.apache.org/jira/browse/IGNITE-4091 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.7 >Reporter: Alexey Kuznetsov >Assignee: Alexander Kalinin >Priority: Major > > It is not recommended to use Angular API in user code (because it may be > changed by Angular developers). > All usage of angular.XXX should be replaced with appropriate functions from > lodash library. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8216) Minor javadoc improvement (missing group for new package)
[ https://issues.apache.org/jira/browse/IGNITE-8216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-8216: Summary: Minor javadoc improvement (missing group for new package) (was: Zookeeper test-jar artifact building and minor javadoc improvement) > Minor javadoc improvement (missing group for new package) > - > > Key: IGNITE-8216 > URL: https://issues.apache.org/jira/browse/IGNITE-8216 > Project: Ignite > Issue Type: Improvement > Components: zookeeper >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Major > Fix For: 2.5 > > > Zookeeper test-jar artifact should be built like core module test-jar. > Javadoc title should be provided to *org.apache.ignite.failure* package. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8216) Minor javadoc improvement (missing group for new package)
[ https://issues.apache.org/jira/browse/IGNITE-8216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-8216: Description: Javadoc title should be provided to *org.apache.ignite.failure* package. (was: Zookeeper test-jar artifact should be built like core module test-jar. Javadoc title should be provided to *org.apache.ignite.failure* package.) > Minor javadoc improvement (missing group for new package) > - > > Key: IGNITE-8216 > URL: https://issues.apache.org/jira/browse/IGNITE-8216 > Project: Ignite > Issue Type: Improvement > Components: zookeeper >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Major > Fix For: 2.5 > > > Javadoc title should be provided to *org.apache.ignite.failure* package. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6252) Cassandra Cache Store Session does not retry if prepare statement failed
[ https://issues.apache.org/jira/browse/IGNITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433582#comment-16433582 ] Yashasvi Kotamraju commented on IGNITE-6252: Hi Igor Sorry. I was looking at the final commit changes mentioned here in the ticket. [https://github.com/apache/ignite/pull/2583]. But I see there is another issue here. *In CassandraSessionImpl.java* When handlePreparedStatementClusterError method is called during Exception, the session is refreshed.There might be many preparedstatements created with old session(since a session object can be shared between different batches). So when we execute the preparedstatements created with old session on a new session created , we get the the Exception "com.datastax.driver.core.exceptions.InvalidQueryException You may have used a PreparedStatement that was created with another Cluster instance". Which would again call handlePreparedStatementClusterError and refresh session again and this happens continuously. We have observed continuous cassandra session refresh warnings when this scenario occurred. > Cassandra Cache Store Session does not retry if prepare statement failed > > > Key: IGNITE-6252 > URL: https://issues.apache.org/jira/browse/IGNITE-6252 > Project: Ignite > Issue Type: Bug > Components: cassandra >Affects Versions: 2.0, 2.1 >Reporter: Sunny Chan >Assignee: Igor Rudyak >Priority: Major > Fix For: 2.5 > > > During our testing, we have found that certain warning about prepared > statement: > 2017-08-31 11:27:19.479 > org.apache.ignite.cache.store.cassandra.CassandraCacheStore > flusher-0-#265%% WARN CassandraCacheStore - Prepared statement cluster > error detected, refreshing Cassandra session > com.datastax.driver.core.exceptions.InvalidQueryException: Tried to execute > unknown prepared query : 0xc7647611fd755386ef63478ee7de577b. You may have > used a PreparedStatement that was created with another Cluster instance. > We notice that after this warning occurs some of the data didn't persist > properly in cassandra cache. After further examining the Ignite's > CassandraSessionImpl code in method > execute(BatchExecutionAssistance,Iterable), we found that at around [line > 283|https://github.com/apache/ignite/blob/86bd544a557663bce497134f7826be6b24d53330/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L283], > if the prepare statement fails in the asnyc call, it will not retry the > operation as the error is stored in [line > 269|https://github.com/apache/ignite/blob/86bd544a557663bce497134f7826be6b24d53330/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L269] > and cleared in [line > 277|https://github.com/apache/ignite/blob/86bd544a557663bce497134f7826be6b24d53330/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L277] > but it was not checked again after going through the [ResultSetFuture > |https://github.com/apache/ignite/blob/86bd544a557663bce497134f7826be6b24d53330/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L307]. > I believe in line 307 you should check for error != null such that any > failure will be retry. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-4091) Refactor direct usage of Angular API
[ https://issues.apache.org/jira/browse/IGNITE-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kalinin reassigned IGNITE-4091: - Assignee: Alexey Kuznetsov (was: Alexander Kalinin) > Refactor direct usage of Angular API > > > Key: IGNITE-4091 > URL: https://issues.apache.org/jira/browse/IGNITE-4091 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.7 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > > It is not recommended to use Angular API in user code (because it may be > changed by Angular developers). > All usage of angular.XXX should be replaced with appropriate functions from > lodash library. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4091) Refactor direct usage of Angular API
[ https://issues.apache.org/jira/browse/IGNITE-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433611#comment-16433611 ] Alexander Kalinin commented on IGNITE-4091: --- [~kuaw26] Reviewed by Ilya Borisov. Ready for merge. > Refactor direct usage of Angular API > > > Key: IGNITE-4091 > URL: https://issues.apache.org/jira/browse/IGNITE-4091 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.7 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > > It is not recommended to use Angular API in user code (because it may be > changed by Angular developers). > All usage of angular.XXX should be replaced with appropriate functions from > lodash library. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7077) Spark Data Frame Support. Strategy to convert complete query to Ignite SQL
[ https://issues.apache.org/jira/browse/IGNITE-7077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433620#comment-16433620 ] Nikolay Izhikov commented on IGNITE-7077: - Hello, [~vkulichenko]. Thank you for review. I've fixed PR according to your comments. Please, take a look. > Spark Data Frame Support. Strategy to convert complete query to Ignite SQL > -- > > Key: IGNITE-7077 > URL: https://issues.apache.org/jira/browse/IGNITE-7077 > Project: Ignite > Issue Type: New Feature > Components: spark >Affects Versions: 2.3 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: bigdata > Fix For: 2.5 > > > Basic support of Spark Data Frame for Ignite implemented in IGNITE-3084. > We need to implement custom spark strategy that can convert whole Spark SQL > query to Ignite SQL Query if query consists of only Ignite tables. > The strategy does nothing if spark query includes not only Ignite tables. > Memsql implementation can be taken as an example - > https://github.com/memsql/memsql-spark-connector -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7830) Adopt kNN regression model to the new Partitioned Dataset
[ https://issues.apache.org/jira/browse/IGNITE-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433623#comment-16433623 ] ASF GitHub Bot commented on IGNITE-7830: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3583 > Adopt kNN regression model to the new Partitioned Dataset > - > > Key: IGNITE-7830 > URL: https://issues.apache.org/jira/browse/IGNITE-7830 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8217) Example DbH2ServerStartup produces a huge annoying output
Sergey Kozlov created IGNITE-8217:
-
Summary: Example DbH2ServerStartup produces a huge annoying output
Key: IGNITE-8217
URL: https://issues.apache.org/jira/browse/IGNITE-8217
Project: Ignite
Issue Type: Bug
Affects Versions: 2.4
Reporter: Sergey Kozlov
Fix For: 2.5
Example DbH2ServerStartup produces a huge annoying output:
{noformat}
Type 'q' and press 'Enter' to stop H2 TCP server...
{noformat}
Due to code following:
{code:java}
try {
do {
System.out.println("Type 'q' and press 'Enter' to stop H2 TCP
server...");
}
while ('q' != System.in.read());
}
catch (IOException ignored) {
// No-op.
}
}
{code}
I suppose we can put {{Thread.sleep(1000)}} in the \{{while}} loop and reduce
repeating lines
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8218) Add exchange latch state to diagnostic messages
Pavel Kovalenko created IGNITE-8218: --- Summary: Add exchange latch state to diagnostic messages Key: IGNITE-8218 URL: https://issues.apache.org/jira/browse/IGNITE-8218 Project: Ignite Issue Type: Improvement Components: cache Affects Versions: 2.5 Reporter: Pavel Kovalenko Assignee: Pavel Kovalenko Fix For: 2.5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5960) Ignite Continuous Query (Queries 3): CacheContinuousQueryConcurrentPartitionUpdateTest::testConcurrentUpdatesAndQueryStartAtomic is flaky
[
https://issues.apache.org/jira/browse/IGNITE-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-5960:
Fix Version/s: (was: 2.5)
2.6
> Ignite Continuous Query (Queries 3):
> CacheContinuousQueryConcurrentPartitionUpdateTest::testConcurrentUpdatesAndQueryStartAtomic
> is flaky
> -
>
> Key: IGNITE-5960
> URL: https://issues.apache.org/jira/browse/IGNITE-5960
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Labels: MakeTeamcityGreenAgain, test-failure
> Fix For: 2.6
>
>
> According to [TC
> history|http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&testNameId=6546112007182082024&tab=testDetails&branch_Ignite20Tests=%3Cdefault%3E]
> test is flaky.
> It is possible to reproduce it locally, sample run shows 9 failed tests out
> of 30 overall executed.
> Test fails with jUnit assertion check:
> {noformat}
> junit.framework.AssertionFailedError:
> Expected :1
> Actual :0
>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at junit.framework.TestCase.assertEquals(TestCase.java:409)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryConcurrentPartitionUpdateTest.concurrentUpdatesAndQueryStart(CacheContinuousQueryConcurrentPartitionUpdateTest.java:385)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryConcurrentPartitionUpdateTest.testConcurrentUpdatesAndQueryStartTx(CacheContinuousQueryConcurrentPartitionUpdateTest.java:245)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-7693) New node joining via ZookeeperDiscoverySpi should print out its ZooKeeper sessionId
[
https://issues.apache.org/jira/browse/IGNITE-7693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov resolved IGNITE-7693.
-
Resolution: Fixed
This minor logging improvement was done as part of a bigger ticket IGNITE-7222.
> New node joining via ZookeeperDiscoverySpi should print out its ZooKeeper
> sessionId
> ---
>
> Key: IGNITE-7693
> URL: https://issues.apache.org/jira/browse/IGNITE-7693
> Project: Ignite
> Issue Type: Improvement
>Reporter: Sergey Chugunov
>Priority: Major
> Fix For: 2.5
>
>
> For now there is no way to match Ignite nodes joining to Ignite cluster with
> log entries in ZooKeeper nodes' logs.
> In ZooKeeper logs there are entries like this:
> {noformat}
> myid:1] - INFO [CommitProcessor:1:ZooKeeperServer@687] - Established session
> 0x161575d88530007 with negotiated timeout 1 for client
> /:{noformat}
> but it is hard to match them with Ignite nodes when there are several started
> on the same host.
> If Ignite node prints out its session on join it makes correlating them with
> particular ZooKeeper instance much easier.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8219) B+Tree operation may result in an infinite loop in some case
Alexey Stelmak created IGNITE-8219: -- Summary: B+Tree operation may result in an infinite loop in some case Key: IGNITE-8219 URL: https://issues.apache.org/jira/browse/IGNITE-8219 Project: Ignite Issue Type: Bug Affects Versions: 2.4 Reporter: Alexey Stelmak Assignee: Alexey Stelmak Fix For: 2.5 B+Tree operation may result in an infinite loop in case. Test DynamicIndexServerCoordinatorBasicSelfTest#testCreateIndexWithInlineSizePartitionedAtomic region size = 512Mb, KEY_BEFORE=1, KEY_AFTER=2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8174) Web console: new cluster name missing
[
https://issues.apache.org/jira/browse/IGNITE-8174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Borisov reassigned IGNITE-8174:
Assignee: Dmitriy Shabalin (was: Ilya Borisov)
[~Dmitriyff] please review.
> Web console: new cluster name missing
> -
>
> Key: IGNITE-8174
> URL: https://issues.apache.org/jira/browse/IGNITE-8174
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Affects Versions: 2.5
>Reporter: Vasiliy Sisko
>Assignee: Dmitriy Shabalin
>Priority: Major
>
> *Steps to reproduce:*
> 1. Open advanced cluster creation form (/configuration/new/advanced/cluster)
> 2. Go to caches tab, add a cache and press "Save" button
> 3. Go back to cluster tab
> *What happens:*
> The cluster is saved with no name, the "Name" field is empty.
> *What should happen:*
> Cluster name should be "Cluster${N}".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8174) Web console: new cluster name missing
[
https://issues.apache.org/jira/browse/IGNITE-8174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433666#comment-16433666
]
Ilya Borisov commented on IGNITE-8174:
--
The issue was caused by the lack of "name" property in blank cluster
configuration object. I've fixed that.
> Web console: new cluster name missing
> -
>
> Key: IGNITE-8174
> URL: https://issues.apache.org/jira/browse/IGNITE-8174
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Affects Versions: 2.5
>Reporter: Vasiliy Sisko
>Assignee: Dmitriy Shabalin
>Priority: Major
>
> *Steps to reproduce:*
> 1. Open advanced cluster creation form (/configuration/new/advanced/cluster)
> 2. Go to caches tab, add a cache and press "Save" button
> 3. Go back to cluster tab
> *What happens:*
> The cluster is saved with no name, the "Name" field is empty.
> *What should happen:*
> Cluster name should be "Cluster${N}".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8217) Example DbH2ServerStartup produces a huge annoying output
[
https://issues.apache.org/jira/browse/IGNITE-8217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-8217:
--
Description:
Example DbH2ServerStartup produces a huge annoying output on STDOUT redirected
to file:
{noformat}
Type 'q' and press 'Enter' to stop H2 TCP server...
{noformat}
Due to code following:
{code:java}
try {
do {
System.out.println("Type 'q' and press 'Enter' to stop H2 TCP
server...");
}
while ('q' != System.in.read());
}
catch (IOException ignored) {
// No-op.
}
}
{code}
I suppose we can put {{Thread.sleep(1000)}} in the {{while}} loop and reduce
repeating lines
was:
Example DbH2ServerStartup produces a huge annoying output:
{noformat}
Type 'q' and press 'Enter' to stop H2 TCP server...
{noformat}
Due to code following:
{code:java}
try {
do {
System.out.println("Type 'q' and press 'Enter' to stop H2 TCP
server...");
}
while ('q' != System.in.read());
}
catch (IOException ignored) {
// No-op.
}
}
{code}
I suppose we can put {{Thread.sleep(1000)}} in the \{{while}} loop and reduce
repeating lines
> Example DbH2ServerStartup produces a huge annoying output
> -
>
> Key: IGNITE-8217
> URL: https://issues.apache.org/jira/browse/IGNITE-8217
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Sergey Kozlov
>Priority: Minor
> Fix For: 2.5
>
>
> Example DbH2ServerStartup produces a huge annoying output on STDOUT
> redirected to file:
> {noformat}
> Type 'q' and press 'Enter' to stop H2 TCP server...
> {noformat}
> Due to code following:
> {code:java}
> try {
> do {
> System.out.println("Type 'q' and press 'Enter' to stop H2 TCP
> server...");
> }
> while ('q' != System.in.read());
> }
> catch (IOException ignored) {
> // No-op.
> }
> }
> {code}
> I suppose we can put {{Thread.sleep(1000)}} in the {{while}} loop and reduce
> repeating lines
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8111) Add extra validation for WAL segment size
[ https://issues.apache.org/jira/browse/IGNITE-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433677#comment-16433677 ] ASF GitHub Bot commented on IGNITE-8111: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3768 > Add extra validation for WAL segment size > - > > Key: IGNITE-8111 > URL: https://issues.apache.org/jira/browse/IGNITE-8111 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Ivan Rakov >Assignee: Denis Garus >Priority: Major > Labels: newbie > Fix For: 2.6 > > > Currently we can set extra small DataStorageConfiguration#walSegmentSize (10 > pages or even less than one page), which will trigger multiple assertion > errors in code. > We have to implement validation on node start that WAL segment size has > reasonable value (512KB or more). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7854) Java thin client: add username/password authentication support
[ https://issues.apache.org/jira/browse/IGNITE-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov resolved IGNITE-7854. -- Resolution: Duplicate > Java thin client: add username/password authentication support > -- > > Key: IGNITE-7854 > URL: https://issues.apache.org/jira/browse/IGNITE-7854 > Project: Ignite > Issue Type: Task > Components: thin client >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Major > Fix For: 2.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-4091) Refactor direct usage of Angular API
[ https://issues.apache.org/jira/browse/IGNITE-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-4091: - Fix Version/s: 2.5 > Refactor direct usage of Angular API > > > Key: IGNITE-4091 > URL: https://issues.apache.org/jira/browse/IGNITE-4091 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.7 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.5 > > > It is not recommended to use Angular API in user code (because it may be > changed by Angular developers). > All usage of angular.XXX should be replaced with appropriate functions from > lodash library. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-4091) Refactor direct usage of Angular API
[ https://issues.apache.org/jira/browse/IGNITE-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-4091. > Refactor direct usage of Angular API > > > Key: IGNITE-4091 > URL: https://issues.apache.org/jira/browse/IGNITE-4091 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.7 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.5 > > > It is not recommended to use Angular API in user code (because it may be > changed by Angular developers). > All usage of angular.XXX should be replaced with appropriate functions from > lodash library. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8217) Example DbH2ServerStartup produces a huge annoying output
[
https://issues.apache.org/jira/browse/IGNITE-8217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-8217:
--
Description:
Example DbH2ServerStartup produces a huge annoying output on STDOUT redirected
to file in autotests:
{noformat}
Type 'q' and press 'Enter' to stop H2 TCP server...
{noformat}
Due to code following:
{code:java}
try {
do {
System.out.println("Type 'q' and press 'Enter' to stop H2 TCP
server...");
}
while ('q' != System.in.read());
}
catch (IOException ignored) {
// No-op.
}
}
{code}
I suppose we can put {{Thread.sleep(1000)}} in the {{while}} loop and reduce
repeating lines
was:
Example DbH2ServerStartup produces a huge annoying output on STDOUT redirected
to file:
{noformat}
Type 'q' and press 'Enter' to stop H2 TCP server...
{noformat}
Due to code following:
{code:java}
try {
do {
System.out.println("Type 'q' and press 'Enter' to stop H2 TCP
server...");
}
while ('q' != System.in.read());
}
catch (IOException ignored) {
// No-op.
}
}
{code}
I suppose we can put {{Thread.sleep(1000)}} in the {{while}} loop and reduce
repeating lines
> Example DbH2ServerStartup produces a huge annoying output
> -
>
> Key: IGNITE-8217
> URL: https://issues.apache.org/jira/browse/IGNITE-8217
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Sergey Kozlov
>Priority: Minor
> Fix For: 2.5
>
>
> Example DbH2ServerStartup produces a huge annoying output on STDOUT
> redirected to file in autotests:
> {noformat}
> Type 'q' and press 'Enter' to stop H2 TCP server...
> {noformat}
> Due to code following:
> {code:java}
> try {
> do {
> System.out.println("Type 'q' and press 'Enter' to stop H2 TCP
> server...");
> }
> while ('q' != System.in.read());
> }
> catch (IOException ignored) {
> // No-op.
> }
> }
> {code}
> I suppose we can put {{Thread.sleep(1000)}} in the {{while}} loop and reduce
> repeating lines
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8220) Discovery worker termination in PDS test
Dmitriy Pavlov created IGNITE-8220:
--
Summary: Discovery worker termination in PDS test
Key: IGNITE-8220
URL: https://issues.apache.org/jira/browse/IGNITE-8220
Project: Ignite
Issue Type: Test
Components: persistence
Reporter: Dmitriy Pavlov
Assignee: Pavel Kovalenko
Fix For: 2.6
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePds1&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsDirectIo1&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ActivateDeactivateCluster&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
{noformat}
[2018-04-11
02:43:09,769][ERROR][tcp-disco-srvr-#2298%cache.IgniteClusterActivateDeactivateTestWithPersistence0%][IgniteTestResources]
Critical failure. Will be handled accordingly to configured handler [hnd=class
o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread
tcp-disco-srvr-#2298%cache.IgniteClusterActivateDeactivateTestWithPersistence0%
is terminated unexpectedly.]]
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7871) Implement 2-phase waiting for partition release
[ https://issues.apache.org/jira/browse/IGNITE-7871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433743#comment-16433743 ] ASF GitHub Bot commented on IGNITE-7871: GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3793 IGNITE-7871 Check local join future on error. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7871-micro-fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3793.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3793 commit 427cb4c4025534134bb448ecbdc1172845a7adaa Author: Pavel Kovalenko Date: 2018-04-11T11:11:22Z IGNITE-7871 Check local join future on error. > Implement 2-phase waiting for partition release > --- > > Key: IGNITE-7871 > URL: https://issues.apache.org/jira/browse/IGNITE-7871 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.4 >Reporter: Pavel Kovalenko >Assignee: Alexey Goncharuk >Priority: Major > Fix For: 2.5 > > > Using validation implemented in IGNITE-7467 we can observe the following > situation: > Let's we have some partition and nodes which owning it N1 (primary) and N2 > (backup) > 1) Exchange is started > 2) N2 finished waiting for partitions release and started to create Single > message (with update counters). > 3) N1 waits for partitions release. > 4) We have pending cache update N1 -> N2. This update is done after step 2. > 5) This update increments update counters both on N1 and N2. > 6) N1 finished waiting for partitions release, while N2 already sent Single > message to coordinator with outdated update counter. > 7) Coordinator sees different partition update counters for N1 and N2. > Validation is failed, while data is equal. > Solution: > Every server node participating in PME should wait while all other server > nodes will finish their ongoing updates (finish wait for partition release > method) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7871) Implement 2-phase waiting for partition release
[ https://issues.apache.org/jira/browse/IGNITE-7871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433747#comment-16433747 ] ASF GitHub Bot commented on IGNITE-7871: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3793 > Implement 2-phase waiting for partition release > --- > > Key: IGNITE-7871 > URL: https://issues.apache.org/jira/browse/IGNITE-7871 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.4 >Reporter: Pavel Kovalenko >Assignee: Alexey Goncharuk >Priority: Major > Fix For: 2.5 > > > Using validation implemented in IGNITE-7467 we can observe the following > situation: > Let's we have some partition and nodes which owning it N1 (primary) and N2 > (backup) > 1) Exchange is started > 2) N2 finished waiting for partitions release and started to create Single > message (with update counters). > 3) N1 waits for partitions release. > 4) We have pending cache update N1 -> N2. This update is done after step 2. > 5) This update increments update counters both on N1 and N2. > 6) N1 finished waiting for partitions release, while N2 already sent Single > message to coordinator with outdated update counter. > 7) Coordinator sees different partition update counters for N1 and N2. > Validation is failed, while data is equal. > Solution: > Every server node participating in PME should wait while all other server > nodes will finish their ongoing updates (finish wait for partition release > method) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8220) Discovery worker termination in PDS test
[
https://issues.apache.org/jira/browse/IGNITE-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kovalenko reassigned IGNITE-8220:
---
Assignee: Andrey Gura (was: Pavel Kovalenko)
> Discovery worker termination in PDS test
>
>
> Key: IGNITE-8220
> URL: https://issues.apache.org/jira/browse/IGNITE-8220
> Project: Ignite
> Issue Type: Test
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Andrey Gura
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePds1&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsDirectIo1&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ActivateDeactivateCluster&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
> {noformat}
> [2018-04-11
> 02:43:09,769][ERROR][tcp-disco-srvr-#2298%cache.IgniteClusterActivateDeactivateTestWithPersistence0%][IgniteTestResources]
> Critical failure. Will be handled accordingly to configured handler
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread
> tcp-disco-srvr-#2298%cache.IgniteClusterActivateDeactivateTestWithPersistence0%
> is terminated unexpectedly.]]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8141) Improve OS config suggestions: SWAPPINESS
[ https://issues.apache.org/jira/browse/IGNITE-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433770#comment-16433770 ] Dmitriy Pavlov commented on IGNITE-8141: [~daradurvs], are you agree with (0,10) allowed? > Improve OS config suggestions: SWAPPINESS > - > > Key: IGNITE-8141 > URL: https://issues.apache.org/jira/browse/IGNITE-8141 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.4 >Reporter: Reed Sandberg >Assignee: Reed Sandberg >Priority: Minor > Labels: pull-request-available > Fix For: 2.6 > > > Acknowledge suggested SWAPPINESS OS param adjustment using a range (<= 10). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-4756:
-
Fix Version/s: (was: 2.5)
2.6
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vyacheslav Daradur
>Priority: Minor
> Labels: newbie
> Fix For: 2.6
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=3(75%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7863) Cleanup spark and spark_2.10 dependencies
[ https://issues.apache.org/jira/browse/IGNITE-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7863: --- Fix Version/s: 2.5 > Cleanup spark and spark_2.10 dependencies > - > > Key: IGNITE-7863 > URL: https://issues.apache.org/jira/browse/IGNITE-7863 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.5 > > > After solving issue with flatten plugin it possible to cleanup dependency > list in spark and spark_2.10 modules. Transitive dependencies should be > resolved using standart maven mechanism. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7863) Cleanup spark and spark_2.10 dependencies
[ https://issues.apache.org/jira/browse/IGNITE-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433778#comment-16433778 ] Dmitriy Pavlov commented on IGNITE-7863: I've set fix version 2.5. Is it correct? > Cleanup spark and spark_2.10 dependencies > - > > Key: IGNITE-7863 > URL: https://issues.apache.org/jira/browse/IGNITE-7863 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.5 > > > After solving issue with flatten plugin it possible to cleanup dependency > list in spark and spark_2.10 modules. Transitive dependencies should be > resolved using standart maven mechanism. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8141) Improve OS config suggestions: SWAPPINESS
[ https://issues.apache.org/jira/browse/IGNITE-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433782#comment-16433782 ] Vyacheslav Daradur commented on IGNITE-8141: [~dpavlov], I'm not an RHEL expert, therefore I follow vendor's recommendation. > Improve OS config suggestions: SWAPPINESS > - > > Key: IGNITE-8141 > URL: https://issues.apache.org/jira/browse/IGNITE-8141 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.4 >Reporter: Reed Sandberg >Assignee: Reed Sandberg >Priority: Minor > Labels: pull-request-available > Fix For: 2.6 > > > Acknowledge suggested SWAPPINESS OS param adjustment using a range (<= 10). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8220) Discovery worker termination in PDS test
[
https://issues.apache.org/jira/browse/IGNITE-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8220:
---
Description:
3 suites failed
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePds1&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsDirectIo1&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ActivateDeactivateCluster&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
Example of tests failed:
- IgniteClusterActivateDeactivateTestWithPersistence.testActivateFailover3
- IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateFailover3
{noformat}
[2018-04-11
02:43:09,769][ERROR][tcp-disco-srvr-#2298%cache.IgniteClusterActivateDeactivateTestWithPersistence0%][IgniteTestResources]
Critical failure. Will be handled accordingly to configured handler [hnd=class
o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread
tcp-disco-srvr-#2298%cache.IgniteClusterActivateDeactivateTestWithPersistence0%
is terminated unexpectedly.]]
{noformat}
was:
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePds1&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsDirectIo1&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ActivateDeactivateCluster&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
{noformat}
[2018-04-11
02:43:09,769][ERROR][tcp-disco-srvr-#2298%cache.IgniteClusterActivateDeactivateTestWithPersistence0%][IgniteTestResources]
Critical failure. Will be handled accordingly to configured handler [hnd=class
o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread
tcp-disco-srvr-#2298%cache.IgniteClusterActivateDeactivateTestWithPersistence0%
is terminated unexpectedly.]]
{noformat}
> Discovery worker termination in PDS test
>
>
> Key: IGNITE-8220
> URL: https://issues.apache.org/jira/browse/IGNITE-8220
> Project: Ignite
> Issue Type: Test
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Andrey Gura
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> 3 suites failed
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePds1&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsDirectIo1&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ActivateDeactivateCluster&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
> Example of tests failed:
> - IgniteClusterActivateDeactivateTestWithPersistence.testActivateFailover3
> - IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateFailover3
> {noformat}
> [2018-04-11
> 02:43:09,769][ERROR][tcp-disco-srvr-#2298%cache.IgniteClusterActivateDeactivateTestWithPersistence0%][IgniteTestResources]
> Critical failure. Will be handled accordingly to configured handler
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread
> tcp-disco-srvr-#2298%cache.IgniteClusterActivateDeactivateTestWithPersistence0%
> is terminated unexpectedly.]]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense
[ https://issues.apache.org/jira/browse/IGNITE-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-5097: --- Fix Version/s: (was: 2.5) 2.6 > BinaryMarshaller should write ints in "varint" encoding where it makes sense > > > Key: IGNITE-5097 > URL: https://issues.apache.org/jira/browse/IGNITE-5097 > Project: Ignite > Issue Type: Task > Components: binary >Affects Versions: 2.0 >Reporter: Vladimir Ozerov >Assignee: Vyacheslav Daradur >Priority: Major > Labels: iep-2, performance > Fix For: 2.6 > > > There are a lot of places in the code where we write integers for some > special purposes. Quite often their value will be vary small, so that > applying "varint" format could save a lot of space at the cost of very low > additional CPU overhead. > Specifically: > 1) Array/collection/map lengths > 2) BigDecimal's (usually will save ~6 bytes) > 3) Strings > 4) Enum ordinals -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense
[ https://issues.apache.org/jira/browse/IGNITE-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433800#comment-16433800 ] Vyacheslav Daradur commented on IGNITE-5097: Moving to 2.6 because CPP part is not finished. > BinaryMarshaller should write ints in "varint" encoding where it makes sense > > > Key: IGNITE-5097 > URL: https://issues.apache.org/jira/browse/IGNITE-5097 > Project: Ignite > Issue Type: Task > Components: binary >Affects Versions: 2.0 >Reporter: Vladimir Ozerov >Assignee: Vyacheslav Daradur >Priority: Major > Labels: iep-2, performance > Fix For: 2.6 > > > There are a lot of places in the code where we write integers for some > special purposes. Quite often their value will be vary small, so that > applying "varint" format could save a lot of space at the cost of very low > additional CPU overhead. > Specifically: > 1) Array/collection/map lengths > 2) BigDecimal's (usually will save ~6 bytes) > 3) Strings > 4) Enum ordinals -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7791) Ignite Client Nodes: failed test IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()
[
https://issues.apache.org/jira/browse/IGNITE-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-7791:
Fix Version/s: (was: 2.5)
2.6
> Ignite Client Nodes: failed test
> IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()
> ---
>
> Key: IGNITE-7791
> URL: https://issues.apache.org/jira/browse/IGNITE-7791
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
> Attachments: IgniteClientReconnectCacheDelayExchangeTest.java
>
>
> Test is flaky, success rate: 32.4%, test history is
> [here|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-9174769196124217030&tab=testDetails]
> Reproducible locally.
> Test fails on waiting for disco cache content:
> {noformat}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertTrue(Assert.java:31)
> at junit.framework.TestCase.assertTrue(TestCase.java:201)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.checkCacheDiscoveryData(IgniteClientReconnectCacheTest.java:1414)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated(IgniteClientReconnectCacheTest.java:897)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> This fail may be caused by another exception earlier in the log:
> {noformat}
> [2018-02-22
> 14:32:57,972][ERROR][exchange-worker-#3025%internal.IgniteClientReconnectCacheTest3%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=6,
> minorTopVer=1], discoEvt=DiscoveryCustomEvent
> [customMsg=CacheAffinityChangeMessage
> [id=3cea94db161-760b7b18-b776-4ee7-ae5a-64f9494eaa36,
> topVer=AffinityTopologyVersion [topVer=3, minorTopVer=0], exchId=null,
> partsMsg=null, exchangeNeeded=true], affTopVer=AffinityTopologyVersion
> [topVer=6, minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=1b7f7330-69d8-4bd0-b2e9-71773610, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
> lastExchangeTime=1519299177395, loc=false, ver=2.5.0#19700101-sha1:,
> isClient=false], topVer=6, nodeId8=658aeb36, msg=null,
> type=DISCOVERY_CUSTOM_EVT, tstamp=1519299177971]], nodeId=1b7f7330,
> evt=DISCOVERY_CUSTOM_EVT]
> java.lang.AssertionError: 236160867
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$CachesInfo.group(CacheAffinitySharedManager.java:2636)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:989)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:983)
> at
> org.apache.ignite.internal.util.lang.IgniteInClosureX.apply(IgniteInClosureX.java:38)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllCacheGroups(CacheAffinitySharedManager.java:1118)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onChangeAffinityMessage(CacheAffinitySharedManager.java:983)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAffinityChangeRequest(GridDhtPartitionsExchangeFuture.java:992)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:648)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
> at
> org.apache.ignite.internal.util.wor
[jira] [Commented] (IGNITE-8129) JDBC: JdbcThinConnectionSSLTest.testDefaultContext
[
https://issues.apache.org/jira/browse/IGNITE-8129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433801#comment-16433801
]
Taras Ledkov commented on IGNITE-8129:
--
*Root cause:* sometimes default SSL context is set up by maven to download
dependencies.
*Fix:* modify test to setup default SSL context at the test.
> JDBC: JdbcThinConnectionSSLTest.testDefaultContext
> --
>
> Key: IGNITE-8129
> URL: https://issues.apache.org/jira/browse/IGNITE-8129
> Project: Ignite
> Issue Type: Bug
>Reporter: Peter Ivanov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> Test fails under strange conditions: it runs successful if is executed by
> {{mvn test}} command and fails if is executed by {{mvn surefire:test}}. Seems
> some maven reactor dependencies and/or race condition problems.
> {code}
> [2018-04-04 05:52:26,389][ERROR][main][root] Test failed.
> java.sql.SQLException: Failed to SSL connect to server
> [url=jdbc:ignite:thin://127.0.0.1:10800]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinSSLUtil.createSSLSocket(JdbcThinSSLUtil.java:93)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.connect(JdbcThinTcpIo.java:214)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.start(JdbcThinTcpIo.java:156)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.start(JdbcThinTcpIo.java:131)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.ensureConnected(JdbcThinConnection.java:156)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.(JdbcThinConnection.java:145)
> at
> org.apache.ignite.IgniteJdbcThinDriver.connect(IgniteJdbcThinDriver.java:157)
> at java.sql.DriverManager.getConnection(DriverManager.java:664)
> at java.sql.DriverManager.getConnection(DriverManager.java:270)
> at
> org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection
> during handshake
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:992)
> at
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinSSLUtil.createSSLSocket(JdbcThinSSLUtil.java:88)
> ... 18 more
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
> at sun.security.ssl.InputRecord.read(InputRecord.java:505)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
> ... 22 more
> [08:54:52][org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext]
> java.sql.SQLException: Failed to SSL connect to server
> [url=jdbc:ignite:thin://127.0.0.1:10800]
> [08:54:52]
> [org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext]
> java.sql.SQLException: Failed to SSL connect to server
> [url=jdbc:ignite:thin://127.0.0.1:10800]
> at
> org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
> Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection
> during handshake
> at
> org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
> at
> org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8086) Flaky test timeouts in Activate/Deactivate Cluster suite
[ https://issues.apache.org/jira/browse/IGNITE-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-8086: Fix Version/s: 2.6 > Flaky test timeouts in Activate/Deactivate Cluster suite > > > Key: IGNITE-8086 > URL: https://issues.apache.org/jira/browse/IGNITE-8086 > Project: Ignite > Issue Type: Test >Reporter: Dmitriy Pavlov >Assignee: Maxim Muzafarov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.6 > > > Activate | Deactivate Cluster > IgniteStandByClusterSuite: > CacheBaselineTopologyTest.testPrimaryLeftAndClusterRestart (master fail rate > 37,1%) > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=6798733272445954906&branch=%3Cdefault%3E&tab=testDetails > IgniteStandByClusterSuite: > CacheBaselineTopologyTest.testBaselineTopologyChangesFromClient (master fail > rate 24,9%) > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-9217764610687235146&branch=%3Cdefault%3E&tab=testDetails > IgniteStandByClusterSuite: > IgniteClusterActivateDeactivateTest.testClientReconnectClusterDeactivateInProgress > (master fail rate 12,8%) > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=5210129488604303757&branch=%3Cdefault%3E&tab=testDetails > java.util.concurrent.TimeoutException: Test has been timed out > [test=testPrimaryLeftAndClusterRestart, timeout=30] - no obivious > assertions and exceptions generated in logs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7986) GridPartitionStateMap.entrySet() optimization.
[ https://issues.apache.org/jira/browse/IGNITE-7986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaliy Biryukov updated IGNITE-7986: - Fix Version/s: (was: 2.5) 2.6 > GridPartitionStateMap.entrySet() optimization. > -- > > Key: IGNITE-7986 > URL: https://issues.apache.org/jira/browse/IGNITE-7986 > Project: Ignite > Issue Type: Improvement >Reporter: Vitaliy Biryukov >Assignee: Vitaliy Biryukov >Priority: Major > Fix For: 2.6 > > Attachments: GridPartitionStateMapBench.java, fullResult.txt > > > GridPartitionStateMap based on BitSet. And the size of a BitSet depends on > the maximum key element, and not on the number of elements. > Just using the "BitSet.nextSetBit" method, will improve the performance of > the iterator for big clusters or caches with a large number of partitions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6445) IgniteTxManager.txLocksInfo method misses locks
[ https://issues.apache.org/jira/browse/IGNITE-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaliy Biryukov updated IGNITE-6445: - Fix Version/s: (was: 2.5) 2.6 > IgniteTxManager.txLocksInfo method misses locks > --- > > Key: IGNITE-6445 > URL: https://issues.apache.org/jira/browse/IGNITE-6445 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Vitaliy Biryukov >Assignee: Vitaliy Biryukov >Priority: Major > Fix For: 2.6 > > > In some cases "IgniteTxManager.txLocksInfo" method (searches for locks) > misses locks. > For example: > # In case of a configuration with near cache, entries are created for the > near cache and for the ordinal cache. For each entry, their own MVCC > candidates are created. > # For non-custom objects of type (Integer, etc.), the entry stored in > "GridNearTxLocal" is not associated with MVCC candidates with which the same > entity is associated in another format stored in "GridDhtTxLocal" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6793) NPE in InitNewCoordinatorFuture leading to Cache3 suite hang
[
https://issues.apache.org/jira/browse/IGNITE-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaliy Biryukov updated IGNITE-6793:
-
Fix Version/s: (was: 2.5)
2.6
> NPE in InitNewCoordinatorFuture leading to Cache3 suite hang
>
>
> Key: IGNITE-6793
> URL: https://issues.apache.org/jira/browse/IGNITE-6793
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Alexey Goncharuk
>Assignee: Vitaliy Biryukov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> Got the following exception in the IgniteCacheGroupsTest run:
> {code}
> [17:59:25]W: [org.apache.ignite:ignite-core] [2017-10-30
> 14:59:25,159][ERROR][sys-#35070%cache.IgniteCacheGroupsTest2%][GridCacheIoManager]
> Failed processing message [senderId=9a523ce6-a252-457f-8175-7246b6c4,
> msg=GridDhtPartitionsSingleMessage [parts={3181548=GridDhtPartitionMap
> [moving=0, top=AffinityTopologyVersion [topVer=42, minorTopVer=2],
> updateSeq=1098, size=191], -2100569601=GridDhtPartitionMap [moving=0,
> top=AffinityTopologyVersion [topVer=42, minorTopVer=2], updateSeq=654,
> size=100]},
> partCntrs={3181548=o.a.i.i.processors.cache.distributed.dht.preloader.CachePartitionPartialCountersMap@78b1774,
>
> -2100569601=o.a.i.i.processors.cache.distributed.dht.preloader.CachePartitionPartialCountersMap@3cb0c48a},
> partHistCntrs=null, err=null, client=false, compress=false,
> finishMsg=GridDhtPartitionsFullMessage [parts=null, partCntrs=null,
> partCntrs2=null, partHistSuppliers=null, partsToReload=null,
> topVer=AffinityTopologyVersion [topVer=42, minorTopVer=2], errs=null,
> compress=false, resTopVer=null, partCnt=0,
> super=GridDhtPartitionsAbstractMessage [exchId=GridDhtPartitionExchangeId
> [topVer=AffinityTopologyVersion [topVer=42, minorTopVer=2], discoEvt=null,
> nodeId=33c058c3, evt=DISCOVERY_CUSTOM_EVT], lastVer=GridCacheVersion
> [topVer=120855515, order=1509375572161, nodeOrder=32], super=GridCacheMessage
> [msgId=4153599, depInfo=null, err=null, skipPrepare=false]]],
> super=GridDhtPartitionsAbstractMessage [exchId=GridDhtPartitionExchangeId
> [topVer=AffinityTopologyVersion [topVer=42, minorTopVer=2], discoEvt=null,
> nodeId=33c058c3, evt=DISCOVERY_CUSTOM_EVT], lastVer=GridCacheVersion
> [topVer=120855515, order=1509375572153, nodeOrder=38], super=GridCacheMessage
> [msgId=4153605, depInfo=null, err=null, skipPrepare=false
> [17:59:25]W: [org.apache.ignite:ignite-core]
> java.lang.NullPointerException
> [17:59:25]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.InitNewCoordinatorFuture.onMessage(InitNewCoordinatorFuture.java:238)
> [17:59:25]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:1749)
> [17:59:25]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1484)
> [17:59:25]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1000(GridCachePartitionExchangeManager.java:131)
> [17:59:25]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:327)
> [17:59:25]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:307)
> [17:59:25]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:2627)
> [17:59:25]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:2606)
> [17:59:25]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
> [17:59:25]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> [17:59:25]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
[jira] [Updated] (IGNITE-6333) Improve cache transaction metrics to better understand transactions efficiency.
[ https://issues.apache.org/jira/browse/IGNITE-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-6333: - Fix Version/s: (was: 2.5) 2.6 > Improve cache transaction metrics to better understand transactions > efficiency. > --- > > Key: IGNITE-6333 > URL: https://issues.apache.org/jira/browse/IGNITE-6333 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Alexei Scherbakov >Assignee: Pavel Pereslegin >Priority: Major > Labels: cache, newbie > Fix For: 2.6 > > > I suggest to add: > 1. Count of rollbacks due to transaction timeout. Depends on IGNITE-6181 > 2. Count of rollbacks due to deadlocks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8220) Discovery worker termination in PDS test
[
https://issues.apache.org/jira/browse/IGNITE-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433807#comment-16433807
]
Anton Kalashnikov commented on IGNITE-8220:
---
In fact, the problem is in the absence DiscoveryDataClusterState.
Unfortunately, I do not know whether this behavior is expected or not. Maybe we
will just add not null check for it or problem is more deeper.
{noformat}
[2018-04-11
02:10:22,081][ERROR][tcp-disco-msg-worker-#2107%cache.IgniteClusterActivateDeactivateTestWithPersistence5%][IgniteClientReconnectAbstractTest$TestTcpDiscoverySpi]
TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node in
order to prevent cluster wide instability.
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.ClusterCachesInfo.initStartCachesForLocalJoin(ClusterCachesInfo.java:1110)
at
org.apache.ignite.internal.processors.cache.ClusterCachesInfo.onStateChangeFinish(ClusterCachesInfo.java:1180)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onStateChangeFinish(GridCacheProcessor.java:2441)
at
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onStateFinishMessage(GridClusterStateProcessor.java:390)
at
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onNodeLeft(GridClusterStateProcessor.java:370)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:648)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:588)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.notifyDiscovery(ServerImpl.java:1424)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.access$3700(ServerImpl.java:180)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeFailedMessage(ServerImpl.java:4863)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2752)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2535)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6765)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2620)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
{noformat}
> Discovery worker termination in PDS test
>
>
> Key: IGNITE-8220
> URL: https://issues.apache.org/jira/browse/IGNITE-8220
> Project: Ignite
> Issue Type: Test
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Andrey Gura
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> 3 suites failed
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePds1&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsDirectIo1&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ActivateDeactivateCluster&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
> Example of tests failed:
> - IgniteClusterActivateDeactivateTestWithPersistence.testActivateFailover3
> - IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateFailover3
> {noformat}
> [2018-04-11
> 02:43:09,769][ERROR][tcp-disco-srvr-#2298%cache.IgniteClusterActivateDeactivateTestWithPersistence0%][IgniteTestResources]
> Critical failure. Will be handled accordingly to configured handler
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread
> tcp-disco-srvr-#2298%cache.IgniteClusterActivateDeactivateTestWithPersistence0%
> is terminated unexpectedly.]]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7823) Enrich IgniteCache with asSet method
[
https://issues.apache.org/jira/browse/IGNITE-7823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-7823:
-
Fix Version/s: (was: 2.5)
2.6
> Enrich IgniteCache with asSet method
>
>
> Key: IGNITE-7823
> URL: https://issues.apache.org/jira/browse/IGNITE-7823
> Project: Ignite
> Issue Type: New Feature
> Components: data structures
>Reporter: Andrey Kuznetsov
>Assignee: Pavel Pereslegin
>Priority: Major
> Fix For: 2.6
>
>
> Existing {{IgniteSet}} datastructure is good enough for small sets. For big
> sets it's too expensive to maintain redundant onheap data copies. Thus we'd
> better to add new {{IgniteCache::asSet}} method returning set adapter to
> existing cache. The difference between these two kinds of sets should be
> properly documented afterwards.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8221) Cache management and server node authorisation
Alexey Kukushkin created IGNITE-8221: Summary: Cache management and server node authorisation Key: IGNITE-8221 URL: https://issues.apache.org/jira/browse/IGNITE-8221 Project: Ignite Issue Type: Task Reporter: Alexey Kukushkin Assignee: Vladimir Ozerov Add new authorisation checks requested by multiple Apache Ignite users: CACHE_CREATE CACHE_DESTROY JOIN_AS_SERVER Also, create an Ignite system property to allow disabling "on-heap" cache feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8148) JDBC thin driver: use semicolon as parameter's delimiter
[ https://issues.apache.org/jira/browse/IGNITE-8148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433827#comment-16433827 ] ASF GitHub Bot commented on IGNITE-8148: GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/3794 IGNITE-8148 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8148 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3794.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3794 commit 97b7a5ec172a1bb8fa5ca05d56255d1b44411d57 Author: devozerov Date: 2018-04-11T12:06:21Z Done. commit 421494724879d14ba1694f91c50f4f3864d829ee Author: devozerov Date: 2018-04-11T12:21:58Z Tests. > JDBC thin driver: use semicolon as parameter's delimiter > > > Key: IGNITE-8148 > URL: https://issues.apache.org/jira/browse/IGNITE-8148 > Project: Ignite > Issue Type: Task > Components: jdbc >Affects Versions: 2.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.5 > > > Currently we split JDBC parameters using ampersand. This causes a number of > usability concerns with escaping, especially when it is needed to pass > connection URL to command line (e.g. sqlline in bash or PowerShell). A number > of other vendors use either parentheses or semicolon as a delimiter. I > propose to choose semicolon. > Also it is necessary to make sure that old-style connection URLs work fine > after this change. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8148) JDBC thin driver: use semicolon as parameter's delimiter
[ https://issues.apache.org/jira/browse/IGNITE-8148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433828#comment-16433828 ] Vladimir Ozerov commented on IGNITE-8148: - Test run: https://ci.ignite.apache.org/viewQueued.html?itemId=1192160&tab=queuedBuildOverviewTab > JDBC thin driver: use semicolon as parameter's delimiter > > > Key: IGNITE-8148 > URL: https://issues.apache.org/jira/browse/IGNITE-8148 > Project: Ignite > Issue Type: Task > Components: jdbc >Affects Versions: 2.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.5 > > > Currently we split JDBC parameters using ampersand. This causes a number of > usability concerns with escaping, especially when it is needed to pass > connection URL to command line (e.g. sqlline in bash or PowerShell). A number > of other vendors use either parentheses or semicolon as a delimiter. I > propose to choose semicolon. > Also it is necessary to make sure that old-style connection URLs work fine > after this change. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8106) In control.sh -active, exception will be eaten and not displayed
[
https://issues.apache.org/jira/browse/IGNITE-8106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-8106:
-
Fix Version/s: 2.5
> In control.sh -active, exception will be eaten and not displayed
>
>
> Key: IGNITE-8106
> URL: https://issues.apache.org/jira/browse/IGNITE-8106
> Project: Ignite
> Issue Type: Bug
> Components: clients
>Affects Versions: 2.5
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Minor
> Fix For: 2.5
>
>
> Here is the relevant code from GridChangeStateCommandHandler:
> {code}
> sb.a(e.getMessage()).a("\n").a("suppressed: \n");
> for (Throwable t:e.getSuppressed())
> sb.a(t.getMessage()).a("\n");
> {code}
> However, before that code the exception will pass through
> IgniteUtils.convertException(), which will wrap the old
> IgniteCheckedException with suppressed parts with a new IgniteException with
> 0 suppressed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8222) Add docker image build for Nightly Release
Peter Ivanov created IGNITE-8222: Summary: Add docker image build for Nightly Release Key: IGNITE-8222 URL: https://issues.apache.org/jira/browse/IGNITE-8222 Project: Ignite Issue Type: New Feature Reporter: Peter Ivanov Assignee: Peter Ivanov # Create Meta-runner for Docker images building in TeamCity. # Add new build on TeamCity which will build docker image from master. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8106) In control.sh -active, exception will be eaten and not displayed
[
https://issues.apache.org/jira/browse/IGNITE-8106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433848#comment-16433848
]
ASF GitHub Bot commented on IGNITE-8106:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3735
> In control.sh -active, exception will be eaten and not displayed
>
>
> Key: IGNITE-8106
> URL: https://issues.apache.org/jira/browse/IGNITE-8106
> Project: Ignite
> Issue Type: Bug
> Components: clients
>Affects Versions: 2.5
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Minor
> Fix For: 2.5
>
>
> Here is the relevant code from GridChangeStateCommandHandler:
> {code}
> sb.a(e.getMessage()).a("\n").a("suppressed: \n");
> for (Throwable t:e.getSuppressed())
> sb.a(t.getMessage()).a("\n");
> {code}
> However, before that code the exception will pass through
> IgniteUtils.convertException(), which will wrap the old
> IgniteCheckedException with suppressed parts with a new IgniteException with
> 0 suppressed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8042) .NET thin client: Add username/password to handshake
[ https://issues.apache.org/jira/browse/IGNITE-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433850#comment-16433850 ] Alexey Kukushkin commented on IGNITE-8042: -- [~vozerov], the code looks fine to me. > .NET thin client: Add username/password to handshake > > > Key: IGNITE-8042 > URL: https://issues.apache.org/jira/browse/IGNITE-8042 > Project: Ignite > Issue Type: Task > Components: platforms, thin client >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.5 > > > We added username/password authentication recently (IGNITE-7860). Need to > optionally pass username and password in .NET thin client handshake. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8129) JDBC: JdbcThinConnectionSSLTest.testDefaultContext
[
https://issues.apache.org/jira/browse/IGNITE-8129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433857#comment-16433857
]
ASF GitHub Bot commented on IGNITE-8129:
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/3795
IGNITE-8129: fix test: setup default SSL context at the test
(because sometimes default SSL context may be setup by build system)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8129
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3795.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3795
commit cb053d060d77d80bbb848578e72808ec0c8d16f5
Author: tledkov-gridgain
Date: 2018-04-11T12:14:26Z
IGNITE-8129: fix test: setup default SSL context at the test
(because sometimes default SSL context may be setup by build system)
> JDBC: JdbcThinConnectionSSLTest.testDefaultContext
> --
>
> Key: IGNITE-8129
> URL: https://issues.apache.org/jira/browse/IGNITE-8129
> Project: Ignite
> Issue Type: Bug
>Reporter: Peter Ivanov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> Test fails under strange conditions: it runs successful if is executed by
> {{mvn test}} command and fails if is executed by {{mvn surefire:test}}. Seems
> some maven reactor dependencies and/or race condition problems.
> {code}
> [2018-04-04 05:52:26,389][ERROR][main][root] Test failed.
> java.sql.SQLException: Failed to SSL connect to server
> [url=jdbc:ignite:thin://127.0.0.1:10800]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinSSLUtil.createSSLSocket(JdbcThinSSLUtil.java:93)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.connect(JdbcThinTcpIo.java:214)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.start(JdbcThinTcpIo.java:156)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.start(JdbcThinTcpIo.java:131)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.ensureConnected(JdbcThinConnection.java:156)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.(JdbcThinConnection.java:145)
> at
> org.apache.ignite.IgniteJdbcThinDriver.connect(IgniteJdbcThinDriver.java:157)
> at java.sql.DriverManager.getConnection(DriverManager.java:664)
> at java.sql.DriverManager.getConnection(DriverManager.java:270)
> at
> org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection
> during handshake
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:992)
> at
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinSSLUtil.createSSLSocket(JdbcThinSSLUtil.java:88)
> ... 18 more
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
> at sun.security.ssl.InputRecord.read(InputRecord.java:505)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
> ... 22 more
> [08:54:52][org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext]
> java.sql.SQLException: Failed to SSL connect to server
> [url=jdbc:ignite:thin://127.0.0.1:10800]
> [08:54:52]
> [org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext]
> java.sql.SQLException: Failed to SSL connect to server
> [url=jdbc:ignite:thin://127.0.0.1:10800]
> at
> org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnection
[jira] [Commented] (IGNITE-7691) Provide info about DECIMAL column scale and precision
[ https://issues.apache.org/jira/browse/IGNITE-7691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433876#comment-16433876 ] Nikolay Izhikov commented on IGNITE-7691: - [~dpavlov] Thank you. Actually, these failures ARE related to my changes. I fixed it and start "run all" one more time. > Provide info about DECIMAL column scale and precision > - > > Key: IGNITE-7691 > URL: https://issues.apache.org/jira/browse/IGNITE-7691 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Minor > Fix For: 2.5 > > > Currently, it impossible to obtain scale and precision of DECIMAL column from > sql table metadata. > Ignite should provide those type of meta information. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8172) Update Apache Ignite's release scripts to match new RPM build and deploy architecture
[
https://issues.apache.org/jira/browse/IGNITE-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433892#comment-16433892
]
ASF GitHub Bot commented on IGNITE-8172:
Github user alamar commented on a diff in the pull request:
https://github.com/apache/ignite-release/pull/1#discussion_r180746462
--- Diff: scripts/vote_3_step_1[rpm]create_repository.sh ---
@@ -19,17 +27,19 @@ then
fi
echo
+
#
# Build package
#
echo "# Building RPM package #"
-if [ ! -f rpmbuild ]; then rm -rf rpmbuild; fi
-mkdir -pv rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS}
+if [ -d rpmbuild ]; then rm -r rpmbuild; fi
+mkdir -pv rpmbuild/{BUILD,RPMS,SRPMS}
cp -rfv git/packaging/rpm/* rpmbuild
-cp -rfv svn/vote/apache-ignite-fabric-${ignite_version}-bin.zip
rpmbuild/SOURCES/apache-ignite.zip
+cp -rfv svn/vote/apache-ignite-fabric-${ignite_version}-bin.zip
rpmbuild/SOURCES/
rpmbuild -bb --define "_topdir $(pwd)/rpmbuild"
rpmbuild/SPECS/apache-ignite.spec
--- End diff --
I thought we don't want to be a 'fabric' anymore.
> Update Apache Ignite's release scripts to match new RPM build and deploy
> architecture
> -
>
> Key: IGNITE-8172
> URL: https://issues.apache.org/jira/browse/IGNITE-8172
> Project: Ignite
> Issue Type: Improvement
> Components: build
>Affects Versions: 2.4
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
> Fix For: 2.5
>
>
> # Implement new multi-package build scheme for RPM packages.
> # Update release process: deploy RPM packages to {{ignite-rpm}} Bintray
> repository (with removal from Apache's Development Distribution SVN) instead
> of moving to ASF's release.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8204) Tests hang with lazy query flag on
[
https://issues.apache.org/jira/browse/IGNITE-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433909#comment-16433909
]
ASF GitHub Bot commented on IGNITE-8204:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3785
> Tests hang with lazy query flag on
> --
>
> Key: IGNITE-8204
> URL: https://issues.apache.org/jira/browse/IGNITE-8204
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
>Priority: Major
> Fix For: 2.5
>
>
> Affected tests:
> {{IgniteCacheClientQueryReplicatedNodeRestartSelfTest.testRestart}}
> {{IgniteCacheDistributedPartitionQueryNodeRestartsSelfTest.testJoinQueryUnstableTopology}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (IGNITE-8042) .NET thin client: Add username/password to handshake
[ https://issues.apache.org/jira/browse/IGNITE-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reopened IGNITE-8042: - > .NET thin client: Add username/password to handshake > > > Key: IGNITE-8042 > URL: https://issues.apache.org/jira/browse/IGNITE-8042 > Project: Ignite > Issue Type: Task > Components: platforms, thin client >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.5 > > > We added username/password authentication recently (IGNITE-7860). Need to > optionally pass username and password in .NET thin client handshake. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6083) Null value have appear in the entry processor, but the entry is existing
[
https://issues.apache.org/jira/browse/IGNITE-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-6083:
-
Fix Version/s: 2.6
> Null value have appear in the entry processor, but the entry is existing
>
>
> Key: IGNITE-6083
> URL: https://issues.apache.org/jira/browse/IGNITE-6083
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.1
>Reporter: Vladislav Pyatkov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
> Attachments: EntryProcessorInOptimisticTxTest.java
>
>
> In one thread load some data in a cache, after that I have execute
> OPTIMISTIC, SERIALIZABLE transaction with two {{IgniteCache.invoke()}}
> methods.
> The value had been corrected at first {{EntryProcessor}}, but it is NULL at
> second.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-6846) Add metrics for entry processor invocations
[
https://issues.apache.org/jira/browse/IGNITE-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-6846:
-
Fix Version/s: (was: 2.5)
2.6
> Add metrics for entry processor invocations
> ---
>
> Key: IGNITE-6846
> URL: https://issues.apache.org/jira/browse/IGNITE-6846
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Labels: iep-6
> Fix For: 2.6
>
>
> {{CacheMetrics}} object has multiple metrics for various cache operations
> like {{get}}, {{put}} and {{remove}}, but nothing for
> {{invoke}}/{{EntryProcessor}}. It makes sense to add such metrics, for
> example:
> * Total number of `invoke` operations executed.
> * Number of `invoke` operations that included updates.
> * Number of read-only `invoke` operations.
> * Min/max/avg execution time.
> * ...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8172) Update Apache Ignite's release scripts to match new RPM build and deploy architecture
[
https://issues.apache.org/jira/browse/IGNITE-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433917#comment-16433917
]
ASF GitHub Bot commented on IGNITE-8172:
Github user vveider commented on a diff in the pull request:
https://github.com/apache/ignite-release/pull/1#discussion_r180753764
--- Diff: scripts/vote_3_step_1[rpm]create_repository.sh ---
@@ -19,17 +27,19 @@ then
fi
echo
+
#
# Build package
#
echo "# Building RPM package #"
-if [ ! -f rpmbuild ]; then rm -rf rpmbuild; fi
-mkdir -pv rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS}
+if [ -d rpmbuild ]; then rm -r rpmbuild; fi
+mkdir -pv rpmbuild/{BUILD,RPMS,SRPMS}
cp -rfv git/packaging/rpm/* rpmbuild
-cp -rfv svn/vote/apache-ignite-fabric-${ignite_version}-bin.zip
rpmbuild/SOURCES/apache-ignite.zip
+cp -rfv svn/vote/apache-ignite-fabric-${ignite_version}-bin.zip
rpmbuild/SOURCES/
rpmbuild -bb --define "_topdir $(pwd)/rpmbuild"
rpmbuild/SPECS/apache-ignite.spec
--- End diff --
Not until https://issues.apache.org/jira/browse/IGNITE-7251 is reviewed and
merged to master.
> Update Apache Ignite's release scripts to match new RPM build and deploy
> architecture
> -
>
> Key: IGNITE-8172
> URL: https://issues.apache.org/jira/browse/IGNITE-8172
> Project: Ignite
> Issue Type: Improvement
> Components: build
>Affects Versions: 2.4
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
> Fix For: 2.5
>
>
> # Implement new multi-package build scheme for RPM packages.
> # Update release process: deploy RPM packages to {{ignite-rpm}} Bintray
> repository (with removal from Apache's Development Distribution SVN) instead
> of moving to ASF's release.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8221) Cache management and server node authorisation
[ https://issues.apache.org/jira/browse/IGNITE-8221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-8221: Component/s: security > Cache management and server node authorisation > -- > > Key: IGNITE-8221 > URL: https://issues.apache.org/jira/browse/IGNITE-8221 > Project: Ignite > Issue Type: Task > Components: security >Reporter: Alexey Kukushkin >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.5 > > > Add new authorisation checks requested by multiple Apache Ignite users: > CACHE_CREATE > CACHE_DESTROY > JOIN_AS_SERVER > Also, create an Ignite system property to allow disabling "on-heap" cache > feature. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8221) Cache management and server node authorisation
[ https://issues.apache.org/jira/browse/IGNITE-8221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-8221: Fix Version/s: 2.5 > Cache management and server node authorisation > -- > > Key: IGNITE-8221 > URL: https://issues.apache.org/jira/browse/IGNITE-8221 > Project: Ignite > Issue Type: Task > Components: security >Reporter: Alexey Kukushkin >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.5 > > > Add new authorisation checks requested by multiple Apache Ignite users: > CACHE_CREATE > CACHE_DESTROY > JOIN_AS_SERVER > Also, create an Ignite system property to allow disabling "on-heap" cache > feature. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8221) Cache management and server node authorisation
[ https://issues.apache.org/jira/browse/IGNITE-8221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-8221: --- Assignee: Alexey Kukushkin (was: Vladimir Ozerov) > Cache management and server node authorisation > -- > > Key: IGNITE-8221 > URL: https://issues.apache.org/jira/browse/IGNITE-8221 > Project: Ignite > Issue Type: Task > Components: security >Reporter: Alexey Kukushkin >Assignee: Alexey Kukushkin >Priority: Major > Fix For: 2.5 > > > Add new authorisation checks requested by multiple Apache Ignite users: > CACHE_CREATE > CACHE_DESTROY > JOIN_AS_SERVER > Also, create an Ignite system property to allow disabling "on-heap" cache > feature. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8148) JDBC thin driver: use semicolon as parameter's delimiter
[ https://issues.apache.org/jira/browse/IGNITE-8148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433935#comment-16433935 ] ASF GitHub Bot commented on IGNITE-8148: Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/3794 > JDBC thin driver: use semicolon as parameter's delimiter > > > Key: IGNITE-8148 > URL: https://issues.apache.org/jira/browse/IGNITE-8148 > Project: Ignite > Issue Type: Task > Components: jdbc >Affects Versions: 2.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.5 > > > Currently we split JDBC parameters using ampersand. This causes a number of > usability concerns with escaping, especially when it is needed to pass > connection URL to command line (e.g. sqlline in bash or PowerShell). A number > of other vendors use either parentheses or semicolon as a delimiter. I > propose to choose semicolon. > Also it is necessary to make sure that old-style connection URLs work fine > after this change. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8223) GridNearTxLocal.clearPrepareFuture does effectively nothing
Andrey Kuznetsov created IGNITE-8223:
Summary: GridNearTxLocal.clearPrepareFuture does effectively
nothing
Key: IGNITE-8223
URL: https://issues.apache.org/jira/browse/IGNITE-8223
Project: Ignite
Issue Type: Improvement
Affects Versions: 2.4
Reporter: Andrey Kuznetsov
Fix For: 2.6
It's unclear whether {{GridNearTxLocal.clearPrepareFuture}} is called at all,
but the method does nothing, since its argument type is never used as target
field value. Proposed change is to make the method no-op explicitly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-6478) IndexOutOfBoundsException jdbc2
[
https://issues.apache.org/jira/browse/IGNITE-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov reassigned IGNITE-6478:
Assignee: (was: Taras Ledkov)
> IndexOutOfBoundsException jdbc2
> ---
>
> Key: IGNITE-6478
> URL: https://issues.apache.org/jira/browse/IGNITE-6478
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.1
>Reporter: Ilya Suntsov
>Priority: Major
>
> I've connected to grid via jdbc2 (https://github.com/julianhyde/sqlline) :
> {noformat}./sqlline -d org.apache.ignite.IgniteJdbcDriver --color=true
> --verbose=true --showWarnings=true --showNestedErrs=true -u
> jdbc:ignite:cfg://cache=cache123:transactionsAllowed=true@/path_to_config/ignite-jdbc-config.xml
> {noformat}
> when I tried to get list of tables I got exception:
> {noformat}
> 0: jdbc:ignite:cfg://cache=cache123:transacti> !tables
> java.lang.IndexOutOfBoundsException: Index: 0
> at java.util.Collections$EmptyList.get(Collections.java:4454)
> at
> org.apache.ignite.internal.jdbc2.JdbcResultSetMetadata.getTableName(JdbcResultSetMetadata.java:120)
> at sqlline.Rows.isPrimaryKey(Rows.java:68)
> at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:106)
> at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:91)
> at sqlline.TableOutputFormat.print(TableOutputFormat.java:35)
> at sqlline.SqlLine.print(SqlLine.java:1648)
> at sqlline.Commands.metadata(Commands.java:199)
> at sqlline.Commands.tables(Commands.java:332)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
> at sqlline.SqlLine.dispatch(SqlLine.java:791)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8097) Java thin client: throw handshake exception on connect phase
[
https://issues.apache.org/jira/browse/IGNITE-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kukushkin reassigned IGNITE-8097:
Assignee: Alexey Kukushkin
> Java thin client: throw handshake exception on connect phase
>
>
> Key: IGNITE-8097
> URL: https://issues.apache.org/jira/browse/IGNITE-8097
> Project: Ignite
> Issue Type: Task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Alexey Kukushkin
>Priority: Major
> Fix For: 2.5
>
>
> Currently a call to {{Ignition.startClient}} return client instance even if
> we know for sure that connection is not usable. Real exception (e.g. protocol
> mismatch, auth error, etc.) is thrown on attempt to execute first operation
> on the client. This is bad UX - use may think that everything is OK for a
> long time.
> Instead, connection should be established eagerly in {{startClient}}, any
> exception should be propagated to the user immediately.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5439) JDBC thin: support query cancel
[
https://issues.apache.org/jira/browse/IGNITE-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433946#comment-16433946
]
ASF GitHub Bot commented on IGNITE-5439:
Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/2436
> JDBC thin: support query cancel
> ---
>
> Key: IGNITE-5439
> URL: https://issues.apache.org/jira/browse/IGNITE-5439
> Project: Ignite
> Issue Type: Task
> Components: jdbc
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.6
>
>
> The JDBC {{Statement.cancel}} method must be supported.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-6679) Clean up some deprecated cache metrics
[ https://issues.apache.org/jira/browse/IGNITE-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-6679: - Fix Version/s: (was: 2.5) 2.6 > Clean up some deprecated cache metrics > --- > > Key: IGNITE-6679 > URL: https://issues.apache.org/jira/browse/IGNITE-6679 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Sergey Puchnin >Assignee: Amelchev Nikita >Priority: Trivial > Labels: Newbie > Fix For: 2.6 > > > An old optimistic serializable mode implementation was removed in 2.0 but > some cache metrics still present in CacheMetrics interface. > Need to clean up and remove these metrics: > *TxCommitQueueSize* > *TxPrepareQueueSize* > *TxStartVersionCountsSize* > *TxDhtCommitQueueSize* > *TxDhtPrepareQueueSize* > *TxDhtStartVersionCountsSize* > An algorithm for page eviction was changed and metric > *DhtEvictQueueCurrentSize* should be removed also. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-6679) Clean up some deprecated cache metrics
[ https://issues.apache.org/jira/browse/IGNITE-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-6679. -- Resolution: Fixed Merged to master. Thanks for contribution. > Clean up some deprecated cache metrics > --- > > Key: IGNITE-6679 > URL: https://issues.apache.org/jira/browse/IGNITE-6679 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Sergey Puchnin >Assignee: Amelchev Nikita >Priority: Trivial > Labels: Newbie > Fix For: 2.6 > > > An old optimistic serializable mode implementation was removed in 2.0 but > some cache metrics still present in CacheMetrics interface. > Need to clean up and remove these metrics: > *TxCommitQueueSize* > *TxPrepareQueueSize* > *TxStartVersionCountsSize* > *TxDhtCommitQueueSize* > *TxDhtPrepareQueueSize* > *TxDhtStartVersionCountsSize* > An algorithm for page eviction was changed and metric > *DhtEvictQueueCurrentSize* should be removed also. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8129) JDBC: JdbcThinConnectionSSLTest.testDefaultContext
[
https://issues.apache.org/jira/browse/IGNITE-8129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433975#comment-16433975
]
Peter Ivanov commented on IGNITE-8129:
--
Looks like test is fixed:
https://ci.ignite.apache.org/viewLog.html?buildId=1192275
> JDBC: JdbcThinConnectionSSLTest.testDefaultContext
> --
>
> Key: IGNITE-8129
> URL: https://issues.apache.org/jira/browse/IGNITE-8129
> Project: Ignite
> Issue Type: Bug
>Reporter: Peter Ivanov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> Test fails under strange conditions: it runs successful if is executed by
> {{mvn test}} command and fails if is executed by {{mvn surefire:test}}. Seems
> some maven reactor dependencies and/or race condition problems.
> {code}
> [2018-04-04 05:52:26,389][ERROR][main][root] Test failed.
> java.sql.SQLException: Failed to SSL connect to server
> [url=jdbc:ignite:thin://127.0.0.1:10800]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinSSLUtil.createSSLSocket(JdbcThinSSLUtil.java:93)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.connect(JdbcThinTcpIo.java:214)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.start(JdbcThinTcpIo.java:156)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.start(JdbcThinTcpIo.java:131)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.ensureConnected(JdbcThinConnection.java:156)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.(JdbcThinConnection.java:145)
> at
> org.apache.ignite.IgniteJdbcThinDriver.connect(IgniteJdbcThinDriver.java:157)
> at java.sql.DriverManager.getConnection(DriverManager.java:664)
> at java.sql.DriverManager.getConnection(DriverManager.java:270)
> at
> org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection
> during handshake
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:992)
> at
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinSSLUtil.createSSLSocket(JdbcThinSSLUtil.java:88)
> ... 18 more
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
> at sun.security.ssl.InputRecord.read(InputRecord.java:505)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
> ... 22 more
> [08:54:52][org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext]
> java.sql.SQLException: Failed to SSL connect to server
> [url=jdbc:ignite:thin://127.0.0.1:10800]
> [08:54:52]
> [org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext]
> java.sql.SQLException: Failed to SSL connect to server
> [url=jdbc:ignite:thin://127.0.0.1:10800]
> at
> org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
> Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection
> during handshake
> at
> org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
> at
> org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8224) Print out a warning message if there are partitions mapped only to offline nodes
[ https://issues.apache.org/jira/browse/IGNITE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-8224: - Fix Version/s: 2.5 > Print out a warning message if there are partitions mapped only to offline > nodes > > > Key: IGNITE-8224 > URL: https://issues.apache.org/jira/browse/IGNITE-8224 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Priority: Major > Fix For: 2.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8224) Print out a warning message if there are partitions mapped only to offline nodes
Alexey Goncharuk created IGNITE-8224: Summary: Print out a warning message if there are partitions mapped only to offline nodes Key: IGNITE-8224 URL: https://issues.apache.org/jira/browse/IGNITE-8224 Project: Ignite Issue Type: Improvement Reporter: Alexey Goncharuk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8224) Print out a warning message if there are partitions mapped only to offline nodes
[ https://issues.apache.org/jira/browse/IGNITE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-8224: - Priority: Blocker (was: Major) > Print out a warning message if there are partitions mapped only to offline > nodes > > > Key: IGNITE-8224 > URL: https://issues.apache.org/jira/browse/IGNITE-8224 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Priority: Blocker > Fix For: 2.5 > > > We need to print out the following: > 1) A warning on partition map exchange if we got a partition mapped only to > offline baseline nodes > 2) Add periodic printouts if we have a cache with configured backups, but the > actual number of backups for any partition is 0 because of offline baseline > nodes (the warning should suggest ways to fix this - either start the offline > baseline node or change the baseline topology) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8224) Print out a warning message if there are partitions mapped only to offline nodes
[ https://issues.apache.org/jira/browse/IGNITE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-8224: - Description: We need to print out the following: 1) A warning on partition map exchange if we got a partition mapped only to offline baseline nodes 2) Add periodic printouts if we have a cache with configured backups, but the actual number of backups for any partition is 0 because of offline baseline nodes (the warning should suggest ways to fix this - either start the offline baseline node or change the baseline topology) > Print out a warning message if there are partitions mapped only to offline > nodes > > > Key: IGNITE-8224 > URL: https://issues.apache.org/jira/browse/IGNITE-8224 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Priority: Major > Fix For: 2.5 > > > We need to print out the following: > 1) A warning on partition map exchange if we got a partition mapped only to > offline baseline nodes > 2) Add periodic printouts if we have a cache with configured backups, but the > actual number of backups for any partition is 0 because of offline baseline > nodes (the warning should suggest ways to fix this - either start the offline > baseline node or change the baseline topology) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8110) GridCacheWriteBehindStore.Flusher thread uses the wrong transformation from milliseconds to nanoseconds.
[
https://issues.apache.org/jira/browse/IGNITE-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433999#comment-16433999
]
Anton Kurbanov commented on IGNITE-8110:
[~dpavlov], looks like this test is unrelated. Only affected functionality is
write-behind cache, also found several failures in test's history. On my local
machine this test in suite runs fine.
Failed tests are also different on separate runs for my branch:
RunAll execution, these test succeeded:
[https://ci.ignite.apache.org/viewLog.html?buildId=1176364&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Cache2]
Separate Cache tests execution where they failed:
[https://ci.ignite.apache.org/viewLog.html?buildId=1177272&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Cache2]
> GridCacheWriteBehindStore.Flusher thread uses the wrong transformation from
> milliseconds to nanoseconds.
>
>
> Key: IGNITE-8110
> URL: https://issues.apache.org/jira/browse/IGNITE-8110
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Vyacheslav Koptilin
>Assignee: Anton Kurbanov
>Priority: Minor
> Fix For: 2.6
>
>
> The initial value of a cache flushing frequency is defined as follows:
> {code}
> /** Cache flushing frequence in nanos. */
> protected long cacheFlushFreqNanos = cacheFlushFreq * 1000;
> {code}
> where is {{cacheFlushFreq}} is equal to
> {code}
> /** Default flush frequency for write-behind cache store in milliseconds.
> */
> public static final long DFLT_WRITE_BEHIND_FLUSH_FREQUENCY = 5000;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8224) Print out a warning message if there are partitions mapped only to offline nodes
[ https://issues.apache.org/jira/browse/IGNITE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kukushkin updated IGNITE-8224: - Fix Version/s: (was: 2.5) 2.6 > Print out a warning message if there are partitions mapped only to offline > nodes > > > Key: IGNITE-8224 > URL: https://issues.apache.org/jira/browse/IGNITE-8224 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Priority: Blocker > Fix For: 2.6 > > > We need to print out the following: > 1) A warning on partition map exchange if we got a partition mapped only to > offline baseline nodes > 2) Add periodic printouts if we have a cache with configured backups, but the > actual number of backups for any partition is 0 because of offline baseline > nodes (the warning should suggest ways to fix this - either start the offline > baseline node or change the baseline topology) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5795) @AffinityKeyMapped ignored if QueryEntity used
[ https://issues.apache.org/jira/browse/IGNITE-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kukushkin updated IGNITE-5795: - Fix Version/s: (was: 2.5) 2.6 > @AffinityKeyMapped ignored if QueryEntity used > -- > > Key: IGNITE-5795 > URL: https://issues.apache.org/jira/browse/IGNITE-5795 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.0 >Reporter: Dmitry Karachentsev >Assignee: Alexey Kukushkin >Priority: Major > Labels: usability > Fix For: 2.6 > > > When cache configured with QueryEntity and used key type with > @AffinityKeyMapped field, it will be ignored and wrong partition calculated. > This happens because QueryEntity processing precedes key type registering in > binary meta cache. On that step > CacheObjectBinaryProcessorImpl#affinityKeyField called and unable to resolve > type, so null returned and null putted in affKeyFields. > On next put/get operation CacheObjectBinaryProcessorImpl#affinityKeyField > will return null from affKeyFields, but should be affinity key field. > Test that reproduces problem in [PR > 2330|https://github.com/apache/ignite/pull/2330] > To wrorkaround the issue, set IgniteConfiguration#setKeyConfiguration(), it > will force registering key. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8042) .NET thin client: Add username/password to handshake
[ https://issues.apache.org/jira/browse/IGNITE-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434006#comment-16434006 ] Vladimir Ozerov commented on IGNITE-8042: - One more run: https://ci.ignite.apache.org/viewQueued.html?itemId=1192682&tab=queuedBuildOverviewTab > .NET thin client: Add username/password to handshake > > > Key: IGNITE-8042 > URL: https://issues.apache.org/jira/browse/IGNITE-8042 > Project: Ignite > Issue Type: Task > Components: platforms, thin client >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.5 > > > We added username/password authentication recently (IGNITE-7860). Need to > optionally pass username and password in .NET thin client handshake. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5551) Optimize service deployment assignments object
[ https://issues.apache.org/jira/browse/IGNITE-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kukushkin updated IGNITE-5551: - Fix Version/s: (was: 2.5) 2.6 > Optimize service deployment assignments object > -- > > Key: IGNITE-5551 > URL: https://issues.apache.org/jira/browse/IGNITE-5551 > Project: Ignite > Issue Type: Improvement > Components: managed services >Affects Versions: 1.7 >Reporter: Alexey Goncharuk >Assignee: Alexey Kukushkin >Priority: Critical > Fix For: 2.6 > > > 1) The deployment assignment is stored using a map [node ID -> number of > assigned services]. However, this assignment is not very effective for cases > when service configuration is (maxPerCluster = 0, maxPerNode > 0), because in > this case, we can avoid assignment recalculation at all. The assignment for > this case may look like (eachNode=N). In this case, the assignment does not > change and we can effectively skip it during the reassign loop. > 2) We store zero assignment counters, which does not make sense at all - if > there are no service deployments for a node, there should be no corresponding > entry in the map at all. The size of assignments for (maxPerCluster > 0) > configurations is O(number of nodes in the cluster), but it should be > O(maxPerCluster). > 3) If an assignment did not change, we should not commit the assignment > transaction - this is redundant > 4) Perhaps, it also makes sense to calculate several assignments at once and > do a putAll commit instead of single puts - this should also decrease the > assignment calculation latency -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8225) Add a command to control script to print current topology version
Alexey Goncharuk created IGNITE-8225: Summary: Add a command to control script to print current topology version Key: IGNITE-8225 URL: https://issues.apache.org/jira/browse/IGNITE-8225 Project: Ignite Issue Type: Improvement Reporter: Alexey Goncharuk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8225) Add a command to control script to print current topology version
[
https://issues.apache.org/jira/browse/IGNITE-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-8225:
-
Priority: Blocker (was: Major)
> Add a command to control script to print current topology version
> -
>
> Key: IGNITE-8225
> URL: https://issues.apache.org/jira/browse/IGNITE-8225
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Priority: Blocker
> Fix For: 2.5
>
>
> The command should be {{./control.sh --topology}} and should print a short
> summary about the current topology (topology version, number of client nodes,
> number of server nodes, baseline topology information)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8225) Add a command to control script to print current topology version
[
https://issues.apache.org/jira/browse/IGNITE-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-8225:
-
Description: The command should be {{./control.sh --topology}} and should
print a short summary about the current topology (topology version, number of
client nodes, number of server nodes, baseline topology information)
> Add a command to control script to print current topology version
> -
>
> Key: IGNITE-8225
> URL: https://issues.apache.org/jira/browse/IGNITE-8225
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> The command should be {{./control.sh --topology}} and should print a short
> summary about the current topology (topology version, number of client nodes,
> number of server nodes, baseline topology information)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8225) Add a command to control script to print current topology version
[
https://issues.apache.org/jira/browse/IGNITE-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-8225:
-
Fix Version/s: 2.5
> Add a command to control script to print current topology version
> -
>
> Key: IGNITE-8225
> URL: https://issues.apache.org/jira/browse/IGNITE-8225
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> The command should be {{./control.sh --topology}} and should print a short
> summary about the current topology (topology version, number of client nodes,
> number of server nodes, baseline topology information)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8226) Thousands of warning messages per second in log files.
Oleg Ostanin created IGNITE-8226: Summary: Thousands of warning messages per second in log files. Key: IGNITE-8226 URL: https://issues.apache.org/jira/browse/IGNITE-8226 Project: Ignite Issue Type: Improvement Reporter: Oleg Ostanin Sometimes I see this message in log file: [2018-04-11 15:45:30,999][WARN ][sys-#454] Partition has been scheduled for rebalancing due to outdated update counter [nodeId=bed11708-090f-4e44-a1a7-e3d2b717fcb2, grp=cache_group_5, partId=239, haveHistory=false] The problem is that there is about 4 messages per 2 seconds. Also this message: [2018-04-11 15:03:39,997][WARN ][sys-#75] Stale update for single partition map update (will ignore) [grp=cache_group_46, exchId=null, curMap=GridDhtPartitionMap [moving=1024, top=AffinityTopologyVersion [topVer=4, minorTopVer=1], updateSeq=6, size=1024], newMap=GridDhtPartitionMap [moving=1024, top=AffinityTopologyVersion [topVer=4, minorTopVer=1], updateSeq=6, size=1024]] appears about 1 times per 2 seconds. Can we move this messages to debug level or do something else? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8129) JDBC: JdbcThinConnectionSSLTest.testDefaultContext
[
https://issues.apache.org/jira/browse/IGNITE-8129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434039#comment-16434039
]
Taras Ledkov commented on IGNITE-8129:
--
[~vozerov], please take a look and merge the patch.
> JDBC: JdbcThinConnectionSSLTest.testDefaultContext
> --
>
> Key: IGNITE-8129
> URL: https://issues.apache.org/jira/browse/IGNITE-8129
> Project: Ignite
> Issue Type: Bug
>Reporter: Peter Ivanov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> Test fails under strange conditions: it runs successful if is executed by
> {{mvn test}} command and fails if is executed by {{mvn surefire:test}}. Seems
> some maven reactor dependencies and/or race condition problems.
> {code}
> [2018-04-04 05:52:26,389][ERROR][main][root] Test failed.
> java.sql.SQLException: Failed to SSL connect to server
> [url=jdbc:ignite:thin://127.0.0.1:10800]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinSSLUtil.createSSLSocket(JdbcThinSSLUtil.java:93)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.connect(JdbcThinTcpIo.java:214)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.start(JdbcThinTcpIo.java:156)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.start(JdbcThinTcpIo.java:131)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.ensureConnected(JdbcThinConnection.java:156)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.(JdbcThinConnection.java:145)
> at
> org.apache.ignite.IgniteJdbcThinDriver.connect(IgniteJdbcThinDriver.java:157)
> at java.sql.DriverManager.getConnection(DriverManager.java:664)
> at java.sql.DriverManager.getConnection(DriverManager.java:270)
> at
> org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection
> during handshake
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:992)
> at
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinSSLUtil.createSSLSocket(JdbcThinSSLUtil.java:88)
> ... 18 more
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
> at sun.security.ssl.InputRecord.read(InputRecord.java:505)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
> ... 22 more
> [08:54:52][org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext]
> java.sql.SQLException: Failed to SSL connect to server
> [url=jdbc:ignite:thin://127.0.0.1:10800]
> [08:54:52]
> [org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext]
> java.sql.SQLException: Failed to SSL connect to server
> [url=jdbc:ignite:thin://127.0.0.1:10800]
> at
> org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
> Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection
> during handshake
> at
> org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
> at
> org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8226) Thousands of warning messages per second in log files.
[ https://issues.apache.org/jira/browse/IGNITE-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Kovalenko reassigned IGNITE-8226: --- Assignee: Pavel Kovalenko > Thousands of warning messages per second in log files. > -- > > Key: IGNITE-8226 > URL: https://issues.apache.org/jira/browse/IGNITE-8226 > Project: Ignite > Issue Type: Improvement >Reporter: Oleg Ostanin >Assignee: Pavel Kovalenko >Priority: Minor > > Sometimes I see this message in log file: > [2018-04-11 15:45:30,999][WARN ][sys-#454] Partition has been scheduled for > rebalancing due to outdated update counter > [nodeId=bed11708-090f-4e44-a1a7-e3d2b717fcb2, grp=cache_group_5, partId=239, > haveHistory=false] > The problem is that there is about 4 messages per 2 seconds. > Also this message: > [2018-04-11 15:03:39,997][WARN ][sys-#75] Stale update for single partition > map update (will ignore) [grp=cache_group_46, exchId=null, > curMap=GridDhtPartitionMap [moving=1024, top=AffinityTopologyVersion > [topVer=4, minorTopVer=1], updateSeq=6, size=1024], > newMap=GridDhtPartitionMap [moving=1024, top=AffinityTopologyVersion > [topVer=4, minorTopVer=1], updateSeq=6, size=1024]] > appears about 1 times per 2 seconds. > > Can we move this messages to debug level or do something else? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8226) Thousands of warning messages per second in log files.
[ https://issues.apache.org/jira/browse/IGNITE-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Kovalenko updated IGNITE-8226: Component/s: cache > Thousands of warning messages per second in log files. > -- > > Key: IGNITE-8226 > URL: https://issues.apache.org/jira/browse/IGNITE-8226 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Oleg Ostanin >Assignee: Pavel Kovalenko >Priority: Minor > Fix For: 2.5 > > > Sometimes I see this message in log file: > [2018-04-11 15:45:30,999][WARN ][sys-#454] Partition has been scheduled for > rebalancing due to outdated update counter > [nodeId=bed11708-090f-4e44-a1a7-e3d2b717fcb2, grp=cache_group_5, partId=239, > haveHistory=false] > The problem is that there is about 4 messages per 2 seconds. > Also this message: > [2018-04-11 15:03:39,997][WARN ][sys-#75] Stale update for single partition > map update (will ignore) [grp=cache_group_46, exchId=null, > curMap=GridDhtPartitionMap [moving=1024, top=AffinityTopologyVersion > [topVer=4, minorTopVer=1], updateSeq=6, size=1024], > newMap=GridDhtPartitionMap [moving=1024, top=AffinityTopologyVersion > [topVer=4, minorTopVer=1], updateSeq=6, size=1024]] > appears about 1 times per 2 seconds. > > Can we move this messages to debug level or do something else? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8226) Thousands of warning messages per second in log files.
[ https://issues.apache.org/jira/browse/IGNITE-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Kovalenko updated IGNITE-8226: Fix Version/s: 2.5 > Thousands of warning messages per second in log files. > -- > > Key: IGNITE-8226 > URL: https://issues.apache.org/jira/browse/IGNITE-8226 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Oleg Ostanin >Assignee: Pavel Kovalenko >Priority: Minor > Fix For: 2.5 > > > Sometimes I see this message in log file: > [2018-04-11 15:45:30,999][WARN ][sys-#454] Partition has been scheduled for > rebalancing due to outdated update counter > [nodeId=bed11708-090f-4e44-a1a7-e3d2b717fcb2, grp=cache_group_5, partId=239, > haveHistory=false] > The problem is that there is about 4 messages per 2 seconds. > Also this message: > [2018-04-11 15:03:39,997][WARN ][sys-#75] Stale update for single partition > map update (will ignore) [grp=cache_group_46, exchId=null, > curMap=GridDhtPartitionMap [moving=1024, top=AffinityTopologyVersion > [topVer=4, minorTopVer=1], updateSeq=6, size=1024], > newMap=GridDhtPartitionMap [moving=1024, top=AffinityTopologyVersion > [topVer=4, minorTopVer=1], updateSeq=6, size=1024]] > appears about 1 times per 2 seconds. > > Can we move this messages to debug level or do something else? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7603) Waiting on reconnect future doesn't help when client reconnects after full cluster restart
[
https://issues.apache.org/jira/browse/IGNITE-7603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434052#comment-16434052
]
Ilya Kasnacheev commented on IGNITE-7603:
-
[~agoncharuk] amended fix ready for review, tests passed
> Waiting on reconnect future doesn't help when client reconnects after full
> cluster restart
> --
>
> Key: IGNITE-7603
> URL: https://issues.apache.org/jira/browse/IGNITE-7603
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Attachments: ClientReconnectAfterClusterRestartTest.java
>
>
> See attached modified test. It will fail on
> {code:java}
> icde.reconnectFuture().get();
> assertNull(client.getOrCreateCache(CACHE_PARAMS).get(1L));{code}
> about 20% of time. I expect that I can get cache after waiting on reconnect
> future.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8226) Thousands of warning messages per second in log files.
[ https://issues.apache.org/jira/browse/IGNITE-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434084#comment-16434084 ] ASF GitHub Bot commented on IGNITE-8226: GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3796 IGNITE-8226 Logs minor improvement. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8226 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3796.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3796 commit fb9372fde043bd349ab6a1660a1b7dabb7453b46 Author: Pavel Kovalenko Date: 2018-04-11T15:25:12Z IGNITE-8226 Hide not important warn messages. > Thousands of warning messages per second in log files. > -- > > Key: IGNITE-8226 > URL: https://issues.apache.org/jira/browse/IGNITE-8226 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Oleg Ostanin >Assignee: Pavel Kovalenko >Priority: Minor > Fix For: 2.5 > > > Sometimes I see this message in log file: > [2018-04-11 15:45:30,999][WARN ][sys-#454] Partition has been scheduled for > rebalancing due to outdated update counter > [nodeId=bed11708-090f-4e44-a1a7-e3d2b717fcb2, grp=cache_group_5, partId=239, > haveHistory=false] > The problem is that there is about 4 messages per 2 seconds. > Also this message: > [2018-04-11 15:03:39,997][WARN ][sys-#75] Stale update for single partition > map update (will ignore) [grp=cache_group_46, exchId=null, > curMap=GridDhtPartitionMap [moving=1024, top=AffinityTopologyVersion > [topVer=4, minorTopVer=1], updateSeq=6, size=1024], > newMap=GridDhtPartitionMap [moving=1024, top=AffinityTopologyVersion > [topVer=4, minorTopVer=1], updateSeq=6, size=1024]] > appears about 1 times per 2 seconds. > > Can we move this messages to debug level or do something else? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8141) Improve OS config suggestions: SWAPPINESS
[ https://issues.apache.org/jira/browse/IGNITE-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434121#comment-16434121 ] Dmitriy Pavlov commented on IGNITE-8141: [~agoncharuk], is idea of this ticket to suggest SWAPPINESS in (0,10) instead of exact value 10 valid? Do we need advicing 0 in case of PDS mode? > Improve OS config suggestions: SWAPPINESS > - > > Key: IGNITE-8141 > URL: https://issues.apache.org/jira/browse/IGNITE-8141 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.4 >Reporter: Reed Sandberg >Assignee: Reed Sandberg >Priority: Minor > Labels: pull-request-available > Fix For: 2.6 > > > Acknowledge suggested SWAPPINESS OS param adjustment using a range (<= 10). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8227) Research possibility and implement JUnit test failure handler for TeamCity
Dmitriy Pavlov created IGNITE-8227: -- Summary: Research possibility and implement JUnit test failure handler for TeamCity Key: IGNITE-8227 URL: https://issues.apache.org/jira/browse/IGNITE-8227 Project: Ignite Issue Type: Test Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Fix For: 2.6 After IEP-14 we found a lot of TC failures involving unexpected nodes stop. To avoid suites exit codes, tests have NoOpFailureHandler as default. But instead of this, better handler could be stopNode + fail currenly running test with message. This default allows to identify such failures without log-message fail condition. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
