[jira] [Closed] (IGNITE-7119) Web Agent: Implement support for comma-delimited list of node URIs
[
https://issues.apache.org/jira/browse/IGNITE-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov closed IGNITE-7119.
--
> Web Agent: Implement support for comma-delimited list of node URIs
> --
>
> Key: IGNITE-7119
> URL: https://issues.apache.org/jira/browse/IGNITE-7119
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.5
>
>
> We need to support several URLs for load-balancing and fault tolerance:
> It could look like this:
> {code}
> node-uri=http://10.1.1.1:8080,http://10.1.1.2:8080
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7119) Web Agent: Implement support for comma-delimited list of node URIs
[
https://issues.apache.org/jira/browse/IGNITE-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471539#comment-16471539
]
Pavel Konstantinov commented on IGNITE-7119:
Tested on 2.5
> Web Agent: Implement support for comma-delimited list of node URIs
> --
>
> Key: IGNITE-7119
> URL: https://issues.apache.org/jira/browse/IGNITE-7119
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.5
>
>
> We need to support several URLs for load-balancing and fault tolerance:
> It could look like this:
> {code}
> node-uri=http://10.1.1.1:8080,http://10.1.1.2:8080
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8155) Warning in log on opening of cluster tab in advanced mode
[
https://issues.apache.org/jira/browse/IGNITE-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16430595#comment-16430595
]
Alexey Kuznetsov edited comment on IGNITE-8155 at 5/11/18 4:58 AM:
---
Looks good. Merged to master and 2.5.
was (Author: kuaw26):
Looks good. Merged to master.
> Warning in log on opening of cluster tab in advanced mode
> -
>
> Key: IGNITE-8155
> URL: https://issues.apache.org/jira/browse/IGNITE-8155
> Project: Ignite
> Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.5
>
>
> # Create new cluster
> # Save cluster
> # Open cluster tab in advanced mode
> In browser console next message is shown:
> {code}
> The specified value "value" is not a valid number. The value must match to
> the following regular expression: -?(\d+|\d+\.\d+|\.\d+)([eE][-+]?\d+)?
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-7927) Web console: failed to execute query in demo
[
https://issues.apache.org/jira/browse/IGNITE-7927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov closed IGNITE-7927.
--
> Web console: failed to execute query in demo
>
>
> Key: IGNITE-7927
> URL: https://issues.apache.org/jira/browse/IGNITE-7927
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.5
>
>
> If I set 'Allow non-collocated joins' option for demo query
> {code}
> SELECT p.name, count(*) AS cnt
> FROM "ParkingCache".Parking p
> INNER JOIN "CarCache".Car c
> ON (p.id) = (c.parkingId)
> GROUP BY P.NAME
> {code}
> then I got the following error
> {code}
> Error: Failed to prepare distributed join query: join condition does not use
> index [joinedCache=CarCache, plan=SELECT P__Z0.NAME AS __C0_0, COUNT(*) AS
> __C0_1 FROM "ParkingCache".PARKING P__Z0 /* "ParkingCache".PARKING.__SCAN_ */
> INNER JOIN "CarCache".CAR C__Z1 /* batched:broadcast "CarCache".CAR.__SCAN_
> */ ON 1=1 WHERE P__Z0.ID = C__Z1.PARKINGID GROUP BY P__Z0.NAME]
> {code}
> Please add necessary indices
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7927) Web console: failed to execute query in demo
[
https://issues.apache.org/jira/browse/IGNITE-7927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471494#comment-16471494
]
Pavel Konstantinov commented on IGNITE-7927:
Tested on 2.5
> Web console: failed to execute query in demo
>
>
> Key: IGNITE-7927
> URL: https://issues.apache.org/jira/browse/IGNITE-7927
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.5
>
>
> If I set 'Allow non-collocated joins' option for demo query
> {code}
> SELECT p.name, count(*) AS cnt
> FROM "ParkingCache".Parking p
> INNER JOIN "CarCache".Car c
> ON (p.id) = (c.parkingId)
> GROUP BY P.NAME
> {code}
> then I got the following error
> {code}
> Error: Failed to prepare distributed join query: join condition does not use
> index [joinedCache=CarCache, plan=SELECT P__Z0.NAME AS __C0_0, COUNT(*) AS
> __C0_1 FROM "ParkingCache".PARKING P__Z0 /* "ParkingCache".PARKING.__SCAN_ */
> INNER JOIN "CarCache".CAR C__Z1 /* batched:broadcast "CarCache".CAR.__SCAN_
> */ ON 1=1 WHERE P__Z0.ID = C__Z1.PARKINGID GROUP BY P__Z0.NAME]
> {code}
> Please add necessary indices
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-8140) Web console: "integer number too large" in generated project
[
https://issues.apache.org/jira/browse/IGNITE-8140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov closed IGNITE-8140.
--
> Web console: "integer number too large" in generated project
>
>
> Key: IGNITE-8140
> URL: https://issues.apache.org/jira/browse/IGNITE-8140
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.5
>
>
> Some methods expected Long type but we set Integer, please fix
> {code}
> dataStorageCfg.setSystemRegionMaxSize(2147483648);
> eventStorage.setExpireAgeMs(2323232323232323);
> cfg.setMetricsExpireTime(2323232323);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8140) Web console: "integer number too large" in generated project
[
https://issues.apache.org/jira/browse/IGNITE-8140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471492#comment-16471492
]
Pavel Konstantinov commented on IGNITE-8140:
Tested on 2.5
> Web console: "integer number too large" in generated project
>
>
> Key: IGNITE-8140
> URL: https://issues.apache.org/jira/browse/IGNITE-8140
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.5
>
>
> Some methods expected Long type but we set Integer, please fix
> {code}
> dataStorageCfg.setSystemRegionMaxSize(2147483648);
> eventStorage.setExpireAgeMs(2323232323232323);
> cfg.setMetricsExpireTime(2323232323);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8155) Warning in log on opening of cluster tab in advanced mode
[
https://issues.apache.org/jira/browse/IGNITE-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471490#comment-16471490
]
Pavel Konstantinov commented on IGNITE-8155:
Tested on 2.5
> Warning in log on opening of cluster tab in advanced mode
> -
>
> Key: IGNITE-8155
> URL: https://issues.apache.org/jira/browse/IGNITE-8155
> Project: Ignite
> Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.5
>
>
> # Create new cluster
> # Save cluster
> # Open cluster tab in advanced mode
> In browser console next message is shown:
> {code}
> The specified value "value" is not a valid number. The value must match to
> the following regular expression: -?(\d+|\d+\.\d+|\.\d+)([eE][-+]?\d+)?
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-8200) Web console: unexpected confirmation
[ https://issues.apache.org/jira/browse/IGNITE-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-8200. -- > Web console: unexpected confirmation > > > Key: IGNITE-8200 > URL: https://issues.apache.org/jira/browse/IGNITE-8200 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.5 > > > # initial state - there are no clusters > # create a new one, do not save > # open Advanced screen, save > # import from DB, save > # open Caches screen - unexpected confirmation about unsaved changes appear > # click Cancel, save, open Caches again - unexpected confirmation again -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8200) Web console: unexpected confirmation
[ https://issues.apache.org/jira/browse/IGNITE-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471480#comment-16471480 ] Pavel Konstantinov commented on IGNITE-8200: Tested on 2.5 > Web console: unexpected confirmation > > > Key: IGNITE-8200 > URL: https://issues.apache.org/jira/browse/IGNITE-8200 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.5 > > > # initial state - there are no clusters > # create a new one, do not save > # open Advanced screen, save > # import from DB, save > # open Caches screen - unexpected confirmation about unsaved changes appear > # click Cancel, save, open Caches again - unexpected confirmation again -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8294) Web console: make "Beta" ribbon less obtrusive
[ https://issues.apache.org/jira/browse/IGNITE-8294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471460#comment-16471460 ] Pavel Konstantinov commented on IGNITE-8294: Tested on 2.5 > Web console: make "Beta" ribbon less obtrusive > -- > > Key: IGNITE-8294 > URL: https://issues.apache.org/jira/browse/IGNITE-8294 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.5 > > Attachments: screenshot-1.png, screenshot-2.png > > > As of now, the ribbon obstructs important controls underneath it, especially > connected clusters user menu. Something has to be done with this issue, but > the ribbon should remain in some form or another. > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8294) Web console: make "Beta" ribbon less obtrusive
[ https://issues.apache.org/jira/browse/IGNITE-8294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-8294. -- > Web console: make "Beta" ribbon less obtrusive > -- > > Key: IGNITE-8294 > URL: https://issues.apache.org/jira/browse/IGNITE-8294 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.5 > > Attachments: screenshot-1.png, screenshot-2.png > > > As of now, the ribbon obstructs important controls underneath it, especially > connected clusters user menu. Something has to be done with this issue, but > the ribbon should remain in some form or another. > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8317) Web console: Loader bug in safari
[ https://issues.apache.org/jira/browse/IGNITE-8317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-8317. -- > Web console: Loader bug in safari > - > > Key: IGNITE-8317 > URL: https://issues.apache.org/jira/browse/IGNITE-8317 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Dmitriy Shabalin >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.5 > > > Loader (that indicating data loadin) is never finished under Safary sometimes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8317) Web console: Loader bug in safari
[ https://issues.apache.org/jira/browse/IGNITE-8317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471458#comment-16471458 ] Pavel Konstantinov commented on IGNITE-8317: No issues noticed on 2.5 > Web console: Loader bug in safari > - > > Key: IGNITE-8317 > URL: https://issues.apache.org/jira/browse/IGNITE-8317 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Dmitriy Shabalin >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.5 > > > Loader (that indicating data loadin) is never finished under Safary sometimes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8317) Web console: Loader bug in safari
[ https://issues.apache.org/jira/browse/IGNITE-8317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-8317: --- Summary: Web console: Loader bug in safari (was: Loader bug in safari) > Web console: Loader bug in safari > - > > Key: IGNITE-8317 > URL: https://issues.apache.org/jira/browse/IGNITE-8317 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Dmitriy Shabalin >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.5 > > > Loader (that indicating data loadin) is never finished under Safary sometimes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8298) Broken UI of the latest table cell
[ https://issues.apache.org/jira/browse/IGNITE-8298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471450#comment-16471450 ] Pavel Konstantinov commented on IGNITE-8298: Tested on 2.5 > Broken UI of the latest table cell > -- > > Key: IGNITE-8298 > URL: https://issues.apache.org/jira/browse/IGNITE-8298 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Dmitriy Shabalin >Assignee: Dmitriy Shabalin >Priority: Major > Fix For: 2.5 > > > Check the latest cell in a table. It's UI looks broken. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8291) Web Console: Unable to build generated Dockerfile "apt-get not found"
[ https://issues.apache.org/jira/browse/IGNITE-8291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471445#comment-16471445 ] Pavel Konstantinov commented on IGNITE-8291: Tested in 2.5 > Web Console: Unable to build generated Dockerfile "apt-get not found" > - > > Key: IGNITE-8291 > URL: https://issues.apache.org/jira/browse/IGNITE-8291 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.5 > > > Since IGNITE-2.1 docker image based on alpine. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471270#comment-16471270
]
Alexey Kosenchuk commented on IGNITE-8463:
--
Please use the latest PR with the full API&implementation
https://github.com/apache/ignite/pull/3978
Test instructions are in a separate readme now:
ignite/modules/platforms/nodejs/spec/README.md
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.6
>
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7777) Thin Client lib: Node.js
[ https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471261#comment-16471261 ] ASF GitHub Bot commented on IGNITE-: GitHub user ekaterina-nbl opened a pull request: https://github.com/apache/ignite/pull/3978 IGNITE- Node.js client: full API & implementation You can merge this pull request into a Git repository by running: $ git pull https://github.com/nobitlost/ignite ignite- Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3978.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 #3978 commit 4b444dff62c04b97bc2cdb0676ad52880374 Author: ekaterina-nbl Date: 2018-03-20T21:12:21Z initial implementation commit d1e8014c80f698028d23e09cafd7ea190ac3e929 Author: ekaterina-nbl Date: 2018-03-20T21:32:52Z initial implementation commit f79229e233ffa7bff1e7c22f04749924af6d712a Author: ekaterina-nbl Date: 2018-03-22T09:39:32Z initial implementation commit 658d60b58840080b664e02815f4ba6aac76e5804 Author: ekaterina-nbl Date: 2018-03-22T16:52:18Z minor update commit 617cef12ad72791c7e7e67179e1b0c3f7f3ae6bb Author: ekaterina-nbl Date: 2018-03-25T13:33:27Z api spec commit d9729585f5a901977e2a2e40e86a2b715fab79fa Author: alexey-nbl Date: 2018-03-25T21:27:11Z link to api_spec added commit ea847eba62e556fa81cbf9838ffe17af60f464e4 Author: ekaterina-nbl Date: 2018-03-31T22:07:50Z error types modified commit c2ad53fe625cc3a05155eeef318421538830 Author: ekaterina-nbl Date: 2018-03-31T23:41:56Z client states commit 6d2233864b4d891361d38a7143846570bd6c0ef6 Author: ekaterina-nbl Date: 2018-04-01T13:11:27Z object types improvement commit 52fbc5f87143da068596141cb59b17b684fd2c1f Author: ekaterina-nbl Date: 2018-04-02T16:59:52Z complex objects commit cae5a28e7e0d610434debcc140738e2f48d061cf Author: ekaterina-nbl Date: 2018-04-02T20:13:00Z object types improvement commit 3165405d4eae09519dc9b5f40f162eb74a9b3c5d Author: ekaterina-nbl Date: 2018-04-02T21:21:26Z client states commit fdbb8f86b32fe4c038d38620a80921be3038f31f Author: alexey-nbl Date: 2018-04-03T08:26:04Z Ignite client states described commit 04b946885db0ea2f6fe56a75e28302641dad5f61 Author: alexey-nbl Date: 2018-04-03T09:35:49Z minor update commit f4aaf1c3f23c82ba7974b4c571a9984748e5e82e Author: alexey-nbl Date: 2018-04-03T12:47:54Z Update ObjectType.js commit e4c8279f4e83b3ed13383420ab3d1417b090a3fa Author: ekaterina-nbl Date: 2018-04-03T13:46:19Z minor updates + api spec commit ed2e4ee830ca40a28dc31958665f52fab6a0bcdd Author: alexey-nbl Date: 2018-04-04T14:34:52Z Update ObjectType.js commit 7e1666eb5df82b622a028c0ea949fa21c79e66c2 Author: alexey-nbl Date: 2018-04-04T15:14:00Z Update ObjectType.js commit 7b0270d65b597dc1b0d164e78f07c3a21c37ca67 Author: ekaterina-nbl Date: 2018-04-08T17:16:43Z sql queries, key value ops commit fe90f53fd08f77add17fbf06d014f9a9b0a11c65 Author: alexey-nbl Date: 2018-04-08T18:31:47Z Update IgniteClient.js commit 04137bf5ec3b7077e194edd0100a01bb43f7933a Author: alexey-nbl Date: 2018-04-08T18:37:04Z Update CacheConfiguration.js commit b63ad5980718da1b0c44fa4ca138c6e85e47aef3 Author: alexey-nbl Date: 2018-04-08T19:11:11Z Update ObjectType.js commit 756b908c9dc38ae497e4d7d740f836dabed93e48 Author: alexey-nbl Date: 2018-04-08T22:41:54Z Update CacheClient.js commit e96ffee17298dd25d26a7029738132478271cf92 Author: ekaterina-nbl Date: 2018-04-08T23:23:33Z object array, minor updates commit c050e671f74232c4efc41f51c2018d08b152cbbc Author: alexey-nbl Date: 2018-04-09T21:04:35Z Update CacheClient.js commit 25052a4e93d6fcc0b0c4789fdd5a1eb85413b5a2 Author: alexey-nbl Date: 2018-04-09T22:43:50Z Update ObjectType.js commit c516b4147c10398d4f34d78a8830dd0fcb5f28f4 Author: alexey-nbl Date: 2018-04-10T11:50:13Z Update CacheClient.js commit 0e9924a0df8a1d41718fb929698b8e4416f2efa2 Author: ekaterina-nbl Date: 2018-04-10T13:21:16Z cache key value operations tests commit e09ee0e7969bffd6f4cfd11579f6d0ff9b486c99 Author: ekaterina-nbl Date: 2018-04-10T13:21:50Z Merge branch 'master' of https://github.com/nobitlost/ignite commit 15d2abce41b4f1c9d4d5fecd44a99a5393177482 Author: alexey-nbl Date: 2018-04-10T14:38:57Z Update Query.js > Thin Client lib: Node.js > > > Key: IGNITE- > URL: https://issues.apache.org/jira/browse/IGNITE- > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Alexey Kosenchuk >Assignee: Alexey
[jira] [Commented] (IGNITE-7777) Thin Client lib: Node.js
[ https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471249#comment-16471249 ] Alexey Kosenchuk commented on IGNITE-: -- Issues against Binary Client Protocol 2.4: IGNITE-8039 IGNITE-8212 IGNITE-8411 > Thin Client lib: Node.js > > > Key: IGNITE- > URL: https://issues.apache.org/jira/browse/IGNITE- > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Alexey Kosenchuk >Assignee: Alexey Kosenchuk >Priority: Major > > Implement Thin (lightweight) Client lib in Node.js programming language for > Ignite Binary Client Protocol. > Examples of other Thin Clients: > .net > https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Client > java https://github.com/gridgain/apache-ignite/tree/ignite-7421 > https://apacheignite.readme.io/v2.3/docs/java-thin-client > Scope of work > - > Functionality: > Support all operations of the Ignite Binary Client Protocol 2.4: > https://apacheignite.readme.io/v2.4/docs/binary-client-protocol > Except: > OP_QUERY_SCAN (requires changes on the server side) > OP_REGISTER_BINARY_TYPE_NAME, OP_GET_BINARY_TYPE_NAME (not applicable) > Support name/password authentication (not in the protocol yet). > Support optional SSL/TLS communication. > Support failover/reconnect algorithm: > https://issues.apache.org/jira/browse/IGNITE-7282 > http://apache-ignite-developers.2346864.n4.nabble.com/Thin-client-failover-mechanism-ODBC-JDBC-td26553.html > Minimal Node.js version - 8.0 > Promise asynch/await to be used. > Examples: > Cover all basic features - Key-value API, SQL queries, Cluster > configuration/management, Authentication, SSL/TLS. > Tests: > Jasmine tests for all API methods and all basic features. > Simple Jasmine tests to start examples. > The tests should call external commands/scripts to start/stop the nodes. > Docs: > Auto-generated API spec from jsdoc comments: > http://usejsdoc.org/ > https://www.npmjs.com/package/jsdoc > Readme for the lib. > Simple instruction to setup/run examples. > Simple instruction to setup/run Jasmine tests. > Docs should be on readme.io or in github - TBD > Released as NPM module on https://www.npmjs.com > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8444) Authentication: add documentation about user management SQL command and authentication feature
[ https://issues.apache.org/jira/browse/IGNITE-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg reassigned IGNITE-8444: --- Assignee: Denis Magda (was: Prachi Garg) > Authentication: add documentation about user management SQL command and > authentication feature > -- > > Key: IGNITE-8444 > URL: https://issues.apache.org/jira/browse/IGNITE-8444 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.5 > Environment: Adds overview for authentication feature and > documentation for SQL commands: > - CREATE USER > - ALTER USER > - DROP USER >Reporter: Taras Ledkov >Assignee: Denis Magda >Priority: Major > Fix For: 2.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8444) Authentication: add documentation about user management SQL command and authentication feature
[ https://issues.apache.org/jira/browse/IGNITE-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470962#comment-16470962 ] Prachi Garg commented on IGNITE-8444: - Reviewed the DDL commands; looks good. [~dmagda], I have added a section for Authentication under Security in the main documentation - [https://apacheignite.readme.io/v2.4/docs/advanced-security-25] . Please review. > Authentication: add documentation about user management SQL command and > authentication feature > -- > > Key: IGNITE-8444 > URL: https://issues.apache.org/jira/browse/IGNITE-8444 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.5 > Environment: Adds overview for authentication feature and > documentation for SQL commands: > - CREATE USER > - ALTER USER > - DROP USER >Reporter: Taras Ledkov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7992) Clarify how expiration policy works for durable memory and 3rd pary
[ https://issues.apache.org/jira/browse/IGNITE-7992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470934#comment-16470934 ] Denis Magda commented on IGNITE-7992: - Updated the doc with the following information. The expiration policies work this way depending on a memory configuration of your deployment: * In-Memory Mode (data is stored solely in RAM): expired entries are purged from RAM completely. * Memory + Ignite persistence: expired entries are removed from both memory and disk tiers. * Memory + 3rd party persistence: expired entries are removed from the memory tier only (Ignite) and left untouched in the 3rd party persistence (RDBMS, NoSQL, and other databases). * Memory + Swap: expired entries are removed from both RAM and swap files. > Clarify how expiration policy works for durable memory and 3rd pary > --- > > Key: IGNITE-7992 > URL: https://issues.apache.org/jira/browse/IGNITE-7992 > Project: Ignite > Issue Type: New Feature > Components: documentation >Affects Versions: 2.4 >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > Fix For: 2.5 > > > Update the expiration policies page with the result of the following > discussion: > http://apache-ignite-developers.2346864.n4.nabble.com/Data-eviction-expiration-from-Ignite-persistence-td24419i20.html#a28081 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7992) Clarify how expiration policy works for durable memory and 3rd pary
[ https://issues.apache.org/jira/browse/IGNITE-7992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-7992. --- > Clarify how expiration policy works for durable memory and 3rd pary > --- > > Key: IGNITE-7992 > URL: https://issues.apache.org/jira/browse/IGNITE-7992 > Project: Ignite > Issue Type: New Feature > Components: documentation >Affects Versions: 2.4 >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > Fix For: 2.5 > > > Update the expiration policies page with the result of the following > discussion: > http://apache-ignite-developers.2346864.n4.nabble.com/Data-eviction-expiration-from-Ignite-persistence-td24419i20.html#a28081 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7992) Clarify how expiration policy works for durable memory and 3rd pary
[ https://issues.apache.org/jira/browse/IGNITE-7992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-7992. - Resolution: Fixed > Clarify how expiration policy works for durable memory and 3rd pary > --- > > Key: IGNITE-7992 > URL: https://issues.apache.org/jira/browse/IGNITE-7992 > Project: Ignite > Issue Type: New Feature > Components: documentation >Affects Versions: 2.4 >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > Fix For: 2.5 > > > Update the expiration policies page with the result of the following > discussion: > http://apache-ignite-developers.2346864.n4.nabble.com/Data-eviction-expiration-from-Ignite-persistence-td24419i20.html#a28081 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-6489) Expiration Policies and Durable Memory Doc
[ https://issues.apache.org/jira/browse/IGNITE-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-6489. --- > Expiration Policies and Durable Memory Doc > -- > > Key: IGNITE-6489 > URL: https://issues.apache.org/jira/browse/IGNITE-6489 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Blocker > Fix For: 2.5 > > > We must make sure that the existing expiration policies documentation [1] > makes sense for the off-heap space of the durable memory: > https://apacheignite.readme.io/docs/expiry-policies -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-6489) Expiration Policies and Durable Memory Doc
[ https://issues.apache.org/jira/browse/IGNITE-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-6489. - Resolution: Duplicate Duplicate of IGNITE-7992 > Expiration Policies and Durable Memory Doc > -- > > Key: IGNITE-6489 > URL: https://issues.apache.org/jira/browse/IGNITE-6489 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Blocker > Fix For: 2.5 > > > We must make sure that the existing expiration policies documentation [1] > makes sense for the off-heap space of the durable memory: > https://apacheignite.readme.io/docs/expiry-policies -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7992) Clarify how expiration policy works for durable memory and 3rd pary
[ https://issues.apache.org/jira/browse/IGNITE-7992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-7992: --- Assignee: Denis Magda (was: Prachi Garg) > Clarify how expiration policy works for durable memory and 3rd pary > --- > > Key: IGNITE-7992 > URL: https://issues.apache.org/jira/browse/IGNITE-7992 > Project: Ignite > Issue Type: New Feature > Components: documentation >Affects Versions: 2.4 >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > Fix For: 2.5 > > > Update the expiration policies page with the result of the following > discussion: > http://apache-ignite-developers.2346864.n4.nabble.com/Data-eviction-expiration-from-Ignite-persistence-td24419i20.html#a28081 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7683) ContinuousQueryWithTransformer needs to be documented
[ https://issues.apache.org/jira/browse/IGNITE-7683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470912#comment-16470912 ] Denis Magda commented on IGNITE-7683: - [~NIzhikov], thanks a lot, great job! I've reviewed and adjusted the doc a little bit. > ContinuousQueryWithTransformer needs to be documented > - > > Key: IGNITE-7683 > URL: https://issues.apache.org/jira/browse/IGNITE-7683 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Denis Magda >Priority: Minor > Fix For: 2.5 > > > New API - ContinuousQueryWithTransformer should be documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7683) ContinuousQueryWithTransformer needs to be documented
[ https://issues.apache.org/jira/browse/IGNITE-7683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-7683. --- > ContinuousQueryWithTransformer needs to be documented > - > > Key: IGNITE-7683 > URL: https://issues.apache.org/jira/browse/IGNITE-7683 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Denis Magda >Priority: Minor > Fix For: 2.5 > > > New API - ContinuousQueryWithTransformer should be documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8093) Document IGNITE_MARSHALLER_WHITELIST and IGNITE_MARSHALLER_BLACKLIST properties
[ https://issues.apache.org/jira/browse/IGNITE-8093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-8093. --- > Document IGNITE_MARSHALLER_WHITELIST and IGNITE_MARSHALLER_BLACKLIST > properties > --- > > Key: IGNITE-8093 > URL: https://issues.apache.org/jira/browse/IGNITE-8093 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Critical > Fix For: 2.5 > > > Document how to use and configure two system properties that help to prevent > the execution of arbitrary 3rd party code - IGNITE_MARSHALLER_WHITELIST and > IGNITE_MARSHALLER_BLACKLIST. > Use JavaDocs for more details and this disclosure message: > https://lists.apache.org/thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5a558da80d0209@%3Cdev.ignite.apache.org%3E > The documentation needs to be under "Security" section and has a reference > from a production readiness. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8469) Non-heap memroy leak for calling cluster activation multi times
Maxim Muzafarov created IGNITE-8469:
---
Summary: Non-heap memroy leak for calling cluster activation multi
times
Key: IGNITE-8469
URL: https://issues.apache.org/jira/browse/IGNITE-8469
Project: Ignite
Issue Type: Bug
Components: persistence
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.6
Calling multiple time cluster (with enabled persistence and started client
nodes) activation {{ig3CB.cluster().active(true);}} leads to non-heap memory
leak.
Line {{org/apache/ignite/internal/pagemem/impl/PageMemoryNoStoreImpl.java:234}}
looks suspicious because of in case method
{{org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl#start}} callled
multi times (e.g. activate(true) called multi times) we lost info about
allocated regions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-8268) Add documentation for linear regression (release 2.5)
[ https://issues.apache.org/jira/browse/IGNITE-8268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-8268. --- > Add documentation for linear regression (release 2.5) > - > > Key: IGNITE-8268 > URL: https://issues.apache.org/jira/browse/IGNITE-8268 > Project: Ignite > Issue Type: Improvement > Components: documentation, ml >Affects Versions: 2.5 >Reporter: Anton Dmitriev >Assignee: Denis Magda >Priority: Major > Fix For: 2.5 > > > In Apache Ignite 2.5 we have added two implementation of linear regression > based on partition based dataset: LSQR and gradient descent and now we need > to add documentation for these features. > Affected pages: > [Linear > Regression|https://apacheignite.readme.io/v2.4/docs/linear-regression-25] > In release 2.5 > [https://apacheignite.readme.io/v2.4/docs/ols-multiple-linear-regression|https://apacheignite.readme.io/v2.4/docs/ols-multiple-linear-regression] > should be changed to > [https://apacheignite.readme.io/docs/linear-regression-25|https://apacheignite.readme.io/docs/linear-regression-25]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8268) Add documentation for linear regression (release 2.5)
[ https://issues.apache.org/jira/browse/IGNITE-8268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470879#comment-16470879 ] Denis Magda commented on IGNITE-8268: - Looks good, thanks! > Add documentation for linear regression (release 2.5) > - > > Key: IGNITE-8268 > URL: https://issues.apache.org/jira/browse/IGNITE-8268 > Project: Ignite > Issue Type: Improvement > Components: documentation, ml >Affects Versions: 2.5 >Reporter: Anton Dmitriev >Assignee: Denis Magda >Priority: Major > Fix For: 2.5 > > > In Apache Ignite 2.5 we have added two implementation of linear regression > based on partition based dataset: LSQR and gradient descent and now we need > to add documentation for these features. > Affected pages: > [Linear > Regression|https://apacheignite.readme.io/v2.4/docs/linear-regression-25] > In release 2.5 > [https://apacheignite.readme.io/v2.4/docs/ols-multiple-linear-regression|https://apacheignite.readme.io/v2.4/docs/ols-multiple-linear-regression] > should be changed to > [https://apacheignite.readme.io/docs/linear-regression-25|https://apacheignite.readme.io/docs/linear-regression-25]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8269) Add documentation for decision tree (release 2.5)
[ https://issues.apache.org/jira/browse/IGNITE-8269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-8269. --- > Add documentation for decision tree (release 2.5) > - > > Key: IGNITE-8269 > URL: https://issues.apache.org/jira/browse/IGNITE-8269 > Project: Ignite > Issue Type: Improvement > Components: documentation, ml >Affects Versions: 2.5 >Reporter: Anton Dmitriev >Assignee: Denis Magda >Priority: Major > Fix For: 2.5 > > > In Apache Ignite 2.5 we have added a decision tree based on partition based > dataset and now we need to documentation for this feature. > Affected pages: > [Decision Tree|https://apacheignite.readme.io/v2.4/docs/decision-tree-25] > In release 2.5 > [https://apacheignite.readme.io/docs/decision-trees|https://apacheignite.readme.io/docs/decision-trees] > page should be changed to > [https://apacheignite.readme.io/docs/decision-tree-25|https://apacheignite.readme.io/docs/decision-tree-25]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8269) Add documentation for decision tree (release 2.5)
[ https://issues.apache.org/jira/browse/IGNITE-8269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470869#comment-16470869 ] Denis Magda commented on IGNITE-8269: - Looks good. Closing the ticket. [~dmitrievanthony], please make sure the references to examples go to the master branch all the times. Corrected this time. > Add documentation for decision tree (release 2.5) > - > > Key: IGNITE-8269 > URL: https://issues.apache.org/jira/browse/IGNITE-8269 > Project: Ignite > Issue Type: Improvement > Components: documentation, ml >Affects Versions: 2.5 >Reporter: Anton Dmitriev >Assignee: Denis Magda >Priority: Major > Fix For: 2.5 > > > In Apache Ignite 2.5 we have added a decision tree based on partition based > dataset and now we need to documentation for this feature. > Affected pages: > [Decision Tree|https://apacheignite.readme.io/v2.4/docs/decision-tree-25] > In release 2.5 > [https://apacheignite.readme.io/docs/decision-trees|https://apacheignite.readme.io/docs/decision-trees] > page should be changed to > [https://apacheignite.readme.io/docs/decision-tree-25|https://apacheignite.readme.io/docs/decision-tree-25]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8271) Add documentation for partition based dataset (release 2.5)
[ https://issues.apache.org/jira/browse/IGNITE-8271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-8271: --- Assignee: Anton Dmitriev (was: Denis Magda) > Add documentation for partition based dataset (release 2.5) > --- > > Key: IGNITE-8271 > URL: https://issues.apache.org/jira/browse/IGNITE-8271 > Project: Ignite > Issue Type: Improvement > Components: documentation, ml >Affects Versions: 2.5 >Reporter: Anton Dmitriev >Assignee: Anton Dmitriev >Priority: Major > Fix For: 2.5 > > > In Apache Ignite 2.5 we have added new infrastructure layer - partition based > dataset, so now we need to add correspondent documentation. > Affected pages: > [Machine > Learning|https://apacheignite.readme.io/v2.4/docs/machine-learning-25] > [Partition Based > Dataset|https://apacheignite.readme.io/v2.4/docs/partition-based-dataset-25] > In release 2.5 > [https://apacheignite.readme.io/docs/machine-learning|https://apacheignite.readme.io/docs/machine-learning] > page should be changed to > [https://apacheignite.readme.io/docs/machine-learning-25|https://apacheignite.readme.io/docs/machine-learning-25]. > In release 2.5 > [https://apacheignite.readme.io/docs/partition-based-dataset-25|https://apacheignite.readme.io/docs/partition-based-dataset-25] > page should be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8271) Add documentation for partition based dataset (release 2.5)
[ https://issues.apache.org/jira/browse/IGNITE-8271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470855#comment-16470855 ] Denis Magda commented on IGNITE-8271: - Reviewed and adjusted the docs a little bit. [~dmitrievanthony], do we have any example of the partition-based data set in GitHub repo? I would add a reference to it to Example section of the doc. > Add documentation for partition based dataset (release 2.5) > --- > > Key: IGNITE-8271 > URL: https://issues.apache.org/jira/browse/IGNITE-8271 > Project: Ignite > Issue Type: Improvement > Components: documentation, ml >Affects Versions: 2.5 >Reporter: Anton Dmitriev >Assignee: Denis Magda >Priority: Major > Fix For: 2.5 > > > In Apache Ignite 2.5 we have added new infrastructure layer - partition based > dataset, so now we need to add correspondent documentation. > Affected pages: > [Machine > Learning|https://apacheignite.readme.io/v2.4/docs/machine-learning-25] > [Partition Based > Dataset|https://apacheignite.readme.io/v2.4/docs/partition-based-dataset-25] > In release 2.5 > [https://apacheignite.readme.io/docs/machine-learning|https://apacheignite.readme.io/docs/machine-learning] > page should be changed to > [https://apacheignite.readme.io/docs/machine-learning-25|https://apacheignite.readme.io/docs/machine-learning-25]. > In release 2.5 > [https://apacheignite.readme.io/docs/partition-based-dataset-25|https://apacheignite.readme.io/docs/partition-based-dataset-25] > page should be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-5789) After client reconnects to server if server was restarted, client doesn't create caches defined in client's configuration
[ https://issues.apache.org/jira/browse/IGNITE-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470816#comment-16470816 ] Dmitriy Pavlov edited comment on IGNITE-5789 at 5/10/18 5:43 PM: - I've queued one more TC run with actual master with this fix, [https://ci.ignite.apache.org/viewQueued.html?itemId=1281364&tab=queuedBuildOverviewTab] But for PR merge it is still desired to rebase/merge current branch to avoid conflicts. was (Author: dpavlov): I've queued one more TC run with actual master with this fix, [https://ci.ignite.apache.org/viewQueued.html?itemId=1281364&tab=queuedBuildOverviewTab] But for merge it is still desired to rebase/merge to avoid conflicts. > After client reconnects to server if server was restarted, client doesn't > create caches defined in client's configuration > - > > Key: IGNITE-5789 > URL: https://issues.apache.org/jira/browse/IGNITE-5789 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Evgenii Zhuravlev >Assignee: vk >Priority: Major > Fix For: 2.6 > > Attachments: ClientReconnectAfterClusterRestartTest.java > > > User with this problem on SO: > https://stackoverflow.com/questions/46053089/ignite-cache-reconnection-issue-cache-is-stopped -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-5789) After client reconnects to server if server was restarted, client doesn't create caches defined in client's configuration
[ https://issues.apache.org/jira/browse/IGNITE-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470793#comment-16470793 ] Dmitriy Pavlov edited comment on IGNITE-5789 at 5/10/18 5:39 PM: - [~vk] could you please merge master into your branch? There are a number of conflicts now. Run-all shows too much test failures (~135), but I guess most of these failures were fixed already. was (Author: dpavlov): [~vk] please merge master into your branch, there are conflicts now. Run-all shows too much test failures (~135), but I guess most of these failures were fixed already. > After client reconnects to server if server was restarted, client doesn't > create caches defined in client's configuration > - > > Key: IGNITE-5789 > URL: https://issues.apache.org/jira/browse/IGNITE-5789 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Evgenii Zhuravlev >Assignee: vk >Priority: Major > Fix For: 2.6 > > Attachments: ClientReconnectAfterClusterRestartTest.java > > > User with this problem on SO: > https://stackoverflow.com/questions/46053089/ignite-cache-reconnection-issue-cache-is-stopped -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5789) After client reconnects to server if server was restarted, client doesn't create caches defined in client's configuration
[ https://issues.apache.org/jira/browse/IGNITE-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470816#comment-16470816 ] Dmitriy Pavlov commented on IGNITE-5789: I've queued one more TC run with actual master with this fix, [https://ci.ignite.apache.org/viewQueued.html?itemId=1281364&tab=queuedBuildOverviewTab] But for merge it is still desired to rebase/merge to avoid conflicts. > After client reconnects to server if server was restarted, client doesn't > create caches defined in client's configuration > - > > Key: IGNITE-5789 > URL: https://issues.apache.org/jira/browse/IGNITE-5789 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Evgenii Zhuravlev >Assignee: vk >Priority: Major > Fix For: 2.6 > > Attachments: ClientReconnectAfterClusterRestartTest.java > > > User with this problem on SO: > https://stackoverflow.com/questions/46053089/ignite-cache-reconnection-issue-cache-is-stopped -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5945) Flaky failure in IgniteCache 5: IgniteCacheAtomicProtocolTest.testPutReaderUpdate2
[
https://issues.apache.org/jira/browse/IGNITE-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470817#comment-16470817
]
Alexander Menshikov commented on IGNITE-5945:
-
I found out the reason for the problem. As I see, rebalancing can change
primary node with near cache when new client nodes appear. I'm not sure this is
a valid behaver, but this is what really happens (I have checked it).
So adding a call for *awaitPartitionMapExchange* can fix the problem. I will
double check this solution (locally and on TC), prepare PR and update status of
the issue when done.
> Flaky failure in IgniteCache 5:
> IgniteCacheAtomicProtocolTest.testPutReaderUpdate2
> --
>
> Key: IGNITE-5945
> URL: https://issues.apache.org/jira/browse/IGNITE-5945
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Alexander Menshikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.IgniteCacheAtomicProtocolTest#testPutReaderUpdate2
> {noformat}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertFalse(Assert.java:39)
> at junit.framework.Assert.assertFalse(Assert.java:47)
> at junit.framework.TestCase.assertFalse(TestCase.java:219)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.IgniteCacheAtomicProtocolTest.readerUpdateDhtFails(IgniteCacheAtomicProtocolTest.java:865)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.IgniteCacheAtomicProtocolTest.testPutReaderUpdate2(IgniteCacheAtomicProtocolTest.java:765)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Fail is reproducable locally 2 times per 20 runs
> On TeamCity test success rate is 88,2%
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-6430) CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails periodically.
[
https://issues.apache.org/jira/browse/IGNITE-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470351#comment-16470351
]
Alexander Menshikov edited comment on IGNITE-6430 at 5/10/18 5:31 PM:
--
[~agura] [~dpavlov]
I have finished the task. Please review and merge if okay.
[~alex_pl]
Thanks for the review.
was (Author: sharpler):
[~agura]
I have finished the task. Please review and merge if okay.
[~alex_pl]
Thanks for the review.
> CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails
> periodically.
>
>
> Key: IGNITE-6430
> URL: https://issues.apache.org/jira/browse/IGNITE-6430
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Alexander Menshikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> {{CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime}} test
> fails periodically.
> {noformat}
> [2017-09-18 15:18:20,073][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: Expected less 5000, Actual:-100969
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime(CacheGroupsMetricsRebalanceTest.java:261)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> After fix test should be unmuted on TC.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8468) Adding and searching UUIDs in index tree produces a lot of garbage
[ https://issues.apache.org/jira/browse/IGNITE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470619#comment-16470619 ] Andrew Mashenkov edited comment on IGNITE-8468 at 5/10/18 5:31 PM: --- [~gvvinblade] Would you please take a look at the PR? was (Author: amashenkov): [~gvvinblade] Would you please take a look at the patch attached? > Adding and searching UUIDs in index tree produces a lot of garbage > -- > > Key: IGNITE-8468 > URL: https://issues.apache.org/jira/browse/IGNITE-8468 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrew Mashenkov >Priority: Major > Labels: performance > Fix For: 2.6 > > > Seems, optimization for UUIDs was missed in IGNITE-5918. > PFA patch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8272) Add documentation for normalization preprocessor (release 2.5)
[ https://issues.apache.org/jira/browse/IGNITE-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-8272. --- > Add documentation for normalization preprocessor (release 2.5) > -- > > Key: IGNITE-8272 > URL: https://issues.apache.org/jira/browse/IGNITE-8272 > Project: Ignite > Issue Type: Improvement > Components: documentation, ml >Affects Versions: 2.5 >Reporter: Anton Dmitriev >Assignee: Denis Magda >Priority: Major > Fix For: 2.5 > > > In Apache Ignite 2.5 we have added a normalization preprocessor working on > top of partition based dataset and now we need to add documentation for this > feature. > Affected pages: > [Preprocessing|https://apacheignite.readme.io/v2.4/docs/preprocessing-25] > In release 2.5 > [https://apacheignite.readme.io/v2.4/docs/preprocessing-25|https://apacheignite.readme.io/v2.4/docs/preprocessing-25] > page should be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8468) Adding and searching UUIDs in index tree produces a lot of garbage
[ https://issues.apache.org/jira/browse/IGNITE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470794#comment-16470794 ] ASF GitHub Bot commented on IGNITE-8468: GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/3977 IGNITE-8468: Optimization for UUID fields. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8468 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3977.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 #3977 commit 67f2a6cee88a104c6d00864cb89d9248eef50460 Author: Andrey V. Mashenkov Date: 2018-05-10T17:29:41Z Optimization for UUID fields. > Adding and searching UUIDs in index tree produces a lot of garbage > -- > > Key: IGNITE-8468 > URL: https://issues.apache.org/jira/browse/IGNITE-8468 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrew Mashenkov >Priority: Major > Labels: performance > Fix For: 2.6 > > > Seems, optimization for UUIDs was missed in IGNITE-5918. > PFA patch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8468) Adding and searching UUIDs in index tree produces a lot of garbage
[ https://issues.apache.org/jira/browse/IGNITE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-8468: - Attachment: (was: Optimization_for_UUID_fields.patch) > Adding and searching UUIDs in index tree produces a lot of garbage > -- > > Key: IGNITE-8468 > URL: https://issues.apache.org/jira/browse/IGNITE-8468 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrew Mashenkov >Priority: Major > Labels: performance > Fix For: 2.6 > > > Seems, optimization for UUIDs was missed in IGNITE-5918. > PFA patch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5789) After client reconnects to server if server was restarted, client doesn't create caches defined in client's configuration
[ https://issues.apache.org/jira/browse/IGNITE-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470793#comment-16470793 ] Dmitriy Pavlov commented on IGNITE-5789: [~vk] please merge master into your branch, there are conflicts now. Run-all shows too much test failures (~135), but I guess most of these failures were fixed already. > After client reconnects to server if server was restarted, client doesn't > create caches defined in client's configuration > - > > Key: IGNITE-5789 > URL: https://issues.apache.org/jira/browse/IGNITE-5789 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Evgenii Zhuravlev >Assignee: vk >Priority: Major > Fix For: 2.6 > > Attachments: ClientReconnectAfterClusterRestartTest.java > > > User with this problem on SO: > https://stackoverflow.com/questions/46053089/ignite-cache-reconnection-issue-cache-is-stopped -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8468) Adding and searching UUIDs in index tree produces a lot of garbage
[ https://issues.apache.org/jira/browse/IGNITE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-8468: Fix Version/s: 2.6 > Adding and searching UUIDs in index tree produces a lot of garbage > -- > > Key: IGNITE-8468 > URL: https://issues.apache.org/jira/browse/IGNITE-8468 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrew Mashenkov >Priority: Major > Labels: performance > Fix For: 2.6 > > Attachments: Optimization_for_UUID_fields.patch > > > Seems, optimization for UUIDs was missed in IGNITE-5918. > PFA patch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8468) Adding and searching UUIDs in index tree produces a lot of garbage
[ https://issues.apache.org/jira/browse/IGNITE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-8468: Labels: performance (was: ) > Adding and searching UUIDs in index tree produces a lot of garbage > -- > > Key: IGNITE-8468 > URL: https://issues.apache.org/jira/browse/IGNITE-8468 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrew Mashenkov >Priority: Major > Labels: performance > Fix For: 2.6 > > Attachments: Optimization_for_UUID_fields.patch > > > Seems, optimization for UUIDs was missed in IGNITE-5918. > PFA patch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8468) Adding and searching UUIDs in index tree produces a lot of garbage
[ https://issues.apache.org/jira/browse/IGNITE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-8468: Component/s: sql > Adding and searching UUIDs in index tree produces a lot of garbage > -- > > Key: IGNITE-8468 > URL: https://issues.apache.org/jira/browse/IGNITE-8468 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrew Mashenkov >Priority: Major > Labels: performance > Fix For: 2.6 > > Attachments: Optimization_for_UUID_fields.patch > > > Seems, optimization for UUIDs was missed in IGNITE-5918. > PFA patch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7896) Files of evicted partitions are not removed from disk storage
[ https://issues.apache.org/jira/browse/IGNITE-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470751#comment-16470751 ] Andrey Gura commented on IGNITE-7896: - LGTM. Merged to master branch. Thanks for contribution! > Files of evicted partitions are not removed from disk storage > - > > Key: IGNITE-7896 > URL: https://issues.apache.org/jira/browse/IGNITE-7896 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.6 > > Attachments: IgnitePdsRebalanceCompletionAndPartitionFilesTest.java > > > Look at test reproduction: > [^IgnitePdsRebalanceCompletionAndPartitionFilesTest.java] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8441) Java 9 (Stage II)
[ https://issues.apache.org/jira/browse/IGNITE-8441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8441: Priority: Critical (was: Blocker) > Java 9 (Stage II) > - > > Key: IGNITE-8441 > URL: https://issues.apache.org/jira/browse/IGNITE-8441 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > Fix For: 2.6 > > > Enhance [Ignite Tests 2.4+ (Java > 8)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&tab=projectOverview] > project with ability to run build and tests under JDK9. Fix all incoming > problems so that full Run All test runs on same branches provide similar > results (excluding flaky tests). > Some known problems: > * some current versions of used maven plugins and 3rd party dependencies are > still not ready for Java 9 > * some JVM options of current test build configurations require revision > * scala -- both 2.10 and 2.11 currently used in building and testing do not > support Java 9 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8441) Java 9 (Stage II)
[ https://issues.apache.org/jira/browse/IGNITE-8441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8441: Fix Version/s: (was: 2.5) 2.6 > Java 9 (Stage II) > - > > Key: IGNITE-8441 > URL: https://issues.apache.org/jira/browse/IGNITE-8441 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Blocker > Fix For: 2.6 > > > Enhance [Ignite Tests 2.4+ (Java > 8)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&tab=projectOverview] > project with ability to run build and tests under JDK9. Fix all incoming > problems so that full Run All test runs on same branches provide similar > results (excluding flaky tests). > Some known problems: > * some current versions of used maven plugins and 3rd party dependencies are > still not ready for Java 9 > * some JVM options of current test build configurations require revision > * scala -- both 2.10 and 2.11 currently used in building and testing do not > support Java 9 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8461) Scala-2.10 modules compilation failure under JDK 9
[
https://issues.apache.org/jira/browse/IGNITE-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8461:
Fix Version/s: (was: 2.5)
2.6
> Scala-2.10 modules compilation failure under JDK 9
> --
>
> Key: IGNITE-8461
> URL: https://issues.apache.org/jira/browse/IGNITE-8461
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Peter Ivanov
>Priority: Critical
> Fix For: 2.6
>
>
> {code}
> [ERROR] error: java.lang.NoClassDefFoundError: javax/tools/ToolProvider
> [INFO]at
> scala.reflect.io.JavaToolsPlatformArchive.iterator(ZipArchive.scala:242)
> [INFO]at
> scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
> [INFO]at scala.reflect.io.AbstractFile.foreach(AbstractFile.scala:92)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.traverse(ClassPath.scala:308)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.x$16$lzycompute(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.x$16(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.packages$lzycompute(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.packages(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.packages(ClassPath.scala:297)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath$$anonfun$packages$1.apply(ClassPath.scala:375)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath$$anonfun$packages$1.apply(ClassPath.scala:375)
> [INFO]at scala.collection.Iterator$class.foreach(Iterator.scala:727)
> [INFO]at
> scala.collection.AbstractIterator.foreach(Iterator.scala:1157)
> [INFO]at
> scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
> [INFO]at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath.packages$lzycompute(ClassPath.scala:375)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath.packages(ClassPath.scala:370)
> [INFO]at
> scala.tools.nsc.symtab.SymbolLoaders$PackageLoader.doComplete(SymbolLoaders.scala:243)
> [INFO]at
> scala.tools.nsc.symtab.SymbolLoaders$SymbolLoader.complete(SymbolLoaders.scala:194)
> [INFO]at
> scala.reflect.internal.Symbols$Symbol.info(Symbols.scala:1231)
> [INFO]at
> scala.reflect.internal.Mirrors$RootsBase.init(Mirrors.scala:240)
> [INFO]at scala.tools.nsc.Global.rootMirror$lzycompute(Global.scala:59)
> [INFO]at scala.tools.nsc.Global.rootMirror(Global.scala:57)
> [INFO]at scala.tools.nsc.Global.rootMirror(Global.scala:37)
> [INFO]at
> scala.reflect.internal.Definitions$DefinitionsClass.(Definitions.scala:166)
> [INFO]at
> scala.reflect.internal.Definitions$definitions$.(Definitions.scala:20)
> [INFO]at
> scala.reflect.internal.SymbolTable.definitions$lzycompute(SymbolTable.scala:13)
> [INFO]at
> scala.reflect.internal.SymbolTable.definitions(SymbolTable.scala:13)
> [INFO]at scala.tools.nsc.Global$Run.(Global.scala:1290)
> [INFO]at scala.tools.nsc.Driver.doCompile(Driver.scala:32)
> [INFO]at scala.tools.nsc.Main$.doCompile(Main.scala:79)
> [INFO]at scala.tools.nsc.Driver.process(Driver.scala:54)
> [INFO]at scala.tools.nsc.Driver.main(Driver.scala:67)
> [INFO]at scala.tools.nsc.Main.main(Main.scala)
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [INFO]at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [INFO]at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> [INFO]at
> scala_maven_executions.MainHelper.runMain(MainHelper.java:164)
> [INFO]at
> scala_maven_executions.MainWithArgsInFile.main(MainWithArgsInFile.java:26)
> [INFO]
> [INFO] java.lang.reflect.InvocationTargetException
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [INFO]at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [INFO]at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> [INFO]at
> scala_maven_executions.MainHelper.runMain(MainHelper.java:164)
> [INFO]at
> scala_maven_executions.MainWithArgsInFile.main(MainWithArgsInFile.java:26)
> [ERROR] Caused by: java.lang.NoClassDefFo
[jira] [Updated] (IGNITE-8461) Scala-2.10 modules compilation failure under JDK 9
[
https://issues.apache.org/jira/browse/IGNITE-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8461:
Priority: Critical (was: Blocker)
> Scala-2.10 modules compilation failure under JDK 9
> --
>
> Key: IGNITE-8461
> URL: https://issues.apache.org/jira/browse/IGNITE-8461
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Peter Ivanov
>Priority: Critical
> Fix For: 2.6
>
>
> {code}
> [ERROR] error: java.lang.NoClassDefFoundError: javax/tools/ToolProvider
> [INFO]at
> scala.reflect.io.JavaToolsPlatformArchive.iterator(ZipArchive.scala:242)
> [INFO]at
> scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
> [INFO]at scala.reflect.io.AbstractFile.foreach(AbstractFile.scala:92)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.traverse(ClassPath.scala:308)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.x$16$lzycompute(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.x$16(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.packages$lzycompute(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.packages(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.packages(ClassPath.scala:297)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath$$anonfun$packages$1.apply(ClassPath.scala:375)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath$$anonfun$packages$1.apply(ClassPath.scala:375)
> [INFO]at scala.collection.Iterator$class.foreach(Iterator.scala:727)
> [INFO]at
> scala.collection.AbstractIterator.foreach(Iterator.scala:1157)
> [INFO]at
> scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
> [INFO]at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath.packages$lzycompute(ClassPath.scala:375)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath.packages(ClassPath.scala:370)
> [INFO]at
> scala.tools.nsc.symtab.SymbolLoaders$PackageLoader.doComplete(SymbolLoaders.scala:243)
> [INFO]at
> scala.tools.nsc.symtab.SymbolLoaders$SymbolLoader.complete(SymbolLoaders.scala:194)
> [INFO]at
> scala.reflect.internal.Symbols$Symbol.info(Symbols.scala:1231)
> [INFO]at
> scala.reflect.internal.Mirrors$RootsBase.init(Mirrors.scala:240)
> [INFO]at scala.tools.nsc.Global.rootMirror$lzycompute(Global.scala:59)
> [INFO]at scala.tools.nsc.Global.rootMirror(Global.scala:57)
> [INFO]at scala.tools.nsc.Global.rootMirror(Global.scala:37)
> [INFO]at
> scala.reflect.internal.Definitions$DefinitionsClass.(Definitions.scala:166)
> [INFO]at
> scala.reflect.internal.Definitions$definitions$.(Definitions.scala:20)
> [INFO]at
> scala.reflect.internal.SymbolTable.definitions$lzycompute(SymbolTable.scala:13)
> [INFO]at
> scala.reflect.internal.SymbolTable.definitions(SymbolTable.scala:13)
> [INFO]at scala.tools.nsc.Global$Run.(Global.scala:1290)
> [INFO]at scala.tools.nsc.Driver.doCompile(Driver.scala:32)
> [INFO]at scala.tools.nsc.Main$.doCompile(Main.scala:79)
> [INFO]at scala.tools.nsc.Driver.process(Driver.scala:54)
> [INFO]at scala.tools.nsc.Driver.main(Driver.scala:67)
> [INFO]at scala.tools.nsc.Main.main(Main.scala)
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [INFO]at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [INFO]at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> [INFO]at
> scala_maven_executions.MainHelper.runMain(MainHelper.java:164)
> [INFO]at
> scala_maven_executions.MainWithArgsInFile.main(MainWithArgsInFile.java:26)
> [INFO]
> [INFO] java.lang.reflect.InvocationTargetException
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [INFO]at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [INFO]at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> [INFO]at
> scala_maven_executions.MainHelper.runMain(MainHelper.java:164)
> [INFO]at
> scala_maven_executions.MainWithArgsInFile.main(MainWithArgsInFile.java:26)
> [ERROR] Caused by: java.lang.NoClassDefFoundError: javax/to
[jira] [Commented] (IGNITE-7535) SQL COPY command: implement encoding option
[
https://issues.apache.org/jira/browse/IGNITE-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470719#comment-16470719
]
Dmitriy Pavlov commented on IGNITE-7535:
Classnames properties generation fix for master
619d6c575a267ac8585a76fc82889d5073bfb861
for ignite 2.5 46dac58cdd1ee7e57fc165333e84452dc414cbf3
> SQL COPY command: implement encoding option
> ---
>
> Key: IGNITE-7535
> URL: https://issues.apache.org/jira/browse/IGNITE-7535
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.5
>Reporter: Kirill Shirokov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: sql
> Fix For: 2.5
>
>
> The syntax can be something like:
> {noformat}
> COPY
> ...
> FORMAT CSV
> ...
> [CHARSET ""]
> {noformat}
> CHARSET is optional. By default the encoding is UTF-8.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8266) Remove afterTestsStopped method due to stopAllGrids by default
[
https://issues.apache.org/jira/browse/IGNITE-8266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470691#comment-16470691
]
Dmitriy Pavlov commented on IGNITE-8266:
[~NIzhikov], according to my feeling of "Apache way", we should come to an
agreement here and only then apply the patch.
I suggest to move deletion of super.afterTestsStopped() out of scope by 2
reasons..
# First of all after applying patch without such removal less test will start
to fail. Clean up after test may cause flaky failures, so I prefer to move by
smaller steps. It will be easier to identify failure reason.
# afterTestsStopped() may now contain no-op code, but some time later, base
class may be changed, so new base class will require additional cleanup. E.g.
non persistence Ignite test can be transformed to persistence enabled, so call
to super would become reasonable. Same for system options setupa and cleanup.
System option which was forgotten to be reset can cause a number of
non-intuitive flaky failures.
I, of course , can proceed with review, but would like to enlist your support
in final solution.
> Remove afterTestsStopped method due to stopAllGrids by default
> --
>
> Key: IGNITE-8266
> URL: https://issues.apache.org/jira/browse/IGNITE-8266
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.5
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Minor
> Labels: test
> Fix For: 2.6
>
>
> Remove this types of method from test in whole ignite-core module.
> {code:java}
> @Override protected void afterTestsStopped() throws Exception {
> super.afterTestsStopped();
> stopAllGrids();
> }{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7896) Files of evicted partitions are not removed from disk storage
[ https://issues.apache.org/jira/browse/IGNITE-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470624#comment-16470624 ] Ivan Daschinskiy commented on IGNITE-7896: -- [New TC run|https://ci.ignite.apache.org/viewLog.html?buildId=1280055&buildTypeId=IgniteTests24Java8_RunAll&tab=buildResultsDiv] > Files of evicted partitions are not removed from disk storage > - > > Key: IGNITE-7896 > URL: https://issues.apache.org/jira/browse/IGNITE-7896 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.6 > > Attachments: IgnitePdsRebalanceCompletionAndPartitionFilesTest.java > > > Look at test reproduction: > [^IgnitePdsRebalanceCompletionAndPartitionFilesTest.java] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8468) Adding and searching UUIDs in index tree produces a lot of garbage
[ https://issues.apache.org/jira/browse/IGNITE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470619#comment-16470619 ] Andrew Mashenkov commented on IGNITE-8468: -- [~gvvinblade] Would you please take a look at the patch attached? > Adding and searching UUIDs in index tree produces a lot of garbage > -- > > Key: IGNITE-8468 > URL: https://issues.apache.org/jira/browse/IGNITE-8468 > Project: Ignite > Issue Type: Improvement >Reporter: Andrew Mashenkov >Priority: Major > Attachments: Optimization_for_UUID_fields.patch > > > Seems, optimization for UUIDs was missed in IGNITE-5918. > PFA patch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8468) Adding and searching UUIDs in index tree produces a lot of garbage
[ https://issues.apache.org/jira/browse/IGNITE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-8468: - Issue Type: Improvement (was: Test) > Adding and searching UUIDs in index tree produces a lot of garbage > -- > > Key: IGNITE-8468 > URL: https://issues.apache.org/jira/browse/IGNITE-8468 > Project: Ignite > Issue Type: Improvement >Reporter: Andrew Mashenkov >Priority: Major > Attachments: Optimization_for_UUID_fields.patch > > > Seems, optimization for UUIDs was missed in IGNITE-5918. > PFA patch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8468) Adding and searching UUIDs in index tree produces a lot of garbage
Andrew Mashenkov created IGNITE-8468: Summary: Adding and searching UUIDs in index tree produces a lot of garbage Key: IGNITE-8468 URL: https://issues.apache.org/jira/browse/IGNITE-8468 Project: Ignite Issue Type: Test Reporter: Andrew Mashenkov Attachments: Optimization_for_UUID_fields.patch Seems, optimization for UUIDs was missed in IGNITE-5918. PFA patch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8456) Print warning if IGNITE_HOME & WORK and persistentStoreDir is not set, but persistence enabled
[ https://issues.apache.org/jira/browse/IGNITE-8456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470602#comment-16470602 ] ASF GitHub Bot commented on IGNITE-8456: GitHub user SomeFire opened a pull request: https://github.com/apache/ignite/pull/3976 IGNITE-8456: Print warning if IGNITE_HOME & WORK and persistentStoreD… …ir is not set, but persistence enabled You can merge this pull request into a Git repository by running: $ git pull https://github.com/SomeFire/ignite ignite-8456 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3976.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 #3976 commit 3661276e60b7f5f05c186c7992e172512aa86669 Author: Dmitrii Ryabov Date: 2018-05-10T15:51:12Z IGNITE-8456: Print warning if IGNITE_HOME & WORK and persistentStoreDir is not set, but persistence enabled > Print warning if IGNITE_HOME & WORK and persistentStoreDir is not set, but > persistence enabled > -- > > Key: IGNITE-8456 > URL: https://issues.apache.org/jira/browse/IGNITE-8456 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Dmitriy Pavlov >Assignee: Ryabov Dmitrii >Priority: Critical > Labels: easyfix, newbie > Fix For: 2.6 > > > In method org.apache.ignite.internal.util.IgniteUtils#workDirectory > Ignite determine Work dir to be set, same value may be used in case > persistence Store Folder is not set and IGNITE_HOME is not specified. > In case work dir is not specified, temp directory is used for Ignite Work. > But for persistence enabled case this means user DB goes to temp folder and > may be removed later. > User may be confused by this behaviour. See: > [https://stackoverflow.com/questions/48434929/apache-ignite-persistent-storage] > and related Dev.List discussion > [http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-HOME-for-persistence-td26470.html] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8138) Incorrect uptime in Ignite metrics for long running server node (1+ days)
[
https://issues.apache.org/jira/browse/IGNITE-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470596#comment-16470596
]
Sergey Skudnov commented on IGNITE-8138:
Totally agree with that.
Thanx.
> Incorrect uptime in Ignite metrics for long running server node (1+ days)
> -
>
> Key: IGNITE-8138
> URL: https://issues.apache.org/jira/browse/IGNITE-8138
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.1, 2.4
>Reporter: Max Shonichev
>Assignee: Sergey Skudnov
>Priority: Major
> Fix For: 2.6
>
> Attachments: Screenshot from 2018-04-08 23-37-39.png, Screenshot from
> 2018-04-16 09-33-24.png
>
>
> Ignite prints a metrics to the log with uptime, formatted as 'XX:YY:ZZ:TTT'.
> It looks, like XX corresponds to hours, YY to minutes, ZZ to seconds, however
> if we filter uptime metric from a long running server (few days), we would
> see that :
> {noformat}
> ^-- Node [id=684d2761, name=null, uptime=00:01:00:009]
> ^-- Node [id=684d2761, name=null, uptime=00:02:00:009]
> ^-- Node [id=684d2761, name=null, uptime=00:03:00:009]
> ^-- Node [id=684d2761, name=null, uptime=00:04:00:021]
> ...
> ^-- Node [id=684d2761, name=null, uptime=23:58:08:391]
> ^-- Node [id=684d2761, name=null, uptime=23:59:08:393]
> ^-- Node [id=684d2761, name=null, uptime=24:00:08:395]
> ^-- Node [id=684d2761, name=null, uptime=24:01:08:406]
> ...
> ^-- Node [id=684d2761, name=null, uptime=59:59:23:542]
> ^-- Node [id=684d2761, name=null, uptime=00:00:23:554]
> ...
> {noformat}
> BUG:
> 1. hours do not rollover at 23:59:59
> 2. there's no simple means for user to get uptime days, because hours do
> actually rollover after 59:59:59
> what is expected:
> 1. add a day counter, init with 0
> 2. make hours correctly rollover after full day (24hrs) run
> {noformat}
> ^-- Node [id=684d2761, name=null, uptime=0:00:01:00:009]
> ...
> ^-- Node [id=684d2761, name=null, uptime=0:23:59:00:009]
> ^-- Node [id=684d2761, name=null, uptime=1:00:00:00:009]
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7535) SQL COPY command: implement encoding option
[
https://issues.apache.org/jira/browse/IGNITE-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470532#comment-16470532
]
ASF GitHub Bot commented on IGNITE-7535:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3487
> SQL COPY command: implement encoding option
> ---
>
> Key: IGNITE-7535
> URL: https://issues.apache.org/jira/browse/IGNITE-7535
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.5
>Reporter: Kirill Shirokov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: sql
> Fix For: 2.5
>
>
> The syntax can be something like:
> {noformat}
> COPY
> ...
> FORMAT CSV
> ...
> [CHARSET ""]
> {noformat}
> CHARSET is optional. By default the encoding is UTF-8.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5945) Flaky failure in IgniteCache 5: IgniteCacheAtomicProtocolTest.testPutReaderUpdate2
[
https://issues.apache.org/jira/browse/IGNITE-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470527#comment-16470527
]
Alexander Menshikov commented on IGNITE-5945:
-
The test works fine when I added blocking of *GridDhtAtomicNearResponse*
message from the other server (400+ passes).
But it's unclear why that work. I mean cache is FULL_SYNC so have to wait for
responses from all nodes. I keep investigating the problem and will write about
any result.
> Flaky failure in IgniteCache 5:
> IgniteCacheAtomicProtocolTest.testPutReaderUpdate2
> --
>
> Key: IGNITE-5945
> URL: https://issues.apache.org/jira/browse/IGNITE-5945
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Alexander Menshikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.IgniteCacheAtomicProtocolTest#testPutReaderUpdate2
> {noformat}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertFalse(Assert.java:39)
> at junit.framework.Assert.assertFalse(Assert.java:47)
> at junit.framework.TestCase.assertFalse(TestCase.java:219)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.IgniteCacheAtomicProtocolTest.readerUpdateDhtFails(IgniteCacheAtomicProtocolTest.java:865)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.IgniteCacheAtomicProtocolTest.testPutReaderUpdate2(IgniteCacheAtomicProtocolTest.java:765)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Fail is reproducable locally 2 times per 20 runs
> On TeamCity test success rate is 88,2%
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8354) Ignite Continuosly refreshes Cassandra Session when there is an Exception in execute method of CassandraSessionImpl
[ https://issues.apache.org/jira/browse/IGNITE-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470520#comment-16470520 ] Alexey Kuznetsov edited comment on IGNITE-8354 at 5/10/18 3:08 PM: --- [~irudyak] I reviewed PR on github. Only minor issues found from my side. Other than that - looks good for me. was (Author: kuaw26): [~irudyak] I reviewed PR. Only minor issues found from my side. Other than that - looks good for me. > Ignite Continuosly refreshes Cassandra Session when there is an Exception in > execute method of CassandraSessionImpl > > > Key: IGNITE-8354 > URL: https://issues.apache.org/jira/browse/IGNITE-8354 > Project: Ignite > Issue Type: Bug > Components: cassandra >Reporter: Yashasvi Kotamraju >Assignee: Igor Rudyak >Priority: Major > > *In CassandraSessionImpl.java* > When handlePreparedStatementClusterError method is called during Exception, > the session is refreshed.There might be many preparedstatements created with > old session(since a session object can be shared between different batches). > So when we execute the preparedstatements created with old session on a new > session created , we get the the Exception > "com.datastax.driver.core.exceptions.InvalidQueryException You may have used > a PreparedStatement that was created with another Cluster instance". Which > would again call handlePreparedStatementClusterError and refresh session > again and this happens continuously. We have observed continuous cassandra > session refresh warnings when this scenario occurred. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8354) Ignite Continuosly refreshes Cassandra Session when there is an Exception in execute method of CassandraSessionImpl
[ https://issues.apache.org/jira/browse/IGNITE-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470520#comment-16470520 ] Alexey Kuznetsov commented on IGNITE-8354: -- [~irudyak] I reviewed PR. Only minor issues found from my side. Other than that - looks good for me. > Ignite Continuosly refreshes Cassandra Session when there is an Exception in > execute method of CassandraSessionImpl > > > Key: IGNITE-8354 > URL: https://issues.apache.org/jira/browse/IGNITE-8354 > Project: Ignite > Issue Type: Bug > Components: cassandra >Reporter: Yashasvi Kotamraju >Assignee: Igor Rudyak >Priority: Major > > *In CassandraSessionImpl.java* > When handlePreparedStatementClusterError method is called during Exception, > the session is refreshed.There might be many preparedstatements created with > old session(since a session object can be shared between different batches). > So when we execute the preparedstatements created with old session on a new > session created , we get the the Exception > "com.datastax.driver.core.exceptions.InvalidQueryException You may have used > a PreparedStatement that was created with another Cluster instance". Which > would again call handlePreparedStatementClusterError and refresh session > again and this happens continuously. We have observed continuous cassandra > session refresh warnings when this scenario occurred. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8039) Binary Client Protocol spec: data types/format clarifications
[
https://issues.apache.org/jira/browse/IGNITE-8039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470519#comment-16470519
]
Igor Sapego commented on IGNITE-8039:
-
[~alexey.kosenchuk], well, because version 2.5 of the doc is not yet created.
> Binary Client Protocol spec: data types/format clarifications
> -
>
> Key: IGNITE-8039
> URL: https://issues.apache.org/jira/browse/IGNITE-8039
> Project: Ignite
> Issue Type: Bug
> Components: documentation, thin client
>Affects Versions: 2.4
>Reporter: Alexey Kosenchuk
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.5
>
>
> Assuming the Binary Client Protocol spec should be detalized enough to allow
> a client development basing on the spec only, w/o looking at other client
> implementations and asking additional questions...
> The following should be clarified / corrected in the Binary Client Protocol
> spec (v.2.4)
> (https://apacheignite.readme.io/v2.4/docs/binary-client-protocol#section-data-format):
> Type Codes table:
> -
> - UUID (Guid) size: should be 16 bytes, not 8 (?)
> - what is Object array (type code 23) ? What is the difference between it and
> Objects Wrapped In Array (type code 27) ?
> - what is Collection USER_SET ?
> - what is Collection USER_COL ?
> - what is Collection SINGLETON_LIST ?
> - Collection: misprint: should be "... + length ..."
> - what is Decimal ?
> - what is Timestamp ?
> - what is Time ?
> Complex Objects:
>
> - what does flag USER_TYPE mean ?
> - Schema "field Id; Java-style hash code of field" -> should be "... of field
> name".
> - "Repeat for as many times as the total number of schemas you have" ->
> should be "... total number of fields you have".
> - is it mandated that the number of fields in the Schema must be equal to the
> number of fields in the Data Object ?
> Objects Wrapped In Array
>
> - may binary objects with different type codes be in the same array ?
> - may complex objects with different type ids be in the same array ?
> - "All cache operations return complex objects inside a wrapper (but not
> primitives)." -> does it mean that in general a complex object (103) must
> always be sent via the Binary Protocol in a wrapper (27)?
> - "Byte array size" -> "Payload size" or "Size of the whole array with
> header" ?
> - Offset. What is "object graph" here ? The Binary Protocol nowhere describes
> any relations ("graph") between data objects in the protocol.
> Terminology
> ---
> Not critical but would be really convenient to define and use the same terms
> along the whole spec. For example:
> - "binary object" is always the same as "data object" of any type (?). Can be
> "standard/predefined type object" or "complex object".
> - "cluster" or "server" ?
> - "cluster member" or "server nodes" ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8467) minSize filter for transactions utility control.sh doesn't work
[
https://issues.apache.org/jira/browse/IGNITE-8467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov reassigned IGNITE-8467:
-
Assignee: Alexei Scherbakov
> minSize filter for transactions utility control.sh doesn't work
> ---
>
> Key: IGNITE-8467
> URL: https://issues.apache.org/jira/browse/IGNITE-8467
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Dmitry Sherstobitov
>Assignee: Alexei Scherbakov
>Priority: Minor
>
> I have following output when define control.sh utility with minSize filter
> Looks like it doesn't work.
> {code:java}
> Control utility --tx minDuration 15 minSize 10 order SIZE
> Control utility
> 2018 Copyright(C) Apache Software Foundation
> User:
>
> Matching transactions:
> [16:52:30][:688] TcpDiscoveryNode [id=02f47e9a-efca-4d8c-a49f-3de4ca82d3ee,
> addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.17.0.1, 172.25.1.40],
> sockAddrs=[/172.17.0.1:0, /0:0:0:0:0:0:0:1%lo:0,
> lab40.gridgain.local/172.25.1.40:0, /127.0.0.1:0], discPort=0, order=5,
> intOrder=5, lastExchangeTime=1525960350163, loc=false,
> ver=2.5.1#20180427-sha1:48601cbd, isClient=true]
> Tx: [xid=0f1d25a4361--0831-2c15--0005, label=tx_5,
> state=ACTIVE, duration=16, isolation=REPEATABLE_READ,
> concurrency=PESSIMISTIC, timeout=0, size=1, dhtNodes=[63e05a51]]
> Tx: [xid=05ad25a4361--0831-2c15--0005, label=tx_6,
> state=ACTIVE, duration=15, isolation=REPEATABLE_READ,
> concurrency=PESSIMISTIC, timeout=0, size=1, dhtNodes=[473df74e]]
> Tx: [xid=7b2b25a4361--0831-2c15--0005, label=tx_1,
> state=ACTIVE, duration=20, isolation=REPEATABLE_READ,
> concurrency=PESSIMISTIC, timeout=0, size=1, dhtNodes=[63e05a51]]
> Tx: [xid=73ab25a4361--0831-2c15--0005, label=tx_2,
> state=ACTIVE, duration=19, isolation=REPEATABLE_READ,
> concurrency=PESSIMISTIC, timeout=0, size=1, dhtNodes=[473df74e]]
> Tx: [xid=47ca25a4361--0831-2c15--0005, label=tx_0,
> state=ACTIVE, duration=22, isolation=REPEATABLE_READ,
> concurrency=PESSIMISTIC, timeout=0, size=1, dhtNodes=[63e05a51]]
> Tx: [xid=b0ac25a4361--0831-2c15--0005, label=tx_4,
> state=ACTIVE, duration=17, isolation=REPEATABLE_READ,
> concurrency=PESSIMISTIC, timeout=0, size=1, dhtNodes=[473df74e]]
> Tx: [xid=3a1c25a4361--0831-2c15--0005, label=tx_3,
> state=ACTIVE, duration=18, isolation=REPEATABLE_READ,
> concurrency=PESSIMISTIC, timeout=0, size=1, dhtNodes=[0cd15184]]{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8039) Binary Client Protocol spec: data types/format clarifications
[
https://issues.apache.org/jira/browse/IGNITE-8039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470488#comment-16470488
]
Alexey Kosenchuk commented on IGNITE-8039:
--
why v.2.4 is being updated? I believe, all fixes should go to 2.5 (?)
> Binary Client Protocol spec: data types/format clarifications
> -
>
> Key: IGNITE-8039
> URL: https://issues.apache.org/jira/browse/IGNITE-8039
> Project: Ignite
> Issue Type: Bug
> Components: documentation, thin client
>Affects Versions: 2.4
>Reporter: Alexey Kosenchuk
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.5
>
>
> Assuming the Binary Client Protocol spec should be detalized enough to allow
> a client development basing on the spec only, w/o looking at other client
> implementations and asking additional questions...
> The following should be clarified / corrected in the Binary Client Protocol
> spec (v.2.4)
> (https://apacheignite.readme.io/v2.4/docs/binary-client-protocol#section-data-format):
> Type Codes table:
> -
> - UUID (Guid) size: should be 16 bytes, not 8 (?)
> - what is Object array (type code 23) ? What is the difference between it and
> Objects Wrapped In Array (type code 27) ?
> - what is Collection USER_SET ?
> - what is Collection USER_COL ?
> - what is Collection SINGLETON_LIST ?
> - Collection: misprint: should be "... + length ..."
> - what is Decimal ?
> - what is Timestamp ?
> - what is Time ?
> Complex Objects:
>
> - what does flag USER_TYPE mean ?
> - Schema "field Id; Java-style hash code of field" -> should be "... of field
> name".
> - "Repeat for as many times as the total number of schemas you have" ->
> should be "... total number of fields you have".
> - is it mandated that the number of fields in the Schema must be equal to the
> number of fields in the Data Object ?
> Objects Wrapped In Array
>
> - may binary objects with different type codes be in the same array ?
> - may complex objects with different type ids be in the same array ?
> - "All cache operations return complex objects inside a wrapper (but not
> primitives)." -> does it mean that in general a complex object (103) must
> always be sent via the Binary Protocol in a wrapper (27)?
> - "Byte array size" -> "Payload size" or "Size of the whole array with
> header" ?
> - Offset. What is "object graph" here ? The Binary Protocol nowhere describes
> any relations ("graph") between data objects in the protocol.
> Terminology
> ---
> Not critical but would be really convenient to define and use the same terms
> along the whole spec. For example:
> - "binary object" is always the same as "data object" of any type (?). Can be
> "standard/predefined type object" or "complex object".
> - "cluster" or "server" ?
> - "cluster member" or "server nodes" ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-7564) Document IgniteSet memory consumption
[ https://issues.apache.org/jira/browse/IGNITE-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-7564. -- Resolution: Duplicate Closing as duplicate (see. IGNITE-7823) > Document IgniteSet memory consumption > - > > Key: IGNITE-7564 > URL: https://issues.apache.org/jira/browse/IGNITE-7564 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 2.2 >Reporter: Alexander Belyak >Assignee: Denis Magda >Priority: Minor > > We need to document onheap memory consumption of IgniteSet collections (all > values stored in durable memory AND in java heap). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7565) Remove IgniteSet from heap
[ https://issues.apache.org/jira/browse/IGNITE-7565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-7565. -- Resolution: Duplicate Closing as duplicate (see. IGNITE-7823) > Remove IgniteSet from heap > -- > > Key: IGNITE-7565 > URL: https://issues.apache.org/jira/browse/IGNITE-7565 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.2 >Reporter: Alexander Belyak >Assignee: Pavel Pereslegin >Priority: Major > > IgniteSet store all data in durable memory and in java heap. It's not good > for big clusters and big sets, so we need to remove values from heap. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8467) minSize filter for transactions utility control.sh doesn't work
[
https://issues.apache.org/jira/browse/IGNITE-8467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Sherstobitov updated IGNITE-8467:
Priority: Minor (was: Major)
> minSize filter for transactions utility control.sh doesn't work
> ---
>
> Key: IGNITE-8467
> URL: https://issues.apache.org/jira/browse/IGNITE-8467
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Dmitry Sherstobitov
>Priority: Minor
>
> I have following output when define control.sh utility with minSize filter
> Looks like it doesn't work.
> {code:java}
> Control utility --tx minDuration 15 minSize 10 order SIZE
> Control utility
> 2018 Copyright(C) Apache Software Foundation
> User:
>
> Matching transactions:
> [16:52:30][:688] TcpDiscoveryNode [id=02f47e9a-efca-4d8c-a49f-3de4ca82d3ee,
> addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.17.0.1, 172.25.1.40],
> sockAddrs=[/172.17.0.1:0, /0:0:0:0:0:0:0:1%lo:0,
> lab40.gridgain.local/172.25.1.40:0, /127.0.0.1:0], discPort=0, order=5,
> intOrder=5, lastExchangeTime=1525960350163, loc=false,
> ver=2.5.1#20180427-sha1:48601cbd, isClient=true]
> Tx: [xid=0f1d25a4361--0831-2c15--0005, label=tx_5,
> state=ACTIVE, duration=16, isolation=REPEATABLE_READ,
> concurrency=PESSIMISTIC, timeout=0, size=1, dhtNodes=[63e05a51]]
> Tx: [xid=05ad25a4361--0831-2c15--0005, label=tx_6,
> state=ACTIVE, duration=15, isolation=REPEATABLE_READ,
> concurrency=PESSIMISTIC, timeout=0, size=1, dhtNodes=[473df74e]]
> Tx: [xid=7b2b25a4361--0831-2c15--0005, label=tx_1,
> state=ACTIVE, duration=20, isolation=REPEATABLE_READ,
> concurrency=PESSIMISTIC, timeout=0, size=1, dhtNodes=[63e05a51]]
> Tx: [xid=73ab25a4361--0831-2c15--0005, label=tx_2,
> state=ACTIVE, duration=19, isolation=REPEATABLE_READ,
> concurrency=PESSIMISTIC, timeout=0, size=1, dhtNodes=[473df74e]]
> Tx: [xid=47ca25a4361--0831-2c15--0005, label=tx_0,
> state=ACTIVE, duration=22, isolation=REPEATABLE_READ,
> concurrency=PESSIMISTIC, timeout=0, size=1, dhtNodes=[63e05a51]]
> Tx: [xid=b0ac25a4361--0831-2c15--0005, label=tx_4,
> state=ACTIVE, duration=17, isolation=REPEATABLE_READ,
> concurrency=PESSIMISTIC, timeout=0, size=1, dhtNodes=[473df74e]]
> Tx: [xid=3a1c25a4361--0831-2c15--0005, label=tx_3,
> state=ACTIVE, duration=18, isolation=REPEATABLE_READ,
> concurrency=PESSIMISTIC, timeout=0, size=1, dhtNodes=[0cd15184]]{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8422) Zookeeper discovery split brain detection shouldn't consider client nodes
[ https://issues.apache.org/jira/browse/IGNITE-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470474#comment-16470474 ] ASF GitHub Bot commented on IGNITE-8422: GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3975 IGNITE-8422 Improve tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8422 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3975.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 #3975 commit e3c92229a67e929e98f70f7c7e2b163da1f66823 Author: Pavel Kovalenko Date: 2018-04-28T17:38:54Z IGNITE-8442 WIP commit e49fdde215171c4edbcbada497d23aadae4d5d88 Author: Pavel Kovalenko Date: 2018-05-03T17:43:28Z IGNITE-8442 WIP commit 7a19bd0486fe3a615264039068c3b95b202e5299 Author: Pavel Kovalenko Date: 2018-05-04T14:34:49Z IGNITE-8442 WIP commit f7dd585d2497333d0607ce6b5a469fa0e5026932 Author: Pavel Kovalenko Date: 2018-05-04T17:39:22Z IGNITE-8442 WIP commit e3fe0355ca00ad341ac075c1ad459667bf68b905 Author: Pavel Kovalenko Date: 2018-05-07T13:19:32Z IGNITE-8442 WIP commit 71385486cbb0eda24ddea24921aecfdc19d228e7 Author: Pavel Kovalenko Date: 2018-05-07T13:23:02Z IGNITE-8422 Remove unused class. commit 7351a75f725647639334d5de3374894a9fd9513a Author: Pavel Kovalenko Date: 2018-05-08T16:09:36Z IGNITE-8422 Code style fixes. commit 50c222d856cc6ece6fc91c0ec4dd55fdc8da799a Author: Pavel Kovalenko Date: 2018-05-08T16:11:11Z IGNITE-8422 Remove empty line. commit dc61d69afa3e1e9f74c9cffb0b2203f55d5ae601 Author: Pavel Kovalenko Date: 2018-05-08T16:16:02Z IGNITE-8422 Minor docs fix. commit bb642f465279ba677d1b136f24ee07927b1dfcfc Author: Pavel Kovalenko Date: 2018-05-08T16:48:10Z Merge branch 'master' into ignite-8422 commit ec9977065f7cbf2d58a9aee3a1301caef67c1223 Author: Pavel Kovalenko Date: 2018-05-08T17:40:31Z IGNITE-8422 Create TCP client properly. commit d29d17bb79ee30894a2d035cea3ff6c477bcc913 Author: Pavel Kovalenko Date: 2018-05-08T18:41:52Z IGNITE-8422 Create TCP client properly. commit 4b9e0588efc7803070550e73e64c99b5820430fa Author: Pavel Kovalenko Date: 2018-05-10T09:07:18Z IGNITE-8422 Fixed split brain tests. commit 057bff9b5eddbf82cd0cf7c791a4680552ba5942 Author: Pavel Kovalenko Date: 2018-05-10T09:08:47Z IGNITE-8422 Fixed split brain tests. commit 968ae352d49205459ab7ed5e474b30414d1695b7 Author: Pavel Kovalenko Date: 2018-05-10T11:57:18Z IGNITE-8422 Fixed split brain tests. commit c288e4deb596da50f716028afb5ccf70268b34f7 Author: Pavel Kovalenko Date: 2018-05-10T14:39:39Z IGNITE-8422 Fixed split brain tests. > Zookeeper discovery split brain detection shouldn't consider client nodes > - > > Key: IGNITE-8422 > URL: https://issues.apache.org/jira/browse/IGNITE-8422 > Project: Ignite > Issue Type: Bug > Components: zookeeper >Affects Versions: 2.5 >Reporter: Pavel Kovalenko >Assignee: Pavel Kovalenko >Priority: Major > Fix For: 2.6 > > > Currently Zookeeper discovery checks each splitted cluster on full > connectivity taking into account client nodes. This is not correct, because > server and client nodes may use different networks to connect to each other. > It means that there can be client which sees both parts of splitted cluster > and breaks split brain recovery - full connected part of server nodes will be > never find. > We should exclude client nodes from split brain analysis and improve split > brain tests to make them truly fair. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8467) minSize filter for transactions utility control.sh doesn't work
Dmitry Sherstobitov created IGNITE-8467:
---
Summary: minSize filter for transactions utility control.sh
doesn't work
Key: IGNITE-8467
URL: https://issues.apache.org/jira/browse/IGNITE-8467
Project: Ignite
Issue Type: Bug
Affects Versions: 2.5
Reporter: Dmitry Sherstobitov
I have following output when define control.sh utility with minSize filter
Looks like it doesn't work.
{code:java}
Control utility --tx minDuration 15 minSize 10 order SIZE
Control utility
2018 Copyright(C) Apache Software Foundation
User:
Matching transactions:
[16:52:30][:688] TcpDiscoveryNode [id=02f47e9a-efca-4d8c-a49f-3de4ca82d3ee,
addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.17.0.1, 172.25.1.40],
sockAddrs=[/172.17.0.1:0, /0:0:0:0:0:0:0:1%lo:0,
lab40.gridgain.local/172.25.1.40:0, /127.0.0.1:0], discPort=0, order=5,
intOrder=5, lastExchangeTime=1525960350163, loc=false,
ver=2.5.1#20180427-sha1:48601cbd, isClient=true]
Tx: [xid=0f1d25a4361--0831-2c15--0005, label=tx_5,
state=ACTIVE, duration=16, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
timeout=0, size=1, dhtNodes=[63e05a51]]
Tx: [xid=05ad25a4361--0831-2c15--0005, label=tx_6,
state=ACTIVE, duration=15, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
timeout=0, size=1, dhtNodes=[473df74e]]
Tx: [xid=7b2b25a4361--0831-2c15--0005, label=tx_1,
state=ACTIVE, duration=20, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
timeout=0, size=1, dhtNodes=[63e05a51]]
Tx: [xid=73ab25a4361--0831-2c15--0005, label=tx_2,
state=ACTIVE, duration=19, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
timeout=0, size=1, dhtNodes=[473df74e]]
Tx: [xid=47ca25a4361--0831-2c15--0005, label=tx_0,
state=ACTIVE, duration=22, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
timeout=0, size=1, dhtNodes=[63e05a51]]
Tx: [xid=b0ac25a4361--0831-2c15--0005, label=tx_4,
state=ACTIVE, duration=17, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
timeout=0, size=1, dhtNodes=[473df74e]]
Tx: [xid=3a1c25a4361--0831-2c15--0005, label=tx_3,
state=ACTIVE, duration=18, isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
timeout=0, size=1, dhtNodes=[0cd15184]]{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7968) IgniteAtomicSequence.incrementAndGet throws ClusterTopologyException: Failed to acquire lock for keys
[ https://issues.apache.org/jira/browse/IGNITE-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470467#comment-16470467 ] ASF GitHub Bot commented on IGNITE-7968: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3868 > IgniteAtomicSequence.incrementAndGet throws ClusterTopologyException: Failed > to acquire lock for keys > - > > Key: IGNITE-7968 > URL: https://issues.apache.org/jira/browse/IGNITE-7968 > Project: Ignite > Issue Type: Bug > Components: data structures >Affects Versions: 2.3, 2.4 >Reporter: Pavel Vinokurov >Assignee: Pavel Vinokurov >Priority: Major > Fix For: 2.6 > > Attachments: AtomicSeqAndClusterTopologyReproducer.java > > > When a primary node for a atomic sequnce has left cluster, > IgniteAtomicSequence.incrementAndGet could throw ClusterTopologyException. > The reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8039) Binary Client Protocol spec: data types/format clarifications
[
https://issues.apache.org/jira/browse/IGNITE-8039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470437#comment-16470437
]
Igor Sapego edited comment on IGNITE-8039 at 5/10/18 2:24 PM:
--
[~dmagda], [~pgarg], [~alexey.kosenchuk], guys,
I've added short {{Binary Enum}} type description, {{Complex Object}}
description and moved {{Wrapped Data}} description to the type description
page. Also, I've renamed the page from "Standard Types" => "Data Format".
So, I'm putting this ticket on review and going to make other changes in other
tickets. Please, take a look and tell me what do you think.
The page URL: [https://apacheignite.readme.io/v2.4/docs/data-format]
Updated Binary Client Protocol page URL:
https://apacheignite.readme.io/v2.4/docs/binary-client-protocol-edited
was (Author: isapego):
[~dmagda], [~pgarg], [~alexey.kosenchuk], guys,
I've added short \{{Binary Enum}} type description, \{{Complex Object}}
description and moved \{{Wrapped Data}} description to the type description
page. Also, I've renamed the page from "Standard Types" => "Data Format".
So, I'm putting this ticket on review and going to make other changes in other
tickets. Please, take a look and tell me what do you think.
The page URL: [https://apacheignite.readme.io/v2.4/docs/data-format]
> Binary Client Protocol spec: data types/format clarifications
> -
>
> Key: IGNITE-8039
> URL: https://issues.apache.org/jira/browse/IGNITE-8039
> Project: Ignite
> Issue Type: Bug
> Components: documentation, thin client
>Affects Versions: 2.4
>Reporter: Alexey Kosenchuk
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.5
>
>
> Assuming the Binary Client Protocol spec should be detalized enough to allow
> a client development basing on the spec only, w/o looking at other client
> implementations and asking additional questions...
> The following should be clarified / corrected in the Binary Client Protocol
> spec (v.2.4)
> (https://apacheignite.readme.io/v2.4/docs/binary-client-protocol#section-data-format):
> Type Codes table:
> -
> - UUID (Guid) size: should be 16 bytes, not 8 (?)
> - what is Object array (type code 23) ? What is the difference between it and
> Objects Wrapped In Array (type code 27) ?
> - what is Collection USER_SET ?
> - what is Collection USER_COL ?
> - what is Collection SINGLETON_LIST ?
> - Collection: misprint: should be "... + length ..."
> - what is Decimal ?
> - what is Timestamp ?
> - what is Time ?
> Complex Objects:
>
> - what does flag USER_TYPE mean ?
> - Schema "field Id; Java-style hash code of field" -> should be "... of field
> name".
> - "Repeat for as many times as the total number of schemas you have" ->
> should be "... total number of fields you have".
> - is it mandated that the number of fields in the Schema must be equal to the
> number of fields in the Data Object ?
> Objects Wrapped In Array
>
> - may binary objects with different type codes be in the same array ?
> - may complex objects with different type ids be in the same array ?
> - "All cache operations return complex objects inside a wrapper (but not
> primitives)." -> does it mean that in general a complex object (103) must
> always be sent via the Binary Protocol in a wrapper (27)?
> - "Byte array size" -> "Payload size" or "Size of the whole array with
> header" ?
> - Offset. What is "object graph" here ? The Binary Protocol nowhere describes
> any relations ("graph") between data objects in the protocol.
> Terminology
> ---
> Not critical but would be really convenient to define and use the same terms
> along the whole spec. For example:
> - "binary object" is always the same as "data object" of any type (?). Can be
> "standard/predefined type object" or "complex object".
> - "cluster" or "server" ?
> - "cluster member" or "server nodes" ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8039) Binary Client Protocol spec: data types/format clarifications
[
https://issues.apache.org/jira/browse/IGNITE-8039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470437#comment-16470437
]
Igor Sapego commented on IGNITE-8039:
-
[~dmagda], [~pgarg], [~alexey.kosenchuk], guys,
I've added short \{{Binary Enum}} type description, \{{Complex Object}}
description and moved \{{Wrapped Data}} description to the type description
page. Also, I've renamed the page from "Standard Types" => "Data Format".
So, I'm putting this ticket on review and going to make other changes in other
tickets. Please, take a look and tell me what do you think.
The page URL: [https://apacheignite.readme.io/v2.4/docs/data-format]
> Binary Client Protocol spec: data types/format clarifications
> -
>
> Key: IGNITE-8039
> URL: https://issues.apache.org/jira/browse/IGNITE-8039
> Project: Ignite
> Issue Type: Bug
> Components: documentation, thin client
>Affects Versions: 2.4
>Reporter: Alexey Kosenchuk
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.5
>
>
> Assuming the Binary Client Protocol spec should be detalized enough to allow
> a client development basing on the spec only, w/o looking at other client
> implementations and asking additional questions...
> The following should be clarified / corrected in the Binary Client Protocol
> spec (v.2.4)
> (https://apacheignite.readme.io/v2.4/docs/binary-client-protocol#section-data-format):
> Type Codes table:
> -
> - UUID (Guid) size: should be 16 bytes, not 8 (?)
> - what is Object array (type code 23) ? What is the difference between it and
> Objects Wrapped In Array (type code 27) ?
> - what is Collection USER_SET ?
> - what is Collection USER_COL ?
> - what is Collection SINGLETON_LIST ?
> - Collection: misprint: should be "... + length ..."
> - what is Decimal ?
> - what is Timestamp ?
> - what is Time ?
> Complex Objects:
>
> - what does flag USER_TYPE mean ?
> - Schema "field Id; Java-style hash code of field" -> should be "... of field
> name".
> - "Repeat for as many times as the total number of schemas you have" ->
> should be "... total number of fields you have".
> - is it mandated that the number of fields in the Schema must be equal to the
> number of fields in the Data Object ?
> Objects Wrapped In Array
>
> - may binary objects with different type codes be in the same array ?
> - may complex objects with different type ids be in the same array ?
> - "All cache operations return complex objects inside a wrapper (but not
> primitives)." -> does it mean that in general a complex object (103) must
> always be sent via the Binary Protocol in a wrapper (27)?
> - "Byte array size" -> "Payload size" or "Size of the whole array with
> header" ?
> - Offset. What is "object graph" here ? The Binary Protocol nowhere describes
> any relations ("graph") between data objects in the protocol.
> Terminology
> ---
> Not critical but would be really convenient to define and use the same terms
> along the whole spec. For example:
> - "binary object" is always the same as "data object" of any type (?). Can be
> "standard/predefined type object" or "complex object".
> - "cluster" or "server" ?
> - "cluster member" or "server nodes" ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7968) IgniteAtomicSequence.incrementAndGet throws ClusterTopologyException: Failed to acquire lock for keys
[ https://issues.apache.org/jira/browse/IGNITE-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470432#comment-16470432 ] Dmitriy Pavlov commented on IGNITE-7968: Unfortunately status of Run-All is outdated, builds were removed from TC history, so I've triggered [https://ci.ignite.apache.org/viewQueued.html?itemId=1280255] Only .Net tests I can see in TC. > IgniteAtomicSequence.incrementAndGet throws ClusterTopologyException: Failed > to acquire lock for keys > - > > Key: IGNITE-7968 > URL: https://issues.apache.org/jira/browse/IGNITE-7968 > Project: Ignite > Issue Type: Bug > Components: data structures >Affects Versions: 2.3, 2.4 >Reporter: Pavel Vinokurov >Assignee: Pavel Vinokurov >Priority: Major > Fix For: 2.6 > > Attachments: AtomicSeqAndClusterTopologyReproducer.java > > > When a primary node for a atomic sequnce has left cluster, > IgniteAtomicSequence.incrementAndGet could throw ClusterTopologyException. > The reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-3999) Support case insensitive search in SQL
[
https://issues.apache.org/jira/browse/IGNITE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470424#comment-16470424
]
Dmitriy Pavlov commented on IGNITE-3999:
Hi [~vkulichenko] are you agree with "Won't fix" resolution?
> Support case insensitive search in SQL
> --
>
> Key: IGNITE-3999
> URL: https://issues.apache.org/jira/browse/IGNITE-3999
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Amir Akhmedov
>Priority: Critical
> Labels: sql-engine
> Fix For: 2.6
>
>
> Currently case insensitive search is possible only with the help of
> {{lower()}} function:
> {code}
> select name from MyValue where lower(name) = 'abc_5'
> {code}
> But this will always be a full scan, even if {{name}} field is indexed.
> We need to correctly support {{VARCHAR_IGNORECASE}} H2 type in Ignite and add
> a respective property to {{@QuerySqlField}} annotation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8266) Remove afterTestsStopped method due to stopAllGrids by default
[
https://issues.apache.org/jira/browse/IGNITE-8266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470420#comment-16470420
]
Nikolay Izhikov commented on IGNITE-8266:
-
[~dpavlov]
> can we remove after tests in separate issue?
In my opinion, we should do as few refactorings as we can.
So I still propose to remove {{super.afterAllTests()}}.
But, if you have another opinion, please proceed with the review and merge.
> Remove afterTestsStopped method due to stopAllGrids by default
> --
>
> Key: IGNITE-8266
> URL: https://issues.apache.org/jira/browse/IGNITE-8266
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.5
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Minor
> Labels: test
> Fix For: 2.6
>
>
> Remove this types of method from test in whole ignite-core module.
> {code:java}
> @Override protected void afterTestsStopped() throws Exception {
> super.afterTestsStopped();
> stopAllGrids();
> }{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8466) Control.sh transacitions utility may hang on case with loading
[ https://issues.apache.org/jira/browse/IGNITE-8466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Sherstobitov updated IGNITE-8466: Description: Start nodes, activate and preload some Accounts data Start client and run transactional loading (8 threads with ~1000ops/second - moving some amount from one value to another) Start 10 long running transactions (transactions with flexible sleep inside) with label tx_* Start control.sh --tx label tx kill Last run of control.sh utility hangs. Attachment info: grid1,2,3 - server logs grid20001 - client with preloading grid20002 - client with transactional loading and LRTs (with stack trace) was: Start nodes, activate and preload some Accounts data Start client and run transactional loading (8 threads with ~1000ops/second - moving some amount from one value to another) Start long running transactions (transactions with flexible sleep inside) with label tx_* Start control.sh --tx label tx kill Last run of control.sh utility hangs. Attachment info: grid1,2,3 - server logs grid20001 - client with preloading grid20002 - client with transactional loading and LRTs (with stack trace) > Control.sh transacitions utility may hang on case with loading > -- > > Key: IGNITE-8466 > URL: https://issues.apache.org/jira/browse/IGNITE-8466 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Dmitry Sherstobitov >Priority: Critical > Attachments: IGNITE-8466.zip > > > Start nodes, activate and preload some Accounts data > Start client and run transactional loading (8 threads with ~1000ops/second - > moving some amount from one value to another) > Start 10 long running transactions (transactions with flexible sleep inside) > with label tx_* > Start control.sh --tx label tx kill > > Last run of control.sh utility hangs. > > Attachment info: > grid1,2,3 - server logs > grid20001 - client with preloading > grid20002 - client with transactional loading and LRTs (with stack trace) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8162) Handle ClassNotFoundException during deserialization of persisted cache configuration
[ https://issues.apache.org/jira/browse/IGNITE-8162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-8162. -- Resolution: Fixed Looks good to me. Thanks for contribution. Merged to master. > Handle ClassNotFoundException during deserialization of persisted cache > configuration > -- > > Key: IGNITE-8162 > URL: https://issues.apache.org/jira/browse/IGNITE-8162 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 2.4 >Reporter: Ivan Rakov >Assignee: Denis Garus >Priority: Major > Labels: newbie > Fix For: 2.6 > > > Ticket is created according to dev list discussion: > http://apache-ignite-developers.2346864.n4.nabble.com/Fwd-Data-Loss-while-upgrading-custom-jar-from-old-jar-in-server-and-client-nodes-td28808.html > Cache configuration is serialized by JDK marshaller and persisted in > cache_data.dat file. It may contain instances of classes that disappeared > from runtime classpath (e.g. if implementation of CacheStore has been > renamed). In such case, node will fail on start. > We should handle this and show meaningful message with instruction how to > overcome this issue - delete cache_data.dat and restart cache. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6055) SQL: Add String length constraint
[
https://issues.apache.org/jira/browse/IGNITE-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470386#comment-16470386
]
ASF GitHub Bot commented on IGNITE-6055:
GitHub user nizhikov opened a pull request:
https://github.com/apache/ignite/pull/3973
IGNITE-6055: SQL: Add String length constraint
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nizhikov/ignite IGNITE-6055
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3973.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 #3973
commit 98f7102523f0513b359ffc72bf59de05efc53fae
Author: Nikolay Izhikov
Date: 2018-05-10T08:59:30Z
IGNITE-6005: Failed test for a new feature
commit b8720ce622881596ebd8e864a4357eb2a7ccc0ae
Author: Nikolay Izhikov
Date: 2018-05-10T09:00:12Z
Merge branch 'master' into IGNITE-6055
commit 233543ee128819906f419607bb20a7c2c73136ba
Author: Nikolay Izhikov
Date: 2018-05-10T13:26:04Z
IGNITE-6005: Changes to save and process string field length
> SQL: Add String length constraint
> -
>
> Key: IGNITE-6055
> URL: https://issues.apache.org/jira/browse/IGNITE-6055
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: sql-engine
>
> We should support {{CHAR(X)}} and {{VARCHAR{X}} syntax. Currently, we ignore
> it. First, it affects semantics. E.g., one can insert a string with greater
> length into a cache/table without any problems. Second, it limits efficiency
> of our default configuration. E.g., index inline cannot be applied to
> {{String}} data type as we cannot guess it's length.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8465) Reject control.sh connecton to a cluster in case the versions differ
[ https://issues.apache.org/jira/browse/IGNITE-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Sherstobitov updated IGNITE-8465: Summary: Reject control.sh connecton to a cluster in case the versions differ (was: Support compatibility in control.sh utility) > Reject control.sh connecton to a cluster in case the versions differ > > > Key: IGNITE-8465 > URL: https://issues.apache.org/jira/browse/IGNITE-8465 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Dmitry Sherstobitov >Priority: Major > > control.sh --tx from 2.5 for now may be launched with 2.4 cluster e.g > It may cause errors on cluster > > This communications should be prevented in control.sh utility -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8465) Support compatibility in control.sh utility
[ https://issues.apache.org/jira/browse/IGNITE-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Sherstobitov updated IGNITE-8465: Description: control.sh --tx from 2.5 for now may be launched with 2.4 cluster e.g It may cause errors on cluster This communications should be prevented in control.sh utility was: control.sh --tx from 2.5.1 for now may be launched with 2.4.x cluster e.g It may cause errors on cluster This communications should be prevented in control.sh utility > Support compatibility in control.sh utility > --- > > Key: IGNITE-8465 > URL: https://issues.apache.org/jira/browse/IGNITE-8465 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Dmitry Sherstobitov >Priority: Major > > control.sh --tx from 2.5 for now may be launched with 2.4 cluster e.g > It may cause errors on cluster > > This communications should be prevented in control.sh utility -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8167) Recovery after crash sometimes leads to starting from beginning absolute wal segment index
[ https://issues.apache.org/jira/browse/IGNITE-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470375#comment-16470375 ] ASF GitHub Bot commented on IGNITE-8167: Github user amelius0712 closed the pull request at: https://github.com/apache/ignite/pull/3771 > Recovery after crash sometimes leads to starting from beginning absolute wal > segment index > -- > > Key: IGNITE-8167 > URL: https://issues.apache.org/jira/browse/IGNITE-8167 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 > Environment: Doesn't meter. We saw these behavior in k8s deployment > as in local deployment too. Using any of WAL_MOD. >Reporter: Pavel Sapezhko >Assignee: Pavel Sapezhko >Priority: Major > Fix For: 2.5 > > Attachments: ignite_precrash.log > > > When we are trying to restore after crash using wal log, sometimes we can > find corrupted wal messages which can leads to starting from beginning > absolute wal index. So, we will have broken wal archiver thread due to > assertation error(but we still having working Ignite instance. I think we > need to discuss if we are really want it) and as a result on next restart we > can see "Wal history is too short" message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8167) Recovery after crash sometimes leads to starting from beginning absolute wal segment index
[ https://issues.apache.org/jira/browse/IGNITE-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470371#comment-16470371 ] Dmitriy Pavlov commented on IGNITE-8167: [~pavel.sapezhko], only you I guess can close PR. Also it is preferred if author closes issue as Won't fix according to Apache philosophy. > Recovery after crash sometimes leads to starting from beginning absolute wal > segment index > -- > > Key: IGNITE-8167 > URL: https://issues.apache.org/jira/browse/IGNITE-8167 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 > Environment: Doesn't meter. We saw these behavior in k8s deployment > as in local deployment too. Using any of WAL_MOD. >Reporter: Pavel Sapezhko >Assignee: Pavel Sapezhko >Priority: Major > Fix For: 2.5 > > Attachments: ignite_precrash.log > > > When we are trying to restore after crash using wal log, sometimes we can > find corrupted wal messages which can leads to starting from beginning > absolute wal index. So, we will have broken wal archiver thread due to > assertation error(but we still having working Ignite instance. I think we > need to discuss if we are really want it) and as a result on next restart we > can see "Wal history is too short" message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8456) Print warning if IGNITE_HOME & WORK and persistentStoreDir is not set, but persistence enabled
[ https://issues.apache.org/jira/browse/IGNITE-8456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii reassigned IGNITE-8456: -- Assignee: Ryabov Dmitrii > Print warning if IGNITE_HOME & WORK and persistentStoreDir is not set, but > persistence enabled > -- > > Key: IGNITE-8456 > URL: https://issues.apache.org/jira/browse/IGNITE-8456 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Dmitriy Pavlov >Assignee: Ryabov Dmitrii >Priority: Critical > Labels: easyfix, newbie > Fix For: 2.6 > > > In method org.apache.ignite.internal.util.IgniteUtils#workDirectory > Ignite determine Work dir to be set, same value may be used in case > persistence Store Folder is not set and IGNITE_HOME is not specified. > In case work dir is not specified, temp directory is used for Ignite Work. > But for persistence enabled case this means user DB goes to temp folder and > may be removed later. > User may be confused by this behaviour. See: > [https://stackoverflow.com/questions/48434929/apache-ignite-persistent-storage] > and related Dev.List discussion > [http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-HOME-for-persistence-td26470.html] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8138) Incorrect uptime in Ignite metrics for long running server node (1+ days)
[
https://issues.apache.org/jira/browse/IGNITE-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470369#comment-16470369
]
Dmitriy Pavlov commented on IGNITE-8138:
Please see my proposals of change here,
[https://github.com/apache/ignite/pull/3972]
and timeSpan2HMSM usage remains uncovered in this PR.
> Incorrect uptime in Ignite metrics for long running server node (1+ days)
> -
>
> Key: IGNITE-8138
> URL: https://issues.apache.org/jira/browse/IGNITE-8138
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.1, 2.4
>Reporter: Max Shonichev
>Assignee: Sergey Skudnov
>Priority: Major
> Fix For: 2.6
>
> Attachments: Screenshot from 2018-04-08 23-37-39.png, Screenshot from
> 2018-04-16 09-33-24.png
>
>
> Ignite prints a metrics to the log with uptime, formatted as 'XX:YY:ZZ:TTT'.
> It looks, like XX corresponds to hours, YY to minutes, ZZ to seconds, however
> if we filter uptime metric from a long running server (few days), we would
> see that :
> {noformat}
> ^-- Node [id=684d2761, name=null, uptime=00:01:00:009]
> ^-- Node [id=684d2761, name=null, uptime=00:02:00:009]
> ^-- Node [id=684d2761, name=null, uptime=00:03:00:009]
> ^-- Node [id=684d2761, name=null, uptime=00:04:00:021]
> ...
> ^-- Node [id=684d2761, name=null, uptime=23:58:08:391]
> ^-- Node [id=684d2761, name=null, uptime=23:59:08:393]
> ^-- Node [id=684d2761, name=null, uptime=24:00:08:395]
> ^-- Node [id=684d2761, name=null, uptime=24:01:08:406]
> ...
> ^-- Node [id=684d2761, name=null, uptime=59:59:23:542]
> ^-- Node [id=684d2761, name=null, uptime=00:00:23:554]
> ...
> {noformat}
> BUG:
> 1. hours do not rollover at 23:59:59
> 2. there's no simple means for user to get uptime days, because hours do
> actually rollover after 59:59:59
> what is expected:
> 1. add a day counter, init with 0
> 2. make hours correctly rollover after full day (24hrs) run
> {noformat}
> ^-- Node [id=684d2761, name=null, uptime=0:00:01:00:009]
> ...
> ^-- Node [id=684d2761, name=null, uptime=0:23:59:00:009]
> ^-- Node [id=684d2761, name=null, uptime=1:00:00:00:009]
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8138) Incorrect uptime in Ignite metrics for long running server node (1+ days)
[
https://issues.apache.org/jira/browse/IGNITE-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470360#comment-16470360
]
Dmitriy Pavlov commented on IGNITE-8138:
Was this fix reviewed by someone else?
IMO initial reason of this bug was unclear code, with magic numbers, so new
version of code still has this issue.
Why usage of org.apache.ignite.internal.util.typedef.X#timeSpan2HMSM was not
replaced to new method?
> Incorrect uptime in Ignite metrics for long running server node (1+ days)
> -
>
> Key: IGNITE-8138
> URL: https://issues.apache.org/jira/browse/IGNITE-8138
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.1, 2.4
>Reporter: Max Shonichev
>Assignee: Sergey Skudnov
>Priority: Major
> Fix For: 2.6
>
> Attachments: Screenshot from 2018-04-08 23-37-39.png, Screenshot from
> 2018-04-16 09-33-24.png
>
>
> Ignite prints a metrics to the log with uptime, formatted as 'XX:YY:ZZ:TTT'.
> It looks, like XX corresponds to hours, YY to minutes, ZZ to seconds, however
> if we filter uptime metric from a long running server (few days), we would
> see that :
> {noformat}
> ^-- Node [id=684d2761, name=null, uptime=00:01:00:009]
> ^-- Node [id=684d2761, name=null, uptime=00:02:00:009]
> ^-- Node [id=684d2761, name=null, uptime=00:03:00:009]
> ^-- Node [id=684d2761, name=null, uptime=00:04:00:021]
> ...
> ^-- Node [id=684d2761, name=null, uptime=23:58:08:391]
> ^-- Node [id=684d2761, name=null, uptime=23:59:08:393]
> ^-- Node [id=684d2761, name=null, uptime=24:00:08:395]
> ^-- Node [id=684d2761, name=null, uptime=24:01:08:406]
> ...
> ^-- Node [id=684d2761, name=null, uptime=59:59:23:542]
> ^-- Node [id=684d2761, name=null, uptime=00:00:23:554]
> ...
> {noformat}
> BUG:
> 1. hours do not rollover at 23:59:59
> 2. there's no simple means for user to get uptime days, because hours do
> actually rollover after 59:59:59
> what is expected:
> 1. add a day counter, init with 0
> 2. make hours correctly rollover after full day (24hrs) run
> {noformat}
> ^-- Node [id=684d2761, name=null, uptime=0:00:01:00:009]
> ...
> ^-- Node [id=684d2761, name=null, uptime=0:23:59:00:009]
> ^-- Node [id=684d2761, name=null, uptime=1:00:00:00:009]
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6430) CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails periodically.
[
https://issues.apache.org/jira/browse/IGNITE-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470351#comment-16470351
]
Alexander Menshikov commented on IGNITE-6430:
-
[~agura]
I have finished the task. Please review and merge if okay.
[~alex_pl]
Thanks for the review.
> CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails
> periodically.
>
>
> Key: IGNITE-6430
> URL: https://issues.apache.org/jira/browse/IGNITE-6430
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Alexander Menshikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> {{CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime}} test
> fails periodically.
> {noformat}
> [2017-09-18 15:18:20,073][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: Expected less 5000, Actual:-100969
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime(CacheGroupsMetricsRebalanceTest.java:261)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> After fix test should be unmuted on TC.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8167) Recovery after crash sometimes leads to starting from beginning absolute wal segment index
[ https://issues.apache.org/jira/browse/IGNITE-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470343#comment-16470343 ] Pavel Sapezhko commented on IGNITE-8167: Got it. Ok, so could you please close this issue/PR. On Thu, May 10, 2018 at 2:50 PM Dmitriy Pavlov (JIRA) -- С уважением, Cапежко Павел Александрович Инженер-программист ООО "Synesis" Skype: p.sapezhko > Recovery after crash sometimes leads to starting from beginning absolute wal > segment index > -- > > Key: IGNITE-8167 > URL: https://issues.apache.org/jira/browse/IGNITE-8167 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 > Environment: Doesn't meter. We saw these behavior in k8s deployment > as in local deployment too. Using any of WAL_MOD. >Reporter: Pavel Sapezhko >Assignee: Pavel Sapezhko >Priority: Major > Fix For: 2.5 > > Attachments: ignite_precrash.log > > > When we are trying to restore after crash using wal log, sometimes we can > find corrupted wal messages which can leads to starting from beginning > absolute wal index. So, we will have broken wal archiver thread due to > assertation error(but we still having working Ignite instance. I think we > need to discuss if we are really want it) and as a result on next restart we > can see "Wal history is too short" message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8466) Control.sh transacitions utility may hang on case with loading
[ https://issues.apache.org/jira/browse/IGNITE-8466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Sherstobitov updated IGNITE-8466: Description: Start nodes, activate and preload some Accounts data Start client and run transactional loading (8 threads with ~1000ops/second - moving some amount from one value to another) Start long running transactions (transactions with flexible sleep inside) with label tx_* Start control.sh --tx label tx kill Last run of control.sh utility hangs. Attachment info: grid1,2,3 - server logs grid20001 - client with preloading grid20002 - client with transactional loading and LRTs (with stack trace) was: Start nodes Start client and run transactional loading (8 threads with ~1000ops/second - moving some amount from one value to another) Start long running transactions (transactions with flexible sleep inside) with label tx_* Start control.sh --tx label tx kill Last run of control.sh utility hangs. Attachment info: grid1,2,3 - server logs grid20001 - client with preloading grid20002 - client with transactional loading and LRTs (with stack trace) > Control.sh transacitions utility may hang on case with loading > -- > > Key: IGNITE-8466 > URL: https://issues.apache.org/jira/browse/IGNITE-8466 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Dmitry Sherstobitov >Priority: Critical > Attachments: IGNITE-8466.zip > > > Start nodes, activate and preload some Accounts data > Start client and run transactional loading (8 threads with ~1000ops/second - > moving some amount from one value to another) > Start long running transactions (transactions with flexible sleep inside) > with label tx_* > Start control.sh --tx label tx kill > > Last run of control.sh utility hangs. > > Attachment info: > grid1,2,3 - server logs > grid20001 - client with preloading > grid20002 - client with transactional loading and LRTs (with stack trace) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8466) Control.sh transacitions utility may hang on case with loading
[ https://issues.apache.org/jira/browse/IGNITE-8466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Sherstobitov updated IGNITE-8466: Description: Start nodes Start client and run transactional loading (8 threads with ~1000ops/second - moving some amount from one value to another) Start long running transactions (transactions with flexible sleep inside) with label tx_* Start control.sh --tx label tx kill Last run of control.sh utility hangs. Attachment info: grid1,2,3 - server logs grid20001 - client with preloading grid20002 - client with transactional loading and LRTs (with stack trace) was: Start nodes Start client and run transactional loading (8 threads with ~1000ops/second - moving some amount from one value to another) Start long running transactions (transactions with flexible sleep inside) with label tx_* Start control.sh --tx label tx kill > Control.sh transacitions utility may hang on case with loading > -- > > Key: IGNITE-8466 > URL: https://issues.apache.org/jira/browse/IGNITE-8466 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Dmitry Sherstobitov >Priority: Critical > Attachments: IGNITE-8466.zip > > > Start nodes > Start client and run transactional loading (8 threads with ~1000ops/second - > moving some amount from one value to another) > Start long running transactions (transactions with flexible sleep inside) > with label tx_* > Start control.sh --tx label tx kill > > Last run of control.sh utility hangs. > > Attachment info: > grid1,2,3 - server logs > grid20001 - client with preloading > grid20002 - client with transactional loading and LRTs (with stack trace) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8466) Control.sh transacitions utility may hang on case with loading
[ https://issues.apache.org/jira/browse/IGNITE-8466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Sherstobitov updated IGNITE-8466: Attachment: IGNITE-8466.zip > Control.sh transacitions utility may hang on case with loading > -- > > Key: IGNITE-8466 > URL: https://issues.apache.org/jira/browse/IGNITE-8466 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Dmitry Sherstobitov >Priority: Critical > Attachments: IGNITE-8466.zip > > > Start nodes > Start client and run transactional loading (8 threads with ~1000ops/second - > moving some amount from one value to another) > Start long running transactions (transactions with flexible sleep inside) > with label tx_* > Start control.sh --tx label tx kill -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8466) Control.sh transacitions utility may hang on case with loading
Dmitry Sherstobitov created IGNITE-8466: --- Summary: Control.sh transacitions utility may hang on case with loading Key: IGNITE-8466 URL: https://issues.apache.org/jira/browse/IGNITE-8466 Project: Ignite Issue Type: Bug Affects Versions: 2.5 Reporter: Dmitry Sherstobitov Start nodes Start client and run transactional loading (8 threads with ~1000ops/second - moving some amount from one value to another) Start long running transactions (transactions with flexible sleep inside) with label tx_* Start control.sh --tx label tx kill -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8459) Searching checkpoint history for WAL rebalance is broken
[
https://issues.apache.org/jira/browse/IGNITE-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Govorukhin updated IGNITE-8459:
---
Fix Version/s: 2.6
> Searching checkpoint history for WAL rebalance is broken
>
>
> Key: IGNITE-8459
> URL: https://issues.apache.org/jira/browse/IGNITE-8459
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Critical
> Fix For: 2.6
>
>
> Currently the mechanism to search available checkpoint records in WAL to have
> history for WAL rebalance is broken. It means that WAL (Historical) rebalance
> will never find history for rebalance and full rebalance will be always used.
> This mechanism was broken in
> https://github.com/apache/ignite/commit/ec04cd174ed5476fba83e8682214390736321b37
> by unclear reasons.
> If we swap the following two code blocks (database().beforeExchange() and
> exchCtx if block):
> {noformat}
> /* It is necessary to run database callback before all topology
> callbacks.
>In case of persistent store is enabled we first restore partitions
> presented on disk.
>We need to guarantee that there are no partition state changes
> logged to WAL before this callback
>to make sure that we correctly restored last actual states. */
> cctx.database().beforeExchange(this);
> if (!exchCtx.mergeExchanges()) {
> for (CacheGroupContext grp : cctx.cache().cacheGroups()) {
> if (grp.isLocal() || cacheGroupStopping(grp.groupId()))
> continue;
> // It is possible affinity is not initialized yet if node
> joins to cluster.
> if (grp.affinity().lastVersion().topologyVersion() > 0)
> grp.topology().beforeExchange(this, !centralizedAff &&
> !forceAffReassignment, false);
> }
> }
> {noformat}
> the searching mechanism will start to work correctly. Currently it's unclear
> why it's happened.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7912) control.sh script should show used WAL-segments
[ https://issues.apache.org/jira/browse/IGNITE-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470310#comment-16470310 ] Dmitriy Pavlov commented on IGNITE-7912: [~vozerov] could you please write comment to ticket after merge, so it would be clear who did the review. > control.sh script should show used WAL-segments > --- > > Key: IGNITE-7912 > URL: https://issues.apache.org/jira/browse/IGNITE-7912 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Filatov >Assignee: Ivan Daschinskiy >Priority: Minor > Fix For: 2.6 > > > We have to erase wal archive because wal archive can grow large and we must > have safe way to remove unused segments to free disk space. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
