[jira] [Resolved] (IGNITE-3845) Web console > Model: the preview of 'general' and 'SQL' sections shows the same content
[ https://issues.apache.org/jira/browse/IGNITE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov resolved IGNITE-3845. Resolution: Fixed Assignee: Vasiliy Sisko (was: Dmitriy Shabalin) Fixed. Vasiliy, please retest. > Web console > Model: the preview of 'general' and 'SQL' sections shows the > same content > --- > > Key: IGNITE-3845 > URL: https://issues.apache.org/jira/browse/IGNITE-3845 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko > Attachments: ig-3845.png > > > Create new model. > Enter any info in the SQL section. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3847) Cross-platform example for the cluster of Java, .NET and C++ nodes
[ https://issues.apache.org/jira/browse/IGNITE-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-3847: --- Priority: Minor (was: Major) > Cross-platform example for the cluster of Java, .NET and C++ nodes > -- > > Key: IGNITE-3847 > URL: https://issues.apache.org/jira/browse/IGNITE-3847 > Project: Ignite > Issue Type: Bug >Reporter: Denis Magda >Assignee: Pavel Tupitsyn >Priority: Minor > Fix For: 2.0 > > > Example should demonstrate the following: > - ability to have nodes of different types (Java, C++ and .Net) in a single > cluster. > - execute basic cache.get/put operations converting objects from binary > format to a specific class/type. > - execute SQL queries. > - execute continuous queries. > A good example is the one that is described in this blog post > https://ptupitsyn.github.io/Ignite-Multi-Platform-Cluster/ > There can be a chat like example where each node can post a message into a > cache and the rest can listen for the changes in the cache using continuous > queries. In addition, we should provide a special keyword like "SQL_history" > that will trigger a SQL query execution when it's typed in the console. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3847) Cross-platform example for the cluster of Java, .NET and C++ nodes
[ https://issues.apache.org/jira/browse/IGNITE-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-3847: --- Issue Type: Improvement (was: Bug) > Cross-platform example for the cluster of Java, .NET and C++ nodes > -- > > Key: IGNITE-3847 > URL: https://issues.apache.org/jira/browse/IGNITE-3847 > Project: Ignite > Issue Type: Improvement >Reporter: Denis Magda >Assignee: Pavel Tupitsyn >Priority: Minor > Fix For: 2.0 > > > Example should demonstrate the following: > - ability to have nodes of different types (Java, C++ and .Net) in a single > cluster. > - execute basic cache.get/put operations converting objects from binary > format to a specific class/type. > - execute SQL queries. > - execute continuous queries. > A good example is the one that is described in this blog post > https://ptupitsyn.github.io/Ignite-Multi-Platform-Cluster/ > There can be a chat like example where each node can post a message into a > cache and the rest can listen for the changes in the cache using continuous > queries. In addition, we should provide a special keyword like "SQL_history" > that will trigger a SQL query execution when it's typed in the console. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3847) Cross-platform example for the cluster of Java, .NET and C++ nodes
[ https://issues.apache.org/jira/browse/IGNITE-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-3847: --- Summary: Cross-platform example for the cluster of Java, .NET and C++ nodes (was: Cross-platform example for the cluster of Java, .Net and C++ nodes) > Cross-platform example for the cluster of Java, .NET and C++ nodes > -- > > Key: IGNITE-3847 > URL: https://issues.apache.org/jira/browse/IGNITE-3847 > Project: Ignite > Issue Type: Bug >Reporter: Denis Magda >Assignee: Pavel Tupitsyn > Fix For: 2.0 > > > Example should demonstrate the following: > - ability to have nodes of different types (Java, C++ and .Net) in a single > cluster. > - execute basic cache.get/put operations converting objects from binary > format to a specific class/type. > - execute SQL queries. > - execute continuous queries. > A good example is the one that is described in this blog post > https://ptupitsyn.github.io/Ignite-Multi-Platform-Cluster/ > There can be a chat like example where each node can post a message into a > cache and the rest can listen for the changes in the cache using continuous > queries. In addition, we should provide a special keyword like "SQL_history" > that will trigger a SQL query execution when it's typed in the console. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3376) IGFS: Allow direct PROXY mode invocations.
[ https://issues.apache.org/jira/browse/IGNITE-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov reassigned IGNITE-3376: Assignee: Taras Ledkov > IGFS: Allow direct PROXY mode invocations. > -- > > Key: IGNITE-3376 > URL: https://issues.apache.org/jira/browse/IGNITE-3376 > Project: Ignite > Issue Type: Task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Critical > Labels: roadmap > > Currently we do not have special handling for PROXY mode. So we will either > hit AssertionError during dev, or will go to incorrect code path in > productions systems. > We need to fix that - PROXY mode should be handled correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-3809) ArrayIndexOutOfBoundsException in GridUnsafeLru
[
https://issues.apache.org/jira/browse/IGNITE-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shtykh closed IGNITE-3809.
Merged.
> ArrayIndexOutOfBoundsException in GridUnsafeLru
> ---
>
> Key: IGNITE-3809
> URL: https://issues.apache.org/jira/browse/IGNITE-3809
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Roman Shtykh
> Fix For: 1.8
>
>
> {{GridUnsafeLru.offer(..)}} method uses atomic integer as a counter. In case
> of integer overflow this method will throw {{ArrayIndexOutOfBoundsException}}.
> We should use {{abs}} to avoid this. For example, like this:
> {code}
> return lrus[U.safeAbs(addIdx.getAndIncrement()) % cnt].offer(part, addr,
> hash);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3809) ArrayIndexOutOfBoundsException in GridUnsafeLru
[
https://issues.apache.org/jira/browse/IGNITE-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469626#comment-15469626
]
ASF GitHub Bot commented on IGNITE-3809:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1017
> ArrayIndexOutOfBoundsException in GridUnsafeLru
> ---
>
> Key: IGNITE-3809
> URL: https://issues.apache.org/jira/browse/IGNITE-3809
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Roman Shtykh
> Fix For: 1.8
>
>
> {{GridUnsafeLru.offer(..)}} method uses atomic integer as a counter. In case
> of integer overflow this method will throw {{ArrayIndexOutOfBoundsException}}.
> We should use {{abs}} to avoid this. For example, like this:
> {code}
> return lrus[U.safeAbs(addIdx.getAndIncrement()) % cnt].offer(part, addr,
> hash);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3809) ArrayIndexOutOfBoundsException in GridUnsafeLru
[
https://issues.apache.org/jira/browse/IGNITE-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469617#comment-15469617
]
Semen Boikov commented on IGNITE-3809:
--
Thanks Roman, looks good to merge now.
> ArrayIndexOutOfBoundsException in GridUnsafeLru
> ---
>
> Key: IGNITE-3809
> URL: https://issues.apache.org/jira/browse/IGNITE-3809
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Roman Shtykh
> Fix For: 1.8
>
>
> {{GridUnsafeLru.offer(..)}} method uses atomic integer as a counter. In case
> of integer overflow this method will throw {{ArrayIndexOutOfBoundsException}}.
> We should use {{abs}} to avoid this. For example, like this:
> {code}
> return lrus[U.safeAbs(addIdx.getAndIncrement()) % cnt].offer(part, addr,
> hash);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3400) IGFS: Does not correctly deallocate free space in courner case.
[
https://issues.apache.org/jira/browse/IGNITE-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469599#comment-15469599
]
Taras Ledkov edited comment on IGNITE-3400 at 9/7/16 5:24 AM:
--
{{[IgfsDataManager.processPartialBlockWrite|https://github.com/gridgain/apache-ignite/blob/sprint-2/modules/core/src/main/java/org/apache/ignite/internal/processors/igfs/IgfsDataManager.java#L1090]}}
completes the future if the size limit is exceeded. Then the *format()* method
doesn't remove entries of this file from the data cache.
When the feature completion is normal and the completion with
{{IgfsOutOfSpaceException}} doesn't work the clean up works properly.
I heard that the limits logic will be redesigned soon. Should the issue is
fixed now or with limits redesign?
was (Author: tledkov-gridgain):
{{[IgfsDataManager.processPartialBlockWrite|https://github.com/gridgain/apache-ignite/blob/sprint-2/modules/core/src/main/java/org/apache/ignite/internal/processors/igfs/IgfsDataManager.java#L1081]}}
completes the future if the size limit is exceeded. Then the *format()* method
doesn't remove entries of this file from the data cache.
When the feature completion is normal and the completion with
{{IgfsOutOfSpaceException}} doesn't work the clean up works properly.
I heard that the limits logic will be redesigned soon. Should the issue is
fixed now or with limits redesign?
> IGFS: Does not correctly deallocate free space in courner case.
> ---
>
> Key: IGNITE-3400
> URL: https://issues.apache.org/jira/browse/IGNITE-3400
> Project: Ignite
> Issue Type: Bug
> Components: IGFS
>Affects Versions: 1.7
>Reporter: Vasiliy Sisko
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>
> Steps to reproduce:
> 1) Run node with configured IGFS limited by max space (f.e. 104857600).
> 2) Copy to IGFS file with size less than IGFS space size. (f.e. 10-15 Mb)
> 3) Copy to IGFS file with size more than free space size.
> Second file have 0 size in IGFS. Used IGFS size approximately equal to the
> IGFS space size.
> 4) Copy to IGFS file with size less than expected IGFS free space size. (f.e.
> 10-15 Mb)
> New file have 0 size.
> 5) Remove all files of format IGFS
> IGFS free space approximately equal to the size of first file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3400) IGFS: Does not correctly deallocate free space in courner case.
[
https://issues.apache.org/jira/browse/IGNITE-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469599#comment-15469599
]
Taras Ledkov commented on IGNITE-3400:
--
{{[IgfsDataManager.processPartialBlockWrite|https://github.com/gridgain/apache-ignite/blob/sprint-2/modules/core/src/main/java/org/apache/ignite/internal/processors/igfs/IgfsDataManager.java#L1081]}}
completes the future if the size limit is exceeded. Then the *format()* method
doesn't remove entries of this file from the data cache.
When the feature completion is normal and the completion with
{{IgfsOutOfSpaceException}} doesn't work the clean up works properly.
I heard that the limits logic will be redesigned soon. Should the issue is
fixed now or with limits redesign?
> IGFS: Does not correctly deallocate free space in courner case.
> ---
>
> Key: IGNITE-3400
> URL: https://issues.apache.org/jira/browse/IGNITE-3400
> Project: Ignite
> Issue Type: Bug
> Components: IGFS
>Affects Versions: 1.7
>Reporter: Vasiliy Sisko
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>
> Steps to reproduce:
> 1) Run node with configured IGFS limited by max space (f.e. 104857600).
> 2) Copy to IGFS file with size less than IGFS space size. (f.e. 10-15 Mb)
> 3) Copy to IGFS file with size more than free space size.
> Second file have 0 size in IGFS. Used IGFS size approximately equal to the
> IGFS space size.
> 4) Copy to IGFS file with size less than expected IGFS free space size. (f.e.
> 10-15 Mb)
> New file have 0 size.
> 5) Remove all files of format IGFS
> IGFS free space approximately equal to the size of first file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3849) Web console: Custom table values does not have autofocus field.
Vasiliy Sisko created IGNITE-3849: - Summary: Web console: Custom table values does not have autofocus field. Key: IGNITE-3849 URL: https://issues.apache.org/jira/browse/IGNITE-3849 Project: Ignite Issue Type: Sub-task Components: wizards Affects Versions: 1.8 Reporter: Vasiliy Sisko F.e. Binary types table or cache key configuration table. Add new row. No one field has focus. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3250) Web console: incorrect Undo behavior in corner case
[ https://issues.apache.org/jira/browse/IGNITE-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469391#comment-15469391 ] Vasiliy Sisko commented on IGNITE-3250: --- Also undo does not work for simple table values. F.e. add some addresses in multicast addresses. Press section undo. Undo button is hidden but changes stay in table. > Web console: incorrect Undo behavior in corner case > --- > > Key: IGNITE-3250 > URL: https://issues.apache.org/jira/browse/IGNITE-3250 > Project: Ignite > Issue Type: Bug > Components: UI >Reporter: Pavel Konstantinov >Assignee: Dmitriy Shabalin >Priority: Minor > > # open any section with checkboxes > # enable any checkbox - Undo buttons in the section and on the top level are > become enabled > # disable the same checkbox - Undo still enabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-336) We need to add dynamic turn on/off cache statistics for Visor.
[ https://issues.apache.org/jira/browse/IGNITE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-336: Assignee: (was: Vasiliy Sisko) > We need to add dynamic turn on/off cache statistics for Visor. > -- > > Key: IGNITE-336 > URL: https://issues.apache.org/jira/browse/IGNITE-336 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: sprint-2 >Reporter: Vasiliy Sisko > > We need create task to turn on/off of cache statistics collecting. > Create Visor command for toggling. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3845) Web console > Model: the preview of 'general' and 'SQL' sections shows the same content
[ https://issues.apache.org/jira/browse/IGNITE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-3845: - Assignee: Dmitriy Shabalin (was: Vasiliy Sisko) > Web console > Model: the preview of 'general' and 'SQL' sections shows the > same content > --- > > Key: IGNITE-3845 > URL: https://issues.apache.org/jira/browse/IGNITE-3845 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Dmitriy Shabalin > Attachments: ig-3845.png > > > Create new model. > Enter any info in the SQL section. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3846) Some of the job execution events are recorded for internal tasks
[
https://issues.apache.org/jira/browse/IGNITE-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov reassigned IGNITE-3846:
Assignee: Alexey Kuznetsov
> Some of the job execution events are recorded for internal tasks
>
>
> Key: IGNITE-3846
> URL: https://issues.apache.org/jira/browse/IGNITE-3846
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 1.8
>
>
> {{GridTaskWorker.recordJobEvent(..)}} method doesn't filter out internal
> tasks. This is how the code should look like:
> {code}
> if (!internal && ctx.event().isRecordable(evtType)) {
> ...
> }
> {code}
> Tests should be added as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-532) Implement IgniteAkkaStreamer to stream data from Akka actors.
[
https://issues.apache.org/jira/browse/IGNITE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469242#comment-15469242
]
Roman Shtykh edited comment on IGNITE-532 at 9/7/16 2:13 AM:
-
Hi [~Chandresh Pancholi]
_(It seems Semen has started the review, but since I had a look at your code, I
will write my comments too)_
Putting aside minor issues, in your implementation what the actor is doing is
just creating a new streamer with data on invocation. To process it, you use
`AkkaStreamer` that has no relation to the created actor. I would recommend to
revise the code keeping in mind how it will be used the the user.
As I see it, each actor invocation has to inject data into Ignite (as in
earlier Dmitriy's and Joshua's discussion).
was (Author: roman_s):
Hi [~Chandresh Pancholi]
_(It seems Semen has started the review, but since I had a look at your code, I
will write my comments too)_
Putting aside minor issues, in your implementation what the actor is doing is
just creating a new streamer with data on invocation. To process it, you use
`AkkaStreamer` that has no relation to the created actor. I would recommend to
revise the code keeping in mind how it will be used the the user.
As I see it, each actor invocation has to inject data into Ignite.
> Implement IgniteAkkaStreamer to stream data from Akka actors.
> -
>
> Key: IGNITE-532
> URL: https://issues.apache.org/jira/browse/IGNITE-532
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Semen Boikov
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Akka|http://akka.io/] for more information. Given that Akka is a Scala
> frameworks, this streamer should be available in Scala.
> We should create {{IgniteAkkaStreamer}} which will consume messages from Akka
> Actors and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert data from Akka to Ignite using an optional pluggable converter. If
> not provided, then we should have some default mechanism.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-532) Implement IgniteAkkaStreamer to stream data from Akka actors.
[
https://issues.apache.org/jira/browse/IGNITE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469242#comment-15469242
]
Roman Shtykh edited comment on IGNITE-532 at 9/7/16 2:11 AM:
-
Hi [~Chandresh Pancholi]
_(It seems Semen has started the review, but since I had a look at your code, I
will write my comments too)_
Putting aside minor issues, in your implementation what the actor is doing is
just creating a new streamer with data on invocation. To process it, you use
`AkkaStreamer` that has no relation to the created actor. I would recommend to
revise the code keeping in mind how it will be used the the user.
As I see it, each actor invocation has to inject data into Ignite.
was (Author: roman_s):
Hi [~Chandresh Pancholi]
_(It seems Semen has started the review, but since I had a look at your code, I
will write my comments too)_
Putting aside minor issues, in your implementation what the actor is doing is
just creating a new streamer with data on invocation. To process it, you use
`AkkaStreamer` that no relation to the created actor. I would recommend to
revise the code keeping in mind how it will be used the the user.
As I see it, each actor invocation has to inject data into Ignite.
> Implement IgniteAkkaStreamer to stream data from Akka actors.
> -
>
> Key: IGNITE-532
> URL: https://issues.apache.org/jira/browse/IGNITE-532
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Semen Boikov
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Akka|http://akka.io/] for more information. Given that Akka is a Scala
> frameworks, this streamer should be available in Scala.
> We should create {{IgniteAkkaStreamer}} which will consume messages from Akka
> Actors and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert data from Akka to Ignite using an optional pluggable converter. If
> not provided, then we should have some default mechanism.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-532) Implement IgniteAkkaStreamer to stream data from Akka actors.
[
https://issues.apache.org/jira/browse/IGNITE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469242#comment-15469242
]
Roman Shtykh commented on IGNITE-532:
-
Hi [~Chandresh Pancholi]
_(It seems Semen has started the review, but since I had a look at your code, I
will write my comments too)_
Putting aside minor issues, in your implementation what the actor is doing is
just creating a new streamer with data on invocation. To process it, you use
`AkkaStreamer` that no relation to the created actor. I would recommend to
revise the code keeping in mind how it will be used the the user.
As I see it, each actor invocation has to inject data into Ignite.
> Implement IgniteAkkaStreamer to stream data from Akka actors.
> -
>
> Key: IGNITE-532
> URL: https://issues.apache.org/jira/browse/IGNITE-532
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Semen Boikov
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Akka|http://akka.io/] for more information. Given that Akka is a Scala
> frameworks, this streamer should be available in Scala.
> We should create {{IgniteAkkaStreamer}} which will consume messages from Akka
> Actors and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert data from Akka to Ignite using an optional pluggable converter. If
> not provided, then we should have some default mechanism.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3665) Update KafkaStreamer dependencies
[ https://issues.apache.org/jira/browse/IGNITE-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469172#comment-15469172 ] Roman Shtykh commented on IGNITE-3665: -- [~dmagda] Ok, sure. > Update KafkaStreamer dependencies > - > > Key: IGNITE-3665 > URL: https://issues.apache.org/jira/browse/IGNITE-3665 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Shtykh >Assignee: Roman Shtykh > Fix For: 1.8 > > > Update for Kafka 0.10 > https://archive.apache.org/dist/kafka/0.10.0.0/RELEASE_NOTES.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3809) ArrayIndexOutOfBoundsException in GridUnsafeLru
[
https://issues.apache.org/jira/browse/IGNITE-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469168#comment-15469168
]
Roman Shtykh commented on IGNITE-3809:
--
[~sboikov] Good simplification indeed. I reworked the code and change
`getAndIncrement` to `incrementAndGet` to return `next`.
Also I removed unit tests I added before -- I think they are not needed any
more, since `incrementAndGet()` takes care of max value.
> ArrayIndexOutOfBoundsException in GridUnsafeLru
> ---
>
> Key: IGNITE-3809
> URL: https://issues.apache.org/jira/browse/IGNITE-3809
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Roman Shtykh
> Fix For: 1.8
>
>
> {{GridUnsafeLru.offer(..)}} method uses atomic integer as a counter. In case
> of integer overflow this method will throw {{ArrayIndexOutOfBoundsException}}.
> We should use {{abs}} to avoid this. For example, like this:
> {code}
> return lrus[U.safeAbs(addIdx.getAndIncrement()) % cnt].offer(part, addr,
> hash);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2294) Implement SQL DML (insert, update, delete) clauses.
[ https://issues.apache.org/jira/browse/IGNITE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-2294: Labels: important (was: ) > Implement SQL DML (insert, update, delete) clauses. > --- > > Key: IGNITE-2294 > URL: https://issues.apache.org/jira/browse/IGNITE-2294 > Project: Ignite > Issue Type: Wish >Reporter: Sergi Vladykin >Assignee: Sergi Vladykin > Labels: important > Fix For: 2.0 > > > We need to add parsing for all the listed SQL commands and translate them > into respective cache operations (putIfAbstent, put, remove). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2294) Implement SQL DML (insert, update, delete) clauses.
[ https://issues.apache.org/jira/browse/IGNITE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-2294: Fix Version/s: (was: 1.8) 2.0 > Implement SQL DML (insert, update, delete) clauses. > --- > > Key: IGNITE-2294 > URL: https://issues.apache.org/jira/browse/IGNITE-2294 > Project: Ignite > Issue Type: Wish >Reporter: Sergi Vladykin >Assignee: Sergi Vladykin > Labels: important > Fix For: 2.0 > > > We need to add parsing for all the listed SQL commands and translate them > into respective cache operations (putIfAbstent, put, remove). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-961) Provide Basic NodeJS Integration
[ https://issues.apache.org/jira/browse/IGNITE-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-961: --- Fix Version/s: (was: 1.8) 2.2 > Provide Basic NodeJS Integration > > > Key: IGNITE-961 > URL: https://issues.apache.org/jira/browse/IGNITE-961 > Project: Ignite > Issue Type: New Feature > Components: clients >Reporter: Yakov Zhdanov >Assignee: Andrey Gura > Fix For: 2.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-961) Provide Basic NodeJS Integration
[ https://issues.apache.org/jira/browse/IGNITE-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-961: --- Summary: Provide Basic NodeJS Integration (was: Provide node.js integration) > Provide Basic NodeJS Integration > > > Key: IGNITE-961 > URL: https://issues.apache.org/jira/browse/IGNITE-961 > Project: Ignite > Issue Type: New Feature > Components: clients >Reporter: Yakov Zhdanov >Assignee: Andrey Gura > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1443) CPP: Implement cache continuous queries.
[ https://issues.apache.org/jira/browse/IGNITE-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-1443: Labels: cpp important roadmap (was: cpp roadmap) > CPP: Implement cache continuous queries. > > > Key: IGNITE-1443 > URL: https://issues.apache.org/jira/browse/IGNITE-1443 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Igor Sapego > Labels: cpp, important, roadmap > Fix For: 2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1443) CPP: Implement cache continuous queries.
[ https://issues.apache.org/jira/browse/IGNITE-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-1443: Fix Version/s: (was: 1.8) 2.0 > CPP: Implement cache continuous queries. > > > Key: IGNITE-1443 > URL: https://issues.apache.org/jira/browse/IGNITE-1443 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Igor Sapego > Labels: cpp, important, roadmap > Fix For: 2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-3848) Copy constructor in ConnectorConfiguration does not copy sslFactory
[
https://issues.apache.org/jira/browse/IGNITE-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko closed IGNITE-3848.
---
> Copy constructor in ConnectorConfiguration does not copy sslFactory
> ---
>
> Key: IGNITE-3848
> URL: https://issues.apache.org/jira/browse/IGNITE-3848
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.8
>
>
> Since {{sslFactory}} is not copied, it's actually ignored. The only way to
> enable SSL is to enable globally on {{IgniteConfiguration}} level.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-3848) Copy constructor in ConnectorConfiguration does not copy sslFactory
[
https://issues.apache.org/jira/browse/IGNITE-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko resolved IGNITE-3848.
-
Resolution: Fixed
> Copy constructor in ConnectorConfiguration does not copy sslFactory
> ---
>
> Key: IGNITE-3848
> URL: https://issues.apache.org/jira/browse/IGNITE-3848
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.8
>
>
> Since {{sslFactory}} is not copied, it's actually ignored. The only way to
> enable SSL is to enable globally on {{IgniteConfiguration}} level.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3848) Copy constructor in ConnectorConfiguration does not copy sslFactory
Valentin Kulichenko created IGNITE-3848:
---
Summary: Copy constructor in ConnectorConfiguration does not copy
sslFactory
Key: IGNITE-3848
URL: https://issues.apache.org/jira/browse/IGNITE-3848
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.7
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Priority: Critical
Fix For: 1.8
Since {{sslFactory}} is not copied, it's actually ignored. The only way to
enable SSL is to enable globally on {{IgniteConfiguration}} level.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3847) Cross-platform example for the cluster of Java, .Net and C++ nodes
Denis Magda created IGNITE-3847: --- Summary: Cross-platform example for the cluster of Java, .Net and C++ nodes Key: IGNITE-3847 URL: https://issues.apache.org/jira/browse/IGNITE-3847 Project: Ignite Issue Type: Bug Reporter: Denis Magda Assignee: Pavel Tupitsyn Fix For: 2.0 Example should demonstrate the following: - ability to have nodes of different types (Java, C++ and .Net) in a single cluster. - execute basic cache.get/put operations converting objects from binary format to a specific class/type. - execute SQL queries. - execute continuous queries. A good example is the one that is described in this blog post https://ptupitsyn.github.io/Ignite-Multi-Platform-Cluster/ There can be a chat like example where each node can post a message into a cache and the rest can listen for the changes in the cache using continuous queries. In addition, we should provide a special keyword like "SQL_history" that will trigger a SQL query execution when it's typed in the console. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3705) Warnings when build ignite and ignite-example cpp projects with Visual Studio 2015 (v140) toolset
[ https://issues.apache.org/jira/browse/IGNITE-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468216#comment-15468216 ] ASF GitHub Bot commented on IGNITE-3705: GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1038 IGNITE-3705: Fixes for MSVC 14.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3705 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1038.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 #1038 commit 12fd4976f482ebc43831754645e34042c9073b2d Author: sboikov Date: 2016-08-25T09:29:04Z Fixed GridQueryParsingTest. commit 12f532986677c30a716f73aeaa7d3587dd701f55 Author: sboikov Date: 2016-09-01T14:05:15Z Merge remote-tracking branch 'remotes/community/ignite-1.6.6' into ignite-1.6.7 commit ae7765329fd6f7d50d13183d13626f39c5682334 Author: dkarachentsev Date: 2016-09-02T15:01:12Z IGNITE-2208 - Queries with object arguments doesn't work wth BinaryMarshaller. commit 7a84ab6a9163ca31fbcfcc6d7ff27e06bf9babef Author: vozerov-gridgain Date: 2016-09-02T15:05:16Z IGNITE-3827: Removed double marshalling of keys in DataStreamerImpl.addData(Map) method. commit 7bb961fd0a2e78334d33b6bc279c4edc323c246a Author: vozerov-gridgain Date: 2016-09-02T15:05:54Z Merge remote-tracking branch 'upstream/ignite-1.6.7' into ignite-1.6.7 commit e3c4868d6737e5a0f0b90f99666242865add750c Author: vozerov-gridgain Date: 2016-09-02T15:23:09Z IGNITE-3829: Optimized affinity key field name handling. commit e9c797fd964727882ad6f40f2a452b17ae7c857e Author: isapego Date: 2016-09-04T13:47:40Z IGNITE-2946: CPP: Optimized GetNext() method for cursors. This closes #992. commit c992213274ec5872ef7ce359efa51e26003424ad Author: isapego Date: 2016-09-04T13:49:42Z IGNITE-3760: ODBC: Added tests for supported SQL92 string functions. This closes #1006. commit d06eaa2344a753e08d1e3cb00e6b4ab83c6a9a01 Author: isapego Date: 2016-09-04T13:52:04Z IGNITE-3801: ODBC: Added tests for OUTER JOIN. This closes #1027. commit f8ae67456703e63e3afc9bb5c21d81d576d59448 Author: tledkov-gridgain Date: 2016-09-04T14:09:08Z IGNITE-3651 IGFS: Implemented "usedSpaceSize()" operation for local secondary file system. This closes #1009. commit fc2fe7bf1905675258d40932a4ff649156c17488 Author: tledkov-gridgain Date: 2016-09-04T14:12:35Z IGNITE-3646: IGFS: Added test for symlinked mkdirs on local secondary file system. This closes #1013. commit 3aa13f716934a6ccfe49f8bf99ec3b654e263900 Author: vozerov-gridgain Date: 2016-09-05T07:19:48Z IGNITE-3829: Additional fix. commit a760918757bee71ab28495496f94e9067ef17888 Author: Igor Sapego Date: 2016-09-05T07:36:38Z IGNITE-3750: ODBC: Added tests for date/time types. This closes #1002. commit d65228e42ec9c84182b8c9c9c8d06a0056d5eed2 Author: Andrey V. Mashenkov Date: 2016-09-05T08:20:26Z IGNITE-2974: ODBC: Added "socketSendBufferSize" and "socketReceiveBufferSize" configuration parameters. This closes #994. commit 40d4b6ac6a71ed541d20018cf7deb2fb9b9bbb9b Author: vozerov-gridgain Date: 2016-09-05T08:35:26Z IGNITE-3834: Fixed a problem with BinaryMarshaller handles resolution. commit 42963e6c99e9b282972e6ad67a813a8038cf580f Author: Alexander Paschenko Date: 2016-09-05T11:10:39Z IGNITE-3817: Fixed binary object re-build with missing schema. commit df8163f1ad3a390bb8d51b0eb2f378b5b3663025 Author: Andrey V. Mashenkov Date: 2016-09-05T11:15:59Z IGNITE-3743: ODBC: Added procedure call escape sequence support. This closes #1008. commit e3533010b584ba986196f9c7dbc36359aebd829e Author: Igor Sapego Date: 2016-09-05T12:02:07Z IGNITE-3819: ODBC: Improved error logging. This closes #1024. commit 008cf64429f40635e396a71f2c0aaf184077ff2b Author: Andrey V. Mashenkov Date: 2016-09-05T12:17:53Z IGNITE-3741: ODBC: Added character escape support to expression parser. This closes #1004. commit bf9371a3ddb020209a6b031e11282706e19c58cb Author: vozerov-gridgain Date: 2016-09-05T14:05:05Z IGNITE-3611: IGFS: Slight refactoring to listPaths() and listFiles() methods. commit 2c397d2fb8851b25aa5f0a5589ad1deffbe7eee9 Author: Andrey V. Mashenkov Date: 2016-09-05T14:38:47Z IGNITE-2629: ODBC: Requests are now processed asynchronously in separate thread pool. This closes #996. commit 355082958b476009179254df9be20e225179cb7c Author: Andrey V. Mashenkov Date: 2016-09-05T15:06:27Z IGNITE-2833: GridCacheTtlManager pending queue retention size optimization. commit 8970b3e3a36b18274b451fddf365627ba23459d6 Author: Igor Sapego Date: 2016-09-05T15:15:11Z IGNITE-3628: ODBC
[jira] [Updated] (IGNITE-3793) Need to fix dependencies and it's licenses.
[ https://issues.apache.org/jira/browse/IGNITE-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-3793: Labels: important (was: ) > Need to fix dependencies and it's licenses. > --- > > Key: IGNITE-3793 > URL: https://issues.apache.org/jira/browse/IGNITE-3793 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Priority: Blocker > Labels: important > Fix For: 2.0 > > > 1) H2 license listed at LICENSE_FABRIC seems to be wrong. > Need to make sure that correct one listed at ignite-indexing-licenses.txt and > remove wrong at LICENSE_FABRIC. > 2) We need to use geronimo instead of JTA dependency. > License will be changed automativally in this case. Need to cleanup > LICENSE_FABRIC. > 3) Apache licenses should be always shown at ignite-*-licenses.txt. > licenses.txt.vm should be fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3793) Need to fix dependencies and it's licenses.
[ https://issues.apache.org/jira/browse/IGNITE-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-3793: Fix Version/s: 2.0 > Need to fix dependencies and it's licenses. > --- > > Key: IGNITE-3793 > URL: https://issues.apache.org/jira/browse/IGNITE-3793 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Priority: Blocker > Labels: important > Fix For: 2.0 > > > 1) H2 license listed at LICENSE_FABRIC seems to be wrong. > Need to make sure that correct one listed at ignite-indexing-licenses.txt and > remove wrong at LICENSE_FABRIC. > 2) We need to use geronimo instead of JTA dependency. > License will be changed automativally in this case. Need to cleanup > LICENSE_FABRIC. > 3) Apache licenses should be always shown at ignite-*-licenses.txt. > licenses.txt.vm should be fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3840) Continue investigation: High memory utilization when OFFHEAP_TIERED mode and expiry policy are enabled.
[ https://issues.apache.org/jira/browse/IGNITE-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467857#comment-15467857 ] ASF GitHub Bot commented on IGNITE-3840: GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1037 IGNITE-3840 : Continue investigation: High memory utilization when OFFHEAP_TIERED mode and expiry policy are enabled You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3840 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1037.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 #1037 commit 30aa287b881d4f9dc3fd5eec9840eab8d9a20828 Author: sboikov Date: 2016-05-24T13:57:20Z ignite-2620 Skip empty entries in GridCacheMapEntry.onTtlExpired (cherry picked from commit 6fc274a) commit e2db87bb1b6c71d7978af17e9f2005ba1c661ab4 Author: sboikov Date: 2016-05-25T07:06:43Z Added trace logging for entry/offheap updates. (cherry picked from commit 9b2767f) commit 6fcc7a41d8676956983792717483318b85781479 Author: MaBiao Date: 2016-05-25T09:54:40Z IGNITE-2538 - IgniteRDD count() and isEmpty() method use IgniteCache API commit e274d44a37fd1269e7a3a5fe1ee6139fd0b0 Author: Denis Magda Date: 2016-05-26T11:57:52Z IGNITE-3188: Binary marshaller doesn't unmarshal a void type (added tests) commit 6687e2bfb9627ce08c1c258527e2927606a500ed Author: Yakov Zhdanov Date: 2016-05-13T08:48:00Z review IGNITE-2708 Need to validate that SPIs are started only once (cherry picked from commit cd063da) commit 40a41fc50bdb73d50e2aa13da8203784be98e38a Author: Yakov Zhdanov Date: 2016-05-13T08:59:02Z reverting review IGNITE-2708 Need to validate that SPIs are started only once (cherry picked from commit bf561e1) commit d05786d8bfc8177223b6db9a98bd3c8170b6bcf1 Author: Ryan Zhao Date: 2016-05-13T09:00:43Z review IGNITE-2708 Need to validate that SPIs are started only once (commit with proper author) (cherry picked from commit 98338ff) commit 9d937ca34775f39b46568eb3fca4585ce00a0fb1 Author: Yakov Zhdanov Date: 2016-05-13T09:54:01Z review IGNITE-2708 Need to validate that SPIs are started only once (added logic to protect properly started grids) (cherry picked from commit b8d624a) commit edc2947d7340cac4a3c90fa726c23d5d47798ab9 Author: vozerov-gridgain Date: 2016-05-25T10:07:03Z IGNITE-3191: IGFS: Improved error logging for operations in dual mode. commit 2f1747d726da87b67f6c5323b3e64762d56398cb Author: vozerov-gridgain Date: 2016-05-27T11:40:17Z Merge remote-tracking branch 'upstream/gridgain-7.6.1' into gridgain-7.6.1 commit 1bb8b647264593034659b7db929c2664dec603e1 Author: sboikov Date: 2016-05-27T11:21:01Z ignite-3116 Fixed NodeStoppingException in GridDhtGetFuture. (cherry picked from commit 303d3ca) commit 47c575c8696d51b675a16aa260ec9d398e0a68e9 Author: nikolay_tikhonov Date: 2016-05-30T09:42:37Z Added benchmark property file. commit 00e2dda9a850f74178ee893a3acf74ddc30d4a13 Author: nikolay_tikhonov Date: 2016-05-30T11:45:38Z Updated benchmark property file. commit a28e16e24adb0a03df959830517db84d2505c481 Author: Vladislav Pyatkov Date: 2016-05-31T07:01:46Z IGNITE-3190: OffHeap cache metrics doesn't work properly for OFFHEAP_TIRED mode. Reviewed and merged by Denis Magda (dma...@gridgain.com) (cherry picked from commit 7533dfc) commit 56c605622dbecf71f3ee87cc41a16d2ee87e92d3 Author: vozerov-gridgain Date: 2016-05-26T08:15:48Z IGNITE-3200: Resolved classloader leak. commit a815067a0e8e7cfc9f49c57efe2b2eba562e9071 Author: vozerov-gridgain Date: 2016-05-31T07:23:00Z IGNITE-3202: Hadoop: Implemented user name mappers. commit 421cf03b03276d0ab6c32ef6665d547746446dfc Author: vozerov-gridgain Date: 2016-05-31T07:40:24Z 7.5.24: Added missing JavaDocs. commit 167e47781f65c056b9d273eea52d268bc9a8fa0b Author: Denis Magda Date: 2016-05-31T10:50:06Z IGNITE-2708: fix tests that don't create unique IndexingSPI per node (cherry picked from commit f90e424) commit 21bdf3148f05481d86e77e13b282ac44c6c3a059 Author: vozerov-gridgain Date: 2016-05-31T10:54:32Z Added pacajge info for java.org.apache.ignite.hadoop.util package. commit 3ca9febeb2bf53d17b6dea739938cff40c5fa67d Author: vozerov-gridgain Date: 2016-05-31T11:03:48Z Merge remote-tracking branch 'upstream/gridgain-7.6.1' into gridgain-7.6.1 commit f175d3c670025bd619ec347dba2a5c5f68f4cc32 Author: Vladislav Pyatkov Date: 2016-06-02T13:14:10Z IGNITE-2655: AffinityFunction: primary and backup copies in different locations Reviewed and merged by Denis Magda (dma...@gridgain.com)
[jira] [Commented] (IGNITE-3840) Continue investigation: High memory utilization when OFFHEAP_TIERED mode and expiry policy are enabled.
[ https://issues.apache.org/jira/browse/IGNITE-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467826#comment-15467826 ] Andrew Mashenkov commented on IGNITE-3840: -- GridCacheTtlManager pendingEntries Set memory consumption reduced by 20%. I have noticed no performance issues with large pendingEntries set with long-live entries as well as set with short-lived entries. > Continue investigation: High memory utilization when OFFHEAP_TIERED mode and > expiry policy are enabled. > --- > > Key: IGNITE-3840 > URL: https://issues.apache.org/jira/browse/IGNITE-3840 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.5.0.final >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Critical > Labels: community, important > Fix For: 1.8 > > Attachments: IgniteExpiryIssue.java, config.xml > > > Continue investigation of high memory utilization. > The problem is originally reported by Neil Wightman: > http://apache-ignite-users.70518.x6.nabble.com/Off-Heap-cache-using-lots-of-heap-memory-td3414.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3846) Some of the job execution events are recorded for internal tasks
Valentin Kulichenko created IGNITE-3846:
---
Summary: Some of the job execution events are recorded for
internal tasks
Key: IGNITE-3846
URL: https://issues.apache.org/jira/browse/IGNITE-3846
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.7
Reporter: Valentin Kulichenko
Priority: Critical
Fix For: 1.8
{{GridTaskWorker.recordJobEvent(..)}} method doesn't filter out internal tasks.
This is how the code should look like:
{code}
if (!internal && ctx.event().isRecordable(evtType)) {
...
}
{code}
Tests should be added as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3665) Update KafkaStreamer dependencies
[ https://issues.apache.org/jira/browse/IGNITE-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467728#comment-15467728 ] Denis Magda commented on IGNITE-3665: - [~roman_s], please send a message to the dev list asking the community for the review. Unfortunately, I won't be able to review this at the nearest time. > Update KafkaStreamer dependencies > - > > Key: IGNITE-3665 > URL: https://issues.apache.org/jira/browse/IGNITE-3665 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Shtykh >Assignee: Roman Shtykh > Fix For: 1.8 > > > Update for Kafka 0.10 > https://archive.apache.org/dist/kafka/0.10.0.0/RELEASE_NOTES.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3809) ArrayIndexOutOfBoundsException in GridUnsafeLru
[
https://issues.apache.org/jira/browse/IGNITE-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467391#comment-15467391
]
Semen Boikov commented on IGNITE-3809:
--
Hi,
There was a mistake in the my code snippet for 'getAndIncrement', it should
return 'next' instead of 'cur'. Also I think code can be simplified a little
for offer/prePoll (here you do not need extra '% cnt' for 'offer'):
{noformat}
final int MAX_CNT;
GridUnsafeLru(short cnt, GridUnsafeMemory mem) {
...
MAX_CNT = cnt - 1;
}
long offer(int part, long addr, int hash) throws
GridOffHeapOutOfMemoryException {
return lrus[getAndIncrement(addIdx, MAX_CNT)].offer(part, addr, hash);
}
long prePoll() {
int idx = getAndIncrement(rmvIdx, MAX_CNT);
// Must try to poll from each LRU.
for (int i = 0; i < lrus.length; i++) {
long qAddr = lrus[(idx + i) % cnt].prePoll();
if (qAddr != 0)
return qAddr;
}
return 0;
}
{noformat}
> ArrayIndexOutOfBoundsException in GridUnsafeLru
> ---
>
> Key: IGNITE-3809
> URL: https://issues.apache.org/jira/browse/IGNITE-3809
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Roman Shtykh
> Fix For: 1.8
>
>
> {{GridUnsafeLru.offer(..)}} method uses atomic integer as a counter. In case
> of integer overflow this method will throw {{ArrayIndexOutOfBoundsException}}.
> We should use {{abs}} to avoid this. For example, like this:
> {code}
> return lrus[U.safeAbs(addIdx.getAndIncrement()) % cnt].offer(part, addr,
> hash);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-3844) Web console: domain models list in the cache shows 'false' instead of an empty list after all models were removed
[ https://issues.apache.org/jira/browse/IGNITE-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Afanasiev resolved IGNITE-3844. - Resolution: Resolved Assignee: Pavel Konstantinov (was: Maxim Afanasiev) Fixed. Please test. > Web console: domain models list in the cache shows 'false' instead of an > empty list after all models were removed > - > > Key: IGNITE-3844 > URL: https://issues.apache.org/jira/browse/IGNITE-3844 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3844) Web console: domain models list in the cache shows 'false' instead of an empty list after all models were removed
[ https://issues.apache.org/jira/browse/IGNITE-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-3844: - Assignee: Maxim Afanasiev (was: Vasiliy Sisko) Link from cache is not removed on single domain remove. Other links is removed correctly. > Web console: domain models list in the cache shows 'false' instead of an > empty list after all models were removed > - > > Key: IGNITE-3844 > URL: https://issues.apache.org/jira/browse/IGNITE-3844 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Maxim Afanasiev > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3845) Web console > Model: the preview of 'general' and 'SQL' sections shows the same content
[ https://issues.apache.org/jira/browse/IGNITE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-3845: --- Attachment: ig-3845.png > Web console > Model: the preview of 'general' and 'SQL' sections shows the > same content > --- > > Key: IGNITE-3845 > URL: https://issues.apache.org/jira/browse/IGNITE-3845 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko > Attachments: ig-3845.png > > > Create new model. > Enter any info in the SQL section. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3845) Web console > Model: the preview of 'general' and 'SQL' sections shows the same content
Pavel Konstantinov created IGNITE-3845: -- Summary: Web console > Model: the preview of 'general' and 'SQL' sections shows the same content Key: IGNITE-3845 URL: https://issues.apache.org/jira/browse/IGNITE-3845 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Vasiliy Sisko Create new model. Enter any info in the SQL section. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3845) Web console > Model: the preview of 'general' and 'SQL' sections shows the same content
[ https://issues.apache.org/jira/browse/IGNITE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-3845: --- Component/s: wizards > Web console > Model: the preview of 'general' and 'SQL' sections shows the > same content > --- > > Key: IGNITE-3845 > URL: https://issues.apache.org/jira/browse/IGNITE-3845 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko > > Create new model. > Enter any info in the SQL section. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3844) Web console: domain models list in the cache shows 'false' instead of an empty list after all models were removed
[ https://issues.apache.org/jira/browse/IGNITE-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-3844: --- Component/s: wizards > Web console: domain models list in the cache shows 'false' instead of an > empty list after all models were removed > - > > Key: IGNITE-3844 > URL: https://issues.apache.org/jira/browse/IGNITE-3844 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2833) High memory utilization when OFFHEAP_TIERED mode and expiry policy are enabled.
[ https://issues.apache.org/jira/browse/IGNITE-2833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov closed IGNITE-2833. > High memory utilization when OFFHEAP_TIERED mode and expiry policy are > enabled. > --- > > Key: IGNITE-2833 > URL: https://issues.apache.org/jira/browse/IGNITE-2833 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.5.0.final >Reporter: Vladimir Ozerov >Assignee: Andrew Mashenkov >Priority: Critical > Labels: community, important > Fix For: 1.8 > > Attachments: IgniteExpiryIssue.java, config.xml > > > The problem is originally reported by Neil Wightman: > http://apache-ignite-users.70518.x6.nabble.com/Off-Heap-cache-using-lots-of-heap-memory-td3414.html > *Steps to reproduce* > 1) Run attached code and XML config. Observe that heap size is about 1Gb. > 2) Comment expiry policy setter in the code, run again. Now only 150Mb is > consumed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3844) Web console: domain models list in the cache shows 'false' instead of an empty list after all models were removed
Pavel Konstantinov created IGNITE-3844: -- Summary: Web console: domain models list in the cache shows 'false' instead of an empty list after all models were removed Key: IGNITE-3844 URL: https://issues.apache.org/jira/browse/IGNITE-3844 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Vasiliy Sisko -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-3420) Visor console doesn't support -cfg and -e options simultaneously
[ https://issues.apache.org/jira/browse/IGNITE-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-3420. > Visor console doesn't support -cfg and -e options simultaneously > > > Key: IGNITE-3420 > URL: https://issues.apache.org/jira/browse/IGNITE-3420 > Project: Ignite > Issue Type: Bug > Components: visor >Affects Versions: 1.6 >Reporter: Igor Rudyak > > Ignite Visor console doesn't support -cfg and -e options simultaneously. It > prints such and error: > *(wrn) : Options can't contains both -cfg and one of -b or -e options.* > Because of this it's not possible to execute several commands in batch mode > providing cluster config xml file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3809) ArrayIndexOutOfBoundsException in GridUnsafeLru
[
https://issues.apache.org/jira/browse/IGNITE-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466932#comment-15466932
]
Roman Shtykh commented on IGNITE-3809:
--
Hi Semen,
[~sboikov]
Thanks a lot for reviewing and pointing to the issue I overlooked!
I reworked the code. Hope I got it right and I can merge it.
> ArrayIndexOutOfBoundsException in GridUnsafeLru
> ---
>
> Key: IGNITE-3809
> URL: https://issues.apache.org/jira/browse/IGNITE-3809
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Roman Shtykh
> Fix For: 1.8
>
>
> {{GridUnsafeLru.offer(..)}} method uses atomic integer as a counter. In case
> of integer overflow this method will throw {{ArrayIndexOutOfBoundsException}}.
> We should use {{abs}} to avoid this. For example, like this:
> {code}
> return lrus[U.safeAbs(addIdx.getAndIncrement()) % cnt].offer(part, addr,
> hash);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3400) IGFS: Does not correctly deallocate free space in courner case.
[ https://issues.apache.org/jira/browse/IGNITE-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov reassigned IGNITE-3400: Assignee: Taras Ledkov > IGFS: Does not correctly deallocate free space in courner case. > --- > > Key: IGNITE-3400 > URL: https://issues.apache.org/jira/browse/IGNITE-3400 > Project: Ignite > Issue Type: Bug > Components: IGFS >Affects Versions: 1.7 >Reporter: Vasiliy Sisko >Assignee: Taras Ledkov > Fix For: 1.8 > > > Steps to reproduce: > 1) Run node with configured IGFS limited by max space (f.e. 104857600). > 2) Copy to IGFS file with size less than IGFS space size. (f.e. 10-15 Mb) > 3) Copy to IGFS file with size more than free space size. > Second file have 0 size in IGFS. Used IGFS size approximately equal to the > IGFS space size. > 4) Copy to IGFS file with size less than expected IGFS free space size. (f.e. > 10-15 Mb) > New file have 0 size. > 5) Remove all files of format IGFS > IGFS free space approximately equal to the size of first file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-532) Implement IgniteAkkaStreamer to stream data from Akka actors.
[
https://issues.apache.org/jira/browse/IGNITE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466849#comment-15466849
]
Chandresh Pancholi commented on IGNITE-532:
---
Thank you Semen.
> Implement IgniteAkkaStreamer to stream data from Akka actors.
> -
>
> Key: IGNITE-532
> URL: https://issues.apache.org/jira/browse/IGNITE-532
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Semen Boikov
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Akka|http://akka.io/] for more information. Given that Akka is a Scala
> frameworks, this streamer should be available in Scala.
> We should create {{IgniteAkkaStreamer}} which will consume messages from Akka
> Actors and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert data from Akka to Ignite using an optional pluggable converter. If
> not provided, then we should have some default mechanism.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3843) Web console: Not work basic validations.
[ https://issues.apache.org/jira/browse/IGNITE-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-3843: -- Description: F.e. On cluster add empty Cache key configuration and try to save cluster. Also field with wrong value should be focused. was:F.e. On cluster add empty Cache key configuration and try to save cluster. > Web console: Not work basic validations. > > > Key: IGNITE-3843 > URL: https://issues.apache.org/jira/browse/IGNITE-3843 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Dmitriy Shabalin > Fix For: 1.8 > > > F.e. On cluster add empty Cache key configuration and try to save cluster. > Also field with wrong value should be focused. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3843) Web console: Not work basic validations.
Vasiliy Sisko created IGNITE-3843: - Summary: Web console: Not work basic validations. Key: IGNITE-3843 URL: https://issues.apache.org/jira/browse/IGNITE-3843 Project: Ignite Issue Type: Sub-task Components: wizards Reporter: Vasiliy Sisko Assignee: Dmitriy Shabalin F.e. On cluster add empty Cache key configuration and try to save cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-532) Implement IgniteAkkaStreamer to stream data from Akka actors.
[
https://issues.apache.org/jira/browse/IGNITE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466817#comment-15466817
]
Semen Boikov commented on IGNITE-532:
-
I start to review PR, will provide comments in next few days.
> Implement IgniteAkkaStreamer to stream data from Akka actors.
> -
>
> Key: IGNITE-532
> URL: https://issues.apache.org/jira/browse/IGNITE-532
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Semen Boikov
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Akka|http://akka.io/] for more information. Given that Akka is a Scala
> frameworks, this streamer should be available in Scala.
> We should create {{IgniteAkkaStreamer}} which will consume messages from Akka
> Actors and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert data from Akka to Ignite using an optional pluggable converter. If
> not provided, then we should have some default mechanism.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-532) Implement IgniteAkkaStreamer to stream data from Akka actors.
[
https://issues.apache.org/jira/browse/IGNITE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov reassigned IGNITE-532:
---
Assignee: Semen Boikov (was: Chandresh Pancholi)
> Implement IgniteAkkaStreamer to stream data from Akka actors.
> -
>
> Key: IGNITE-532
> URL: https://issues.apache.org/jira/browse/IGNITE-532
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Semen Boikov
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Akka|http://akka.io/] for more information. Given that Akka is a Scala
> frameworks, this streamer should be available in Scala.
> We should create {{IgniteAkkaStreamer}} which will consume messages from Akka
> Actors and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert data from Akka to Ignite using an optional pluggable converter. If
> not provided, then we should have some default mechanism.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3199) .NET: ASP.NET Session-State Store Provider
[ https://issues.apache.org/jira/browse/IGNITE-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-3199: -- Assignee: Vladimir Ozerov (was: Pavel Tupitsyn) > .NET: ASP.NET Session-State Store Provider > -- > > Key: IGNITE-3199 > URL: https://issues.apache.org/jira/browse/IGNITE-3199 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Affects Versions: 1.7 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Labels: .net > Fix For: 1.8 > > > See https://msdn.microsoft.com/en-us/library/ms178587.aspx > Code should be put to Apache.Ignite.AspNet assembly (see IGNITE-2379) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
