[jira] [Created] (IGNITE-8644) CacheMetrics.getCacheMisses() returns incorrect values
Roman Guseinov created IGNITE-8644: -- Summary: CacheMetrics.getCacheMisses() returns incorrect values Key: IGNITE-8644 URL: https://issues.apache.org/jira/browse/IGNITE-8644 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.4 Reporter: Roman Guseinov Attachments: CacheMissesMetricTest.java It looks like the correct value of this metric can be achieved only on a cluster of one node. `ignite.cache(CACHE_NAME).metrics().getCacheMisses()` returns different values depending on cache type, backups count, nodes count, node type. The test is attached [^CacheMissesMetricTest.java]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6241) Integrate with Kubernetes StatefulSet to support Ignite Persistence
[ https://issues.apache.org/jira/browse/IGNITE-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494645#comment-16494645 ] Peter Ivanov commented on IGNITE-6241: -- [~guseinov], thanks a lot! > Integrate with Kubernetes StatefulSet to support Ignite Persistence > --- > > Key: IGNITE-6241 > URL: https://issues.apache.org/jira/browse/IGNITE-6241 > Project: Ignite > Issue Type: New Feature >Reporter: Denis Magda >Assignee: Peter Ivanov >Priority: Critical > Fix For: 2.6 > > Attachments: grid.yaml, openshift-pds.xml, service.yaml, > tutorial_k8s.txt > > > Ignite Kubernetes integration has to support StatefulSet which enables Ignite > Persistence usage in Kubernetes deployments. More details are here: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-Persistence-on-Kubernetes-td16396.html > See how it's done for Cassandra and MongoDB: > * https://kubernetes.io/docs/tutorials/stateful-application/cassandra/ > * https://kubernetes.io/docs/tutorials/stateless-application/guestbook/ > We can reach out K8 folks and ask to add a prepared Ignite tutorial to the > list. > Good reading on the stateful set: > https://lenadroid.github.io/posts/stateful-sets-kubernetes-azure.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8643) Web console: Invalid chart width
[ https://issues.apache.org/jira/browse/IGNITE-8643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-8643: Assignee: Dmitriy Shabalin (was: Alexey Kuznetsov) [~Dmitriyff], Please take a look. > Web console: Invalid chart width > > > Key: IGNITE-8643 > URL: https://issues.apache.org/jira/browse/IGNITE-8643 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Vasiliy Sisko >Assignee: Dmitriy Shabalin >Priority: Major > Attachments: Selection_133.png > > > Result charts are to wide and cut from right. > To reproduce: > # Run demo. > # Open Demo query page. > # Switch result of any query to chart presentation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8643) Web console: Invalid chart width
Vasiliy Sisko created IGNITE-8643: - Summary: Web console: Invalid chart width Key: IGNITE-8643 URL: https://issues.apache.org/jira/browse/IGNITE-8643 Project: Ignite Issue Type: Bug Affects Versions: 2.5 Reporter: Vasiliy Sisko Assignee: Alexey Kuznetsov Attachments: Selection_133.png Result charts are to wide and cut from right. To reproduce: # Run demo. # Open Demo query page. # Switch result of any query to chart presentation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6241) Integrate with Kubernetes StatefulSet to support Ignite Persistence
[ https://issues.apache.org/jira/browse/IGNITE-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494578#comment-16494578 ] Roman Guseinov commented on IGNITE-6241: Here are examples of deployment files: [^service.yaml] [^grid.yaml] [^openshift-pds.xml] A small tutorial is here: [^tutorial_k8s.txt] > Integrate with Kubernetes StatefulSet to support Ignite Persistence > --- > > Key: IGNITE-6241 > URL: https://issues.apache.org/jira/browse/IGNITE-6241 > Project: Ignite > Issue Type: New Feature >Reporter: Denis Magda >Assignee: Peter Ivanov >Priority: Critical > Fix For: 2.6 > > Attachments: grid.yaml, openshift-pds.xml, service.yaml, > tutorial_k8s.txt > > > Ignite Kubernetes integration has to support StatefulSet which enables Ignite > Persistence usage in Kubernetes deployments. More details are here: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-Persistence-on-Kubernetes-td16396.html > See how it's done for Cassandra and MongoDB: > * https://kubernetes.io/docs/tutorials/stateful-application/cassandra/ > * https://kubernetes.io/docs/tutorials/stateless-application/guestbook/ > We can reach out K8 folks and ask to add a prepared Ignite tutorial to the > list. > Good reading on the stateful set: > https://lenadroid.github.io/posts/stateful-sets-kubernetes-azure.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6241) Integrate with Kubernetes StatefulSet to support Ignite Persistence
[ https://issues.apache.org/jira/browse/IGNITE-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov updated IGNITE-6241: --- Attachment: tutorial_k8s.txt service.yaml openshift-pds.xml grid.yaml > Integrate with Kubernetes StatefulSet to support Ignite Persistence > --- > > Key: IGNITE-6241 > URL: https://issues.apache.org/jira/browse/IGNITE-6241 > Project: Ignite > Issue Type: New Feature >Reporter: Denis Magda >Assignee: Peter Ivanov >Priority: Critical > Fix For: 2.6 > > Attachments: grid.yaml, openshift-pds.xml, service.yaml, > tutorial_k8s.txt > > > Ignite Kubernetes integration has to support StatefulSet which enables Ignite > Persistence usage in Kubernetes deployments. More details are here: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-Persistence-on-Kubernetes-td16396.html > See how it's done for Cassandra and MongoDB: > * https://kubernetes.io/docs/tutorials/stateful-application/cassandra/ > * https://kubernetes.io/docs/tutorials/stateless-application/guestbook/ > We can reach out K8 folks and ask to add a prepared Ignite tutorial to the > list. > Good reading on the stateful set: > https://lenadroid.github.io/posts/stateful-sets-kubernetes-azure.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494561#comment-16494561
]
Dmitriy Setrakyan commented on IGNITE-3495:
---
[~agoncharuk], any idea what to do with this ticket? Should it be fixed or
closed as "Won't Fix"?
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Major
> Labels: iep-6
> Fix For: 2.6
>
> Attachments: ExampleNodeStartupClient.java, IGNITE_3495.patch,
> example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Setrakyan reassigned IGNITE-3495:
-
Assignee: Alexey Goncharuk
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Major
> Labels: iep-6
> Fix For: 2.6
>
> Attachments: ExampleNodeStartupClient.java, IGNITE_3495.patch,
> example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Setrakyan updated IGNITE-3495:
--
Fix Version/s: 2.6
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Priority: Major
> Labels: iep-6
> Fix For: 2.6
>
> Attachments: ExampleNodeStartupClient.java, IGNITE_3495.patch,
> example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8550) CacheAbstractJdbcStore expects merge to always return 1 but MySQL may also return 2 or 0
[
https://issues.apache.org/jira/browse/IGNITE-8550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Setrakyan reassigned IGNITE-8550:
-
Assignee: Vladimir Ozerov
> CacheAbstractJdbcStore expects merge to always return 1 but MySQL may also
> return 2 or 0
>
>
> Key: IGNITE-8550
> URL: https://issues.apache.org/jira/browse/IGNITE-8550
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Stanislav Lukyanov
>Assignee: Vladimir Ozerov
>Priority: Minor
> Labels: newbie
> Fix For: 2.6
>
>
> CacheAbstractJdbcStore.write attempts to execute a merge update if it is
> available, and expects the merge to always return 1 (as the number of updated
> entries is always 1).
> However, MySQL's `INSERT ... ON DUPLICATE KEY UPDATE`
> (https://dev.mysql.com/doc/refman/8.0/en/insert-on-duplicate.html) may return
> 0 or 2, depending on what was updated:
> {quote}With ON DUPLICATE KEY UPDATE, the affected-rows value per row is 1 if
> the row is inserted as a new row, 2 if an existing row is updated, and 0 if
> an existing row is set to its current values.{quote}
> Because of that, CacheAbstractJdbcStore may report a false warning.
> Need to consider either removing the warning or special-case the MySQL
> dialect to allow to return values other than 1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8549) Include SSL related parameters for JDBC/ODBC
[
https://issues.apache.org/jira/browse/IGNITE-8549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Garg reassigned IGNITE-8549:
---
Assignee: Denis Magda (was: Prachi Garg)
> Include SSL related parameters for JDBC/ODBC
>
>
> Key: IGNITE-8549
> URL: https://issues.apache.org/jira/browse/IGNITE-8549
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Prachi Garg
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.5
>
>
> DRIVER=\{Apache
> Ignite};ADDRESS=13.56.76.37:9954;USER=ignite;PASSWORD=1mSBcc8loX;*SSL_MODE=require;SSL_KEY_FILE=client.pem;SSL_CERT_FILE=client.pem;SSL_CA_FILE=client.pem*
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8549) Include SSL related parameters for JDBC/ODBC
[
https://issues.apache.org/jira/browse/IGNITE-8549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494552#comment-16494552
]
Prachi Garg commented on IGNITE-8549:
-
[~dmagda], Please review the following sections -
* SSL related parameters -
[https://apacheignite-sql.readme.io/docs/connection-string-and-dsn#section-supported-arguments|https://apacheignite-sql.readme.io/v2.5/docs/connection-string-and-dsn#section-supported-arguments]
* Authentication example -
https://apacheignite-sql.readme.io/docs/connection-string-and-dsn#section-connection-string-samples
> Include SSL related parameters for JDBC/ODBC
>
>
> Key: IGNITE-8549
> URL: https://issues.apache.org/jira/browse/IGNITE-8549
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Prachi Garg
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.5
>
>
> DRIVER=\{Apache
> Ignite};ADDRESS=13.56.76.37:9954;USER=ignite;PASSWORD=1mSBcc8loX;*SSL_MODE=require;SSL_KEY_FILE=client.pem;SSL_CERT_FILE=client.pem;SSL_CA_FILE=client.pem*
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8549) Include SSL related parameters for JDBC/ODBC
[
https://issues.apache.org/jira/browse/IGNITE-8549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494552#comment-16494552
]
Prachi Garg edited comment on IGNITE-8549 at 5/30/18 1:05 AM:
--
[~dmagda], Please review the following sections -
* SSL related parameters -
[https://apacheignite-sql.readme.io/docs/connection-string-and-dsn#section-supported-arguments|https://apacheignite-sql.readme.io/v2.5/docs/connection-string-and-dsn#section-supported-arguments]
* Authentication example -
[https://apacheignite-sql.readme.io/docs/connection-string-and-dsn#section-connection-string-samples]
was (Author: pgarg):
[~dmagda], Please review the following sections -
* SSL related parameters -
[https://apacheignite-sql.readme.io/docs/connection-string-and-dsn#section-supported-arguments|https://apacheignite-sql.readme.io/v2.5/docs/connection-string-and-dsn#section-supported-arguments]
* Authentication example -
https://apacheignite-sql.readme.io/docs/connection-string-and-dsn#section-connection-string-samples
> Include SSL related parameters for JDBC/ODBC
>
>
> Key: IGNITE-8549
> URL: https://issues.apache.org/jira/browse/IGNITE-8549
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Prachi Garg
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.5
>
>
> DRIVER=\{Apache
> Ignite};ADDRESS=13.56.76.37:9954;USER=ignite;PASSWORD=1mSBcc8loX;*SSL_MODE=require;SSL_KEY_FILE=client.pem;SSL_CERT_FILE=client.pem;SSL_CA_FILE=client.pem*
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7587) SQL COPY: document the command
[ https://issues.apache.org/jira/browse/IGNITE-7587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg reassigned IGNITE-7587: --- Assignee: Denis Magda (was: Prachi Garg) > SQL COPY: document the command > -- > > Key: IGNITE-7587 > URL: https://issues.apache.org/jira/browse/IGNITE-7587 > Project: Ignite > Issue Type: Improvement > Components: documentation, sql >Affects Versions: 2.4 >Reporter: Kirill Shirokov >Assignee: Denis Magda >Priority: Major > Fix For: 2.5 > > > SQL COPY command needs to be documented at readme.io. > COPY command is supported for Java API and JDBC only in 2.5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7587) SQL COPY: document the command
[ https://issues.apache.org/jira/browse/IGNITE-7587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494534#comment-16494534 ] Prachi Garg commented on IGNITE-7587: - [~dmagda], Please review - https://apacheignite-sql.readme.io/v2.5/docs/copy > SQL COPY: document the command > -- > > Key: IGNITE-7587 > URL: https://issues.apache.org/jira/browse/IGNITE-7587 > Project: Ignite > Issue Type: Improvement > Components: documentation, sql >Affects Versions: 2.4 >Reporter: Kirill Shirokov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.5 > > > SQL COPY command needs to be documented at readme.io. > COPY command is supported for Java API and JDBC only in 2.5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7524) JDBC: Add a note about connection non-thread safety to docs
[ https://issues.apache.org/jira/browse/IGNITE-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg closed IGNITE-7524. --- > JDBC: Add a note about connection non-thread safety to docs > --- > > Key: IGNITE-7524 > URL: https://issues.apache.org/jira/browse/IGNITE-7524 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.5 > > > Our JDBC connection is not thread safe. Let's mention it in docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8549) Include SSL related parameters for JDBC/ODBC
[
https://issues.apache.org/jira/browse/IGNITE-8549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Garg updated IGNITE-8549:
Component/s: documentation
> Include SSL related parameters for JDBC/ODBC
>
>
> Key: IGNITE-8549
> URL: https://issues.apache.org/jira/browse/IGNITE-8549
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Prachi Garg
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.5
>
>
> DRIVER=\{Apache
> Ignite};ADDRESS=13.56.76.37:9954;USER=ignite;PASSWORD=1mSBcc8loX;*SSL_MODE=require;SSL_KEY_FILE=client.pem;SSL_CERT_FILE=client.pem;SSL_CA_FILE=client.pem*
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7524) JDBC: Add a note about connection non-thread safety to docs
[ https://issues.apache.org/jira/browse/IGNITE-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494423#comment-16494423 ] Denis Magda commented on IGNITE-7524: - [~pgarg], please check the spelling and close the ticket. > JDBC: Add a note about connection non-thread safety to docs > --- > > Key: IGNITE-7524 > URL: https://issues.apache.org/jira/browse/IGNITE-7524 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Major > Fix For: 2.5 > > > Our JDBC connection is not thread safe. Let's mention it in docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7524) JDBC: Add a note about connection non-thread safety to docs
[ https://issues.apache.org/jira/browse/IGNITE-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-7524: --- Assignee: Prachi Garg (was: Taras Ledkov) > JDBC: Add a note about connection non-thread safety to docs > --- > > Key: IGNITE-7524 > URL: https://issues.apache.org/jira/browse/IGNITE-7524 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.5 > > > Our JDBC connection is not thread safe. Let's mention it in docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7587) SQL COPY: document the command
[ https://issues.apache.org/jira/browse/IGNITE-7587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494422#comment-16494422 ] Denis Magda commented on IGNITE-7587: - [~pgarg], please use this page for COPY command: https://apacheignite-sql.readme.io/v2.5/docs/copy > SQL COPY: document the command > -- > > Key: IGNITE-7587 > URL: https://issues.apache.org/jira/browse/IGNITE-7587 > Project: Ignite > Issue Type: Improvement > Components: documentation, sql >Affects Versions: 2.4 >Reporter: Kirill Shirokov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.5 > > > SQL COPY command needs to be documented at readme.io. > COPY command is supported for Java API and JDBC only in 2.5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7903) Explain how to tune performance by using WAL modes
[ https://issues.apache.org/jira/browse/IGNITE-7903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-7903: Fix Version/s: (was: 2.5) 2.6 > Explain how to tune performance by using WAL modes > -- > > Key: IGNITE-7903 > URL: https://issues.apache.org/jira/browse/IGNITE-7903 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.6 > > > Explain how to improve performance by switching between the WAL modes: > https://apacheignite.readme.io/docs/durable-memory-tuning > Basically, LOG_ONLY and BACKGROUND mode can be considered as an alternative > for FULL_SYNC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8305) Update metrics page with new storage and memory related metics
[ https://issues.apache.org/jira/browse/IGNITE-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-8305. - Resolution: Fixed Prachi, please create "Memory Usage Calculation" section and explain how to find the size of a single node and the whole cluster. > Update metrics page with new storage and memory related metics > -- > > Key: IGNITE-8305 > URL: https://issues.apache.org/jira/browse/IGNITE-8305 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.5 > > > The new metrics are added by the endeavor: > https://issues.apache.org/jira/browse/IGNITE-8078 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8305) Update metrics page with new storage and memory related metics
[ https://issues.apache.org/jira/browse/IGNITE-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-8305. --- > Update metrics page with new storage and memory related metics > -- > > Key: IGNITE-8305 > URL: https://issues.apache.org/jira/browse/IGNITE-8305 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.5 > > > The new metrics are added by the endeavor: > https://issues.apache.org/jira/browse/IGNITE-8078 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8460) Document JDBC thin driver DataSource
[ https://issues.apache.org/jira/browse/IGNITE-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-8460. --- > Document JDBC thin driver DataSource > > > Key: IGNITE-8460 > URL: https://issues.apache.org/jira/browse/IGNITE-8460 > Project: Ignite > Issue Type: Task > Components: documentation, jdbc >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Major > Fix For: 2.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7867) Document new feature in REST: possibility to get objects inserted via API or SQL
[ https://issues.apache.org/jira/browse/IGNITE-7867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494386#comment-16494386 ] Denis Magda commented on IGNITE-7867: - Looks good, thanks a lot! > Document new feature in REST: possibility to get objects inserted via API or > SQL > > > Key: IGNITE-7867 > URL: https://issues.apache.org/jira/browse/IGNITE-7867 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Kuznetsov >Assignee: Denis Magda >Priority: Major > Fix For: 2.5 > > > [~pgarg] Please document changes from IGNITE-7803. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7867) Document new feature in REST: possibility to get objects inserted via API or SQL
[ https://issues.apache.org/jira/browse/IGNITE-7867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-7867. --- > Document new feature in REST: possibility to get objects inserted via API or > SQL > > > Key: IGNITE-7867 > URL: https://issues.apache.org/jira/browse/IGNITE-7867 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Kuznetsov >Assignee: Denis Magda >Priority: Major > Fix For: 2.5 > > > [~pgarg] Please document changes from IGNITE-7803. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7942) Document streaming in thin JDBC driver
[ https://issues.apache.org/jira/browse/IGNITE-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494383#comment-16494383 ] Denis Magda commented on IGNITE-7942: - Looks good. However, I bet this had to be documented in a more generic place because the streaming should work for all the SQL interfaces. Raised a question on dev. > Document streaming in thin JDBC driver > -- > > Key: IGNITE-7942 > URL: https://issues.apache.org/jira/browse/IGNITE-7942 > Project: Ignite > Issue Type: Task > Components: documentation, jdbc, sql >Reporter: Alexander Paschenko >Assignee: Denis Magda >Priority: Major > Fix For: 2.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7942) Document streaming in thin JDBC driver
[ https://issues.apache.org/jira/browse/IGNITE-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-7942. --- > Document streaming in thin JDBC driver > -- > > Key: IGNITE-7942 > URL: https://issues.apache.org/jira/browse/IGNITE-7942 > Project: Ignite > Issue Type: Task > Components: documentation, jdbc, sql >Reporter: Alexander Paschenko >Assignee: Denis Magda >Priority: Major > Fix For: 2.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-6587) Ignite watchdog service
[
https://issues.apache.org/jira/browse/IGNITE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483947#comment-16483947
]
Andrey Kuznetsov edited comment on IGNITE-6587 at 5/29/18 7:17 PM:
---
Changing critical threads to {{GridWorkers}} has been brought to separate
issue, since it has its own value.
was (Author: andrey-kuznetsov):
Changing critical threads to {{GridWorkers}} has been brought to separate
issue, since it has it's own value.
> Ignite watchdog service
> ---
>
> Key: IGNITE-6587
> URL: https://issues.apache.org/jira/browse/IGNITE-6587
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 2.2
>Reporter: Alexey Goncharuk
>Assignee: Andrey Kuznetsov
>Priority: Major
> Labels: IEP-5
> Fix For: 2.6
>
> Attachments: watchdog.sh
>
>
> As described in [1], each Ignite node has a number of system-critical
> threads. We should implement a periodic check that calls failure handler when
> one of the following conditions has been detected:
> * Critical thread is not alive anymore.
> * Critical thread 'hangs' for a long time, e.g. while executing a task
> extracted from task queue.
> In case of failure condition, call stacks of all threads should be logged
> before invoking failure handler.
> Actual list of system-critical threads can be found at [1].
> Implementations based on separate diagnostic thread seem fragile, cause this
> thread become a vulnerable point with respect to thread termination and CPU
> resource starvation. So we are to use self-monitoring approach: critical
> threads themselves should monitor each other.
> Currently we have {{o.a.i.internal.worker.WorkersRegistry}} facility that
> fits best to store and track system critical threads. All of them should be
> refactored to be {{GridWorker's}} and added to {{WorkersRegistry}}. Each
> worker should periodically choose some subset of peer workers and check
> whether
> * All of them are alive.
> * All of them are actively running.
> It's required to add a 'heartbeat' timestamp to worker in order to implement
> latter check. Additionally, infinite queue polls, waits on monitors or thread
> parks should be refactored to their timed equivalents in system critical
> threads.
> Monitoring parameters (enable/disable, check interval, thread 'hang'
> threshold, etc.) are to be set via system properties.
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg updated IGNITE-7611: Fix Version/s: (was: 2.5) 2.6 > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.6 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8642) Failure processor should dump state of all threads
[
https://issues.apache.org/jira/browse/IGNITE-8642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494067#comment-16494067
]
ASF GitHub Bot commented on IGNITE-8642:
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/4091
IGNITE-8642: Added thread dumping to FailureProcessor.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrey-kuznetsov/ignite ignite-8642
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4091.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 #4091
commit 75353527233477582856b6889b6ea6f36f13984c
Author: Andrey Kuznetsov
Date: 2018-05-29T18:59:15Z
IGNITE-8642: Added thread dumping to FailureProcessor.
> Failure processor should dump state of all threads
> --
>
> Key: IGNITE-8642
> URL: https://issues.apache.org/jira/browse/IGNITE-8642
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
>
> Failure processor should dump state of all threads before failure handler is
> invoked.
> Use {{org.apache.ignite.internal.util.IgniteUtils#dumpThreads}} method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8642) Failure processor should dump state of all threads
[
https://issues.apache.org/jira/browse/IGNITE-8642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kuznetsov updated IGNITE-8642:
-
Description:
Failure processor should dump state of all threads before failure handler will
be invoked.
Use {{org.apache.ignite.internal.util.IgniteUtils#dumpThreads}} method.
was:
Failure processor should dump state of all threads before failure processor
will be invoked.
Use {{org.apache.ignite.internal.util.IgniteUtils#dumpThreads}} method.
> Failure processor should dump state of all threads
> --
>
> Key: IGNITE-8642
> URL: https://issues.apache.org/jira/browse/IGNITE-8642
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
>
> Failure processor should dump state of all threads before failure handler
> will be invoked.
> Use {{org.apache.ignite.internal.util.IgniteUtils#dumpThreads}} method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8642) Failure processor should dump state of all threads
[
https://issues.apache.org/jira/browse/IGNITE-8642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kuznetsov updated IGNITE-8642:
-
Description:
Failure processor should dump state of all threads before failure handler is
invoked.
Use {{org.apache.ignite.internal.util.IgniteUtils#dumpThreads}} method.
was:
Failure processor should dump state of all threads before failure handler will
be invoked.
Use {{org.apache.ignite.internal.util.IgniteUtils#dumpThreads}} method.
> Failure processor should dump state of all threads
> --
>
> Key: IGNITE-8642
> URL: https://issues.apache.org/jira/browse/IGNITE-8642
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
>
> Failure processor should dump state of all threads before failure handler is
> invoked.
> Use {{org.apache.ignite.internal.util.IgniteUtils#dumpThreads}} method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8642) Failure processor should dump state of all threads
[
https://issues.apache.org/jira/browse/IGNITE-8642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kuznetsov reassigned IGNITE-8642:
Assignee: Andrey Kuznetsov
> Failure processor should dump state of all threads
> --
>
> Key: IGNITE-8642
> URL: https://issues.apache.org/jira/browse/IGNITE-8642
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
>
> Failure processor should dump state of all threads before failure processor
> will be invoked.
> Use {{org.apache.ignite.internal.util.IgniteUtils#dumpThreads}} method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8603) Add JMX-metric to cluster: baseline nodes
[
https://issues.apache.org/jira/browse/IGNITE-8603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494019#comment-16494019
]
Ivan Rakov commented on IGNITE-8603:
[~dgladkikh], some comments:
1. Code style
1.1. #getTotalBaselineNodes and #getActiveBaselineNodes in
ClusterLocalNodeMetricsMXBeanImpl class lack {@inheritDoc}
1.2. Semantic units of #getTotalBaselineNodes body should be separated by blank
lines - check "Whitespaces and empty lines" section of
https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines
1.3. One-liner in #getTotalBaselineNodes body shouldn't be enclosed in curly
braces, see "Braces and Identation" section
1.4. Points 1.2 and 1.3 relate to ClusterMetricsMXBeanImpl as well
2. I think, it would be good to add test case when non-baseline server node is
present in the cluster
3. ClusterBaselineNodesMetricsSelfTest is not included in any test suite
4. Please schedule Run All on public TeamCity and attach link here
> Add JMX-metric to cluster: baseline nodes
> -
>
> Key: IGNITE-8603
> URL: https://issues.apache.org/jira/browse/IGNITE-8603
> Project: Ignite
> Issue Type: Improvement
>Reporter: Dmitriy Gladkikh
>Assignee: Dmitriy Gladkikh
>Priority: Major
> Fix For: 2.6
>
>
> Need to add a baseline nodes on JMX:
> {code:java}
> int org.apache.ignite.mxbean.ClusterMetricsMXBean#getTotalBaselineNodes
> int org.apache.ignite.mxbean.ClusterMetricsMXBean#getActiveBaselineNodes
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8642) Failure processor should dump state of all threads
Andrey Gura created IGNITE-8642:
---
Summary: Failure processor should dump state of all threads
Key: IGNITE-8642
URL: https://issues.apache.org/jira/browse/IGNITE-8642
Project: Ignite
Issue Type: Improvement
Reporter: Andrey Gura
Fix For: 2.6
Failure processor should dump state of all threads before failure processor
will be invoked.
Use {{org.apache.ignite.internal.util.IgniteUtils#dumpThreads}} method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8641) SpringDataExample should use example-ignite.xml config
[
https://issues.apache.org/jira/browse/IGNITE-8641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8641:
Description:
{{SpringDataExample}} uses
{{org.apache.ignite.examples.springdata.SpringAppCfg}} as Spring configuration
while all other examples use {{example-ignite.xml}} configuration file.
It leads to inconsistent examples behaviour.
was:
{{SpringDataExample}} uses
{{org.apache.ignite.examples.springdata.SpringAppCfg}} as Spring configuration
while all other example uses {{example-ignite.xml}} configuration file.
It leads to inconsistent examples behaviour.
> SpringDataExample should use example-ignite.xml config
> --
>
> Key: IGNITE-8641
> URL: https://issues.apache.org/jira/browse/IGNITE-8641
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Gura
>Priority: Major
> Labels: newbie
> Fix For: 2.6
>
>
> {{SpringDataExample}} uses
> {{org.apache.ignite.examples.springdata.SpringAppCfg}} as Spring
> configuration while all other examples use {{example-ignite.xml}}
> configuration file.
> It leads to inconsistent examples behaviour.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8641) SpringDataExample should use example-ignite.xml config
Andrey Gura created IGNITE-8641:
---
Summary: SpringDataExample should use example-ignite.xml config
Key: IGNITE-8641
URL: https://issues.apache.org/jira/browse/IGNITE-8641
Project: Ignite
Issue Type: Bug
Reporter: Andrey Gura
Fix For: 2.6
{{SpringDataExample}} uses
{{org.apache.ignite.examples.springdata.SpringAppCfg}} as Spring configuration
while all other example uses {{example-ignite.xml}} configuration file.
It leads to inconsistent examples behaviour.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8293) BinaryUtils#isCustomJavaSerialization fails when only readObject is declared in a class
[
https://issues.apache.org/jira/browse/IGNITE-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493947#comment-16493947
]
Andrey Gura commented on IGNITE-8293:
-
[~MihkelJ], I've reviewed your patch and have a comment:
{{BinaryUtilsIsCustomSerializationTest}} doesn't contains Apache 2.0 license
header and javadocs. Also this test uses JUnit 4 while we still use JUnit 3.
Test is ok, but it isn't related with binary marshaller. I think it would be
great if you remove your tests and add test cases to
{{BinaryMarshallerSelfTest}}. Use existing test cases as examples. Is there any
chance that you fix this comment?
> BinaryUtils#isCustomJavaSerialization fails when only readObject is declared
> in a class
> ---
>
> Key: IGNITE-8293
> URL: https://issues.apache.org/jira/browse/IGNITE-8293
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.4
>Reporter: MihkelJ
>Assignee: MihkelJ
>Priority: Minor
> Fix For: 2.6
>
> Attachments: IGNITE-8293.patch
>
>
> Consider this class:
>
> {code:java}
> public class Test implements Serializable {
> private transient AtomicBoolean dirty = new AtomicBoolean(false);
> private void readObject(java.io.ObjectInputStream in) throws IOException,
> ClassNotFoundException {
> dirty = new AtomicBoolean(false);
> }
> //methods to check and mark class as dirty
> }{code}
> {{isCustomJavaSerialization}} will get a {{NoSuchMethodException}} when
> trying to grab the {{writeObject}} method and falsely conclude that Test
> doesn't use custom serialization.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8610) Searching checkpoint / WAL history for rebalancing is not properly working in case of local/global WAL disabling
[ https://issues.apache.org/jira/browse/IGNITE-8610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493856#comment-16493856 ] ASF GitHub Bot commented on IGNITE-8610: GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/4090 IGNITE-8610 Checkpoint history search fix + refactoring You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8610 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4090.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 #4090 commit df3fb2a24d4d43771094e56fea6680f23e3790e6 Author: Pavel Kovalenko Date: 2018-05-18T09:37:13Z IGNITE-8459 WIP commit 54e88d22bfd4c0b61593b4a8f0d5c319288593b7 Author: Pavel Kovalenko Date: 2018-05-18T16:22:01Z IGNITE-8459 WIP commit e8aeeea9d6c30df2ee03bfada3a8a399cfef7b6b Author: Pavel Kovalenko Date: 2018-05-21T12:42:33Z IGNITE-8459 WIP commit 7d58eb9e3c3fa2358c7937ce3f73715d850a33f1 Author: Pavel Kovalenko Date: 2018-05-24T19:46:24Z IGNITE-8459 Rework. commit bd8ef85034bbf7c03d6c8b40b36fa4398a3b23ca Author: Pavel Kovalenko Date: 2018-05-24T19:50:11Z IGNITE-8459 Remove trash. commit b5addf2b44f8ebebc59823397e134d6796a7e3b6 Author: Pavel Kovalenko Date: 2018-05-25T01:18:45Z IGNITE-8459 Fixed tests. commit fe4d681ae4341accf047b8408a97a22d34f5520f Author: Pavel Kovalenko Date: 2018-05-28T12:09:21Z IGNITE-8459 Tests refactoring. commit 702b88c7466555091c95890a4aa024d869c399f3 Author: Pavel Kovalenko Date: 2018-05-28T12:14:14Z IGNITE-8459 Increase test running time. commit 5b2ccaacafb2ef3c3e02730958c7708768b7c265 Author: Pavel Kovalenko Date: 2018-05-28T13:22:54Z Merge branch 'master' into ignite-8459 # Conflicts: # modules/core/src/test/java/org/apache/ignite/internal/processors/cache/persistence/IgnitePdsCacheRebalancingAbstractTest.java commit cc2fda56ecc48ae878baffe5079d25c917a1280c Author: Pavel Kovalenko Date: 2018-05-28T14:25:30Z IGNITE-8482 Tests improvements. commit edd27a9ba264581e1d0541c2aafc30451dc469b3 Author: Pavel Kovalenko Date: 2018-05-28T14:28:18Z IGNITE-8482 Remove unused import. commit e4e1cb92e016230dc8c8b270c2f8dfe72cc3d098 Author: Pavel Kovalenko Date: 2018-05-29T14:36:01Z IGNITE-8610 WIP commit bae83681794bd02e708647494eba094a4213a9f9 Author: Pavel Kovalenko Date: 2018-05-29T16:55:22Z IGNITE-8610 WIP > Searching checkpoint / WAL history for rebalancing is not properly working in > case of local/global WAL disabling > > > Key: IGNITE-8610 > URL: https://issues.apache.org/jira/browse/IGNITE-8610 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.5 >Reporter: Pavel Kovalenko >Assignee: Pavel Kovalenko >Priority: Major > Fix For: 2.6 > > > After implementation IGNITE-6411 and IGNITE-8087 we can face with situation > when after some checkpoint, WAL was temporarily disabled and enabled again. > In this case we can't treat that checkpoint as start point to rebalance, > because WAL history after such checkpoint may contain gaps. > We should rework our checkpoint / wal history searching mechanism and ignore > such checkpoints. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8605) sqlline can't work with terminal on newer ncurses
[
https://issues.apache.org/jira/browse/IGNITE-8605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493838#comment-16493838
]
Ilya Kasnacheev commented on IGNITE-8605:
-
I've bumped to 2.14.6, it looks like working, I suggest we merge.
[~oleg-ostanin] please do.
> sqlline can't work with terminal on newer ncurses
> -
>
> Key: IGNITE-8605
> URL: https://issues.apache.org/jira/browse/IGNITE-8605
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.5
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> On Ubuntu 18.04:
> {code}
> ~/w/incubator-ignite/modules/sqlline% IGNITE_HOME=~/w/incubator-ignite .
> bin/sqlline.sh
> [ERROR] Failed to construct terminal; falling back to unsupported
> java.lang.NumberFormatException: For input string: "0x100"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.valueOf(Integer.java:766)
> at jline.internal.InfoCmp.parseInfoCmp(InfoCmp.java:59)
> at jline.UnixTerminal.parseInfoCmp(UnixTerminal.java:242)
> at jline.UnixTerminal.(UnixTerminal.java:65)
> at jline.UnixTerminal.(UnixTerminal.java:50)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at jline.TerminalFactory.getFlavor(TerminalFactory.java:211)
> at jline.TerminalFactory.create(TerminalFactory.java:102)
> at jline.TerminalFactory.get(TerminalFactory.java:186)
> at jline.TerminalFactory.get(TerminalFactory.java:192)
> at sqlline.SqlLineOpts.(SqlLineOpts.java:45)
> at sqlline.SqlLine.(SqlLine.java:54)
> at sqlline.SqlLine.start(SqlLine.java:372)
> at sqlline.SqlLine.main(SqlLine.java:265)
> [ERROR] Failed to construct terminal; falling back to unsupported
> java.lang.NumberFormatException: For input string: "0x100"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.valueOf(Integer.java:766)
> at jline.internal.InfoCmp.parseInfoCmp(InfoCmp.java:59)
> at jline.UnixTerminal.parseInfoCmp(UnixTerminal.java:242)
> at jline.UnixTerminal.(UnixTerminal.java:65)
> at jline.UnixTerminal.(UnixTerminal.java:50)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at jline.TerminalFactory.getFlavor(TerminalFactory.java:211)
> at jline.TerminalFactory.create(TerminalFactory.java:102)
> at jline.TerminalFactory.create(TerminalFactory.java:51)
> at sqlline.SqlLine.getConsoleReader(SqlLine.java:705)
> at sqlline.SqlLine.begin(SqlLine.java:639)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> sqlline version 1.3.0
> sqlline>
> ... and then history and command editing won't work
> {code}
> See also https://github.com/jline/jline2/issues/281
> I think we should manually peg jline verison to 2.14.4
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8605) sqlline can't work with terminal on newer ncurses
[
https://issues.apache.org/jira/browse/IGNITE-8605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493793#comment-16493793
]
Peter Ivanov commented on IGNITE-8605:
--
Checked fix: Ubuntu 18.04 and macOS 10.13.4 with latest ncurces works fine.
Also, can we use latest available jline version (2.14.6)?
> sqlline can't work with terminal on newer ncurses
> -
>
> Key: IGNITE-8605
> URL: https://issues.apache.org/jira/browse/IGNITE-8605
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.5
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> On Ubuntu 18.04:
> {code}
> ~/w/incubator-ignite/modules/sqlline% IGNITE_HOME=~/w/incubator-ignite .
> bin/sqlline.sh
> [ERROR] Failed to construct terminal; falling back to unsupported
> java.lang.NumberFormatException: For input string: "0x100"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.valueOf(Integer.java:766)
> at jline.internal.InfoCmp.parseInfoCmp(InfoCmp.java:59)
> at jline.UnixTerminal.parseInfoCmp(UnixTerminal.java:242)
> at jline.UnixTerminal.(UnixTerminal.java:65)
> at jline.UnixTerminal.(UnixTerminal.java:50)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at jline.TerminalFactory.getFlavor(TerminalFactory.java:211)
> at jline.TerminalFactory.create(TerminalFactory.java:102)
> at jline.TerminalFactory.get(TerminalFactory.java:186)
> at jline.TerminalFactory.get(TerminalFactory.java:192)
> at sqlline.SqlLineOpts.(SqlLineOpts.java:45)
> at sqlline.SqlLine.(SqlLine.java:54)
> at sqlline.SqlLine.start(SqlLine.java:372)
> at sqlline.SqlLine.main(SqlLine.java:265)
> [ERROR] Failed to construct terminal; falling back to unsupported
> java.lang.NumberFormatException: For input string: "0x100"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.valueOf(Integer.java:766)
> at jline.internal.InfoCmp.parseInfoCmp(InfoCmp.java:59)
> at jline.UnixTerminal.parseInfoCmp(UnixTerminal.java:242)
> at jline.UnixTerminal.(UnixTerminal.java:65)
> at jline.UnixTerminal.(UnixTerminal.java:50)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at jline.TerminalFactory.getFlavor(TerminalFactory.java:211)
> at jline.TerminalFactory.create(TerminalFactory.java:102)
> at jline.TerminalFactory.create(TerminalFactory.java:51)
> at sqlline.SqlLine.getConsoleReader(SqlLine.java:705)
> at sqlline.SqlLine.begin(SqlLine.java:639)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> sqlline version 1.3.0
> sqlline>
> ... and then history and command editing won't work
> {code}
> See also https://github.com/jline/jline2/issues/281
> I think we should manually peg jline verison to 2.14.4
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8605) sqlline can't work with terminal on newer ncurses
[
https://issues.apache.org/jira/browse/IGNITE-8605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493745#comment-16493745
]
Ilya Kasnacheev commented on IGNITE-8605:
-
[~oleg-ostanin] please take a look!
> sqlline can't work with terminal on newer ncurses
> -
>
> Key: IGNITE-8605
> URL: https://issues.apache.org/jira/browse/IGNITE-8605
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.5
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> On Ubuntu 18.04:
> {code}
> ~/w/incubator-ignite/modules/sqlline% IGNITE_HOME=~/w/incubator-ignite .
> bin/sqlline.sh
> [ERROR] Failed to construct terminal; falling back to unsupported
> java.lang.NumberFormatException: For input string: "0x100"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.valueOf(Integer.java:766)
> at jline.internal.InfoCmp.parseInfoCmp(InfoCmp.java:59)
> at jline.UnixTerminal.parseInfoCmp(UnixTerminal.java:242)
> at jline.UnixTerminal.(UnixTerminal.java:65)
> at jline.UnixTerminal.(UnixTerminal.java:50)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at jline.TerminalFactory.getFlavor(TerminalFactory.java:211)
> at jline.TerminalFactory.create(TerminalFactory.java:102)
> at jline.TerminalFactory.get(TerminalFactory.java:186)
> at jline.TerminalFactory.get(TerminalFactory.java:192)
> at sqlline.SqlLineOpts.(SqlLineOpts.java:45)
> at sqlline.SqlLine.(SqlLine.java:54)
> at sqlline.SqlLine.start(SqlLine.java:372)
> at sqlline.SqlLine.main(SqlLine.java:265)
> [ERROR] Failed to construct terminal; falling back to unsupported
> java.lang.NumberFormatException: For input string: "0x100"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.valueOf(Integer.java:766)
> at jline.internal.InfoCmp.parseInfoCmp(InfoCmp.java:59)
> at jline.UnixTerminal.parseInfoCmp(UnixTerminal.java:242)
> at jline.UnixTerminal.(UnixTerminal.java:65)
> at jline.UnixTerminal.(UnixTerminal.java:50)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at jline.TerminalFactory.getFlavor(TerminalFactory.java:211)
> at jline.TerminalFactory.create(TerminalFactory.java:102)
> at jline.TerminalFactory.create(TerminalFactory.java:51)
> at sqlline.SqlLine.getConsoleReader(SqlLine.java:705)
> at sqlline.SqlLine.begin(SqlLine.java:639)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> sqlline version 1.3.0
> sqlline>
> ... and then history and command editing won't work
> {code}
> See also https://github.com/jline/jline2/issues/281
> I think we should manually peg jline verison to 2.14.4
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8636) Debug logging improvements for Partition Map Exchange process
[ https://issues.apache.org/jira/browse/IGNITE-8636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493733#comment-16493733 ] ASF GitHub Bot commented on IGNITE-8636: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4087 > Debug logging improvements for Partition Map Exchange process > - > > Key: IGNITE-8636 > URL: https://issues.apache.org/jira/browse/IGNITE-8636 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Major > Fix For: 2.6 > > > Debug logging in ExchangeManager and ExchangeFuture lacks important scenario > of client joining topology. > All we see is client sending GridDhtPartitionsSingleMessage and coordinator > receiving this message. > If client doesn't receive GridDhtPartitionsFullMessage for its SingleMessage > there is no information in client or server logs at which moment something > went wrong. > Debug logging of the scenario should be improved, all important steps should > be covered with informative messages in logs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
[ https://issues.apache.org/jira/browse/IGNITE-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493735#comment-16493735 ] Dmitriy Pavlov commented on IGNITE-7766: Hi [~al.psc], could you please look to the change? It seems to be not complex, but I'm not able to do sign-off change because I don't understand risks of the fix. > Ignite Queries 2: Test always failed > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > --- > > Key: IGNITE-7766 > URL: https://issues.apache.org/jira/browse/IGNITE-7766 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Dmitriy Pavlov >Assignee: Evgenii Zagumennov >Priority: Major > Labels: MakeTeamcityGreenAgain > >Ignite Queries 2 > IgniteBinaryCacheQueryTestSuite2: > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > Current failure:refs/heads/master #345No changes > 11 Feb 18 03:03 > > junit.framework.AssertionFailedError: On large page size must retry. > > Last runs fails with 100% probability. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5011) Add validation of input params of disco command
[
https://issues.apache.org/jira/browse/IGNITE-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493705#comment-16493705
]
ASF GitHub Bot commented on IGNITE-5011:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1917
> Add validation of input params of disco command
> ---
>
> Key: IGNITE-5011
> URL: https://issues.apache.org/jira/browse/IGNITE-5011
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Trivial
> Fix For: 2.6
>
>
> {code}
> visor> disco -t=0h
> java.lang.IllegalArgumentException: Time frame size is not positive in: 0h
> at org.apache.ignite.visor.visor$.timeFilter(visor.scala:2671)
> at
> org.apache.ignite.visor.commands.disco.VisorDiscoveryCommand.disco(VisorDiscoveryCommand.scala:127)
> at
> org.apache.ignite.visor.commands.disco.VisorDiscoveryCommand$$anonfun$4.apply(VisorDiscoveryCommand.scala:282)
> at
> org.apache.ignite.visor.commands.disco.VisorDiscoveryCommand$$anonfun$4.apply(VisorDiscoveryCommand.scala:282)
> at
> org.apache.ignite.visor.commands.VisorConsole.mainLoop(VisorConsole.scala:217)
> at
> org.apache.ignite.visor.commands.VisorConsole$.delayedEndpoint$org$apache$ignite$visor$commands$VisorConsole$1(VisorConsole.scala:329)
> at
> org.apache.ignite.visor.commands.VisorConsole$delayedInit$body.apply(VisorConsole.scala:318)
> at scala.Function0$class.apply$mcV$sp(Function0.scala:34)
> at
> scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
> at scala.App$$anonfun$main$1.apply(App.scala:76)
> at scala.App$$anonfun$main$1.apply(App.scala:76)
> at scala.collection.immutable.List.foreach(List.scala:381)
> at
> scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35)
> at scala.App$class.main(App.scala:76)
> at
> org.apache.ignite.visor.commands.VisorConsole$.main(VisorConsole.scala:318)
> at
> org.apache.ignite.visor.commands.VisorConsole.main(VisorConsole.scala)
> (wrn) : Invalid command name: 'disco -t=0h'
> (wrn) : Type 'help' to print commands list.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-5011) Add validation of input params of disco command
[
https://issues.apache.org/jira/browse/IGNITE-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov reassigned IGNITE-5011:
Resolution: Fixed
Assignee: Pavel Konstantinov (was: Alexey Kuznetsov)
Looks good. Merged to master.
> Add validation of input params of disco command
> ---
>
> Key: IGNITE-5011
> URL: https://issues.apache.org/jira/browse/IGNITE-5011
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Trivial
> Fix For: 2.6
>
>
> {code}
> visor> disco -t=0h
> java.lang.IllegalArgumentException: Time frame size is not positive in: 0h
> at org.apache.ignite.visor.visor$.timeFilter(visor.scala:2671)
> at
> org.apache.ignite.visor.commands.disco.VisorDiscoveryCommand.disco(VisorDiscoveryCommand.scala:127)
> at
> org.apache.ignite.visor.commands.disco.VisorDiscoveryCommand$$anonfun$4.apply(VisorDiscoveryCommand.scala:282)
> at
> org.apache.ignite.visor.commands.disco.VisorDiscoveryCommand$$anonfun$4.apply(VisorDiscoveryCommand.scala:282)
> at
> org.apache.ignite.visor.commands.VisorConsole.mainLoop(VisorConsole.scala:217)
> at
> org.apache.ignite.visor.commands.VisorConsole$.delayedEndpoint$org$apache$ignite$visor$commands$VisorConsole$1(VisorConsole.scala:329)
> at
> org.apache.ignite.visor.commands.VisorConsole$delayedInit$body.apply(VisorConsole.scala:318)
> at scala.Function0$class.apply$mcV$sp(Function0.scala:34)
> at
> scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
> at scala.App$$anonfun$main$1.apply(App.scala:76)
> at scala.App$$anonfun$main$1.apply(App.scala:76)
> at scala.collection.immutable.List.foreach(List.scala:381)
> at
> scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35)
> at scala.App$class.main(App.scala:76)
> at
> org.apache.ignite.visor.commands.VisorConsole$.main(VisorConsole.scala:318)
> at
> org.apache.ignite.visor.commands.VisorConsole.main(VisorConsole.scala)
> (wrn) : Invalid command name: 'disco -t=0h'
> (wrn) : Type 'help' to print commands list.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-4210) CacheLoadingConcurrentGridStartSelfTest.testLoadCacheFromStore() test lose data.
[ https://issues.apache.org/jira/browse/IGNITE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493695#comment-16493695 ] Andrey Gura commented on IGNITE-4210: - I'll take a look. > CacheLoadingConcurrentGridStartSelfTest.testLoadCacheFromStore() test lose > data. > > > Key: IGNITE-4210 > URL: https://issues.apache.org/jira/browse/IGNITE-4210 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Assignee: Alexey Kuznetsov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.6 > > > org.apache.ignite.internal.processors.cache.distributed.CacheLoadingConcurrentGridStartSelfTest#testLoadCacheFromStore > sometimes have failures. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8636) Debug logging improvements for Partition Map Exchange process
[ https://issues.apache.org/jira/browse/IGNITE-8636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493685#comment-16493685 ] Pavel Kovalenko commented on IGNITE-8636: - [~sergey-chugunov] Changes are good from my perspective. > Debug logging improvements for Partition Map Exchange process > - > > Key: IGNITE-8636 > URL: https://issues.apache.org/jira/browse/IGNITE-8636 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Major > Fix For: 2.6 > > > Debug logging in ExchangeManager and ExchangeFuture lacks important scenario > of client joining topology. > All we see is client sending GridDhtPartitionsSingleMessage and coordinator > receiving this message. > If client doesn't receive GridDhtPartitionsFullMessage for its SingleMessage > there is no information in client or server logs at which moment something > went wrong. > Debug logging of the scenario should be improved, all important steps should > be covered with informative messages in logs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6284) Add IgniteCompute.withTaskNoResultCache() which should have similar effect as @ComputeTaskNoResultCache
[ https://issues.apache.org/jira/browse/IGNITE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493677#comment-16493677 ] Ihor Parashynets commented on IGNITE-6284: -- hi [~dpavlov], [~EdShangGG] Thank you both for the quick response. I'm not sure if I'll be able reasonably evaluate latest changes here (such as didn't study AI internally as a developer) but anyway very appreciated! In case it's stacked for longer time I might give it a try from my side :) cheers, Ihor P. > Add IgniteCompute.withTaskNoResultCache() which should have similar effect as > @ComputeTaskNoResultCache > --- > > Key: IGNITE-6284 > URL: https://issues.apache.org/jira/browse/IGNITE-6284 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Yakov Zhdanov >Assignee: Mikhail Lipkovich >Priority: Major > Labels: newbie, usability > > New method should save threadlocal context as other IgniteCompute.with...() > methods do and have similar effect as ComputeTaskNoResultCache annotation > attached to a class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6284) Add IgniteCompute.withTaskNoResultCache() which should have similar effect as @ComputeTaskNoResultCache
[ https://issues.apache.org/jira/browse/IGNITE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493676#comment-16493676 ] Eduard Shangareev commented on IGNITE-6284: --- [~dpavlov] Actually, I have finished a review, but I have updated some file. So, I think it's better if someone else looks through with my changes. > Add IgniteCompute.withTaskNoResultCache() which should have similar effect as > @ComputeTaskNoResultCache > --- > > Key: IGNITE-6284 > URL: https://issues.apache.org/jira/browse/IGNITE-6284 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Yakov Zhdanov >Assignee: Mikhail Lipkovich >Priority: Major > Labels: newbie, usability > > New method should save threadlocal context as other IgniteCompute.with...() > methods do and have similar effect as ComputeTaskNoResultCache annotation > attached to a class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-6284) Add IgniteCompute.withTaskNoResultCache() which should have similar effect as @ComputeTaskNoResultCache
[ https://issues.apache.org/jira/browse/IGNITE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Shangareev updated IGNITE-6284: -- Comment: was deleted (was: [~ihorps], hi. Please, look through my changes and if everything is OK, include them in your PR. Thank you. ) > Add IgniteCompute.withTaskNoResultCache() which should have similar effect as > @ComputeTaskNoResultCache > --- > > Key: IGNITE-6284 > URL: https://issues.apache.org/jira/browse/IGNITE-6284 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Yakov Zhdanov >Assignee: Mikhail Lipkovich >Priority: Major > Labels: newbie, usability > > New method should save threadlocal context as other IgniteCompute.with...() > methods do and have similar effect as ComputeTaskNoResultCache annotation > attached to a class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8406) Update IgniteDataStreamer.flush() javadoc
[
https://issues.apache.org/jira/browse/IGNITE-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493673#comment-16493673
]
ASF GitHub Bot commented on IGNITE-8406:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4043
> Update IgniteDataStreamer.flush() javadoc
> -
>
> Key: IGNITE-8406
> URL: https://issues.apache.org/jira/browse/IGNITE-8406
> Project: Ignite
> Issue Type: Task
> Components: streaming
>Affects Versions: 2.4
>Reporter: Andrey Kuznetsov
>Assignee: Ivan Fedotov
>Priority: Minor
> Fix For: 2.6
>
>
> Current {{flush()}} implementation can throw {{CacheException}} if one or
> more futures previously returned by {{addData()}} have been completed
> exceptionally. This behavior should be described in {{IgniteDataStreamer}}
> javadoc. Also it's worth noting explicitly that all futures completion upon
> return from {{flush}} does not imply all those future listeners have been
> completed by this moment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8605) sqlline can't work with terminal on newer ncurses
[
https://issues.apache.org/jira/browse/IGNITE-8605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493670#comment-16493670
]
Ilya Kasnacheev commented on IGNITE-8605:
-
[~vveider] It's May 29 o'clock!
> sqlline can't work with terminal on newer ncurses
> -
>
> Key: IGNITE-8605
> URL: https://issues.apache.org/jira/browse/IGNITE-8605
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.5
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> On Ubuntu 18.04:
> {code}
> ~/w/incubator-ignite/modules/sqlline% IGNITE_HOME=~/w/incubator-ignite .
> bin/sqlline.sh
> [ERROR] Failed to construct terminal; falling back to unsupported
> java.lang.NumberFormatException: For input string: "0x100"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.valueOf(Integer.java:766)
> at jline.internal.InfoCmp.parseInfoCmp(InfoCmp.java:59)
> at jline.UnixTerminal.parseInfoCmp(UnixTerminal.java:242)
> at jline.UnixTerminal.(UnixTerminal.java:65)
> at jline.UnixTerminal.(UnixTerminal.java:50)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at jline.TerminalFactory.getFlavor(TerminalFactory.java:211)
> at jline.TerminalFactory.create(TerminalFactory.java:102)
> at jline.TerminalFactory.get(TerminalFactory.java:186)
> at jline.TerminalFactory.get(TerminalFactory.java:192)
> at sqlline.SqlLineOpts.(SqlLineOpts.java:45)
> at sqlline.SqlLine.(SqlLine.java:54)
> at sqlline.SqlLine.start(SqlLine.java:372)
> at sqlline.SqlLine.main(SqlLine.java:265)
> [ERROR] Failed to construct terminal; falling back to unsupported
> java.lang.NumberFormatException: For input string: "0x100"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.valueOf(Integer.java:766)
> at jline.internal.InfoCmp.parseInfoCmp(InfoCmp.java:59)
> at jline.UnixTerminal.parseInfoCmp(UnixTerminal.java:242)
> at jline.UnixTerminal.(UnixTerminal.java:65)
> at jline.UnixTerminal.(UnixTerminal.java:50)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at jline.TerminalFactory.getFlavor(TerminalFactory.java:211)
> at jline.TerminalFactory.create(TerminalFactory.java:102)
> at jline.TerminalFactory.create(TerminalFactory.java:51)
> at sqlline.SqlLine.getConsoleReader(SqlLine.java:705)
> at sqlline.SqlLine.begin(SqlLine.java:639)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> sqlline version 1.3.0
> sqlline>
> ... and then history and command editing won't work
> {code}
> See also https://github.com/jline/jline2/issues/281
> I think we should manually peg jline verison to 2.14.4
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-5048) NPE in WebSessionFilter
[
https://issues.apache.org/jira/browse/IGNITE-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev resolved IGNITE-5048.
-
Resolution: Duplicate
> NPE in WebSessionFilter
> ---
>
> Key: IGNITE-5048
> URL: https://issues.apache.org/jira/browse/IGNITE-5048
> Project: Ignite
> Issue Type: Bug
> Components: websession
>Affects Versions: 2.0
>Reporter: Cameron Braid
>Priority: Major
>
> ses must be not null during construction. However line 1013 nulls it out.
> Line 1001 should probably have {code}if (ses == null || !ses.isValid())
> {code}
> Line 1002 should have {code} if (ses != null)
> binaryCache.remove(ses.id()){code}
> and a
> {code}
> 283665 ERROR ROOT [http-nio-0.0.0.0-8080-exec-5] Failed to update web
> session: null
> java.lang.NullPointerException: null
> at
> org.apache.ignite.cache.websession.WebSessionFilter$RequestWrapperV2.getSession(WebSessionFilter.java:1001)
> at
> org.apache.ignite.cache.websession.WebSessionFilter.doFilterV2(WebSessionFilter.java:564)
> at
> org.apache.ignite.cache.websession.WebSessionFilter.doFilterDispatch(WebSessionFilter.java:407)
> at
> org.apache.ignite.cache.websession.WebSessionFilter.doFilter(WebSessionFilter.java:383)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
> at
> org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99)
> at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
> at
> org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:89)
> at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
> at
> org.springframework.web.filter.HiddenHttpMethodFilter.doFilterInternal(HiddenHttpMethodFilter.java:77)
> at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
> at
> org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:197)
> at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
> at
> org.springframework.boot.actuate.autoconfigure.MetricsFilter.doFilterInternal(MetricsFilter.java:107)
> at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:108)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
> at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:677)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:349)
> at
> org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:784)
> at
> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
> at
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:802)
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1410)
> at
> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
>
[jira] [Commented] (IGNITE-6284) Add IgniteCompute.withTaskNoResultCache() which should have similar effect as @ComputeTaskNoResultCache
[ https://issues.apache.org/jira/browse/IGNITE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493660#comment-16493660 ] Eduard Shangareev commented on IGNITE-6284: --- [~ihorps], hi. Please, look through my change and if everything is OK, include them in your PR. Thank you. > Add IgniteCompute.withTaskNoResultCache() which should have similar effect as > @ComputeTaskNoResultCache > --- > > Key: IGNITE-6284 > URL: https://issues.apache.org/jira/browse/IGNITE-6284 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Yakov Zhdanov >Assignee: Mikhail Lipkovich >Priority: Major > Labels: newbie, usability > > New method should save threadlocal context as other IgniteCompute.with...() > methods do and have similar effect as ComputeTaskNoResultCache annotation > attached to a class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-6284) Add IgniteCompute.withTaskNoResultCache() which should have similar effect as @ComputeTaskNoResultCache
[ https://issues.apache.org/jira/browse/IGNITE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493660#comment-16493660 ] Eduard Shangareev edited comment on IGNITE-6284 at 5/29/18 3:05 PM: [~ihorps], hi. Please, look through my changes and if everything is OK, include them in your PR. Thank you. was (Author: edshanggg): [~ihorps], hi. Please, look through my change and if everything is OK, include them in your PR. Thank you. > Add IgniteCompute.withTaskNoResultCache() which should have similar effect as > @ComputeTaskNoResultCache > --- > > Key: IGNITE-6284 > URL: https://issues.apache.org/jira/browse/IGNITE-6284 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Yakov Zhdanov >Assignee: Mikhail Lipkovich >Priority: Major > Labels: newbie, usability > > New method should save threadlocal context as other IgniteCompute.with...() > methods do and have similar effect as ComputeTaskNoResultCache annotation > attached to a class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6284) Add IgniteCompute.withTaskNoResultCache() which should have similar effect as @ComputeTaskNoResultCache
[ https://issues.apache.org/jira/browse/IGNITE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493656#comment-16493656 ] Dmitriy Pavlov commented on IGNITE-6284: Hi [~ihorps] strict prediction generally not possible. In the same time [~EdShangGG] kindly agreed to look to this ticket, so I hope fix can come to 2.6 if review will be passed. > Add IgniteCompute.withTaskNoResultCache() which should have similar effect as > @ComputeTaskNoResultCache > --- > > Key: IGNITE-6284 > URL: https://issues.apache.org/jira/browse/IGNITE-6284 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Yakov Zhdanov >Assignee: Mikhail Lipkovich >Priority: Major > Labels: newbie, usability > > New method should save threadlocal context as other IgniteCompute.with...() > methods do and have similar effect as ComputeTaskNoResultCache annotation > attached to a class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6284) Add IgniteCompute.withTaskNoResultCache() which should have similar effect as @ComputeTaskNoResultCache
[ https://issues.apache.org/jira/browse/IGNITE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493649#comment-16493649 ] Ihor Parashynets commented on IGNITE-6284: -- hi guys Is it possible to predict in which version this ticket might come? Is there somebody going to review it? Thanks you in advance > Add IgniteCompute.withTaskNoResultCache() which should have similar effect as > @ComputeTaskNoResultCache > --- > > Key: IGNITE-6284 > URL: https://issues.apache.org/jira/browse/IGNITE-6284 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Yakov Zhdanov >Assignee: Mikhail Lipkovich >Priority: Major > Labels: newbie, usability > > New method should save threadlocal context as other IgniteCompute.with...() > methods do and have similar effect as ComputeTaskNoResultCache annotation > attached to a class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8624) Add test coverage for NPE in TTL Manager [IGNITE-7972]
[ https://issues.apache.org/jira/browse/IGNITE-8624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493622#comment-16493622 ] ASF GitHub Bot commented on IGNITE-8624: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4077 > Add test coverage for NPE in TTL Manager [IGNITE-7972] > -- > > Key: IGNITE-8624 > URL: https://issues.apache.org/jira/browse/IGNITE-8624 > Project: Ignite > Issue Type: Test >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Minor > Fix For: 2.6 > > > Add test coverage (reproducer) to the [IGNITE-7972] case. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8640) If first createCache fail - Ignite is freezing on next createCache
[
https://issues.apache.org/jira/browse/IGNITE-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493542#comment-16493542
]
Nikolay Izhikov commented on IGNITE-8640:
-
The second attempt to createCache will freeze {{IgniteCache cache
= ignite.createCache(new CacheConfiguration<>("default"));}}.
Note, that *any* exception from {{GridCacheProcessor#validate}} leads to the
same freeze.
So error doesn't relate to eviction policy.
It relates to cache creation process.
> If first createCache fail - Ignite is freezing on next createCache
> --
>
> Key: IGNITE-8640
> URL: https://issues.apache.org/jira/browse/IGNITE-8640
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolay Izhikov
>Priority: Critical
> Fix For: 2.6
>
>
> If first {{createCache}} operation fails on some condition inside
> {{GridCacheProcessor#validate}} then second {{createCache}} will freeze
> forever.
> Reproducer:
> {code:java}
> package org.apache.ignite.internal.processors.cache;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.IgniteCheckedException;
> import org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicy;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.internal.IgniteEx;
> import org.apache.ignite.testframework.GridTestUtils;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> public class CreateCacheFreezeTest extends GridCommonAbstractTest {
> public void testCreateEncryptedNotPersistedCacheFail() throws Exception {
> IgniteEx ignite = startGrid(0);
>
> GridTestUtils.assertThrowsWithCause(() -> {
> CacheConfiguration cc = new
> CacheConfiguration<>("failed");
> cc.setEvictionPolicy(new FifoEvictionPolicy());
> cc.setOnheapCacheEnabled(false);
> ignite.createCache(cc);
> return 0;
> }, IgniteCheckedException.class);
> IgniteCache cache = ignite.createCache(new
> CacheConfiguration<>("default"));
> assertNotNull(cache);
> }
> }
> {code}
> Log message:
> {noformat}
> [2018-05-29
> 16:38:11,958][ERROR][exchange-worker-#38%cache.CreateCacheFreezeTest0%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=1,
> minorTopVer=1], discoEvt=DiscoveryCustomEvent
> [customMsg=DynamicCacheChangeBatch
> [id=67cce1ca361-993dd9c2-f4fe-443b-af43-27e06424e1b0,
> reqs=[DynamicCacheChangeRequest [cacheName=failed, hasCfg=true,
> nodeId=a525b74c-aec5-4c62-855a-ff96ef30, clientStartOnly=false,
> stop=false, destroy=false, disabledAfterStartfalse]],
> exchangeActions=ExchangeActions [startCaches=[failed], stopCaches=null,
> startGrps=[failed], stopGrps=[], resetParts=null, stateChangeRequest=null],
> startCaches=false], affTopVer=AffinityTopologyVersion [topVer=1,
> minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=a525b74c-aec5-4c62-855a-ff96ef30, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
> lastExchangeTime=1527601090538, loc=true, ver=2.5.0#19700101-sha1:,
> isClient=false], topVer=1, nodeId8=a525b74c, msg=null,
> type=DISCOVERY_CUSTOM_EVT, tstamp=1527601091938]], nodeId=a525b74c,
> evt=DISCOVERY_CUSTOM_EVT]
> java.lang.AssertionError: stopping=false, groupName=null, caches=[]
> at
> org.apache.ignite.internal.processors.cache.CacheGroupContext.singleCacheContext(CacheGroupContext.java:375)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.(GridDhtLocalPartition.java:197)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.getOrCreatePartition(GridDhtPartitionTopologyImpl.java:828)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.initPartitions(GridDhtPartitionTopologyImpl.java:369)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.beforeExchange(GridDhtPartitionTopologyImpl.java:544)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1190)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:722)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2452)
> at
>
[jira] [Updated] (IGNITE-8640) If first createCache fail - Ignite is freezing on next createCache
[
https://issues.apache.org/jira/browse/IGNITE-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-8640:
Description:
If first {{createCache}} operation fails on some condition inside
{{GridCacheProcessor#validate}} then second {{createCache}} will freeze forever.
Reproducer:
{code:java}
package org.apache.ignite.internal.processors.cache;
import org.apache.ignite.IgniteCache;
import org.apache.ignite.IgniteCheckedException;
import org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicy;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.testframework.GridTestUtils;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
public class CreateCacheFreezeTest extends GridCommonAbstractTest {
public void testCreateEncryptedNotPersistedCacheFail() throws Exception {
IgniteEx ignite = startGrid(0);
GridTestUtils.assertThrowsWithCause(() -> {
CacheConfiguration cc = new
CacheConfiguration<>("failed");
cc.setEvictionPolicy(new FifoEvictionPolicy());
cc.setOnheapCacheEnabled(false);
ignite.createCache(cc);
return 0;
}, IgniteCheckedException.class);
IgniteCache cache = ignite.createCache(new
CacheConfiguration<>("default"));
assertNotNull(cache);
}
}
{code}
Log message:
{noformat}
[2018-05-29
16:38:11,958][ERROR][exchange-worker-#38%cache.CreateCacheFreezeTest0%][GridDhtPartitionsExchangeFuture]
Failed to reinitialize local partitions (preloading will be stopped):
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=1,
minorTopVer=1], discoEvt=DiscoveryCustomEvent
[customMsg=DynamicCacheChangeBatch
[id=67cce1ca361-993dd9c2-f4fe-443b-af43-27e06424e1b0,
reqs=[DynamicCacheChangeRequest [cacheName=failed, hasCfg=true,
nodeId=a525b74c-aec5-4c62-855a-ff96ef30, clientStartOnly=false, stop=false,
destroy=false, disabledAfterStartfalse]], exchangeActions=ExchangeActions
[startCaches=[failed], stopCaches=null, startGrps=[failed], stopGrps=[],
resetParts=null, stateChangeRequest=null], startCaches=false],
affTopVer=AffinityTopologyVersion [topVer=1, minorTopVer=1],
super=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=a525b74c-aec5-4c62-855a-ff96ef30, addrs=[127.0.0.1],
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1527601090538, loc=true, ver=2.5.0#19700101-sha1:,
isClient=false], topVer=1, nodeId8=a525b74c, msg=null,
type=DISCOVERY_CUSTOM_EVT, tstamp=1527601091938]], nodeId=a525b74c,
evt=DISCOVERY_CUSTOM_EVT]
java.lang.AssertionError: stopping=false, groupName=null, caches=[]
at
org.apache.ignite.internal.processors.cache.CacheGroupContext.singleCacheContext(CacheGroupContext.java:375)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.(GridDhtLocalPartition.java:197)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.getOrCreatePartition(GridDhtPartitionTopologyImpl.java:828)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.initPartitions(GridDhtPartitionTopologyImpl.java:369)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.beforeExchange(GridDhtPartitionTopologyImpl.java:544)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1190)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:722)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2452)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2332)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{noformat}
was:
If first {createCache} operation fails on some condition inside
{GridCacheProcessor#validate} then second {createCache} will freeze forever.
Reproducer:
{code:java}
package org.apache.ignite.internal.processors.cache;
import org.apache.ignite.IgniteCache;
import org.apache.ignite.IgniteCheckedException;
import org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicy;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.testframework.GridTestUtils;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
public class CreateCacheFreezeTest extends
[jira] [Created] (IGNITE-8640) If first createCache fail - Ignite is freezing on next createCache
Nikolay Izhikov created IGNITE-8640:
---
Summary: If first createCache fail - Ignite is freezing on next
createCache
Key: IGNITE-8640
URL: https://issues.apache.org/jira/browse/IGNITE-8640
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.6
Reporter: Nikolay Izhikov
Fix For: 2.6
If first {createCache} operation fails on some condition inside
{GridCacheProcessor#validate} then second {createCache} will freeze forever.
Reproducer:
{code:java}
package org.apache.ignite.internal.processors.cache;
import org.apache.ignite.IgniteCache;
import org.apache.ignite.IgniteCheckedException;
import org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicy;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.testframework.GridTestUtils;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
public class CreateCacheFreezeTest extends GridCommonAbstractTest {
public void testCreateEncryptedNotPersistedCacheFail() throws Exception {
IgniteEx ignite = startGrid(0);
GridTestUtils.assertThrowsWithCause(() -> {
CacheConfiguration cc = new
CacheConfiguration<>("failed");
cc.setEvictionPolicy(new FifoEvictionPolicy());
cc.setOnheapCacheEnabled(false);
ignite.createCache(cc);
return 0;
}, IgniteCheckedException.class);
IgniteCache cache = ignite.createCache(new
CacheConfiguration<>("default"));
assertNotNull(cache);
}
}
{code}
Log message:
{noformat}
[2018-05-29
16:38:11,958][ERROR][exchange-worker-#38%cache.CreateCacheFreezeTest0%][GridDhtPartitionsExchangeFuture]
Failed to reinitialize local partitions (preloading will be stopped):
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=1,
minorTopVer=1], discoEvt=DiscoveryCustomEvent
[customMsg=DynamicCacheChangeBatch
[id=67cce1ca361-993dd9c2-f4fe-443b-af43-27e06424e1b0,
reqs=[DynamicCacheChangeRequest [cacheName=failed, hasCfg=true,
nodeId=a525b74c-aec5-4c62-855a-ff96ef30, clientStartOnly=false, stop=false,
destroy=false, disabledAfterStartfalse]], exchangeActions=ExchangeActions
[startCaches=[failed], stopCaches=null, startGrps=[failed], stopGrps=[],
resetParts=null, stateChangeRequest=null], startCaches=false],
affTopVer=AffinityTopologyVersion [topVer=1, minorTopVer=1],
super=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=a525b74c-aec5-4c62-855a-ff96ef30, addrs=[127.0.0.1],
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1527601090538, loc=true, ver=2.5.0#19700101-sha1:,
isClient=false], topVer=1, nodeId8=a525b74c, msg=null,
type=DISCOVERY_CUSTOM_EVT, tstamp=1527601091938]], nodeId=a525b74c,
evt=DISCOVERY_CUSTOM_EVT]
java.lang.AssertionError: stopping=false, groupName=null, caches=[]
at
org.apache.ignite.internal.processors.cache.CacheGroupContext.singleCacheContext(CacheGroupContext.java:375)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.(GridDhtLocalPartition.java:197)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.getOrCreatePartition(GridDhtPartitionTopologyImpl.java:828)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.initPartitions(GridDhtPartitionTopologyImpl.java:369)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.beforeExchange(GridDhtPartitionTopologyImpl.java:544)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1190)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:722)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2452)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2332)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8639) Query with a lot of nesting causes NPE in org.h2.util.StringUtils.indent
[
https://issues.apache.org/jira/browse/IGNITE-8639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-8639:
Attachment: SqlNestedQuerySelfTest.java
> Query with a lot of nesting causes NPE in org.h2.util.StringUtils.indent
>
>
> Key: IGNITE-8639
> URL: https://issues.apache.org/jira/browse/IGNITE-8639
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.6
>Reporter: Ilya Kasnacheev
>Priority: Minor
> Labels: test
> Attachments: SqlNestedQuerySelfTest.java
>
>
> Worked in 1.7!
> But now:
> {code}
> sql("WITH cacheJoin (txId, stage, tStamp)" +
> " AS (SELECT t.txId, o.stage, o.tStamp FROM txs t INNER JOIN
> ops o ON t.txId = o.txId)" +
> " SELECT ou.stage, COUNT(*) as cou, SUM(CASE WHEN ou.stage =
> in.stage THEN 1 ELSE 0 END) AS ttl" +
> " FROM (SELECT txId, stage FROM cacheJoin cte GROUP BY txId,
> stage) ou" +
> " INNER JOIN (SELECT mx.txId, mx.stage FROM (SELECT txId,
> tStamp, stage FROM cacheJoin cte) mx" +
> " INNER JOIN (SELECT txId, MAX(tStamp) AS maxTStamp FROM
> cacheJoin cte GROUP BY txId) mix" +
> " ON mx.txId = mix.txId AND mx.tStamp = mix.maxTStamp) in
> ON ou.txId = in.txId" +
> " GROUP BY ou.stage");
> {code}
> {code}
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to parse query. Внутренняя ошибка: "java.lang.NullPointerException"
> General error: "java.lang.NullPointerException" [5-195]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatementAndCaches(IgniteH2Indexing.java:2026)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.parseAndSplit(IgniteH2Indexing.java:1796)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1652)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2035)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2030)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2578)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2044)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1990)
> at
> org.apache.ignite.internal.processors.query.SqlNestedQuerySelfTest.sql(SqlNestedQuerySelfTest.java:73)
> at
> org.apache.ignite.internal.processors.query.SqlNestedQuerySelfTest.testNestingQuery(SqlNestedQuerySelfTest.java:54)
> 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:2086)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2001)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.h2.jdbc.JdbcSQLException: Внутренняя ошибка:
> "java.lang.NullPointerException"
> General error: "java.lang.NullPointerException" [5-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:168)
> at org.h2.message.DbException.convert(DbException.java:295)
> at org.h2.message.DbException.toSQLException(DbException.java:268)
> at org.h2.message.TraceObject.logAndConvert(TraceObject.java:352)
> at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:292)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepare0(IgniteH2Indexing.java:484)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:452)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:419)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatementAndCaches(IgniteH2Indexing.java:2008)
> ... 19 more
> Caused by:
[jira] [Created] (IGNITE-8639) Query with a lot of nesting causes NPE in org.h2.util.StringUtils.indent
Ilya Kasnacheev created IGNITE-8639:
---
Summary: Query with a lot of nesting causes NPE in
org.h2.util.StringUtils.indent
Key: IGNITE-8639
URL: https://issues.apache.org/jira/browse/IGNITE-8639
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.6
Reporter: Ilya Kasnacheev
Attachments: SqlNestedQuerySelfTest.java
Worked in 1.7!
But now:
{code}
sql("WITH cacheJoin (txId, stage, tStamp)" +
" AS (SELECT t.txId, o.stage, o.tStamp FROM txs t INNER JOIN ops
o ON t.txId = o.txId)" +
" SELECT ou.stage, COUNT(*) as cou, SUM(CASE WHEN ou.stage =
in.stage THEN 1 ELSE 0 END) AS ttl" +
" FROM (SELECT txId, stage FROM cacheJoin cte GROUP BY txId,
stage) ou" +
" INNER JOIN (SELECT mx.txId, mx.stage FROM (SELECT txId,
tStamp, stage FROM cacheJoin cte) mx" +
" INNER JOIN (SELECT txId, MAX(tStamp) AS maxTStamp FROM
cacheJoin cte GROUP BY txId) mix" +
" ON mx.txId = mix.txId AND mx.tStamp = mix.maxTStamp) in
ON ou.txId = in.txId" +
" GROUP BY ou.stage");
{code}
{code}
class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
parse query. Внутренняя ошибка: "java.lang.NullPointerException"
General error: "java.lang.NullPointerException" [5-195]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatementAndCaches(IgniteH2Indexing.java:2026)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.parseAndSplit(IgniteH2Indexing.java:1796)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1652)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2035)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2030)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2578)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2044)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1990)
at
org.apache.ignite.internal.processors.query.SqlNestedQuerySelfTest.sql(SqlNestedQuerySelfTest.java:73)
at
org.apache.ignite.internal.processors.query.SqlNestedQuerySelfTest.testNestingQuery(SqlNestedQuerySelfTest.java:54)
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:2086)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2001)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.h2.jdbc.JdbcSQLException: Внутренняя ошибка:
"java.lang.NullPointerException"
General error: "java.lang.NullPointerException" [5-195]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:168)
at org.h2.message.DbException.convert(DbException.java:295)
at org.h2.message.DbException.toSQLException(DbException.java:268)
at org.h2.message.TraceObject.logAndConvert(TraceObject.java:352)
at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:292)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepare0(IgniteH2Indexing.java:484)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:452)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:419)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatementAndCaches(IgniteH2Indexing.java:2008)
... 19 more
Caused by: java.lang.NullPointerException
at org.h2.util.StringUtils.indent(StringUtils.java:594)
at org.h2.util.StringUtils.indent(StringUtils.java:582)
at org.h2.table.TableView.getSQL(TableView.java:436)
at org.h2.command.dml.Select.getPlanSQL(Select.java:1083)
at org.h2.index.ViewIndex.getPlanSQL(ViewIndex.java:134)
at
[jira] [Updated] (IGNITE-1094) Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization
[ https://issues.apache.org/jira/browse/IGNITE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-1094: Fix Version/s: 2.6 > Ignite.createCache(CacheConfiguration) hangs if some exception occurs during > cache initialization > - > > Key: IGNITE-1094 > URL: https://issues.apache.org/jira/browse/IGNITE-1094 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Sergey Evdokimov >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: Muted_test > Fix For: 2.6 > > > User can pass broken configuration, for example, store factory that throws > exception from create() method. I created test to demonstrate the problem. > See IgniteDynamicCacheStartSelfTest#testBrokenStoreFactory in 'ignite-1094' > branch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8636) Debug logging improvements for Partition Map Exchange process
[ https://issues.apache.org/jira/browse/IGNITE-8636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493522#comment-16493522 ] ASF GitHub Bot commented on IGNITE-8636: GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/4087 IGNITE-8636 debug logging for client join scenario You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8636 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4087.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 #4087 commit a4f650a870f23314e0ce0fdedf5e36627887bfe2 Author: Sergey Chugunov Date: 2018-05-29T12:05:12Z IGNITE-8636 debug logging for client join scenario > Debug logging improvements for Partition Map Exchange process > - > > Key: IGNITE-8636 > URL: https://issues.apache.org/jira/browse/IGNITE-8636 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Major > Fix For: 2.6 > > > Debug logging in ExchangeManager and ExchangeFuture lacks important scenario > of client joining topology. > All we see is client sending GridDhtPartitionsSingleMessage and coordinator > receiving this message. > If client doesn't receive GridDhtPartitionsFullMessage for its SingleMessage > there is no information in client or server logs at which moment something > went wrong. > Debug logging of the scenario should be improved, all important steps should > be covered with informative messages in logs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8530) Exchange hangs during start/stop stress test
[ https://issues.apache.org/jira/browse/IGNITE-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493517#comment-16493517 ] ASF GitHub Bot commented on IGNITE-8530: GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/4086 IGNITE-8530 fixed onNodeLeft for InitNewCoordinatorFuture You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8530 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4086.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 #4086 commit 30e7ea547781d37248445adbd61e709ec27c9ddf Author: Anton Kalashnikov Date: 2018-05-29T13:10:59Z IGNITE-8530 fixed onNodeLeft for InitNewCoordinatorFuture > Exchange hangs during start/stop stress test > > > Key: IGNITE-8530 > URL: https://issues.apache.org/jira/browse/IGNITE-8530 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.4 >Reporter: Mikhail Cherkasov >Assignee: Anton Kalashnikov >Priority: Blocker > Fix For: 2.6 > > Attachments: LocalRunner.java, MyCounterService.java, > MyCounterServiceImpl.java > > > Please see attached test, it starts N_CORES*2+2 nodes first and after this > starts N_CORES*2 threads with while(true) cycle in which closes and starts > nodes with small random pause. > After couple minutes it hangs with Failed to wait for partition map exchange. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8638) CPP Thin: Implement Cache API for C++ thin client
Igor Sapego created IGNITE-8638: --- Summary: CPP Thin: Implement Cache API for C++ thin client Key: IGNITE-8638 URL: https://issues.apache.org/jira/browse/IGNITE-8638 Project: Ignite Issue Type: Sub-task Affects Versions: 2.5 Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 2.6 Add Cache API for C++ thin client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8637) Web Console: Fix the UI bugs
Vica Abramova created IGNITE-8637: - Summary: Web Console: Fix the UI bugs Key: IGNITE-8637 URL: https://issues.apache.org/jira/browse/IGNITE-8637 Project: Ignite Issue Type: Bug Components: UI, wizards Reporter: Vica Abramova Attachments: UI bugs.png, image-2018-05-29-15-40-04-530.png !UI bugs.png! * Move the icon to the right (margin:10px) * Align all the texts -> see attached !image-2018-05-29-15-40-04-530.png! * Move the white icons 1px upward. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8637) Web Console: Fix the UI bugs
[ https://issues.apache.org/jira/browse/IGNITE-8637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vica Abramova reassigned IGNITE-8637: - Assignee: Alexey Kuznetsov > Web Console: Fix the UI bugs > > > Key: IGNITE-8637 > URL: https://issues.apache.org/jira/browse/IGNITE-8637 > Project: Ignite > Issue Type: Bug > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Major > Attachments: UI bugs.png, image-2018-05-29-15-40-04-530.png > > > !UI bugs.png! > * Move the icon to the right (margin:10px) > * Align all the texts -> see attached !image-2018-05-29-15-40-04-530.png! > * Move the white icons 1px upward. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8604) .NET test failures probably after IGNITE-5789 merge
[
https://issues.apache.org/jira/browse/IGNITE-8604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8604:
---
Fix Version/s: 2.6
> .NET test failures probably after IGNITE-5789 merge
> ---
>
> Key: IGNITE-8604
> URL: https://issues.apache.org/jira/browse/IGNITE-8604
> Project: Ignite
> Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Ilya Kasnacheev
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> 62 new failed tests in .NET
> {noformat}
> Store.CacheStoreTest
> Current failure:refs/heads/master #254 Changes (8)
> 24 May 18 02:16
> First failure: refs/heads/master #1 No changes 26 Apr
> 18 10:36
> TearDown method failed. HandleRegistry is not empty in grid '' (expected 4,
> actual 5):
> '[2, Apache.Ignite.Core.Impl.Cache.Store.CacheStore]
> [3, Apache.Ignite.Core.Impl.Cache.Store.CacheStore]
> [4, Apache.Ignite.Core.Impl.Cache.Store.CacheStore]
> [5, Apache.Ignite.Core.Impl.Cache.Store.CacheStore]'
>at NUnit.Framework.Assert.Fail(String message, Object[] args)
>at Apache.Ignite.Core.Tests.TestUtils.AssertHandleRegistryHasItems(IIgnite
> grid, Int32 expectedCount, Int32 timeout) in
> c:\BuildAgent\work\c182b70f2dfa6507\modules\platforms\dotnet\Apache.Ignite.Core.Tests\TestUtils.Common.cs:line
> 339
>at Apache.Ignite.Core.Tests.Cache.Store.CacheStoreTest.AfterTests
> {noformat}
> First time these test failed
> https://ci.ignite.apache.org/viewLog.html?buildId=1323959=buildResultsDiv=IgniteTests24Java8_PlatformNet
> Probably it is caused by merge:
> https://issues.apache.org/jira/browse/IGNITE-5789
> I've tried to revert commit in ignite-5789-1 branch and results:
> https://ci.ignite.apache.org/viewLog.html?buildId=1326520=buildResultsDiv=IgniteTests24Java8_PlatformNet
> Other test failed, but current tests were passed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8604) .NET test failures probably after IGNITE-5789 merge
[
https://issues.apache.org/jira/browse/IGNITE-8604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493477#comment-16493477
]
ASF GitHub Bot commented on IGNITE-8604:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4072
> .NET test failures probably after IGNITE-5789 merge
> ---
>
> Key: IGNITE-8604
> URL: https://issues.apache.org/jira/browse/IGNITE-8604
> Project: Ignite
> Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Ilya Kasnacheev
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> 62 new failed tests in .NET
> {noformat}
> Store.CacheStoreTest
> Current failure:refs/heads/master #254 Changes (8)
> 24 May 18 02:16
> First failure: refs/heads/master #1 No changes 26 Apr
> 18 10:36
> TearDown method failed. HandleRegistry is not empty in grid '' (expected 4,
> actual 5):
> '[2, Apache.Ignite.Core.Impl.Cache.Store.CacheStore]
> [3, Apache.Ignite.Core.Impl.Cache.Store.CacheStore]
> [4, Apache.Ignite.Core.Impl.Cache.Store.CacheStore]
> [5, Apache.Ignite.Core.Impl.Cache.Store.CacheStore]'
>at NUnit.Framework.Assert.Fail(String message, Object[] args)
>at Apache.Ignite.Core.Tests.TestUtils.AssertHandleRegistryHasItems(IIgnite
> grid, Int32 expectedCount, Int32 timeout) in
> c:\BuildAgent\work\c182b70f2dfa6507\modules\platforms\dotnet\Apache.Ignite.Core.Tests\TestUtils.Common.cs:line
> 339
>at Apache.Ignite.Core.Tests.Cache.Store.CacheStoreTest.AfterTests
> {noformat}
> First time these test failed
> https://ci.ignite.apache.org/viewLog.html?buildId=1323959=buildResultsDiv=IgniteTests24Java8_PlatformNet
> Probably it is caused by merge:
> https://issues.apache.org/jira/browse/IGNITE-5789
> I've tried to revert commit in ignite-5789-1 branch and results:
> https://ci.ignite.apache.org/viewLog.html?buildId=1326520=buildResultsDiv=IgniteTests24Java8_PlatformNet
> Other test failed, but current tests were passed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8476) AssertionError exception occurs when trying to remove node from baseline under loading
[
https://issues.apache.org/jira/browse/IGNITE-8476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493433#comment-16493433
]
ASF GitHub Bot commented on IGNITE-8476:
GitHub user glukos opened a pull request:
https://github.com/apache/ignite/pull/4083
IGNITE-8476 AssertionError exception occurs when trying to remove nod…
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8476
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4083.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 #4083
commit e6346f53da593dbe6df8bd7ccfcb1b2d94bc3797
Author: Ivan Rakov
Date: 2018-05-29T11:46:51Z
IGNITE-8476 AssertionError exception occurs when trying to remove node from
baseline under loading
> AssertionError exception occurs when trying to remove node from baseline
> under loading
> --
>
> Key: IGNITE-8476
> URL: https://issues.apache.org/jira/browse/IGNITE-8476
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Dmitry Sherstobitov
>Assignee: Ivan Rakov
>Priority: Blocker
>
> Run 6 nodes, start loading (8 threads, 1000 2x cache.get() and 2x cache.put()
> in each thread per second)
> Kill 2 nodes and try to remove one node from baseline using
> control.sh --baseline remove node1
> control.sh --baseline version TOPOLOGY_VERSION
>
> Utility hangs or connected client may hangs, this assertion appears in log
> For transactional cache:
> {code:java}
> [16:32:58,960][SEVERE][sys-stripe-14-#15][G] Failed to execute runnable.
> java.lang.AssertionError: localNode = be945692-c750-4d72-b9a1-9ac4170ff125,
> dhtNodes = [ZookeeperClusterNode [id=810226e6-656a-460d-8069-ca7d2dd294ef,
> addrs=[172.17.0.1, 0:0:0:0:0:0:0:1%lo, 172.25.1.28, 127.0.0.1], order=1,
> loc=false, client=false], ZookeeperClusterNode
> [id=be945692-c750-4d72-b9a1-9ac4170ff125, addrs=[172.17.0.1, 172.25.1.28,
> 0:0:0:0:0:0:0:1%lo, 127.0.0.1], order=3, loc=true, client=false],
> ZookeeperClusterNode [id=db4503f6-9185-4673-b38c-8890dfa69511,
> addrs=[172.17.0.1, 172.25.1.37, 0:0:0:0:0:0:0:1%lo, 127.0.0.1], order=5,
> loc=false, client=false], ZookeeperClusterNode
> [id=3b8d8d4f-3513-4d39-a1fd-7ec5b15fc653, addrs=[172.17.0.1, 172.25.1.37,
> 127.0.0.1, 0:0:0:0:0:0:0:1%lo], order=4, loc=false, client=false],
> ZookeeperClusterNode [id=2bfc8c2e-2f47-4126-9cc4-6f017ce7efde,
> addrs=[172.17.0.1, 172.25.1.37, 0:0:0:0:0:0:0:1%lo, 127.0.0.1], order=6,
> loc=false, client=false]]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.map(GridDhtTxPrepareFuture.java:1520)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1239)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:671)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1048)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:397)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:516)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest0(IgniteTxHandler.java:150)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest(IgniteTxHandler.java:135)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$000(IgniteTxHandler.java:97)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:177)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:175)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> at
[jira] [Created] (IGNITE-8636) Debug logging improvements for Partition Map Exchange process
Sergey Chugunov created IGNITE-8636: --- Summary: Debug logging improvements for Partition Map Exchange process Key: IGNITE-8636 URL: https://issues.apache.org/jira/browse/IGNITE-8636 Project: Ignite Issue Type: Improvement Affects Versions: 2.5 Reporter: Sergey Chugunov Assignee: Sergey Chugunov Fix For: 2.6 Debug logging in ExchangeManager and ExchangeFuture lacks important scenario of client joining topology. All we see is client sending GridDhtPartitionsSingleMessage and coordinator receiving this message. If client doesn't receive GridDhtPartitionsFullMessage for its SingleMessage there is no information in client or server logs at which moment something went wrong. Debug logging of the scenario should be improved, all important steps should be covered with informative messages in logs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6055) SQL: Add String length constraint
[
https://issues.apache.org/jira/browse/IGNITE-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493349#comment-16493349
]
Nikolay Izhikov commented on IGNITE-6055:
-
Run All results - https://ci.ignite.apache.org/viewLog.html?buildId=1341769
> SQL: Add String length constraint
> -
>
> Key: IGNITE-6055
> URL: https://issues.apache.org/jira/browse/IGNITE-6055
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: sql-engine
>
> We should support {{CHAR(X)}} and {{VARCHAR{X}} syntax. Currently, we ignore
> it. First, it affects semantics. E.g., one can insert a string with greater
> length into a cache/table without any problems. Second, it limits efficiency
> of our default configuration. E.g., index inline cannot be applied to
> {{String}} data type as we cannot guess it's length.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7237) Web console: Wrong switcher behaviour on grid deactivation
[ https://issues.apache.org/jira/browse/IGNITE-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493343#comment-16493343 ] Vasiliy Sisko commented on IGNITE-7237: --- Reproduced when deactivation spend more time, then refresh rate. Grid return false active state before then state is toggled. > Web console: Wrong switcher behaviour on grid deactivation > -- > > Key: IGNITE-7237 > URL: https://issues.apache.org/jira/browse/IGNITE-7237 > Project: Ignite > Issue Type: Bug >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > # Run node and agent. > # Open notebook page. > # Activate grid. > # Deactivate grid. > In process of deactivation switcher transit to off state. In that transition > *Deactivation...* message is changed to "Activation...". Progress animation > is showed in some time after switcher state was changed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7237) Web console: Wrong switcher behaviour on grid deactivation
[ https://issues.apache.org/jira/browse/IGNITE-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-7237: - Assignee: Dmitriy Shabalin (was: Vasiliy Sisko) > Web console: Wrong switcher behaviour on grid deactivation > -- > > Key: IGNITE-7237 > URL: https://issues.apache.org/jira/browse/IGNITE-7237 > Project: Ignite > Issue Type: Bug >Reporter: Vasiliy Sisko >Assignee: Dmitriy Shabalin >Priority: Major > > # Run node and agent. > # Open notebook page. > # Activate grid. > # Deactivate grid. > In process of deactivation switcher transit to off state. In that transition > *Deactivation...* message is changed to "Activation...". Progress animation > is showed in some time after switcher state was changed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8316) Update RPM and DEB documentation
[ https://issues.apache.org/jira/browse/IGNITE-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov resolved IGNITE-8316. -- Resolution: Fixed RPM and DEB documentation updated: https://apacheignite.readme.io/docs/getting-started-25#section-rpm-deb-packages-installation > Update RPM and DEB documentation > > > Key: IGNITE-8316 > URL: https://issues.apache.org/jira/browse/IGNITE-8316 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.5 > > > # Add DEB repository configuration and packages installation. > # Update RPM repository configuration and packages installation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7818) Incorrect assertion in PDS page eviction method
[
https://issues.apache.org/jira/browse/IGNITE-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-7818:
Fix Version/s: 2.6
> Incorrect assertion in PDS page eviction method
> ---
>
> Key: IGNITE-7818
> URL: https://issues.apache.org/jira/browse/IGNITE-7818
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Aleksey Plekhanov
>Assignee: Ivan Fedotov
>Priority: Major
> Fix For: 2.6
>
> Attachments: PageMemoryPdsAssertTest.java
>
>
> There is an assertion in the method
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.Segment#removePageForReplacement:
>
> {code:java}
> assert relRmvAddr != INVALID_REL_PTR;{code}
> Which seems potentially dangerous. In some rare cases, when count of
> interations more then 40% of allocated pages and all processed pages are
> aquired, the {{relRmvAddr}} variable will be uninitialized and
> {{AssertionException}} will be thrown. But it's a correct case and page to
> evict can be found later in the method {{tryToFindSequentially.}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8462) DataStreamerImpl.close(true) should throw exception
[
https://issues.apache.org/jira/browse/IGNITE-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493320#comment-16493320
]
Ryabov Dmitrii commented on IGNITE-8462:
I think we shouldn't throw any exception if there was any unflushed data,
because {{DataStreamerImpl.close(true)}} should cancel all existing operations
and reject new operations.
> DataStreamerImpl.close(true) should throw exception
> ---
>
> Key: IGNITE-8462
> URL: https://issues.apache.org/jira/browse/IGNITE-8462
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Fedotov
>Assignee: Ivan Fedotov
>Priority: Major
>
> DataStreamerImpl.close(true) should throw CacheException in case if there was
> addition data to DataStreamerImpl. Future, returned by
> DataStreamerImpl.addData() also should be done after close streamer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-4775) Web Console: Implement role-based access control
[ https://issues.apache.org/jira/browse/IGNITE-4775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-4775: - Description: We can implement common approach: Declare groups. For each group assign available screens. For each screen assign available actions. Implement adding users to groups. If admin added/removed EXISTING user to some group, that user should receive notification. If admin added NOT EXISTING user to group, that user will receive invite. User should be able to see own permissions, for example on profile page. > Web Console: Implement role-based access control > > > Key: IGNITE-4775 > URL: https://issues.apache.org/jira/browse/IGNITE-4775 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Vica Abramova >Priority: Major > > We can implement common approach: > Declare groups. > For each group assign available screens. > For each screen assign available actions. > Implement adding users to groups. > If admin added/removed EXISTING user to some group, that user should receive > notification. > If admin added NOT EXISTING user to group, that user will receive invite. > User should be able to see own permissions, for example on profile page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5632) Web Console: add some kind of agent management and administration.
[ https://issues.apache.org/jira/browse/IGNITE-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-5632: - Description: In admin mode we should see all connected agents and mange their tokens lists (add / remove). May by stop/restart/agent logs view will be also useful. To implement: Display list of connected agent with list of users(tokens) that configured on them. This could be a master-detail table or tree-like control. Actions to implement 1. Add users(tokens) by selecting from list of users. Will be nice to support adding several users at once. 2. Remove users. Will be nice to support removing several users at once. 3. Restart selected web agents. was: In admin mode we should see all connected agents and mange their tokens lists (add / remove). May by stop/restart/agent logs view will be also useful. > Web Console: add some kind of agent management and administration. > -- > > Key: IGNITE-5632 > URL: https://issues.apache.org/jira/browse/IGNITE-5632 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Vica Abramova >Priority: Major > > In admin mode we should see all connected agents and mange their tokens lists > (add / remove). > May by stop/restart/agent logs view will be also useful. > To implement: > Display list of connected agent with list of users(tokens) that configured > on them. This could be a master-detail table or tree-like control. > Actions to implement > 1. Add users(tokens) by selecting from list of users. Will be nice to support > adding several users at once. > 2. Remove users. Will be nice to support removing several users at once. > 3. Restart selected web agents. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-4775) Web Console: Implement role-based access control
[ https://issues.apache.org/jira/browse/IGNITE-4775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-4775: Assignee: Vica Abramova (was: Alexey Kuznetsov) Please prepare some mockups > Web Console: Implement role-based access control > > > Key: IGNITE-4775 > URL: https://issues.apache.org/jira/browse/IGNITE-4775 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Vica Abramova >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7818) Incorrect assertion in PDS page eviction method
[
https://issues.apache.org/jira/browse/IGNITE-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16492840#comment-16492840
]
Aleksey Plekhanov edited comment on IGNITE-7818 at 5/29/18 8:58 AM:
I write a reproducer for this bug ( [^PageMemoryPdsAssertTest.java]). It's
realy not enough to just remove assertion. Instead, I think, we can return
{{tryToFindSequentially}} if address is invalid.
was (Author: alex_pl):
I write an reproducer for this bug ( [^PageMemoryPdsAssertTest.java]). It's
realy not enough to just remove assertion. Instead, I think, we can return
{{tryToFindSequentially}} if address is invalid.
> Incorrect assertion in PDS page eviction method
> ---
>
> Key: IGNITE-7818
> URL: https://issues.apache.org/jira/browse/IGNITE-7818
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Aleksey Plekhanov
>Assignee: Ivan Fedotov
>Priority: Major
> Attachments: PageMemoryPdsAssertTest.java
>
>
> There is an assertion in the method
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.Segment#removePageForReplacement:
>
> {code:java}
> assert relRmvAddr != INVALID_REL_PTR;{code}
> Which seems potentially dangerous. In some rare cases, when count of
> interations more then 40% of allocated pages and all processed pages are
> aquired, the {{relRmvAddr}} variable will be uninitialized and
> {{AssertionException}} will be thrown. But it's a correct case and page to
> evict can be found later in the method {{tryToFindSequentially.}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
[ https://issues.apache.org/jira/browse/IGNITE-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493235#comment-16493235 ] Evgenii Zagumennov commented on IGNITE-7766: Hi, [~dpavlov]. Ok, got it. Moved to *Patch Available* > Ignite Queries 2: Test always failed > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > --- > > Key: IGNITE-7766 > URL: https://issues.apache.org/jira/browse/IGNITE-7766 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Dmitriy Pavlov >Assignee: Evgenii Zagumennov >Priority: Major > Labels: MakeTeamcityGreenAgain > >Ignite Queries 2 > IgniteBinaryCacheQueryTestSuite2: > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > Current failure:refs/heads/master #345No changes > 11 Feb 18 03:03 > > junit.framework.AssertionFailedError: On large page size must retry. > > Last runs fails with 100% probability. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
[ https://issues.apache.org/jira/browse/IGNITE-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zagumennov reopened IGNITE-7766: > Ignite Queries 2: Test always failed > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > --- > > Key: IGNITE-7766 > URL: https://issues.apache.org/jira/browse/IGNITE-7766 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Dmitriy Pavlov >Assignee: Evgenii Zagumennov >Priority: Major > Labels: MakeTeamcityGreenAgain > >Ignite Queries 2 > IgniteBinaryCacheQueryTestSuite2: > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) > IgniteCacheQueryNodeRestartTxSelfTest.testRestarts > Current failure:refs/heads/master #345No changes > 11 Feb 18 03:03 > > junit.framework.AssertionFailedError: On large page size must retry. > > Last runs fails with 100% probability. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8635) Add a method to inspect BinaryObject size
[
https://issues.apache.org/jira/browse/IGNITE-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-8635:
-
Fix Version/s: 2.6
> Add a method to inspect BinaryObject size
> -
>
> Key: IGNITE-8635
> URL: https://issues.apache.org/jira/browse/IGNITE-8635
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.6
>
>
> Currently only concrete implementations of {{BinaryObject}} interface provide
> some information regarding the object serialized size. It makes it hard for
> users to reason about storage size and estimate required storage capacity.
> We need to add a method to the {{BinaryObject}} interface itself to return
> the actual size required to store the object.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8635) Add a method to inspect BinaryObject size
Alexey Goncharuk created IGNITE-8635:
Summary: Add a method to inspect BinaryObject size
Key: IGNITE-8635
URL: https://issues.apache.org/jira/browse/IGNITE-8635
Project: Ignite
Issue Type: Improvement
Reporter: Alexey Goncharuk
Currently only concrete implementations of {{BinaryObject}} interface provide
some information regarding the object serialized size. It makes it hard for
users to reason about storage size and estimate required storage capacity.
We need to add a method to the {{BinaryObject}} interface itself to return the
actual size required to store the object.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7298) Web console: error on web agent start in case if demo is opened in browser
[
https://issues.apache.org/jira/browse/IGNITE-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko reassigned IGNITE-7298:
-
Assignee: Pavel Konstantinov (was: Vasiliy Sisko)
> Web console: error on web agent start in case if demo is opened in browser
> --
>
> Key: IGNITE-7298
> URL: https://issues.apache.org/jira/browse/IGNITE-7298
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Major
>
> {code}
> [ERROR][demo-nodes-start-0][] Failed to resolve default logging config file:
> config/java.util.logging.properties
> Console logging handler is not configured.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7298) Web console: error on web agent start in case if demo is opened in browser
[
https://issues.apache.org/jira/browse/IGNITE-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493163#comment-16493163
]
Vasiliy Sisko commented on IGNITE-7298:
---
Not reproduced. Please check location of java.util.logging.properties in your
build.
> Web console: error on web agent start in case if demo is opened in browser
> --
>
> Key: IGNITE-7298
> URL: https://issues.apache.org/jira/browse/IGNITE-7298
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Major
>
> {code}
> [ERROR][demo-nodes-start-0][] Failed to resolve default logging config file:
> config/java.util.logging.properties
> Console logging handler is not configured.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-8634) Web Console: Remove shadow from "Beta" ribbon and header delimeter.
[ https://issues.apache.org/jira/browse/IGNITE-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-8634. -- Resolution: Fixed Merged to master. > Web Console: Remove shadow from "Beta" ribbon and header delimeter. > --- > > Key: IGNITE-8634 > URL: https://issues.apache.org/jira/browse/IGNITE-8634 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.6 > > > Lets remove shadows for better UI/UX. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8634) Web Console: Remove shadow from "Beta" ribbon and header delimeter.
[ https://issues.apache.org/jira/browse/IGNITE-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-8634. > Web Console: Remove shadow from "Beta" ribbon and header delimeter. > --- > > Key: IGNITE-8634 > URL: https://issues.apache.org/jira/browse/IGNITE-8634 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.6 > > > Lets remove shadows for better UI/UX. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8634) Web Console: Remove shadow from "Beta" ribbon and header delimeter.
Alexey Kuznetsov created IGNITE-8634: Summary: Web Console: Remove shadow from "Beta" ribbon and header delimeter. Key: IGNITE-8634 URL: https://issues.apache.org/jira/browse/IGNITE-8634 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Alexey Kuznetsov Assignee: Alexey Kuznetsov Fix For: 2.6 Lets remove shadows for better UI/UX. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-6064) Rework control.sh script
[ https://issues.apache.org/jira/browse/IGNITE-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-6064: Assignee: (was: Alexey Kuznetsov) > Rework control.sh script > > > Key: IGNITE-6064 > URL: https://issues.apache.org/jira/browse/IGNITE-6064 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 2.0, 2.1 >Reporter: Dmitriy Govorukhin >Priority: Blocker > Labels: usability > > Current behavior control.sh is not clear. > 1. control.sh is a confusing name, need more suitable name. > 2. Print help description if incorrect command was entered > 3. Do not print stacktrace if connection fail, add more informative message. > 4. Print information about connection, like "Connecting to > [ip-address]:[port] etc." > 5. Document the usage on a special page. Ping Denis Magda when it's time to > do that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
