[jira] [Updated] (IGNITE-9784) Performance drop on sql yardstick benchmarks
[ https://issues.apache.org/jira/browse/IGNITE-9784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Suntsov updated IGNITE-9784: - Attachment: background_primary_sync.png backgroung_full_sync.png fsync_full_sync.png fsync_primary_sync.png log_only_full_sync.png log_only_primary_sync.png > Performance drop on sql yardstick benchmarks > > > Key: IGNITE-9784 > URL: https://issues.apache.org/jira/browse/IGNITE-9784 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.7 >Reporter: Ilya Suntsov >Assignee: Alexey Goncharuk >Priority: Blocker > Fix For: 2.7 > > Attachments: Screen Shot 2018-10-03 at 4.52.22 PM.png, > background_primary_sync.png, backgroung_full_sync.png, fsync_full_sync.png, > fsync_primary_sync.png, log_only_full_sync.png, log_only_primary_sync.png > > > Please take a look at the attachment. > Grid configuration: > * 4 servers / 8 clients > * java 8 > * 64 threads, 60s warmup, 180s duration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9776) FsyncModeFileWriteAheadLogManager can block forever in log() call
[
https://issues.apache.org/jira/browse/IGNITE-9776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656494#comment-16656494
]
ASF GitHub Bot commented on IGNITE-9776:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4953
> FsyncModeFileWriteAheadLogManager can block forever in log() call
> -
>
> Key: IGNITE-9776
> URL: https://issues.apache.org/jira/browse/IGNITE-9776
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Kuznetsov
>Assignee: Alexey Stelmak
>Priority: Major
> Fix For: 2.7
>
> Attachments: FsyncWalRolloverDoesNotBlockTest.java
>
>
> If WAL archiver is disabled and WALRecord being logged has {{rollOver() ==
> true}}, then {{log()}} call blocks forever in {{FileArchiver}}'s (!) method:
> {noformat}
> nextAbsoluteSegmentIndex:1707, FsyncModeFileWriteAheadLogManager$FileArchiver
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> access$3200:1437, FsyncModeFileWriteAheadLogManager$FileArchiver
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> pollNextFile:1384, FsyncModeFileWriteAheadLogManager
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> initNextWriteHandle:1243, FsyncModeFileWriteAheadLogManager
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> rollOver:1130, FsyncModeFileWriteAheadLogManager
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> log:712, FsyncModeFileWriteAheadLogManager
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> {noformat}
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9784) Performance drop on sql yardstick benchmarks
[ https://issues.apache.org/jira/browse/IGNITE-9784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Suntsov updated IGNITE-9784: - Attachment: (was: Screen Shot 2018-10-19 at 12.10.36 PM (2).png) > Performance drop on sql yardstick benchmarks > > > Key: IGNITE-9784 > URL: https://issues.apache.org/jira/browse/IGNITE-9784 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.7 >Reporter: Ilya Suntsov >Assignee: Alexey Goncharuk >Priority: Blocker > Fix For: 2.7 > > Attachments: Screen Shot 2018-10-03 at 4.52.22 PM.png > > > Please take a look at the attachment. > Grid configuration: > * 4 servers / 8 clients > * java 8 > * 64 threads, 60s warmup, 180s duration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9784) Performance drop on sql yardstick benchmarks
[ https://issues.apache.org/jira/browse/IGNITE-9784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Suntsov updated IGNITE-9784: - Attachment: (was: Screen Shot 2018-10-19 at 12.11.41 PM (2).png) > Performance drop on sql yardstick benchmarks > > > Key: IGNITE-9784 > URL: https://issues.apache.org/jira/browse/IGNITE-9784 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.7 >Reporter: Ilya Suntsov >Assignee: Alexey Goncharuk >Priority: Blocker > Fix For: 2.7 > > Attachments: Screen Shot 2018-10-03 at 4.52.22 PM.png > > > Please take a look at the attachment. > Grid configuration: > * 4 servers / 8 clients > * java 8 > * 64 threads, 60s warmup, 180s duration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9784) Performance drop on sql yardstick benchmarks
[ https://issues.apache.org/jira/browse/IGNITE-9784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Suntsov updated IGNITE-9784: - Attachment: (was: Screen Shot 2018-10-19 at 12.12.09 PM (2).png) > Performance drop on sql yardstick benchmarks > > > Key: IGNITE-9784 > URL: https://issues.apache.org/jira/browse/IGNITE-9784 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.7 >Reporter: Ilya Suntsov >Assignee: Alexey Goncharuk >Priority: Blocker > Fix For: 2.7 > > Attachments: Screen Shot 2018-10-03 at 4.52.22 PM.png > > > Please take a look at the attachment. > Grid configuration: > * 4 servers / 8 clients > * java 8 > * 64 threads, 60s warmup, 180s duration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9784) Performance drop on sql yardstick benchmarks
[ https://issues.apache.org/jira/browse/IGNITE-9784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Suntsov updated IGNITE-9784: - Attachment: (was: Screen Shot 2018-10-19 at 12.08.16 PM (2).png) > Performance drop on sql yardstick benchmarks > > > Key: IGNITE-9784 > URL: https://issues.apache.org/jira/browse/IGNITE-9784 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.7 >Reporter: Ilya Suntsov >Assignee: Alexey Goncharuk >Priority: Blocker > Fix For: 2.7 > > Attachments: Screen Shot 2018-10-03 at 4.52.22 PM.png, Screen Shot > 2018-10-19 at 12.10.36 PM (2).png, Screen Shot 2018-10-19 at 12.11.41 PM > (2).png, Screen Shot 2018-10-19 at 12.12.09 PM (2).png > > > Please take a look at the attachment. > Grid configuration: > * 4 servers / 8 clients > * java 8 > * 64 threads, 60s warmup, 180s duration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9784) Performance drop on sql yardstick benchmarks
[ https://issues.apache.org/jira/browse/IGNITE-9784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Suntsov updated IGNITE-9784: - Comment: was deleted (was: I've made some performance tests. I compared master and ignite-9784. Results were attached as pictures. Main finding: last fixes increased throughput from 10 to 100% on SQL !Screen Shot 2018-10-19 at 12.12.09 PM (2).png! benchmarks. ) > Performance drop on sql yardstick benchmarks > > > Key: IGNITE-9784 > URL: https://issues.apache.org/jira/browse/IGNITE-9784 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.7 >Reporter: Ilya Suntsov >Assignee: Alexey Goncharuk >Priority: Blocker > Fix For: 2.7 > > Attachments: Screen Shot 2018-10-03 at 4.52.22 PM.png, Screen Shot > 2018-10-19 at 12.10.36 PM (2).png, Screen Shot 2018-10-19 at 12.11.41 PM > (2).png, Screen Shot 2018-10-19 at 12.12.09 PM (2).png > > > Please take a look at the attachment. > Grid configuration: > * 4 servers / 8 clients > * java 8 > * 64 threads, 60s warmup, 180s duration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9784) Performance drop on sql yardstick benchmarks
[ https://issues.apache.org/jira/browse/IGNITE-9784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Suntsov updated IGNITE-9784: - Attachment: (was: Screen Shot 2018-10-19 at 12.09.55 PM (2).png) > Performance drop on sql yardstick benchmarks > > > Key: IGNITE-9784 > URL: https://issues.apache.org/jira/browse/IGNITE-9784 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.7 >Reporter: Ilya Suntsov >Assignee: Alexey Goncharuk >Priority: Blocker > Fix For: 2.7 > > Attachments: Screen Shot 2018-10-03 at 4.52.22 PM.png, Screen Shot > 2018-10-19 at 12.10.36 PM (2).png, Screen Shot 2018-10-19 at 12.11.41 PM > (2).png, Screen Shot 2018-10-19 at 12.12.09 PM (2).png > > > Please take a look at the attachment. > Grid configuration: > * 4 servers / 8 clients > * java 8 > * 64 threads, 60s warmup, 180s duration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9784) Performance drop on sql yardstick benchmarks
[ https://issues.apache.org/jira/browse/IGNITE-9784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Suntsov updated IGNITE-9784: - Attachment: (was: Screen Shot 2018-10-19 at 12.09.13 PM (2).png) > Performance drop on sql yardstick benchmarks > > > Key: IGNITE-9784 > URL: https://issues.apache.org/jira/browse/IGNITE-9784 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.7 >Reporter: Ilya Suntsov >Assignee: Alexey Goncharuk >Priority: Blocker > Fix For: 2.7 > > Attachments: Screen Shot 2018-10-03 at 4.52.22 PM.png, Screen Shot > 2018-10-19 at 12.10.36 PM (2).png, Screen Shot 2018-10-19 at 12.11.41 PM > (2).png, Screen Shot 2018-10-19 at 12.12.09 PM (2).png > > > Please take a look at the attachment. > Grid configuration: > * 4 servers / 8 clients > * java 8 > * 64 threads, 60s warmup, 180s duration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8719) Index left partially built if a node crashes during index create or rebuild
[ https://issues.apache.org/jira/browse/IGNITE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov reassigned IGNITE-8719: -- Assignee: Sergey Antonov (was: Dmitriy Sorokin) > Index left partially built if a node crashes during index create or rebuild > --- > > Key: IGNITE-8719 > URL: https://issues.apache.org/jira/browse/IGNITE-8719 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Goncharuk >Assignee: Sergey Antonov >Priority: Critical > Fix For: 2.8 > > Attachments: IndexRebuildingTest.java > > > Currently, we do not have any state associated with the index tree. Consider > the following scenario: > 1) Start node, put some data > 2) start CREATE INDEX operation > 3) Wait for a checkpoint and stop node before index create finished > 4) Restart node > Since the checkpoint finished, the new index tree will be persisted to the > disk, but not all data will be present in the index. > We should somehow store information about initializing index tree and mark it > valid only after all data is indexed. The state should be persisted as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9784) Performance drop on sql yardstick benchmarks
[ https://issues.apache.org/jira/browse/IGNITE-9784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656493#comment-16656493 ] Ilya Suntsov commented on IGNITE-9784: -- I've made some performance tests. I compared master and ignite-9784. Results were attached as pictures. Main finding: last fixes increased throughput from 10 to 100% on SQL benchmarks. > Performance drop on sql yardstick benchmarks > > > Key: IGNITE-9784 > URL: https://issues.apache.org/jira/browse/IGNITE-9784 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.7 >Reporter: Ilya Suntsov >Assignee: Alexey Goncharuk >Priority: Blocker > Fix For: 2.7 > > Attachments: Screen Shot 2018-10-03 at 4.52.22 PM.png, Screen Shot > 2018-10-19 at 12.10.36 PM (2).png, Screen Shot 2018-10-19 at 12.11.41 PM > (2).png, Screen Shot 2018-10-19 at 12.12.09 PM (2).png > > > Please take a look at the attachment. > Grid configuration: > * 4 servers / 8 clients > * java 8 > * 64 threads, 60s warmup, 180s duration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9784) Performance drop on sql yardstick benchmarks
[ https://issues.apache.org/jira/browse/IGNITE-9784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Suntsov updated IGNITE-9784: - Attachment: Screen Shot 2018-10-19 at 12.08.16 PM (2).png Screen Shot 2018-10-19 at 12.09.13 PM (2).png Screen Shot 2018-10-19 at 12.09.55 PM (2).png Screen Shot 2018-10-19 at 12.10.36 PM (2).png Screen Shot 2018-10-19 at 12.11.41 PM (2).png Screen Shot 2018-10-19 at 12.12.09 PM (2).png > Performance drop on sql yardstick benchmarks > > > Key: IGNITE-9784 > URL: https://issues.apache.org/jira/browse/IGNITE-9784 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.7 >Reporter: Ilya Suntsov >Assignee: Alexey Goncharuk >Priority: Blocker > Fix For: 2.7 > > Attachments: Screen Shot 2018-10-03 at 4.52.22 PM.png, Screen Shot > 2018-10-19 at 12.08.16 PM (2).png, Screen Shot 2018-10-19 at 12.09.13 PM > (2).png, Screen Shot 2018-10-19 at 12.09.55 PM (2).png, Screen Shot > 2018-10-19 at 12.10.36 PM (2).png, Screen Shot 2018-10-19 at 12.11.41 PM > (2).png, Screen Shot 2018-10-19 at 12.12.09 PM (2).png > > > Please take a look at the attachment. > Grid configuration: > * 4 servers / 8 clients > * java 8 > * 64 threads, 60s warmup, 180s duration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9776) FsyncModeFileWriteAheadLogManager can block forever in log() call
[
https://issues.apache.org/jira/browse/IGNITE-9776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656488#comment-16656488
]
Alexey Goncharuk commented on IGNITE-9776:
--
Blockers are either present in master or not related to the changes.
> FsyncModeFileWriteAheadLogManager can block forever in log() call
> -
>
> Key: IGNITE-9776
> URL: https://issues.apache.org/jira/browse/IGNITE-9776
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Kuznetsov
>Assignee: Alexey Stelmak
>Priority: Major
> Fix For: 2.7
>
> Attachments: FsyncWalRolloverDoesNotBlockTest.java
>
>
> If WAL archiver is disabled and WALRecord being logged has {{rollOver() ==
> true}}, then {{log()}} call blocks forever in {{FileArchiver}}'s (!) method:
> {noformat}
> nextAbsoluteSegmentIndex:1707, FsyncModeFileWriteAheadLogManager$FileArchiver
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> access$3200:1437, FsyncModeFileWriteAheadLogManager$FileArchiver
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> pollNextFile:1384, FsyncModeFileWriteAheadLogManager
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> initNextWriteHandle:1243, FsyncModeFileWriteAheadLogManager
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> rollOver:1130, FsyncModeFileWriteAheadLogManager
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> log:712, FsyncModeFileWriteAheadLogManager
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> {noformat}
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9940) [TC Bot ] TC Bot Needed Contributions
[ https://issues.apache.org/jira/browse/IGNITE-9940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PetrovMikhail reassigned IGNITE-9940: - Assignee: PetrovMikhail > [TC Bot ] TC Bot Needed Contributions > - > > Key: IGNITE-9940 > URL: https://issues.apache.org/jira/browse/IGNITE-9940 > Project: Ignite > Issue Type: Task >Reporter: PetrovMikhail >Assignee: PetrovMikhail >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9940) [TC Bot ] TC Bot Needed Contributions
PetrovMikhail created IGNITE-9940: - Summary: [TC Bot ] TC Bot Needed Contributions Key: IGNITE-9940 URL: https://issues.apache.org/jira/browse/IGNITE-9940 Project: Ignite Issue Type: Task Reporter: PetrovMikhail -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9845) Web Console: Add support of two way ssl authentication in Web Console agent
[ https://issues.apache.org/jira/browse/IGNITE-9845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov updated IGNITE-9845: --- Description: RestExecutor should not be shared between different users requests in case of two way ssl authentication: * For each token with ssl we need create separated RestExecutor and set up socketFactory and trustManager. * RestExecutor should be removed if token expired. Add program arguments for passing client certificate, client password, trust store, trust store password for ignite node connection and web console backend. Example on okhttp: [https://github.com/square/okhttp/blob/cd872fd83824512c128dcd80c04d445c8a2fc8eb/okhttp-tests/src/test/java/okhttp3/internal/tls/ClientAuthTest.java] was: RestExecutor should not be shared between different users requests in case of two way ssl authentication: * For each token with ssl we need create separated RestExecutor and set up socketFactory and trustManager. * RestExecutor should be removed if token expired. Add program arguments for passing client certificate, client password, trust store, trust store password for metrics collection task in agent. Example on okhttp: https://github.com/square/okhttp/blob/cd872fd83824512c128dcd80c04d445c8a2fc8eb/okhttp-tests/src/test/java/okhttp3/internal/tls/ClientAuthTest.java > Web Console: Add support of two way ssl authentication in Web Console agent > --- > > Key: IGNITE-9845 > URL: https://issues.apache.org/jira/browse/IGNITE-9845 > Project: Ignite > Issue Type: Improvement > Components: wizards >Affects Versions: 2.6 >Reporter: Andrey Novikov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > RestExecutor should not be shared between different users requests in case of > two way ssl authentication: > * For each token with ssl we need create separated RestExecutor and set up > socketFactory and trustManager. > * RestExecutor should be removed if token expired. > Add program arguments for passing client certificate, client password, trust > store, trust store password for ignite node connection and web console > backend. > Example on okhttp: > [https://github.com/square/okhttp/blob/cd872fd83824512c128dcd80c04d445c8a2fc8eb/okhttp-tests/src/test/java/okhttp3/internal/tls/ClientAuthTest.java] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9845) Web Console: Add support of two way ssl authentication in Web Console agent
[ https://issues.apache.org/jira/browse/IGNITE-9845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656462#comment-16656462 ] Andrey Novikov commented on IGNITE-9845: Comments was added into pull request. > Web Console: Add support of two way ssl authentication in Web Console agent > --- > > Key: IGNITE-9845 > URL: https://issues.apache.org/jira/browse/IGNITE-9845 > Project: Ignite > Issue Type: Improvement > Components: wizards >Affects Versions: 2.6 >Reporter: Andrey Novikov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > RestExecutor should not be shared between different users requests in case of > two way ssl authentication: > * For each token with ssl we need create separated RestExecutor and set up > socketFactory and trustManager. > * RestExecutor should be removed if token expired. > Add program arguments for passing client certificate, client password, trust > store, trust store password for metrics collection task in agent. > > Example on okhttp: > https://github.com/square/okhttp/blob/cd872fd83824512c128dcd80c04d445c8a2fc8eb/okhttp-tests/src/test/java/okhttp3/internal/tls/ClientAuthTest.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9845) Web Console: Add support of two way ssl authentication in Web Console agent
[ https://issues.apache.org/jira/browse/IGNITE-9845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reassigned IGNITE-9845: -- Assignee: Alexey Kuznetsov (was: Andrey Novikov) > Web Console: Add support of two way ssl authentication in Web Console agent > --- > > Key: IGNITE-9845 > URL: https://issues.apache.org/jira/browse/IGNITE-9845 > Project: Ignite > Issue Type: Improvement > Components: wizards >Affects Versions: 2.6 >Reporter: Andrey Novikov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > RestExecutor should not be shared between different users requests in case of > two way ssl authentication: > * For each token with ssl we need create separated RestExecutor and set up > socketFactory and trustManager. > * RestExecutor should be removed if token expired. > Add program arguments for passing client certificate, client password, trust > store, trust store password for metrics collection task in agent. > > Example on okhttp: > https://github.com/square/okhttp/blob/cd872fd83824512c128dcd80c04d445c8a2fc8eb/okhttp-tests/src/test/java/okhttp3/internal/tls/ClientAuthTest.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7782) Thin Client lib: Python
[ https://issues.apache.org/jira/browse/IGNITE-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656439#comment-16656439 ] Dmitry Melnichuk edited comment on IGNITE-7782 at 10/19/18 8:28 AM: The client was successfully tested on the following OSes/architectures/platforms: * Arch Linux, AMD64, Python 3.4, 3.6, 3.7; * Ubuntu Server 16.04, i386, Python 3.5\*; * Windows Server 2008 R2, x86-64, Python 3.7; * Windows 10 Home N, x86-32, Python 3.7, * FreeBSD 11.2, AMD64, Python 3.6; * FreeBSD 11.2, i386, Python 3.6. \* _pip_ in Ubuntu 16.04 repository is outdated. Make sure to uninstall it, than install with [get-pip|https://pip.pypa.io/en/stable/installing/#installing-with-get-pip-py] script. was (Author: melnichuk): The client was successfully tested on the following OSes/architectures/platforms: * Arch Linux, AMD64, Python 3.4, 3.6, 3.7; * Ubuntu Server 16.04, i386, Python 3.5***; * Windows Server 2008 R2, x86-64, Python 3.7; * Windows 10 Home N, x86-32, Python 3.7, * FreeBSD 11.2, AMD64, Python 3.6; * FreeBSD 11.2, i386, Python 3.6. *** _pip_ in Ubuntu 16.04 repository is outdated. Make sure to uninstall it, than install with [get-pip|https://pip.pypa.io/en/stable/installing/#installing-with-get-pip-py] script. > Thin Client lib: Python > --- > > Key: IGNITE-7782 > URL: https://issues.apache.org/jira/browse/IGNITE-7782 > Project: Ignite > Issue Type: New Feature > Components: thin client >Affects Versions: 2.7 >Reporter: Alexey Kosenchuk >Assignee: Dmitry Melnichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7 > > > Implement Thin (lightweight) Client lib in Python programming language for > Ignite Binary Client Protocol > [https://apacheignite.readme.io/docs/binary-client-protocol] > Prototype: > [https://github.com/skozlov-gridgain/apache-ignite-python-thin-client] > Example - NodeJS client - IGNITE- > [https://github.com/nobitlost/ignite/tree/master/modules/platforms/nodejs] > --- > h5. Package name (for use with setuptools/PyPI): > pyignite > h5. Location of the lib in the repository: > .../modules/platforms/python > h5. Python version: > 3.4+ (tested on 3.4 and 3.6) > h5. Ignite version: > 2.7. > h5. Architecture: > Syncronous (safe for use with threading/multiprocessing), object-oriented. > h5. Documentation: > Sphinx/autodoc + readme.md > h5. Test framework: > pytest, pytest-runner for setuptools pytest integration. > h5. Usage examples included: > - cache management (creating, configuring, deleting), > - key-value operations, > - cache scan, > - basic SQL queries, > - simple and advanced work with Complex objects, > - fail-over connection. > h5. Goal: > Create a full-featured Ignite thin client library: > - carefully implement, test, and document all the features of the binary > protocol, that can be useful in Python programs, > - implement and document features like type IDs or serialization hints, that > are mostly useless in Python, for interoperability's sake, > - skip features, that are not applicable to Python programs, like filter > object in scan query. > h5. Proposed scope of features: > - basic and SSL-wrapped TCP connection, > - authentication and authorization, > - failover mechanism, > - all datatypes, > - all client operations (except Binary-Type operations with type names). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9908) thin python: Can't use client with windows
[
https://issues.apache.org/jira/browse/IGNITE-9908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656441#comment-16656441
]
Dmitry Melnichuk commented on IGNITE-9908:
--
The client was successfully tested on the following
OSes/architectures/platforms:
* Arch Linux, AMD64, Python 3.4, 3.6, 3.7;
* Ubuntu Server 16.04, i386, Python 3.5\*;
* Windows Server 2008 R2, x86-64, Python 3.7;
* Windows 10 Home N, x86-32, Python 3.7,
* FreeBSD 11.2, AMD64, Python 3.6;
* FreeBSD 11.2, i386, Python 3.6.
\* _pip_ in Ubuntu 16.04 repository is outdated. Make sure to uninstall it,
than install with
[get-pip|https://pip.pypa.io/en/stable/installing/#installing-with-get-pip-py]
script.
> thin python: Can't use client with windows
> --
>
> Key: IGNITE-9908
> URL: https://issues.apache.org/jira/browse/IGNITE-9908
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
> Environment: Windows 10 1803
> Python 3.7
> Client module installed from latest sources, branch - master
> Ignite compiled from latest sources
>Reporter: Stepan Pilschikov
>Assignee: Dmitry Melnichuk
>Priority: Major
> Labels: windows
> Fix For: 2.7
>
>
> Trying to use thin python client on Windows and have exception
> Python excetion:
> {code}
> Traceback (most recent call last):
> File "C:\dev\test\put_value.py", line 5, in
> cache = client.get_or_create_cache("test_3")
> File "[ignite path]\platforms\python\pyignite\client.py", line 306, in
> get_or_create_cache
> return Cache(self, settings, with_get=True)
> File "[ignite path]\platforms\python\pyignite\cache.py", line 116, in
> __init__
> result = func(client, settings)
> File "[ignite path]\platforms\python\pyignite\api\cache_config.py", line
> 151, in cache_get_or_create
> 'cache_name': name,
> File "[ignite path]\platforms\python\pyignite\queries\__init__.py", line
> 287, in perform
> response_ctype, recv_buffer = response_struct.parse(conn)
> File "[ignite path]\platforms\python\pyignite\queries\__init__.py", line
> 66, in parse
> buffer = client.recv(ctypes.sizeof(header_class))
> File "[ignite path]\platforms\python\pyignite\connection\__init__.py", line
> 292, in recv
> result += self._recv(buffersize-pref_size, flags)
> File "[ignite path]\platforms\python\pyignite\connection\__init__.py", line
> 316, in _recv
> raise SocketError('Socket connection broken.')
> OSError: Socket connection broken.
> {code}
> In ignite logs:
> {code}
> [11:19:20,522][SEVERE][client-connector-#47][ClientListenerNioListener]
> Failed to parse client request.
> class org.apache.ignite.binary.BinaryObjectException: Unexpected field type
> [pos=10, expected=String, actual=0]
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.checkFlagNoHandles(BinaryReaderExImpl.java:1679)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readString(BinaryReaderExImpl.java:1057)
> at
> org.apache.ignite.internal.processors.platform.client.cache.ClientCacheGetOrCreateWithNameRequest.(ClientCacheGetOrCreateWithNameRequest.java:41)
> at
> org.apache.ignite.internal.processors.platform.client.ClientMessageParser.decode(ClientMessageParser.java:342)
> at
> org.apache.ignite.internal.processors.platform.client.ClientMessageParser.decode(ClientMessageParser.java:238)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:140)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:45)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Python code:
> {code}
> from pyignite import Client
> client = Client()
> client.connect('127.0.0.1', 10800)
> cache = client.get_or_create_cache("test_3")
> cache.put("key3", -3.3)
> {code}
> All others thin clients from same sources and on the same ignite binary works
> well
> On linux from same sources python
[jira] [Commented] (IGNITE-7782) Thin Client lib: Python
[ https://issues.apache.org/jira/browse/IGNITE-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656439#comment-16656439 ] Dmitry Melnichuk commented on IGNITE-7782: -- The client was successfully tested on the following OSes/architectures/platforms: * Arch Linux, AMD64, Python 3.4, 3.6, 3.7; * Ubuntu Server 16.04, i386, Python 3.5***; * Windows Server 2008 R2, x86-64, Python 3.7; * Windows 10 Home N, x86-32, Python 3.7, * FreeBSD 11.2, AMD64, Python 3.6; * FreeBSD 11.2, i386, Python 3.6. *** _pip_ in Ubuntu 16.04 repository is outdated. Make sure to uninstall it, than install with [get-pip|https://pip.pypa.io/en/stable/installing/#installing-with-get-pip-py] script. > Thin Client lib: Python > --- > > Key: IGNITE-7782 > URL: https://issues.apache.org/jira/browse/IGNITE-7782 > Project: Ignite > Issue Type: New Feature > Components: thin client >Affects Versions: 2.7 >Reporter: Alexey Kosenchuk >Assignee: Dmitry Melnichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7 > > > Implement Thin (lightweight) Client lib in Python programming language for > Ignite Binary Client Protocol > [https://apacheignite.readme.io/docs/binary-client-protocol] > Prototype: > [https://github.com/skozlov-gridgain/apache-ignite-python-thin-client] > Example - NodeJS client - IGNITE- > [https://github.com/nobitlost/ignite/tree/master/modules/platforms/nodejs] > --- > h5. Package name (for use with setuptools/PyPI): > pyignite > h5. Location of the lib in the repository: > .../modules/platforms/python > h5. Python version: > 3.4+ (tested on 3.4 and 3.6) > h5. Ignite version: > 2.7. > h5. Architecture: > Syncronous (safe for use with threading/multiprocessing), object-oriented. > h5. Documentation: > Sphinx/autodoc + readme.md > h5. Test framework: > pytest, pytest-runner for setuptools pytest integration. > h5. Usage examples included: > - cache management (creating, configuring, deleting), > - key-value operations, > - cache scan, > - basic SQL queries, > - simple and advanced work with Complex objects, > - fail-over connection. > h5. Goal: > Create a full-featured Ignite thin client library: > - carefully implement, test, and document all the features of the binary > protocol, that can be useful in Python programs, > - implement and document features like type IDs or serialization hints, that > are mostly useless in Python, for interoperability's sake, > - skip features, that are not applicable to Python programs, like filter > object in scan query. > h5. Proposed scope of features: > - basic and SSL-wrapped TCP connection, > - authentication and authorization, > - failover mechanism, > - all datatypes, > - all client operations (except Binary-Type operations with type names). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9939) [TC Bot] Handle situation within BuildObserver when build status is "UNKNOWN"
PetrovMikhail created IGNITE-9939: - Summary: [TC Bot] Handle situation within BuildObserver when build status is "UNKNOWN" Key: IGNITE-9939 URL: https://issues.apache.org/jira/browse/IGNITE-9939 Project: Ignite Issue Type: Task Reporter: PetrovMikhail Assignee: PetrovMikhail -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9769) IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 is flaky
[
https://issues.apache.org/jira/browse/IGNITE-9769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656420#comment-16656420
]
Ryabov Dmitrii commented on IGNITE-9769:
[~agoncharuk], I added awaiting for specific affinity version in PR.
[Test
suite|https://ci.ignite.apache.org/viewLog.html?buildId=2116507=buildResultsDiv=IgniteTests24Java8_Cache5]
is ok. [100
runs|https://ci.ignite.apache.org/viewLog.html?buildId=2068911=buildResultsDiv=IgniteTests24Java8_Cache5]
are ok.
> IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 is flaky
> ---
>
> Key: IGNITE-9769
> URL: https://issues.apache.org/jira/browse/IGNITE-9769
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Trivial
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> {{IgniteCacheAtomicProtocolTest.testPutReaderUpdate1}} and
> {{IgniteCacheAtomicProtocolTest.testPutReaderUpdate2}} are flaky.
> In the {{#readerUpdateDhtFails}} method we blocks
> {{GridDhtAtomicNearResponse}} messages and do put operation. Put should hangs
> always, but sometimes it doesn't.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9719) Extra rebalanceThreadPoolSize check on client node.
[ https://issues.apache.org/jira/browse/IGNITE-9719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656377#comment-16656377 ] Luchnikov Alexander commented on IGNITE-9719: - could someone review again? > Extra rebalanceThreadPoolSize check on client node. > --- > > Key: IGNITE-9719 > URL: https://issues.apache.org/jira/browse/IGNITE-9719 > Project: Ignite > Issue Type: Improvement > Components: clients >Affects Versions: 2.6 >Reporter: Stanilovsky Evgeny >Assignee: Luchnikov Alexander >Priority: Minor > Fix For: 2.8 > > > No need to check rebalance thread pool size on client side in > IgniteKernal#ackRebalanceConfiguration method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9875) GridDhtPartitionsStateValidator speedup proposal.
[ https://issues.apache.org/jira/browse/IGNITE-9875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656375#comment-16656375 ] Alexey Goncharuk commented on IGNITE-9875: -- [~Mmuzaf], thanks for noticing, I've fixed the license in master. > GridDhtPartitionsStateValidator speedup proposal. > -- > > Key: IGNITE-9875 > URL: https://issues.apache.org/jira/browse/IGNITE-9875 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 2.6 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Fix For: 2.8 > > > I check validatePartitionsUpdateCounters and validatePartitionsSizes code > implementations and looks like we can speed up some parts of them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6064) Rework control.sh script
[ https://issues.apache.org/jira/browse/IGNITE-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656359#comment-16656359 ] Alexey Kuznetsov commented on IGNITE-6064: -- I also have a couple of suggestions: # Move this utility to separate module (for example ignite-tools? ignite-cli?) # Add support for --output-format TEXT|JSON|XML ... > 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)
