[jira] [Commented] (IGNITE-4574) Introduce user value types to H2 w/custom conversion logic
[
https://issues.apache.org/jira/browse/IGNITE-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894863#comment-15894863
]
Sergey Kalashnikov commented on IGNITE-4574:
Dmitriy, this is an internal interface that Ignite would internally implement.
It will not be exposed to Ignite users.
> Introduce user value types to H2 w/custom conversion logic
> --
>
> Key: IGNITE-4574
> URL: https://issues.apache.org/jira/browse/IGNITE-4574
> Project: Ignite
> Issue Type: Sub-task
> Components: SQL
>Reporter: Alexander Paschenko
>Assignee: Sergey Kalashnikov
> Fix For: 2.0
>
>
> We need a way to add custom data types in H2 without the need to modify it
> each time around.
> Current approach is to add new interface to H2 like the following:
> {code}
> public interface CustomDataTypesHandler {
> DataType getDataTypeByName(String name);
> DataType getDataTypeById(int type);
> int getDataTypeOrder(int type);
> Value convert(Value source, int targetType);
> }
> {code}
> The H2 will instantiate the class implementing the interface by its name
> provided by user via system properties.
> Then, whenever H2 meets the SQL command with type name missing from its
> internal type system, it will consult this new interface.
> Likewise, whenever H2 needs to convert a value to unknown data type, it will
> delegate the conversion to the CustomDataTypesHandler.
> The ignite will then implement this interface and be able to plug-in support
> for custom types like enum, etc.
> Since convert operation returns object of type Value, all the possible
> operations in custom datatypes can be overriden in a way we like.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4772) CPP: Add documentation for LoadCache feature
[
https://issues.apache.org/jira/browse/IGNITE-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894767#comment-15894767
]
Denis Magda commented on IGNITE-4772:
-
[~isapego], great work, thanks!
[~pgarg], please do the final review of the page below and close the ticket:
https://apacheignite-cpp.readme.io/docs/cache-store
> CPP: Add documentation for LoadCache feature
>
>
> Key: IGNITE-4772
> URL: https://issues.apache.org/jira/browse/IGNITE-4772
> Project: Ignite
> Issue Type: Task
> Components: documentation, platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: C++, DML, cpp, documentation
> Fix For: 1.9
>
>
> {{LoadCache}} feature has been implemented recently for C++ client
> (IGNITE-4670) and needs proper documentation on
> [readme.io|https://apacheignite-cpp.readme.io/docs]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4574) Introduce user value types to H2 w/custom conversion logic
[
https://issues.apache.org/jira/browse/IGNITE-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894704#comment-15894704
]
Dmitriy Setrakyan commented on IGNITE-4574:
---
Sergey, is this something that a user will ever have to implement or is it only
an internal interface?
> Introduce user value types to H2 w/custom conversion logic
> --
>
> Key: IGNITE-4574
> URL: https://issues.apache.org/jira/browse/IGNITE-4574
> Project: Ignite
> Issue Type: Sub-task
> Components: SQL
>Reporter: Alexander Paschenko
>Assignee: Sergey Kalashnikov
> Fix For: 2.0
>
>
> We need a way to add custom data types in H2 without the need to modify it
> each time around.
> Current approach is to add new interface to H2 like the following:
> {code}
> public interface CustomDataTypesHandler {
> DataType getDataTypeByName(String name);
> DataType getDataTypeById(int type);
> int getDataTypeOrder(int type);
> Value convert(Value source, int targetType);
> }
> {code}
> The H2 will instantiate the class implementing the interface by its name
> provided by user via system properties.
> Then, whenever H2 meets the SQL command with type name missing from its
> internal type system, it will consult this new interface.
> Likewise, whenever H2 needs to convert a value to unknown data type, it will
> delegate the conversion to the CustomDataTypesHandler.
> The ignite will then implement this interface and be able to plug-in support
> for custom types like enum, etc.
> Since convert operation returns object of type Value, all the possible
> operations in custom datatypes can be overriden in a way we like.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4787) Performance drop sql-merge-all 1.9 vs 1.8
[
https://issues.apache.org/jira/browse/IGNITE-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Suntsov updated IGNITE-4787:
-
Description:
We have performance drop on sql-merge-all benchmark in 1.9 against 1.8.
Below are numbers of 5 runs of this benchmark:
{noformat}
1.8 1.9delta
4911.89 4400.63 -11.62%
4922.16 4414.56 -11.50%
4899.16 4397.73 -11.40%
4875.75 4389.8 -11.07%
4906.68 4418.05 -11.06%
{noformat}
Logs and configs are in attachment.
was:
We have performance drop on sql-merge-all benchmark in 1.9 against 1.8.
Below are numbers of 5 runs of this benchmark:
{noformat}
1.9 1.8delta
4911.89 4400.63 -11.62%
4922.16 4414.56 -11.50%
4899.16 4397.73 -11.40%
4875.75 4389.8 -11.07%
4906.68 4418.05 -11.06%
{noformat}
Logs and configs are in attachment.
> Performance drop sql-merge-all 1.9 vs 1.8
> -
>
> Key: IGNITE-4787
> URL: https://issues.apache.org/jira/browse/IGNITE-4787
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.9
> Environment: AWS EC2 Instances (r4.2xlarge)
> Yardstick's parameters:
> 1 client/ 4 servers
> primary sync
> 64 threads
> 1 backup
>Reporter: Ilya Suntsov
>Priority: Critical
> Fix For: 2.0
>
> Attachments: configs-and-logs.zip
>
>
> We have performance drop on sql-merge-all benchmark in 1.9 against 1.8.
> Below are numbers of 5 runs of this benchmark:
> {noformat}
> 1.8 1.9delta
> 4911.89 4400.63 -11.62%
> 4922.16 4414.56 -11.50%
> 4899.16 4397.73 -11.40%
> 4875.75 4389.8 -11.07%
> 4906.68 4418.05 -11.06%
> {noformat}
> Logs and configs are in attachment.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Deleted] (IGNITE-4789) [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result.
[ https://issues.apache.org/jira/browse/IGNITE-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov deleted IGNITE-4789: - > [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result. > - > > Key: IGNITE-4789 > URL: https://issues.apache.org/jira/browse/IGNITE-4789 > Project: Ignite > Issue Type: Bug >Reporter: Andrew Mashenkov > > JVM crashed with SIGSEGV error while iterating over SQL query offheap rows. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Deleted] (IGNITE-4790) [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result.
[ https://issues.apache.org/jira/browse/IGNITE-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov deleted IGNITE-4790: - > [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result. > - > > Key: IGNITE-4790 > URL: https://issues.apache.org/jira/browse/IGNITE-4790 > Project: Ignite > Issue Type: Bug >Reporter: Andrew Mashenkov > > JVM crashed with SIGSEGV error while iterating over SQL query offheap rows. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Deleted] (IGNITE-4791) [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result.
[ https://issues.apache.org/jira/browse/IGNITE-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov deleted IGNITE-4791: - > [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result. > - > > Key: IGNITE-4791 > URL: https://issues.apache.org/jira/browse/IGNITE-4791 > Project: Ignite > Issue Type: Bug >Reporter: Andrew Mashenkov > > JVM crashed with SIGSEGV error while iterating over SQL query offheap rows. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4790) [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result.
Semen Boikov created IGNITE-4790: Summary: [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result. Key: IGNITE-4790 URL: https://issues.apache.org/jira/browse/IGNITE-4790 Project: Ignite Issue Type: Bug Reporter: Andrew Mashenkov JVM crashed with SIGSEGV error while iterating over SQL query offheap rows. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4791) [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result.
Semen Boikov created IGNITE-4791: Summary: [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result. Key: IGNITE-4791 URL: https://issues.apache.org/jira/browse/IGNITE-4791 Project: Ignite Issue Type: Bug Reporter: Andrew Mashenkov JVM crashed with SIGSEGV error while iterating over SQL query offheap rows. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4789) [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result.
Semen Boikov created IGNITE-4789: Summary: [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result. Key: IGNITE-4789 URL: https://issues.apache.org/jira/browse/IGNITE-4789 Project: Ignite Issue Type: Bug Reporter: Andrew Mashenkov JVM crashed with SIGSEGV error while iterating over SQL query offheap rows. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4624) ScanQuery shows poor performance.
[ https://issues.apache.org/jira/browse/IGNITE-4624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894472#comment-15894472 ] ASF GitHub Bot commented on IGNITE-4624: Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1509 > ScanQuery shows poor performance. > - > > Key: IGNITE-4624 > URL: https://issues.apache.org/jira/browse/IGNITE-4624 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 1.8 >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov > Fix For: 2.0 > > Attachments: > Change_keyIterator_to_entryIterator_for_local_scan_squery.patch, Demo.java > > > I've found that ScanQuery use cache KeySet iterator which make cache > peek\entry calls for getting value. > It is look like we can avoid this calls by using EntrySet iterator for > iterating over local partitions. > Start point is GridCacheQueryManager.onheapIterator(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4036) Near cache is not expired together with corresponding server cache
[ https://issues.apache.org/jira/browse/IGNITE-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894469#comment-15894469 ] ASF GitHub Bot commented on IGNITE-4036: Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1425 > Near cache is not expired together with corresponding server cache > -- > > Key: IGNITE-4036 > URL: https://issues.apache.org/jira/browse/IGNITE-4036 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.7 >Reporter: Sergej Sidorov >Assignee: Dmitry Karachentsev > Fix For: 1.9 > > > Steps to reproduce: > 1. Configure server cache with expiry time > 2. Start server node > 3. Configure client node with near cache > 4. Start client node > 5. Put elements to cache > 6. Wait for the expiry of the cache > 7. Check cache state (server/client) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4106) SQL: parallelize sql queries over cache local partitions
[ https://issues.apache.org/jira/browse/IGNITE-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894459#comment-15894459 ] ASF GitHub Bot commented on IGNITE-4106: Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1476 > SQL: parallelize sql queries over cache local partitions > > > Key: IGNITE-4106 > URL: https://issues.apache.org/jira/browse/IGNITE-4106 > Project: Ignite > Issue Type: Improvement > Components: SQL >Affects Versions: 1.7 >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov > Labels: performance > Fix For: 1.9 > > Attachments: 1node-4thread.jfr, 4node-1thread.jfr > > > If we run SQL query on cache partitioned over several cluster nodes, it will > be split into several queries running in parallel. But really we will have > one thread per query on each node. > So, for now, to improve SQL query performance we need to run more Ignite > instances or split caches manually. > It seems to be better to split local SQL queries over cache partitions, so we > would be able to parallelize SQL query on every single node and utilize CPU > more efficiently. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4788) JVM crash while accessing offheap rows of SQL query result.
[ https://issues.apache.org/jira/browse/IGNITE-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4788: - Attachment: log.txt > JVM crash while accessing offheap rows of SQL query result. > --- > > Key: IGNITE-4788 > URL: https://issues.apache.org/jira/browse/IGNITE-4788 > Project: Ignite > Issue Type: Bug > Components: SQL, swap >Affects Versions: 1.8 >Reporter: Andrew Mashenkov > Fix For: 2.0 > > Attachments: hs_err_pid18543.log.txt, log.txt > > > JVM crashed with SIGSEGV error while iterating over SQL query offheap rows. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4788) JVM crash while accessing offheap rows of SQL query result.
[ https://issues.apache.org/jira/browse/IGNITE-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4788: - Fix Version/s: 2.0 > JVM crash while accessing offheap rows of SQL query result. > --- > > Key: IGNITE-4788 > URL: https://issues.apache.org/jira/browse/IGNITE-4788 > Project: Ignite > Issue Type: Bug > Components: SQL, swap >Affects Versions: 1.8 >Reporter: Andrew Mashenkov > Fix For: 2.0 > > Attachments: hs_err_pid18543.log.txt > > > JVM crashed with SIGSEGV error while iterating over SQL query offheap rows. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4751) JVM crash while accessing Offheap entry.
[ https://issues.apache.org/jira/browse/IGNITE-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894403#comment-15894403 ] Andrew Mashenkov commented on IGNITE-4751: -- I've split ticket into two issues: 1. this - crash while iterating over cache entries 2. IGNITE-4788 crash while iterating over query results . > JVM crash while accessing Offheap entry. > > > Key: IGNITE-4751 > URL: https://issues.apache.org/jira/browse/IGNITE-4751 > Project: Ignite > Issue Type: Bug > Components: general, swap >Affects Versions: 1.7, 1.8 >Reporter: Andrew Mashenkov >Priority: Critical > Fix For: 2.0 > > Attachments: mm-rbp-server-err-pid8466.log > > > JVM crashed with SIGSEGV error while iterating over offheap entries on stable > topology. > PFA logs attached. > Partitioned OffHeap-Tiered cache with swap enabled has been configured. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4788) JVM crash while accessing offheap rows of SQL query result.
[ https://issues.apache.org/jira/browse/IGNITE-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4788: - Attachment: hs_err_pid18543.log.txt > JVM crash while accessing offheap rows of SQL query result. > --- > > Key: IGNITE-4788 > URL: https://issues.apache.org/jira/browse/IGNITE-4788 > Project: Ignite > Issue Type: Bug > Components: SQL, swap >Affects Versions: 1.8 >Reporter: Andrew Mashenkov > Attachments: hs_err_pid18543.log.txt > > > JVM crashed with SIGSEGV error while iterating over SQL query offheap rows. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4751) JVM crash while accessing Offheap entry.
[ https://issues.apache.org/jira/browse/IGNITE-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4751: - Description: JVM crashed with SIGSEGV error while iterating over offheap entries on stable topology. PFA logs attached. Partitioned OffHeap-Tiered cache with swap enabled has been configured. was: JVM crashed with SIGSEGV error while iterating over offheap entries on stable topology. Also similar issue appears while iterating over SQL query offheap rows. PFA logs attached. Partitioned OffHeap-Tiered cache with swap enabled has been configured in both cases resulted with JVM crush. > JVM crash while accessing Offheap entry. > > > Key: IGNITE-4751 > URL: https://issues.apache.org/jira/browse/IGNITE-4751 > Project: Ignite > Issue Type: Bug > Components: general, swap >Affects Versions: 1.7, 1.8 >Reporter: Andrew Mashenkov >Priority: Critical > Fix For: 2.0 > > Attachments: mm-rbp-server-err-pid8466.log > > > JVM crashed with SIGSEGV error while iterating over offheap entries on stable > topology. > PFA logs attached. > Partitioned OffHeap-Tiered cache with swap enabled has been configured. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4751) JVM crash while accessing Offheap entry.
[ https://issues.apache.org/jira/browse/IGNITE-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4751: - Attachment: (was: hs_err_pid18543.log) > JVM crash while accessing Offheap entry. > > > Key: IGNITE-4751 > URL: https://issues.apache.org/jira/browse/IGNITE-4751 > Project: Ignite > Issue Type: Bug > Components: general, swap >Affects Versions: 1.7, 1.8 >Reporter: Andrew Mashenkov >Priority: Critical > Fix For: 2.0 > > Attachments: mm-rbp-server-err-pid8466.log > > > JVM crashed with SIGSEGV error while iterating over offheap entries on stable > topology. > PFA logs attached. > Partitioned OffHeap-Tiered cache with swap enabled has been configured. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4788) JVM crash while accessing offheap rows of SQL query result.
Andrew Mashenkov created IGNITE-4788: Summary: JVM crash while accessing offheap rows of SQL query result. Key: IGNITE-4788 URL: https://issues.apache.org/jira/browse/IGNITE-4788 Project: Ignite Issue Type: Bug Components: SQL, swap Affects Versions: 1.8 Reporter: Andrew Mashenkov JVM crashed with SIGSEGV error while iterating over SQL query offheap rows. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-3939) Compact long zero values binary representation
[ https://issues.apache.org/jira/browse/IGNITE-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892302#comment-15892302 ] Taras Ledkov edited comment on IGNITE-3939 at 3/3/17 1:28 PM: -- [Tests results|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1587%2Fhead] The reasons of failed tests look like not related to the binary changes. was (Author: tledkov-gridgain): [Tests results|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1587%2Fhead] > Compact long zero values binary representation > -- > > Key: IGNITE-3939 > URL: https://issues.apache.org/jira/browse/IGNITE-3939 > Project: Ignite > Issue Type: Improvement > Components: binary >Affects Versions: 1.7 >Reporter: Andrew Mashenkov >Assignee: Taras Ledkov > Fix For: 2.0 > > > We can use separate type for Long zero values and exclude 8-byte value from > binary representation. This will reduce memory footprint and network load. > Compatibility with previous versions MUST be preserved. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-4577) Ensure that certain interface addresses can be excluded form node attributes
[
https://issues.apache.org/jira/browse/IGNITE-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892280#comment-15892280
]
Evgenii Zhuravlev edited comment on IGNITE-4577 at 3/3/17 1:16 PM:
---
Implemented a new idea with using isReachable for sorting addresses. Review
link: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-110
tc link:
http://ci.ignite.apache.org/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1585%2Fmerge
was (Author: ezhuravl):
Implemented a new idea with using isReachable for sorting addresses. Review
link: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-110
> Ensure that certain interface addresses can be excluded form node attributes
>
>
> Key: IGNITE-4577
> URL: https://issues.apache.org/jira/browse/IGNITE-4577
> Project: Ignite
> Issue Type: Task
> Components: general
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Evgenii Zhuravlev
> Fix For: 2.0
>
>
> *Problem*
> Consider a case when node has some network interface which is not accessible
> from the outside (e.g. in Docker container). Ignite adds this address to
> attributes, which are shared with other nodes. Now if remote want to
> communicate with local node chances that he will try to establish connection
> with invalid address.
> In the worst case connection will be impossible. We use {{AddressResolver}}
> to handle this situation.
> However, it appears that {{AddressResolver}} cannot prevent certain address
> to appear in address list. As a result users may experience communication
> delays as we establish peer-to-peer connection in one thread, iterating over
> all available addresses.
> *Proposed solution*
> We need to examine what happens when address resolver is set. May be it is
> necessary to rethink how we handle returned object. E.g. {{null}} or empty
> collection might mean that this address should not be included into the list
> of address. However, it may break existing applications, so chances that
> other solution is needed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-4761) ServiceProcessor hangs while stopping on unstable topology.
[ https://issues.apache.org/jira/browse/IGNITE-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov reassigned IGNITE-4761: Assignee: Andrew Mashenkov > ServiceProcessor hangs while stopping on unstable topology. > --- > > Key: IGNITE-4761 > URL: https://issues.apache.org/jira/browse/IGNITE-4761 > Project: Ignite > Issue Type: Bug > Components: cache, managed services >Affects Versions: 1.7 >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Critical > Fix For: 2.0 > > > GridServiceProcessor.onKernalStop can be blocked on taking busyLock when > the lock is being held by TopologyListener while infinite waiting for > readyAffinityFuture. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-3194) BinaryObjectException when web session attribute schema is changed
[
https://issues.apache.org/jira/browse/IGNITE-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894296#comment-15894296
]
Alper Tekinalp commented on IGNITE-3194:
Hi.
I would like to fix that bug but I could not find a suitable solution. Can
someone guide me about it?
Regards.
> BinaryObjectException when web session attribute schema is changed
> --
>
> Key: IGNITE-3194
> URL: https://issues.apache.org/jira/browse/IGNITE-3194
> Project: Ignite
> Issue Type: Bug
> Components: websession
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
> Fix For: 2.0
>
>
> The issue is described here:
> http://stackoverflow.com/questions/37410879/binaryobjectexception-cannot-find-schema-for-object-with-compact-footer
> Need to try reproducing it fix if needed.
> {noformat}
> class org.apache.ignite.binary.BinaryObjectException: Cannot find schema for
> object with compact footer [typeId=-2056860774, schemaId=1954049593]
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:1721)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:278)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:177)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:156)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:109)
> at
> org.apache.ignite.cache.websession.WebSessionV2.unmarshal(WebSessionV2.java:336)
> at
> org.apache.ignite.cache.websession.WebSessionV2.getAttribute(WebSessionV2.java:200)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-4772) CPP: Add documentation for LoadCache feature
[
https://issues.apache.org/jira/browse/IGNITE-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894291#comment-15894291
]
Igor Sapego edited comment on IGNITE-4772 at 3/3/17 12:53 PM:
--
Done.
[~dmagda] please, review: https://apacheignite-cpp.readme.io/docs/cache-store
was (Author: isapego):
Done.
[~dmagda] please, review.
> CPP: Add documentation for LoadCache feature
>
>
> Key: IGNITE-4772
> URL: https://issues.apache.org/jira/browse/IGNITE-4772
> Project: Ignite
> Issue Type: Task
> Components: documentation, platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: C++, DML, cpp, documentation
> Fix For: 1.9
>
>
> {{LoadCache}} feature has been implemented recently for C++ client
> (IGNITE-4670) and needs proper documentation on
> [readme.io|https://apacheignite-cpp.readme.io/docs]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-4112) Client is stopped if communication to servers is lost during (re)connect routine.
[
https://issues.apache.org/jira/browse/IGNITE-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Tikhonov resolved IGNITE-4112.
--
Resolution: Duplicate
> Client is stopped if communication to servers is lost during (re)connect
> routine.
> -
>
> Key: IGNITE-4112
> URL: https://issues.apache.org/jira/browse/IGNITE-4112
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Nikolay Tikhonov
> Fix For: 2.0
>
>
> Consider the following situation for the client which is currently
> disconnected:
> 1) Link to servers is restored;
> 2) Clients connects successfully;
> 3) Link is broken again after some time.
> Result: client is disconnected.
> But!
> 1) Link to servers is restored;
> 2) Clients is re-connecting;
> 3) Link is broken again before reconnect is finished.
> Result: client might be stopped (for new client it will exit from
> {{Ignition.start}} routine with exception).
> Apparently, we need to make (re)connect routine "atomic" with respect to
> concurrent network events. That is, we either reconnect all components
> successfully, or client is forcefully moved to disconnected state again.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4787) Performance drop sql-merge-all 1.9 vs 1.8
[
https://issues.apache.org/jira/browse/IGNITE-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Suntsov updated IGNITE-4787:
-
Environment:
AWS EC2 Instances (r4.2xlarge)
Yardstick's parameters:
1 client/ 4 servers
primary sync
64 threads
1 backup
was:
AWS EC2 Instances (r4.2xlarge)
1 client/ 4 servers
primary sync
64 threads
1 backup
> Performance drop sql-merge-all 1.9 vs 1.8
> -
>
> Key: IGNITE-4787
> URL: https://issues.apache.org/jira/browse/IGNITE-4787
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.9
> Environment: AWS EC2 Instances (r4.2xlarge)
> Yardstick's parameters:
> 1 client/ 4 servers
> primary sync
> 64 threads
> 1 backup
>Reporter: Ilya Suntsov
>Priority: Critical
> Fix For: 2.0
>
> Attachments: configs-and-logs.zip
>
>
> We have performance drop on sql-merge-all benchmark in 1.9 against 1.8.
> Below are numbers of 5 runs of this benchmark:
> {noformat}
> 1.9 1.8delta
> 4911.89 4400.63 -11.62%
> 4922.16 4414.56 -11.50%
> 4899.16 4397.73 -11.40%
> 4875.75 4389.8 -11.07%
> 4906.68 4418.05 -11.06%
> {noformat}
> Logs and configs are in attachment.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (IGNITE-4112) Client is stopped if communication to servers is lost during (re)connect routine.
[
https://issues.apache.org/jira/browse/IGNITE-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Tikhonov closed IGNITE-4112.
> Client is stopped if communication to servers is lost during (re)connect
> routine.
> -
>
> Key: IGNITE-4112
> URL: https://issues.apache.org/jira/browse/IGNITE-4112
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Nikolay Tikhonov
> Fix For: 2.0
>
>
> Consider the following situation for the client which is currently
> disconnected:
> 1) Link to servers is restored;
> 2) Clients connects successfully;
> 3) Link is broken again after some time.
> Result: client is disconnected.
> But!
> 1) Link to servers is restored;
> 2) Clients is re-connecting;
> 3) Link is broken again before reconnect is finished.
> Result: client might be stopped (for new client it will exit from
> {{Ignition.start}} routine with exception).
> Apparently, we need to make (re)connect routine "atomic" with respect to
> concurrent network events. That is, we either reconnect all components
> successfully, or client is forcefully moved to disconnected state again.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4787) Performance drop sql-merge-all 1.9 vs 1.8
[
https://issues.apache.org/jira/browse/IGNITE-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Suntsov updated IGNITE-4787:
-
Description:
We have performance drop on sql-merge-all benchmark in 1.9 against 1.8.
Below are numbers of 5 runs of this benchmark:
{noformat}
1.9 1.8delta
4911.89 4400.63 -11.62%
4922.16 4414.56 -11.50%
4899.16 4397.73 -11.40%
4875.75 4389.8 -11.07%
4906.68 4418.05 -11.06%
{noformat}
Logs and configs are in attachment.
was:
We have performance drop on sql-merge-all benchmark in 1.9 against 1.8.
Below are numbers of 5 runs of this benchmark:
1.9..1.8..delta
4911.89...4400.63...-11.62%
4922.16...4414.56...-11.50%
4899.16...4397.73...-11.40%
4875.75...4389.8.-11.07%
4906.68...4418.05...-11.06%
Logs and configs are in attachment.
> Performance drop sql-merge-all 1.9 vs 1.8
> -
>
> Key: IGNITE-4787
> URL: https://issues.apache.org/jira/browse/IGNITE-4787
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.9
> Environment: AWS EC2 Instances (r4.2xlarge)
> 1 client/ 4 servers
> primary sync
> 64 threads
> 1 backup
>Reporter: Ilya Suntsov
>Priority: Critical
> Fix For: 2.0
>
> Attachments: configs-and-logs.zip
>
>
> We have performance drop on sql-merge-all benchmark in 1.9 against 1.8.
> Below are numbers of 5 runs of this benchmark:
> {noformat}
> 1.9 1.8delta
> 4911.89 4400.63 -11.62%
> 4922.16 4414.56 -11.50%
> 4899.16 4397.73 -11.40%
> 4875.75 4389.8 -11.07%
> 4906.68 4418.05 -11.06%
> {noformat}
> Logs and configs are in attachment.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4787) Performance drop sql-merge-all 1.9 vs 1.8
[ https://issues.apache.org/jira/browse/IGNITE-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Suntsov updated IGNITE-4787: - Attachment: configs-and-logs.zip > Performance drop sql-merge-all 1.9 vs 1.8 > - > > Key: IGNITE-4787 > URL: https://issues.apache.org/jira/browse/IGNITE-4787 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.9 > Environment: AWS EC2 Instances (r4.2xlarge) > 1 client/ 4 servers > primary sync > 64 threads > 1 backup >Reporter: Ilya Suntsov >Priority: Critical > Fix For: 2.0 > > Attachments: configs-and-logs.zip > > > We have performance drop on sql-merge-all benchmark in 1.9 against 1.8. > Below are numbers of 5 runs of this benchmark: > 1.9..1.8..delta > 4911.89...4400.63...-11.62% > 4922.16...4414.56...-11.50% > 4899.16...4397.73...-11.40% > 4875.75...4389.8.-11.07% > 4906.68...4418.05...-11.06% > Logs and configs are in attachment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4787) Performance drop sql-merge-all 1.9 vs 1.8
Ilya Suntsov created IGNITE-4787: Summary: Performance drop sql-merge-all 1.9 vs 1.8 Key: IGNITE-4787 URL: https://issues.apache.org/jira/browse/IGNITE-4787 Project: Ignite Issue Type: Bug Components: general Affects Versions: 1.9 Environment: AWS EC2 Instances (r4.2xlarge) 1 client/ 4 servers primary sync 64 threads 1 backup Reporter: Ilya Suntsov Priority: Critical Fix For: 2.0 We have performance drop on sql-merge-all benchmark in 1.9 against 1.8. Below are numbers of 5 runs of this benchmark: 1.9..1.8..delta 4911.89...4400.63...-11.62% 4922.16...4414.56...-11.50% 4899.16...4397.73...-11.40% 4875.75...4389.8.-11.07% 4906.68...4418.05...-11.06% Logs and configs are in attachment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4786) Try get rid of exchange futures and affinity history
Semen Boikov created IGNITE-4786: Summary: Try get rid of exchange futures and affinity history Key: IGNITE-4786 URL: https://issues.apache.org/jira/browse/IGNITE-4786 Project: Ignite Issue Type: Bug Components: cache Reporter: Semen Boikov Assignee: Igor Seliverstov Priority: Critical Currently ignite stores calculated affinity history (GridAffinityAssignmentCache) and finished exchange futures (GridCachePartitionExchangeManager). If requested history data is not available this causes runtime exception and unpredictable consequences. Ideally we need get rid of history and if some operation requires old affinity data then operation should retry on current topology version, or operation handling should be changed so that affinity data is not needed to finish operation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4786) Try get rid of exchange futures history and affinity history
[ https://issues.apache.org/jira/browse/IGNITE-4786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-4786: - Summary: Try get rid of exchange futures history and affinity history (was: Try get rid of exchange futures and affinity history) > Try get rid of exchange futures history and affinity history > > > Key: IGNITE-4786 > URL: https://issues.apache.org/jira/browse/IGNITE-4786 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Semen Boikov >Assignee: Igor Seliverstov >Priority: Critical > > Currently ignite stores calculated affinity history > (GridAffinityAssignmentCache) and finished exchange futures > (GridCachePartitionExchangeManager). If requested history data is not > available this causes runtime exception and unpredictable consequences. > Ideally we need get rid of history and if some operation requires old > affinity data then operation should retry on current topology version, or > operation handling should be changed so that affinity data is not needed to > finish operation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4785) Web Console: Implement floating menu with base buttons
Vica Abramova created IGNITE-4785: - Summary: Web Console: Implement floating menu with base buttons Key: IGNITE-4785 URL: https://issues.apache.org/jira/browse/IGNITE-4785 Project: Ignite Issue Type: Task Components: UI, wizards Reporter: Vica Abramova Assignee: Vica Abramova TBD -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Deleted] (IGNITE-4778) [IGNITE-4777] Web Console: Add notification on 'Download project' button
[ https://issues.apache.org/jira/browse/IGNITE-4778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov deleted IGNITE-4778: - > [IGNITE-4777] Web Console: Add notification on 'Download project' button > > > Key: IGNITE-4778 > URL: https://issues.apache.org/jira/browse/IGNITE-4778 > Project: Ignite > Issue Type: Task >Reporter: Vica Abramova > > After the configuration user need to download project and run it to get the > result. Let's notify about this! > Also in this task we need to revise tips. And improve instructions for new > users. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4784) Web Console: Revise demo mode
Vica Abramova created IGNITE-4784: - Summary: Web Console: Revise demo mode Key: IGNITE-4784 URL: https://issues.apache.org/jira/browse/IGNITE-4784 Project: Ignite Issue Type: Task Components: UI, wizards Reporter: Vica Abramova Assignee: Vica Abramova -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4783) Web Console: Revise 'become a user' mechanics
[ https://issues.apache.org/jira/browse/IGNITE-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vica Abramova reassigned IGNITE-4783: - Assignee: Vica Abramova > Web Console: Revise 'become a user' mechanics > - > > Key: IGNITE-4783 > URL: https://issues.apache.org/jira/browse/IGNITE-4783 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Vica Abramova > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4783) Web Console: Revise 'become a user' mechanics
Vica Abramova created IGNITE-4783: - Summary: Web Console: Revise 'become a user' mechanics Key: IGNITE-4783 URL: https://issues.apache.org/jira/browse/IGNITE-4783 Project: Ignite Issue Type: Task Components: UI, wizards Reporter: Vica Abramova -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4782) Web Console: Revise on-boarding behavior and user's education
[ https://issues.apache.org/jira/browse/IGNITE-4782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vica Abramova reassigned IGNITE-4782: - Assignee: Vica Abramova > Web Console: Revise on-boarding behavior and user's education > - > > Key: IGNITE-4782 > URL: https://issues.apache.org/jira/browse/IGNITE-4782 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Vica Abramova > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4782) Web Console: Revise on-boarding behavior and user's education
Vica Abramova created IGNITE-4782: - Summary: Web Console: Revise on-boarding behavior and user's education Key: IGNITE-4782 URL: https://issues.apache.org/jira/browse/IGNITE-4782 Project: Ignite Issue Type: Task Components: UI, wizards Reporter: Vica Abramova -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-4635) Implement single-threaded DDL worker
[ https://issues.apache.org/jira/browse/IGNITE-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-4635. - Resolution: Fixed > Implement single-threaded DDL worker > > > Key: IGNITE-4635 > URL: https://issues.apache.org/jira/browse/IGNITE-4635 > Project: Ignite > Issue Type: Sub-task > Components: SQL >Reporter: Vladimir Ozerov >Assignee: Alexander Paschenko > Fix For: 2.0 > > > All DDL statement must be performed from within separate worker thread. This > worker thread should listen for discovery events (JOIN, LEAVE, FAIL, CUSTOM) > and act accordingly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4781) Web Console: Revise the Queries Screen
Vica Abramova created IGNITE-4781: - Summary: Web Console: Revise the Queries Screen Key: IGNITE-4781 URL: https://issues.apache.org/jira/browse/IGNITE-4781 Project: Ignite Issue Type: Task Components: UI, wizards Reporter: Vica Abramova Assignee: Vica Abramova -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4780) Web Console: Improve the adaptability of the web console
Vica Abramova created IGNITE-4780: - Summary: Web Console: Improve the adaptability of the web console Key: IGNITE-4780 URL: https://issues.apache.org/jira/browse/IGNITE-4780 Project: Ignite Issue Type: Task Components: UI, wizards Reporter: Vica Abramova Assignee: Vica Abramova TBD layouts for different screen resolutions -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4779) Missed discovery data snapshot during exchange processing
Semen Boikov created IGNITE-4779: Summary: Missed discovery data snapshot during exchange processing Key: IGNITE-4779 URL: https://issues.apache.org/jira/browse/IGNITE-4779 Project: Ignite Issue Type: Bug Components: cache Reporter: Semen Boikov Assignee: Igor Seliverstov Priority: Critical Fix For: 2.0 Currently GridDiscoveryManager stores only 500 last discovery data snapshots, if in 'resolveDiscoCache' requested version is not available it just throws IgniteException. It is possible while exchange is processed on topology version N, lot of discovery events is generated (e.g. in case of client caches start) and version N is removed from history. For exchange solution is simple: when exchange is triggered need save discovery snapshot in exchange future. Also need review others places where discovery history is used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4778) [IGNITE-4777] Web Console: Add notification on 'Download project' button
Semen Boikov created IGNITE-4778: Summary: [IGNITE-4777] Web Console: Add notification on 'Download project' button Key: IGNITE-4778 URL: https://issues.apache.org/jira/browse/IGNITE-4778 Project: Ignite Issue Type: Task Reporter: Vica Abramova After the configuration user need to download project and run it to get the result. Let's notify about this! Also in this task we need to revise tips. And improve instructions for new users. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4777) Web Console: Add notification on 'Download project' button
Vica Abramova created IGNITE-4777: - Summary: Web Console: Add notification on 'Download project' button Key: IGNITE-4777 URL: https://issues.apache.org/jira/browse/IGNITE-4777 Project: Ignite Issue Type: Task Components: UI, wizards Reporter: Vica Abramova After the configuration user need to download project and run it to get the result. Let's notify about this! Also in this task we need to revise tips. And improve instructions for new users. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-4633) Initiate DDL operation through custom discovery message
[
https://issues.apache.org/jira/browse/IGNITE-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-4633.
-
Resolution: Fixed
> Initiate DDL operation through custom discovery message
> ---
>
> Key: IGNITE-4633
> URL: https://issues.apache.org/jira/browse/IGNITE-4633
> Project: Ignite
> Issue Type: Sub-task
> Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>
> Design considerations:
> 1) Create generic DDL custom discovery message pair - {{INIT}} and {{ACK}}
> messages - which will hold concrete DDL commands.
> 2) Originator must generate unique message ID to be able to track it later.
> 3) Coordinator calculates all participants through affinity API and adds them
> to message.
> 4) {{INIT}} message goes through the ring and:performs some fast preliminary
> checks if necessary and collects error; in particular it may verify whether
> schema change is valid to allow for fail-fast client notification.;
> 5) If at least one error occurs during {{INIT}} stage, originator may throw
> exception to the user.
> 6) {{ACK}} message schedules asynchronous execution of the command.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4776) DDL: handle client disconnect
[ https://issues.apache.org/jira/browse/IGNITE-4776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4776: Summary: DDL: handle client disconnect (was: DDL: handle client disconnec) > DDL: handle client disconnect > - > > Key: IGNITE-4776 > URL: https://issues.apache.org/jira/browse/IGNITE-4776 > Project: Ignite > Issue Type: Sub-task > Components: SQL >Reporter: Vladimir Ozerov > Fix For: 2.0 > > > We must handle client disconnects properly. What should happen to the future > in case client disconnects? Should it be completed? Or may be it is better to > poll operation status after re-connect? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4776) DDL: handle client disconnec
Vladimir Ozerov created IGNITE-4776: --- Summary: DDL: handle client disconnec Key: IGNITE-4776 URL: https://issues.apache.org/jira/browse/IGNITE-4776 Project: Ignite Issue Type: Sub-task Components: SQL Reporter: Vladimir Ozerov Fix For: 2.0 We must handle client disconnects properly. What should happen to the future in case client disconnects? Should it be completed? Or may be it is better to poll operation status after re-connect? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4775) Web Console: Implement role-based access control
[ https://issues.apache.org/jira/browse/IGNITE-4775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vica Abramova updated IGNITE-4775: -- Component/s: UI > Web Console: Implement role-based access control > > > Key: IGNITE-4775 > URL: https://issues.apache.org/jira/browse/IGNITE-4775 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4775) Web Console: Implement role-based access control
Vica Abramova created IGNITE-4775: - Summary: Web Console: Implement role-based access control Key: IGNITE-4775 URL: https://issues.apache.org/jira/browse/IGNITE-4775 Project: Ignite Issue Type: Task Components: wizards Reporter: Vica Abramova -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4774) Web Console: Improve design of tables
Vica Abramova created IGNITE-4774: - Summary: Web Console: Improve design of tables Key: IGNITE-4774 URL: https://issues.apache.org/jira/browse/IGNITE-4774 Project: Ignite Issue Type: Task Components: UI, wizards Reporter: Vica Abramova Assignee: Vica Abramova Tables should be adaptive. The height of the lines should be bigger. Buttons need to be more obvious. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4773) Web Console: Create New Design Concept
[ https://issues.apache.org/jira/browse/IGNITE-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vica Abramova reassigned IGNITE-4773: - Assignee: Vica Abramova > Web Console: Create New Design Concept > -- > > Key: IGNITE-4773 > URL: https://issues.apache.org/jira/browse/IGNITE-4773 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Vica Abramova > > Don't forget to support multi-clustering. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4773) Web Console: Create New Design Concept
Vica Abramova created IGNITE-4773: - Summary: Web Console: Create New Design Concept Key: IGNITE-4773 URL: https://issues.apache.org/jira/browse/IGNITE-4773 Project: Ignite Issue Type: Improvement Components: UI, wizards Reporter: Vica Abramova Don't forget to support multi-clustering. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4681) Apply new future adapter
[ https://issues.apache.org/jira/browse/IGNITE-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894019#comment-15894019 ] Igor Seliverstov commented on IGNITE-4681: -- Some fixes after tests run are included > Apply new future adapter > > > Key: IGNITE-4681 > URL: https://issues.apache.org/jira/browse/IGNITE-4681 > Project: Ignite > Issue Type: Improvement >Reporter: Yakov Zhdanov >Assignee: Igor Seliverstov > Fix For: 2.0 > > Attachments: GridFutAdapter over jdk8.java > > > Attached is reference future adapter implementation. It is proven to consume > less memory and it does not require explicit locking on listen(). We need to > apply it. > Known threats: > # if future is completed normally, but with Throwable as result, get() throws > exception. This can be fixed with internal wrapper class > # listener notification order changes - this is known to cause problems > org.apache.ignite.internal.processors.rest.ClientMemcachedProtocolSelfTest#testGetBulk > which is minor but still. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4633) Initiate DDL operation through custom discovery message
[
https://issues.apache.org/jira/browse/IGNITE-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894012#comment-15894012
]
Vladimir Ozerov commented on IGNITE-4633:
-
Looks like my comment about getting participating nodes on clients is wrong.
Instead, we should determine the list of participating nodes as message goes
through the ring, not on coordinator. Otherwise it will be hard to share info
of current schema with concurrently joining nodes.
> Initiate DDL operation through custom discovery message
> ---
>
> Key: IGNITE-4633
> URL: https://issues.apache.org/jira/browse/IGNITE-4633
> Project: Ignite
> Issue Type: Sub-task
> Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>
> Design considerations:
> 1) Create generic DDL custom discovery message pair - {{INIT}} and {{ACK}}
> messages - which will hold concrete DDL commands.
> 2) Originator must generate unique message ID to be able to track it later.
> 3) Coordinator calculates all participants through affinity API and adds them
> to message.
> 4) {{INIT}} message goes through the ring and:performs some fast preliminary
> checks if necessary and collects error; in particular it may verify whether
> schema change is valid to allow for fail-fast client notification.;
> 5) If at least one error occurs during {{INIT}} stage, originator may throw
> exception to the user.
> 6) {{ACK}} message schedules asynchronous execution of the command.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4574) Introduce user value types to H2 w/custom conversion logic
[
https://issues.apache.org/jira/browse/IGNITE-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893981#comment-15893981
]
Sergey Kalashnikov commented on IGNITE-4574:
Dmitriy, I have added the description. Please let me know if it is still not ok.
> Introduce user value types to H2 w/custom conversion logic
> --
>
> Key: IGNITE-4574
> URL: https://issues.apache.org/jira/browse/IGNITE-4574
> Project: Ignite
> Issue Type: Sub-task
> Components: SQL
>Reporter: Alexander Paschenko
>Assignee: Sergey Kalashnikov
> Fix For: 2.0
>
>
> We need a way to add custom data types in H2 without the need to modify it
> each time around.
> Current approach is to add new interface to H2 like the following:
> {code}
> public interface CustomDataTypesHandler {
> DataType getDataTypeByName(String name);
> DataType getDataTypeById(int type);
> int getDataTypeOrder(int type);
> Value convert(Value source, int targetType);
> }
> {code}
> The H2 will instantiate the class implementing the interface by its name
> provided by user via system properties.
> Then, whenever H2 meets the SQL command with type name missing from its
> internal type system, it will consult this new interface.
> Likewise, whenever H2 needs to convert a value to unknown data type, it will
> delegate the conversion to the CustomDataTypesHandler.
> The ignite will then implement this interface and be able to plug-in support
> for custom types like enum, etc.
> Since convert operation returns object of type Value, all the possible
> operations in custom datatypes can be overriden in a way we like.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4633) Initiate DDL operation through custom discovery message
[
https://issues.apache.org/jira/browse/IGNITE-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893977#comment-15893977
]
Vladimir Ozerov commented on IGNITE-4633:
-
[~al.psc], I did some refactoring and simplification. Please see my changes.
Currently my only comment is how we determine set of participating nodes. It
should happen on client, not on coordinator, because in future client will
track alive nodes and complete operation with error if all participants have
left the grid. So we should make set of participating nodes final field and
initialize it on the client. Current {{nodeState}} field must be renamed to
{{nodeErrs}}.
By the way, do we really need to collect errors from all nodes? Will it be
enough to collect only the very first error and simply ignore init message on
further nodes?
> Initiate DDL operation through custom discovery message
> ---
>
> Key: IGNITE-4633
> URL: https://issues.apache.org/jira/browse/IGNITE-4633
> Project: Ignite
> Issue Type: Sub-task
> Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>
> Design considerations:
> 1) Create generic DDL custom discovery message pair - {{INIT}} and {{ACK}}
> messages - which will hold concrete DDL commands.
> 2) Originator must generate unique message ID to be able to track it later.
> 3) Coordinator calculates all participants through affinity API and adds them
> to message.
> 4) {{INIT}} message goes through the ring and:performs some fast preliminary
> checks if necessary and collects error; in particular it may verify whether
> schema change is valid to allow for fail-fast client notification.;
> 5) If at least one error occurs during {{INIT}} stage, originator may throw
> exception to the user.
> 6) {{ACK}} message schedules asynchronous execution of the command.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4574) Introduce user value types to H2 w/custom conversion logic
[
https://issues.apache.org/jira/browse/IGNITE-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kalashnikov updated IGNITE-4574:
---
Description:
We need a way to add custom data types in H2 without the need to modify it each
time around.
Current approach is to add new interface to H2 like the following:
{code}
public interface CustomDataTypesHandler {
DataType getDataTypeByName(String name);
DataType getDataTypeById(int type);
int getDataTypeOrder(int type);
Value convert(Value source, int targetType);
}
{code}
The H2 will instantiate the class implementing the interface by its name
provided by user via system properties.
Then, whenever H2 meets the SQL command with type name missing from its
internal type system, it will consult this new interface.
Likewise, whenever H2 needs to convert a value to unknown data type, it will
delegate the conversion to the CustomDataTypesHandler.
The ignite will then implement this interface and be able to plug-in support
for custom types like enum, etc.
Since convert operation returns object of type Value, all the possible
operations in custom datatypes can be overriden in a way we like.
was:
We need a way to add custom data types in H2 without the need to modify it each
time around.
Current approach is to add new interface to H2 like the following:
{code}
public interface CustomDataTypesHandler {
DataType getDataTypeByName(String name);
DataType getDataTypeById(int type);
int getDataTypeOrder(int type);
Value convert(Value source, int targetType);
}
{code}
The H2 will instantiate the class implementing the interface by its name
provided by user via system properties.
Then, whenever H2 meets the SQL command with type name missing from its
internal type system, it will consult this new interface.
Likewise, whenever H2 needs to convert a value to unknown data type, it will
delegate the conversion to the CustomDataTypesHandler.
The ignite will then implement this interface and necessary and be able to
plug-in support for custom types like enum, etc.
Since convert operation returns object of type Value, all the possible
operations in custom datatypes can be overriden in a way we like.
> Introduce user value types to H2 w/custom conversion logic
> --
>
> Key: IGNITE-4574
> URL: https://issues.apache.org/jira/browse/IGNITE-4574
> Project: Ignite
> Issue Type: Sub-task
> Components: SQL
>Reporter: Alexander Paschenko
>Assignee: Sergey Kalashnikov
> Fix For: 2.0
>
>
> We need a way to add custom data types in H2 without the need to modify it
> each time around.
> Current approach is to add new interface to H2 like the following:
> {code}
> public interface CustomDataTypesHandler {
> DataType getDataTypeByName(String name);
> DataType getDataTypeById(int type);
> int getDataTypeOrder(int type);
> Value convert(Value source, int targetType);
> }
> {code}
> The H2 will instantiate the class implementing the interface by its name
> provided by user via system properties.
> Then, whenever H2 meets the SQL command with type name missing from its
> internal type system, it will consult this new interface.
> Likewise, whenever H2 needs to convert a value to unknown data type, it will
> delegate the conversion to the CustomDataTypesHandler.
> The ignite will then implement this interface and be able to plug-in support
> for custom types like enum, etc.
> Since convert operation returns object of type Value, all the possible
> operations in custom datatypes can be overriden in a way we like.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4574) Introduce user value types to H2 w/custom conversion logic
[
https://issues.apache.org/jira/browse/IGNITE-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kalashnikov updated IGNITE-4574:
---
Description:
We need a way to add custom data types in H2 without the need to modify it each
time around.
Current approach is to add new interface to H2 like the following:
{code}
public interface CustomDataTypesHandler {
DataType getDataTypeByName(String name);
DataType getDataTypeById(int type);
int getDataTypeOrder(int type);
Value convert(Value source, int targetType);
}
{code}
The H2 will instantiate the class implementing the interface by its name
provided by user via system properties.
Then, whenever H2 meets the SQL command with type name missing from its
internal type system, it will consult this new interface.
Likewise, whenever H2 needs to convert a value to unknown data type, it will
delegate the conversion to the CustomDataTypesHandler.
The ignite will then implement this interface and necessary and be able to
plug-in support for custom types like enum, etc.
Since convert operation returns object of type Value, all the possible
operations in custom datatypes can be overriden in a way we like.
> Introduce user value types to H2 w/custom conversion logic
> --
>
> Key: IGNITE-4574
> URL: https://issues.apache.org/jira/browse/IGNITE-4574
> Project: Ignite
> Issue Type: Sub-task
> Components: SQL
>Reporter: Alexander Paschenko
>Assignee: Sergey Kalashnikov
> Fix For: 2.0
>
>
> We need a way to add custom data types in H2 without the need to modify it
> each time around.
> Current approach is to add new interface to H2 like the following:
> {code}
> public interface CustomDataTypesHandler {
> DataType getDataTypeByName(String name);
> DataType getDataTypeById(int type);
> int getDataTypeOrder(int type);
> Value convert(Value source, int targetType);
> }
> {code}
> The H2 will instantiate the class implementing the interface by its name
> provided by user via system properties.
> Then, whenever H2 meets the SQL command with type name missing from its
> internal type system, it will consult this new interface.
> Likewise, whenever H2 needs to convert a value to unknown data type, it will
> delegate the conversion to the CustomDataTypesHandler.
> The ignite will then implement this interface and necessary and be able to
> plug-in support for custom types like enum, etc.
> Since convert operation returns object of type Value, all the possible
> operations in custom datatypes can be overriden in a way we like.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4772) CPP: Add documentation for LoadCache feature
[
https://issues.apache.org/jira/browse/IGNITE-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893967#comment-15893967
]
Igor Sapego commented on IGNITE-4772:
-
[~dmagda], for now you can't configure write-through or read-through with C++
configuration. You only can do that using XML config. I'll add a code snippet
though.
> CPP: Add documentation for LoadCache feature
>
>
> Key: IGNITE-4772
> URL: https://issues.apache.org/jira/browse/IGNITE-4772
> Project: Ignite
> Issue Type: Task
> Components: documentation, platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: C++, DML, cpp, documentation
> Fix For: 1.9
>
>
> {{LoadCache}} feature has been implemented recently for C++ client
> (IGNITE-4670) and needs proper documentation on
> [readme.io|https://apacheignite-cpp.readme.io/docs]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-1094) Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization
[
https://issues.apache.org/jira/browse/IGNITE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893906#comment-15893906
]
Yakov Zhdanov commented on IGNITE-1094:
---
Alexey, implementation is incorrect. I have to cancel this patch.
This should be fixed in the following way (at least it seems so to me)
1. all nodes try to init cache locally
2. if error occurs on any node then exchange coordinator should be notified.
3. coordinator should send
{{org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsFullMessage}}
message containing error flag to all cache nodes
4. all cache nodes should revert the changes
5. exception should be thrown on initiator node (who called create cache)
Please make sure to add multi-node tests with conditional exception throwing
from factories (only on 1 node from several nodes topology).
Thanks!
> Ignite.createCache(CacheConfiguration) hangs if some exception occurs during
> cache initialization
> -
>
> Key: IGNITE-1094
> URL: https://issues.apache.org/jira/browse/IGNITE-1094
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Sergey Evdokimov
>Assignee: Alexey Kuznetsov
> Labels: Muted_test
> Fix For: 2.0
>
>
> User can pass broken configuration, for example, store factory that throws
> exception from create() method. I created test to demonstrate the problem.
> See IgniteDynamicCacheStartSelfTest#testBrokenStoreFactory in 'ignite-1094'
> branch
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
