[jira] [Closed] (IGNITE-5641) Web Console: In addition to export also implement copy result set to clipboard.

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov closed IGNITE-5641.
--

> Web Console: In addition to export also implement copy result set to 
> clipboard.
> ---
>
> Key: IGNITE-5641
> URL: https://issues.apache.org/jira/browse/IGNITE-5641
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-6914) Web console: 'Export All' for scan stucks in Chrome but successfully finish in FireFox

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov closed IGNITE-6914.
--

> Web console: 'Export All' for scan stucks in Chrome but successfully finish 
> in FireFox
> --
>
> Key: IGNITE-6914
> URL: https://issues.apache.org/jira/browse/IGNITE-6914
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> I populated a cache with 100K of data.
> Then I opened Query screen and execute Scan for that cache.
> Then I executed Export All - under Chrome it stuck



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-4454) Web console: add information on query panel UI about node query was executed on

[Alexander Kalinin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Kalinin reassigned IGNITE-4454:
-

Assignee: Pavel Konstantinov  (was: Alexander Kalinin)

Consulted with Alexey: Left column expanded to fit possible long strings.. 
Symmetry doesn't matter. Please verify - ignite-4454.

> Web console: add information on query panel  UI about node query was executed 
> on
> 
>
> Key: IGNITE-4454
> URL: https://issues.apache.org/jira/browse/IGNITE-4454
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> Currently we show only query text  and do not show node in case of 'Execute 
> on selected node'



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6904) SQL: partition reservations are released too early in lazy mode

[Roman Kondakov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263886#comment-16263886
 ] 

Roman Kondakov commented on IGNITE-6904:


[~vozerov], please review. Tests are ok.

> SQL: partition reservations are released too early in lazy mode
> ---
>
> Key: IGNITE-6904
> URL: https://issues.apache.org/jira/browse/IGNITE-6904
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Roman Kondakov
> Fix For: 2.4
>
>
> In lazy mode we advance query execution as new page requests arrive. However, 
> method {{GridMapQueryExecutor#onQueryRequest0}} releases partition 
> reservations when only the very first page is processed:
> {code}
> finally {
> GridH2QueryContext.clearThreadLocal();
> if (distributedJoinMode == OFF)
> qctx.clearContext(false);
> }
> {code}
> It means that incorrect results may be returned on unstable topology. We need 
> to release partitions only after the whole query is executed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6919) Web console: incorrect character in tab name under IE11

[Alexander Kalinin (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263885#comment-16263885
 ] 

Alexander Kalinin commented on IGNITE-6919:
---

[~pkonstantinov] Fixed app-wide charset issue. Please verify.

> Web console: incorrect character in tab name under IE11
> ---
>
> Key: IGNITE-6919
> URL: https://issues.apache.org/jira/browse/IGNITE-6919
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Trivial
> Fix For: 2.4
>
> Attachments: screenshot-1.png
>
>
> !screenshot-1.png!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6919) Web console: incorrect character in tab name under IE11

[Alexander Kalinin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Kalinin reassigned IGNITE-6919:
-

Assignee: Pavel Konstantinov  (was: Alexander Kalinin)

> Web console: incorrect character in tab name under IE11
> ---
>
> Key: IGNITE-6919
> URL: https://issues.apache.org/jira/browse/IGNITE-6919
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Trivial
> Fix For: 2.4
>
> Attachments: screenshot-1.png
>
>
> !screenshot-1.png!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Reopened] (IGNITE-4454) Web console: add information on query panel UI about node query was executed on

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov reopened IGNITE-4454:

  Assignee: Alexander Kalinin  (was: Pavel Konstantinov)

> Web console: add information on query panel  UI about node query was executed 
> on
> 
>
> Key: IGNITE-4454
> URL: https://issues.apache.org/jira/browse/IGNITE-4454
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexander Kalinin
>Priority: Minor
> Fix For: 2.4
>
>
> Currently we show only query text  and do not show node in case of 'Execute 
> on selected node'



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-4454) Web console: add information on query panel UI about node query was executed on

[Pavel Konstantinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263814#comment-16263814
 ] 

Pavel Konstantinov commented on IGNITE-4454:


In case of long duration 'NodeID8' placed on the next row, please fix

> Web console: add information on query panel  UI about node query was executed 
> on
> 
>
> Key: IGNITE-4454
> URL: https://issues.apache.org/jira/browse/IGNITE-4454
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> Currently we show only query text  and do not show node in case of 'Execute 
> on selected node'



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5641) Web Console: In addition to export also implement copy result set to clipboard.

[Pavel Konstantinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263805#comment-16263805
 ] 

Pavel Konstantinov commented on IGNITE-5641:


Tested.

> Web Console: In addition to export also implement copy result set to 
> clipboard.
> ---
>
> Key: IGNITE-5641
> URL: https://issues.apache.org/jira/browse/IGNITE-5641
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6914) Web console: 'Export All' for scan stucks in Chrome but successfully finish in FireFox

[Pavel Konstantinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263804#comment-16263804
 ] 

Pavel Konstantinov commented on IGNITE-6914:


Tested.

> Web console: 'Export All' for scan stucks in Chrome but successfully finish 
> in FireFox
> --
>
> Key: IGNITE-6914
> URL: https://issues.apache.org/jira/browse/IGNITE-6914
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> I populated a cache with 100K of data.
> Then I opened Query screen and execute Scan for that cache.
> Then I executed Export All - under Chrome it stuck



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-4398) Web console: incorrect authentication under IE 11 (windows 10)

[Alexander Kalinin (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263789#comment-16263789
 ] 

Alexander Kalinin commented on IGNITE-4398:
---

[~pkonstantinov] Updated cache disable mechanism. Please test

> Web console: incorrect authentication under IE 11 (windows 10)
> --
>
> Key: IGNITE-4398
> URL: https://issues.apache.org/jira/browse/IGNITE-4398
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>  Time Spent: 0.1m
>  Remaining Estimate: 0h
>
> To reproduce:
> 1) log in as User1
> 2) create some cluster and save
> 3) log out
> 4) log in as User2
> You will see the cluster from User1.
> Note: IE specific only



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-4398) Web console: incorrect authentication under IE 11 (windows 10)

[Alexander Kalinin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Kalinin reassigned IGNITE-4398:
-

Assignee: Pavel Konstantinov  (was: Alexander Kalinin)

> Web console: incorrect authentication under IE 11 (windows 10)
> --
>
> Key: IGNITE-4398
> URL: https://issues.apache.org/jira/browse/IGNITE-4398
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>  Time Spent: 0.1m
>  Remaining Estimate: 0h
>
> To reproduce:
> 1) log in as User1
> 2) create some cluster and save
> 3) log out
> 4) log in as User2
> You will see the cluster from User1.
> Note: IE specific only



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6919) Web console: incorrect character in tab name under IE11

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-6919:
---
Attachment: (was: screenshot-2.png)

> Web console: incorrect character in tab name under IE11
> ---
>
> Key: IGNITE-6919
> URL: https://issues.apache.org/jira/browse/IGNITE-6919
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Trivial
> Fix For: 2.4
>
> Attachments: screenshot-1.png
>
>
> !screenshot-1.png!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6919) Web console: incorrect character in tab name under IE11

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov reassigned IGNITE-6919:
--

Assignee: Alexander Kalinin  (was: Pavel Konstantinov)

> Web console: incorrect character in tab name under IE11
> ---
>
> Key: IGNITE-6919
> URL: https://issues.apache.org/jira/browse/IGNITE-6919
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Alexander Kalinin
>Priority: Trivial
> Fix For: 2.4
>
> Attachments: screenshot-1.png
>
>
> !screenshot-1.png!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-6919) Web console: incorrect character in tab name under IE11

[Pavel Konstantinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263754#comment-16263754
 ] 

Pavel Konstantinov edited comment on IGNITE-6919 at 11/23/17 3:33 AM:
--

Test failed. That issue found not only on 'logout' page.
Could you please find out and fix all places with the same issue


was (Author: pkonstantinov):
That issue found not only on 'logout' page
!screenshot-2.png!

Could you please find out and fix all places with the same issue

> Web console: incorrect character in tab name under IE11
> ---
>
> Key: IGNITE-6919
> URL: https://issues.apache.org/jira/browse/IGNITE-6919
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Trivial
> Fix For: 2.4
>
> Attachments: screenshot-1.png
>
>
> !screenshot-1.png!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6919) Web console: incorrect character in tab name under IE11

[Pavel Konstantinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263754#comment-16263754
 ] 

Pavel Konstantinov commented on IGNITE-6919:


That issue found not only on 'logout' page
!screenshot-2.png!

Could you please find out and fix all places with the same issue

> Web console: incorrect character in tab name under IE11
> ---
>
> Key: IGNITE-6919
> URL: https://issues.apache.org/jira/browse/IGNITE-6919
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Trivial
> Fix For: 2.4
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> !screenshot-1.png!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6919) Web console: incorrect character in tab name under IE11

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-6919:
---
Attachment: screenshot-2.png

> Web console: incorrect character in tab name under IE11
> ---
>
> Key: IGNITE-6919
> URL: https://issues.apache.org/jira/browse/IGNITE-6919
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Trivial
> Fix For: 2.4
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> !screenshot-1.png!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-4452) Web console: add execution time to results panel on Queries screen

[Pavel Konstantinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263740#comment-16263740
 ] 

Pavel Konstantinov edited comment on IGNITE-4452 at 11/23/17 3:16 AM:
--

Tested in branch


was (Author: pkonstantinov):
Tested.

> Web console: add execution time to results panel on Queries screen
> --
>
> Key: IGNITE-4452
> URL: https://issues.apache.org/jira/browse/IGNITE-4452
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Trivial
> Attachments: screenshot-1.png
>
>
> I think it may be useful to know query last execution time, especially if we 
> have a Refresh rate possibility.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-4452) Web console: add execution time to results panel on Queries screen

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov reassigned IGNITE-4452:
--

Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web console: add execution time to results panel on Queries screen
> --
>
> Key: IGNITE-4452
> URL: https://issues.apache.org/jira/browse/IGNITE-4452
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Trivial
> Attachments: screenshot-1.png
>
>
> I think it may be useful to know query last execution time, especially if we 
> have a Refresh rate possibility.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-4452) Web console: add execution time to results panel on Queries screen

[Pavel Konstantinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263740#comment-16263740
 ] 

Pavel Konstantinov commented on IGNITE-4452:


Tested.

> Web console: add execution time to results panel on Queries screen
> --
>
> Key: IGNITE-4452
> URL: https://issues.apache.org/jira/browse/IGNITE-4452
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Trivial
> Attachments: screenshot-1.png
>
>
> I think it may be useful to know query last execution time, especially if we 
> have a Refresh rate possibility.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6995) Visor CMD: Actualize showed grid/cache configuration.

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-6995:
-

 Summary: Visor CMD: Actualize showed grid/cache configuration.
 Key: IGNITE-6995
 URL: https://issues.apache.org/jira/browse/IGNITE-6995
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko


Actualise in accordance to IGNITE-6649 changes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6390) [IGNITE-6390] Web console: Implement component for cluster selection on pages where it make sense

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov reassigned IGNITE-6390:


Assignee: Ilya Borisov  (was: Pavel Konstantinov)

Could you review cluster selector component?

> [IGNITE-6390] Web console: Implement component for cluster selection on pages 
> where it make sense
> -
>
> Key: IGNITE-6390
> URL: https://issues.apache.org/jira/browse/IGNITE-6390
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Ilya Borisov
> Fix For: 2.4
>
>
> 1. add cluster-selector to pages.
> 2. add update information of cluster data in page after change cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-4398) Web console: incorrect authentication under IE 11 (windows 10)

[Alexander Kalinin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Kalinin reassigned IGNITE-4398:
-

Assignee: Alexander Kalinin  (was: Pavel Konstantinov)

> Web console: incorrect authentication under IE 11 (windows 10)
> --
>
> Key: IGNITE-4398
> URL: https://issues.apache.org/jira/browse/IGNITE-4398
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexander Kalinin
>  Time Spent: 0.1m
>  Remaining Estimate: 0h
>
> To reproduce:
> 1) log in as User1
> 2) create some cluster and save
> 3) log out
> 4) log in as User2
> You will see the cluster from User1.
> Note: IE specific only



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6745) Java 9: rework usages of URLClassLoader.getURLs()

[Cergey Chaulin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cergey Chaulin reassigned IGNITE-6745:
--

Assignee: Cergey Chaulin

> Java 9: rework usages of URLClassLoader.getURLs()
> -
>
> Key: IGNITE-6745
> URL: https://issues.apache.org/jira/browse/IGNITE-6745
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Cergey Chaulin
> Fix For: 2.4
>
> Attachments: IGNITE-6745.patch
>
>
> We use this method in multiple places:
> 1) {{MessageCodeGenerator}}
> 2) {{BinaryContext}}
> 3) {{ClassesGenerator}}
> 4) {{GridUriDeploymentFileProcessor}}
> The problem is that in Java 9 application class loader is not 
> {{URLClassLoader}}, so we cannot get URLs easily. Instead typically it is 
> {{BuiltinClassLoader}}, which refers to {{URLClassLoader}} in it's internal 
> field {{ucp}}.
> Let's refactor all usages of {{URLClassLoader.getURLs}} to some utility 
> method, which will be able to handle both Java 7/8 and Java 9 (through 
> reflection).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6944) Fail to execute task with immutable list string

[Valentin Kulichenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263461#comment-16263461
 ] 

Valentin Kulichenko commented on IGNITE-6944:
-

[~agura], you need to search for {{writeReplace}} in parent classes, but this 
doesn't happen anymore after your fix. Was this change intentional?

> Fail to execute task with immutable list string
> ---
>
> Key: IGNITE-6944
> URL: https://issues.apache.org/jira/browse/IGNITE-6944
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 2.3
>Reporter: Edmond Tsang
> Attachments: BinaryMarshellerWithGuavaSelfTest.java, 
> TestClientWithGuava.java
>
>
> Exception occurs when executing task with immutable list of string due to not 
> able to find method readResolve/writeReplace for binary object.
> It appears this is caused by a side effect of Jira 
> https://issues.apache.org/jira/browse/IGNITE-6485 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6994) Need to document PartitionLossPolicy

[Valentin Kulichenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Valentin Kulichenko reassigned IGNITE-6994:
---

Assignee: Prachi Garg

> Need to document PartitionLossPolicy
> 
>
> Key: IGNITE-6994
> URL: https://issues.apache.org/jira/browse/IGNITE-6994
> Project: Ignite
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Prachi Garg
>  Labels: documentation
> Fix For: 2.4
>
>
> Since 2.0 we have a feature that makes cache(s) unavailable in case of data 
> loss; exact behavior is controlled by {{PartitionLossPolicy}}: 
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/PartitionLossPolicy.html
> However, there is no mentioning in documentation about this. Need to provide 
> explanation of how and when it should be used and provide configuration 
> examples.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6994) Need to document PartitionLossPolicy

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-6994:
---

 Summary: Need to document PartitionLossPolicy
 Key: IGNITE-6994
 URL: https://issues.apache.org/jira/browse/IGNITE-6994
 Project: Ignite
  Issue Type: Improvement
  Components: documentation
Affects Versions: 2.3
Reporter: Valentin Kulichenko
 Fix For: 2.4


Since 2.0 we have a feature that makes cache(s) unavailable in case of data 
loss; exact behavior is controlled by {{PartitionLossPolicy}}: 
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/PartitionLossPolicy.html

However, there is no mentioning in documentation about this. Need to provide 
explanation of how and when it should be used and provide configuration 
examples.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6993) Document SMTP server documentation for Web Console

[Denis Magda (JIRA)]

Denis Magda created IGNITE-6993:
---

 Summary: Document SMTP server documentation for Web Console
 Key: IGNITE-6993
 URL: https://issues.apache.org/jira/browse/IGNITE-6993
 Project: Ignite
  Issue Type: Improvement
  Components: documentation
Affects Versions: 2.3
Reporter: Denis Magda
Assignee: Alexey Kuznetsov
 Fix For: 2.4


Document how to configure a custom SMTP server for Web Console on this domain 
under "Ignite Web Console" section:
https://apacheignite-tools.readme.io/docs



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-2766) Cache instance is closed when client disconnects

[Ilya Kasnacheev (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262875#comment-16262875
 ] 

Ilya Kasnacheev commented on IGNITE-2766:
-

I cannot reproduce the original problem - cache stays opened and operational 
after client reconnects with new ID.

I have improved test to check this behavior. Please review.

[~ntikhonov]

> Cache instance is closed when client disconnects
> 
>
> Key: IGNITE-2766
> URL: https://issues.apache.org/jira/browse/IGNITE-2766
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Ilya Kasnacheev
>
> In case client disconnects and reconnects after network timeout (i.e., with a 
> new ID), all cache instances acquired by this client are closed and are not 
> functional. User has to create a special logic to handle this case.
> Cache proxy should be able to handle this automatically.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6992) Ignite MR problem with accessing hdfs with enabled Kerberos

[Evgenii Zhuravlev (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Evgenii Zhuravlev reassigned IGNITE-6992:
-

Assignee: Evgenii Zhuravlev

> Ignite MR problem with accessing hdfs with enabled Kerberos
> ---
>
> Key: IGNITE-6992
> URL: https://issues.apache.org/jira/browse/IGNITE-6992
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0, 2.1, 2.3
>Reporter: Evgenii Zhuravlev
>Assignee: Evgenii Zhuravlev
>
> {code:java}
> class org.apache.ignite.IgniteCheckedException: SIMPLE authentication is not 
> enabled.  Available:[TOKEN, KERBEROS]
>   at 
> org.apache.ignite.internal.processors.hadoop.impl.v2.HadoopV2JobResourceManager.prepareJobEnvironment(HadoopV2JobResourceManager.java:169)
>   at 
> org.apache.ignite.internal.processors.hadoop.impl.v2.HadoopV2Job.initialize(HadoopV2Job.java:328)
>   at 
> org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker.job(HadoopJobTracker.java:1141)
>   at 
> org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker.submit(HadoopJobTracker.java:318)
>   at 
> org.apache.ignite.internal.processors.hadoop.HadoopProcessor.submit(HadoopProcessor.java:173)
>   at 
> org.apache.ignite.internal.processors.hadoop.HadoopImpl.submit(HadoopImpl.java:69)
>   at 
> org.apache.ignite.internal.processors.hadoop.proto.HadoopProtocolSubmitJobTask.run(HadoopProtocolSubmitJobTask.java:50)
>   at 
> org.apache.ignite.internal.processors.hadoop.proto.HadoopProtocolSubmitJobTask.run(HadoopProtocolSubmitJobTask.java:33)
>   at 
> org.apache.ignite.internal.processors.hadoop.proto.HadoopProtocolTaskAdapter$Job.execute(HadoopProtocolTaskAdapter.java:101)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6629)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1181)
>   at 
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1908)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1562)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1190)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1097)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.hadoop.security.AccessControlException: SIMPLE 
> authentication is not enabled.  Available:[TOKEN, KERBEROS]
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
>   at 
> org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)
>   at 
> org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:73)
>   at org.apache.hadoop.hdfs.DFSClient.getFileInfo(DFSClient.java:2110)
>   at 
> org.apache.hadoop.hdfs.DistributedFileSystem$22.doCall(DistributedFileSystem.java:1305)
>   at 
> org.apache.hadoop.hdfs.DistributedFileSystem$22.doCall(DistributedFileSystem.java:1301)
>   at 
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
>   at 
> org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1301)
>   at org.apache.hadoop.fs.FileSystem.exists(FileSystem.java:1426)
>   at 
> org.apache.ignite.internal.processors.hadoop.impl.v2.HadoopV2JobResourceManager.prepareJobEnvironment(HadoopV2JobResourceManager.java:136)
>   ... 22 more
> Caused by: 
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException):
>  SIMPLE authentication is not enabled.  Available:[TOKEN, KERBEROS]
>   at 

[jira] [Commented] (IGNITE-6944) Fail to execute task with immutable list string

[Andrey Gura (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262821#comment-16262821
 ] 

Andrey Gura commented on IGNITE-6944:
-

IGNITE-6485 test case is real and valid case. 

I've took a look to the problem and see that Java serializer use protected 
{{SingletoneImmutableList.writeReplace()/readResolve()}} methods in despite of 
absence of methods parameters. It looks strange for me but it is implementation 
of Java serialization and we should take it into account.

My solution the following:

- try to find in class private writeReplace/readResolve methods with 
output/input stream as parameter.
- if there are no such methods then we should try to find 
writeReplace/readResolve methods with any access modifiers and signatures.

It should work for IGNITE-6485 case and for this issue. But there are some 
problem in case of several methods with equal name but different signatures.

Will check my solution soon.

> Fail to execute task with immutable list string
> ---
>
> Key: IGNITE-6944
> URL: https://issues.apache.org/jira/browse/IGNITE-6944
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 2.3
>Reporter: Edmond Tsang
> Attachments: BinaryMarshellerWithGuavaSelfTest.java, 
> TestClientWithGuava.java
>
>
> Exception occurs when executing task with immutable list of string due to not 
> able to find method readResolve/writeReplace for binary object.
> It appears this is caused by a side effect of Jira 
> https://issues.apache.org/jira/browse/IGNITE-6485 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6867) Implement new JMX metrics for topology monitoring

[Pavel Pereslegin (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262760#comment-16262760
 ] 

Pavel Pereslegin commented on IGNITE-6867:
--

[~avinogradov]
Thank you for your comments, please, review it again.

> Implement new JMX metrics for topology monitoring
> -
>
> Key: IGNITE-6867
> URL: https://issues.apache.org/jira/browse/IGNITE-6867
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Aleksey Plekhanov
>Assignee: Pavel Pereslegin
>  Labels: iep-6, jmx
> Fix For: 2.4
>
>
> These additional metrics and methods should be implemented:
> * Current topology version
> * Total server nodes count
> * Total client nodes count
> * Method to count nodes filtered by some node attribute
> * Method to count nodes grouped by some node attribute
>  
> There is already a ticket to implement first 2 metrics from this list 
> (IGNITE-6844)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-6872) Linear regression should implement Model API

[Oleg Ignatenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259279#comment-16259279
 ] 

Oleg Ignatenko edited comment on IGNITE-6872 at 11/22/17 2:19 PM:
--

Ready to merge: [pull request #3069|https://github.com/apache/ignite/pull/3069].

Compared to prior / draft implementation there are not many changes; 
IGNITE-5846 made impact only on code in example where I had to change local 
vector to distributed one (not surprising given that ticket 5846 involved 
improving consistency of "like" functionality of distributed matrices and 
vectors).

Teamcity run successfully: [build 
#952371|https://ci.ignite.apache.org/viewLog.html?buildId=952371=buildResultsDiv=Ignite20Tests_IgniteMl].
 Licenses and javadoc check also passed at Teamcity: [build 
#958251|https://ci.ignite.apache.org/viewLog.html?buildId=958251=queuedBuildOverviewTab].

[~chief], could you please take a look?


was (Author: oignatenko):
Ready to merge: [pull request #3069|https://github.com/apache/ignite/pull/3069].

Compared to prior / draft implementation there are not many changes; 
IGNITE-5846 made impact only on code in example where I had to change local 
vector to distributed one (not surprising given that ticket 5846 involved 
improving consistency of "like" functionality of distributed matrices and 
vectors).

Teamcity run successfully: [build 
#952371|https://ci.ignite.apache.org/viewLog.html?buildId=952371=buildResultsDiv=Ignite20Tests_IgniteMl].
 Licenses and javadoc check also passed at Teamcity: [build 
#952678|https://ci.ignite.apache.org/viewLog.html?buildId=952678=queuedBuildOverviewTab].

[~chief], could you please take a look?

> Linear regression should implement Model API
> 
>
> Key: IGNITE-6872
> URL: https://issues.apache.org/jira/browse/IGNITE-6872
> Project: Ignite
>  Issue Type: Task
>  Components: ml
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
> Fix For: 2.4
>
>
> When linear regression was originally implemented per IGNITE-5012 we had no 
> Model API.
> Now that this API is available (merged into master with IGNITE-5218) lin 
> regression needs to adapt to implement it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6991) SharedDeploymentTest.testDeploymentFromSecondAndThird Test fails in 100 percentage cases

[Dmitriy Pavlov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-6991:
---
Labels: MakeTeamcityGreenAgain  (was: )

> SharedDeploymentTest.testDeploymentFromSecondAndThird Test fails in 100 
> percentage cases
> 
>
> Key: IGNITE-6991
> URL: https://issues.apache.org/jira/browse/IGNITE-6991
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vladislav Pyatkov
>  Labels: MakeTeamcityGreenAgain
>
> {noformat}
> java.lang.ClassNotFoundException: 
> org.apache.ignite.tests.p2p.compute.ExternalCallable2
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at 
> org.apache.ignite.testframework.GridTestExternalClassLoader.findClass(GridTestExternalClassLoader.java:143)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at 
> org.apache.ignite.testframework.GridTestExternalClassLoader.loadClass(GridTestExternalClassLoader.java:152)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at 
> org.apache.ignite.p2p.SharedDeploymentTest.runJob2(SharedDeploymentTest.java:124)
> at 
> org.apache.ignite.p2p.SharedDeploymentTest.testDeploymentFromSecondAndThird(SharedDeploymentTest.java:82)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6992) Ignite MR problem with accessing hdfs with enabled Kerberos

[Evgenii Zhuravlev (JIRA)]

Evgenii Zhuravlev created IGNITE-6992:
-

 Summary: Ignite MR problem with accessing hdfs with enabled 
Kerberos
 Key: IGNITE-6992
 URL: https://issues.apache.org/jira/browse/IGNITE-6992
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3, 2.1, 2.0
Reporter: Evgenii Zhuravlev


class org.apache.ignite.IgniteCheckedException: SIMPLE authentication is not 
enabled.  Available:[TOKEN, KERBEROS]
at 
org.apache.ignite.internal.processors.hadoop.impl.v2.HadoopV2JobResourceManager.prepareJobEnvironment(HadoopV2JobResourceManager.java:169)
at 
org.apache.ignite.internal.processors.hadoop.impl.v2.HadoopV2Job.initialize(HadoopV2Job.java:328)
at 
org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker.job(HadoopJobTracker.java:1141)
at 
org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker.submit(HadoopJobTracker.java:318)
at 
org.apache.ignite.internal.processors.hadoop.HadoopProcessor.submit(HadoopProcessor.java:173)
at 
org.apache.ignite.internal.processors.hadoop.HadoopImpl.submit(HadoopImpl.java:69)
at 
org.apache.ignite.internal.processors.hadoop.proto.HadoopProtocolSubmitJobTask.run(HadoopProtocolSubmitJobTask.java:50)
at 
org.apache.ignite.internal.processors.hadoop.proto.HadoopProtocolSubmitJobTask.run(HadoopProtocolSubmitJobTask.java:33)
at 
org.apache.ignite.internal.processors.hadoop.proto.HadoopProtocolTaskAdapter$Job.execute(HadoopProtocolTaskAdapter.java:101)
at 
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6629)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1181)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1908)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1562)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1190)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1097)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.hadoop.security.AccessControlException: SIMPLE 
authentication is not enabled.  Available:[TOKEN, KERBEROS]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at 
org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)
at 
org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:73)
at org.apache.hadoop.hdfs.DFSClient.getFileInfo(DFSClient.java:2110)
at 
org.apache.hadoop.hdfs.DistributedFileSystem$22.doCall(DistributedFileSystem.java:1305)
at 
org.apache.hadoop.hdfs.DistributedFileSystem$22.doCall(DistributedFileSystem.java:1301)
at 
org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
at 
org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1301)
at org.apache.hadoop.fs.FileSystem.exists(FileSystem.java:1426)
at 
org.apache.ignite.internal.processors.hadoop.impl.v2.HadoopV2JobResourceManager.prepareJobEnvironment(HadoopV2JobResourceManager.java:136)
... 22 more
Caused by: 
org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException):
 SIMPLE authentication is not enabled.  Available:[TOKEN, KERBEROS]
at org.apache.hadoop.ipc.Client.call(Client.java:1475)
at org.apache.hadoop.ipc.Client.call(Client.java:1412)
at 
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
at com.sun.proxy.$Proxy36.getFileInfo(Unknown Source)
at 

[jira] [Commented] (IGNITE-6872) Linear regression should implement Model API

[Oleg Ignatenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262505#comment-16262505
 ] 

Oleg Ignatenko commented on IGNITE-6872:


per discussion with Yury, we may want to reconsider original decision and try 
implementing Trainer API in the scope of this ticket because this way there 
seems to be a chance to get better Model implementation

> Linear regression should implement Model API
> 
>
> Key: IGNITE-6872
> URL: https://issues.apache.org/jira/browse/IGNITE-6872
> Project: Ignite
>  Issue Type: Task
>  Components: ml
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
> Fix For: 2.4
>
>
> When linear regression was originally implemented per IGNITE-5012 we had no 
> Model API.
> Now that this API is available (merged into master with IGNITE-5218) lin 
> regression needs to adapt to implement it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6992) Ignite MR problem with accessing hdfs with enabled Kerberos

[Evgenii Zhuravlev (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Evgenii Zhuravlev updated IGNITE-6992:
--
Description: 

{code:java}
class org.apache.ignite.IgniteCheckedException: SIMPLE authentication is not 
enabled.  Available:[TOKEN, KERBEROS]
at 
org.apache.ignite.internal.processors.hadoop.impl.v2.HadoopV2JobResourceManager.prepareJobEnvironment(HadoopV2JobResourceManager.java:169)
at 
org.apache.ignite.internal.processors.hadoop.impl.v2.HadoopV2Job.initialize(HadoopV2Job.java:328)
at 
org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker.job(HadoopJobTracker.java:1141)
at 
org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker.submit(HadoopJobTracker.java:318)
at 
org.apache.ignite.internal.processors.hadoop.HadoopProcessor.submit(HadoopProcessor.java:173)
at 
org.apache.ignite.internal.processors.hadoop.HadoopImpl.submit(HadoopImpl.java:69)
at 
org.apache.ignite.internal.processors.hadoop.proto.HadoopProtocolSubmitJobTask.run(HadoopProtocolSubmitJobTask.java:50)
at 
org.apache.ignite.internal.processors.hadoop.proto.HadoopProtocolSubmitJobTask.run(HadoopProtocolSubmitJobTask.java:33)
at 
org.apache.ignite.internal.processors.hadoop.proto.HadoopProtocolTaskAdapter$Job.execute(HadoopProtocolTaskAdapter.java:101)
at 
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6629)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1181)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1908)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1562)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1190)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1097)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.hadoop.security.AccessControlException: SIMPLE 
authentication is not enabled.  Available:[TOKEN, KERBEROS]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at 
org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)
at 
org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:73)
at org.apache.hadoop.hdfs.DFSClient.getFileInfo(DFSClient.java:2110)
at 
org.apache.hadoop.hdfs.DistributedFileSystem$22.doCall(DistributedFileSystem.java:1305)
at 
org.apache.hadoop.hdfs.DistributedFileSystem$22.doCall(DistributedFileSystem.java:1301)
at 
org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
at 
org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1301)
at org.apache.hadoop.fs.FileSystem.exists(FileSystem.java:1426)
at 
org.apache.ignite.internal.processors.hadoop.impl.v2.HadoopV2JobResourceManager.prepareJobEnvironment(HadoopV2JobResourceManager.java:136)
... 22 more
Caused by: 
org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException):
 SIMPLE authentication is not enabled.  Available:[TOKEN, KERBEROS]
at org.apache.hadoop.ipc.Client.call(Client.java:1475)
at org.apache.hadoop.ipc.Client.call(Client.java:1412)
at 
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
at com.sun.proxy.$Proxy36.getFileInfo(Unknown Source)
at 
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getFileInfo(ClientNamenodeProtocolTranslatorPB.java:771)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 

[jira] [Created] (IGNITE-6991) SharedDeploymentTest.testDeploymentFromSecondAndThird Test fails in 100 percentage cases

[Vladislav Pyatkov (JIRA)]

Vladislav Pyatkov created IGNITE-6991:
-

 Summary: SharedDeploymentTest.testDeploymentFromSecondAndThird 
Test fails in 100 percentage cases
 Key: IGNITE-6991
 URL: https://issues.apache.org/jira/browse/IGNITE-6991
 Project: Ignite
  Issue Type: Bug
Reporter: Vladislav Pyatkov


{noformat}
java.lang.ClassNotFoundException: 
org.apache.ignite.tests.p2p.compute.ExternalCallable2
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at 
org.apache.ignite.testframework.GridTestExternalClassLoader.findClass(GridTestExternalClassLoader.java:143)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at 
org.apache.ignite.testframework.GridTestExternalClassLoader.loadClass(GridTestExternalClassLoader.java:152)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at 
org.apache.ignite.p2p.SharedDeploymentTest.runJob2(SharedDeploymentTest.java:124)
at 
org.apache.ignite.p2p.SharedDeploymentTest.testDeploymentFromSecondAndThird(SharedDeploymentTest.java:82)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-3244) Custom arrays are not serialized properly by CacheObjectBinaryProcessorImpl

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262487#comment-16262487
 ] 

ASF GitHub Bot commented on IGNITE-3244:


Github user zstan closed the pull request at:

https://github.com/apache/ignite/pull/3008


> Custom arrays are not serialized properly by CacheObjectBinaryProcessorImpl
> ---
>
> Key: IGNITE-3244
> URL: https://issues.apache.org/jira/browse/IGNITE-3244
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Vladimir Ozerov
>Priority: Minor
> Attachments: tc3.png
>
>
> If to put a custom object array into a cache like this one
> {code}
> TestObject[] arr = new TestObject[] {new TestObject(i)};
> cache.put(0, arr);
> {code}
> then it will be serialized as Object[] array in 
> {{CacheObjectBinaryProcessorImpl.marshallToBinary}} method.
> This leads to the situation when object's array type is lost and on cache.get 
> the code below produces {{ClassCastException}}
> {code}
> TestObject[] obj = cache.get(i);
> {code}
> The full test is already added into 
> {{GridCacheBinaryObjectsAbstractSelfTest.testCustomArrays}}.
> To fix the issue we have to revisit logic of 
> {{CacheObjectBinaryProcessorImpl.marshallToBinary}} and 
> {{CacheObjectContext.unwrapBinary}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6989) .NET: Thin client: Group operation codes by purpose

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn reassigned IGNITE-6989:
--

Assignee: Pavel Tupitsyn

> .NET: Thin client: Group operation codes by purpose
> ---
>
> Key: IGNITE-6989
> URL: https://issues.apache.org/jira/browse/IGNITE-6989
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Currently operation codes are in random order. Let's group things by purpose: 
> cache operations, metadata, queries, etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6990) .NET: Thin client: Remove OP_SQL_QUERY

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-6990:
--

 Summary: .NET: Thin client: Remove OP_SQL_QUERY
 Key: IGNITE-6990
 URL: https://issues.apache.org/jira/browse/IGNITE-6990
 Project: Ignite
  Issue Type: Improvement
  Components: platforms, thin client
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.4


OP_SQL_QUERY is not necessary and can be implemented on the client side with 
OP_SQL_FIELDS_QUERY.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6989) .NET: Thin client: Group operation codes by purpose

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-6989:
---
Fix Version/s: 2.4

> .NET: Thin client: Group operation codes by purpose
> ---
>
> Key: IGNITE-6989
> URL: https://issues.apache.org/jira/browse/IGNITE-6989
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Currently operation codes are in random order. Let's group things by purpose: 
> cache operations, metadata, queries, etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6989) .NET: Thin client: Group operation codes by purpose

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-6989:
--

 Summary: .NET: Thin client: Group operation codes by purpose
 Key: IGNITE-6989
 URL: https://issues.apache.org/jira/browse/IGNITE-6989
 Project: Ignite
  Issue Type: Improvement
  Components: platforms, thin client
Reporter: Pavel Tupitsyn


Currently operation codes are in random order. Let's group things by purpose: 
cache operations, metadata, queries, etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6988) .NET: Thin client: OP_DESTROY_CACHE should take cacheId instead of name

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-6988:
--

 Summary: .NET: Thin client: OP_DESTROY_CACHE should take cacheId 
instead of name
 Key: IGNITE-6988
 URL: https://issues.apache.org/jira/browse/IGNITE-6988
 Project: Ignite
  Issue Type: Bug
  Components: platforms, thin client
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.4


All cache operations take cacheId, not cache name. Fix this for 
OP_DESTROY_CACHE.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6984) Make cache creation slightly more verbose.

[Nikolay Tikhonov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262353#comment-16262353
 ] 

Nikolay Tikhonov commented on IGNITE-6984:
--

[~amashenkov],
Thank you for your contribution! It's really helpful for reading logs. I've 
fixed minor code style of issues and merged to master.

> Make cache creation slightly more verbose.
> --
>
> Key: IGNITE-6984
> URL: https://issues.apache.org/jira/browse/IGNITE-6984
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.4
>
>
> For now we do not print cacheId on cache start, but use cacheId instead of 
> name everywhere in logs.
> So, it is hard to investigate issues in production.
> Also actual number of backups can be helpful when restoring cache from 
> persistence.
> Lets, add cacheId and number of backups to the "cache start" message.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6987) Visor CMD: Config command should show client connector pool size.

[Vasiliy Sisko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vasiliy Sisko reassigned IGNITE-6987:
-

Assignee: Alexey Kuznetsov  (was: Vasiliy Sisko)

> Visor CMD: Config command should show client connector pool size.
> -
>
> Key: IGNITE-6987
> URL: https://issues.apache.org/jira/browse/IGNITE-6987
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
> Fix For: 2.4
>
>
> Now show size for deprecated SqlConnectorConfiguration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6987) Visor CMD: Config command should show client connector pool size.

[Vasiliy Sisko (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262332#comment-16262332
 ] 

Vasiliy Sisko commented on IGNITE-6987:
---

Fixed showed property to actual.

> Visor CMD: Config command should show client connector pool size.
> -
>
> Key: IGNITE-6987
> URL: https://issues.apache.org/jira/browse/IGNITE-6987
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: 2.4
>
>
> Now show size for deprecated SqlConnectorConfiguration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6962) Reduce ExchangeHistory memory consumption

[Alexander Belyak (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Belyak updated IGNITE-6962:
-
Attachment: histo18175_s1.txt

heap object histo:live for my scenario

> Reduce ExchangeHistory memory consumption
> -
>
> Key: IGNITE-6962
> URL: https://issues.apache.org/jira/browse/IGNITE-6962
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Alexander Belyak
> Attachments: histo18175_s1.txt, leak.jpg
>
>
> GridDhtPartitionExchangeManager$ExhcangeFutureSet store huge message 
> GridDhtPartitionsFullMessage with IgniteDhtPartitionCountersMap2 for each 
> cache group with two long[partCount]. If we have big grid (100+ nodes) with 
> large amount of cacheGroups and partitions in 
> CachePartitionFullCountersMap(long[] initialUpdCntrs; long[] updCntrs;)
> *<2 

[jira] [Updated] (IGNITE-6962) Reduce ExchangeHistory memory consumption

[Alexander Belyak (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Belyak updated IGNITE-6962:
-
Attachment: leak.jpg

1) Start server node igSrv
2) 
for i in 1..10:
  for j in 1..10:
igSrv.getOrCreateCache();
Option -DIGNITE_EXCHANGE_HISTORY_SIZE can limit total number of history, but 
single history entry still huge.

> Reduce ExchangeHistory memory consumption
> -
>
> Key: IGNITE-6962
> URL: https://issues.apache.org/jira/browse/IGNITE-6962
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Alexander Belyak
> Attachments: leak.jpg
>
>
> GridDhtPartitionExchangeManager$ExhcangeFutureSet store huge message 
> GridDhtPartitionsFullMessage with IgniteDhtPartitionCountersMap2 for each 
> cache group with two long[partCount]. If we have big grid (100+ nodes) with 
> large amount of cacheGroups and partitions in 
> CachePartitionFullCountersMap(long[] initialUpdCntrs; long[] updCntrs;)
> *<2 

[jira] [Created] (IGNITE-6987) Visor CMD: Config command should show client connector pool size.

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-6987:
-

 Summary: Visor CMD: Config command should show client connector 
pool size.
 Key: IGNITE-6987
 URL: https://issues.apache.org/jira/browse/IGNITE-6987
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko
 Fix For: 2.4


Now show size for deprecated SqlConnectorConfiguration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6171) Native facility to control excessive GC pauses

[Dmitriy Sorokin (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262267#comment-16262267
 ] 

Dmitriy Sorokin commented on IGNITE-6171:
-

[~avinogradov], please review my corrections.

> Native facility to control excessive GC pauses
> --
>
> Key: IGNITE-6171
> URL: https://issues.apache.org/jira/browse/IGNITE-6171
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Sorokin
>  Labels: iep-7, usability
> Fix For: 2.4
>
>
> Ignite is Java-based application. If node experiences long GC pauses it may 
> negatively affect other nodes. We need to find a way to detect long GC pauses 
> within the process and trigger some actions in response, e.g. node stop. 
> This is a kind of Inception \[1\], when you need to understand that you sleep 
> while sleeping. As all Java threads are blocked on safepoint, we cannot use 
> Java's thread to detect Java's GC. Native threads should be used instead.
> Proposed solution:
> 1) Thread 1 should periodically call dummy JNI method returning current time, 
> and set this time to shared variable;
> 2) Thread 2 should periodically check that variable. If it has not been 
> changed for some time - most likely we are in GC pause. Once certain 
> threashold is reached - trigger compensating action, whether this is a 
> warning, process kill, or what so ever.
> Justification: crossing native -> Java boundaries involves safepoints. This 
> way Thread 1 will be trapped if STW pause is in progress. Java method cannot 
> be empty, as JVM is smart enough and can deduce it to no-op. 
> \[1\] http://www.imdb.com/title/tt1375666/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-6973) Node restarts with enabled persistence lead to affinity assignment mismatch on different nodes.

[Semen Boikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov resolved IGNITE-6973.
--
Resolution: Fixed

There was a bug with deploymentId assigned to caches started during activation, 
fixed in master.

> Node restarts with enabled persistence lead to affinity assignment mismatch 
> on different nodes.
> ---
>
> Key: IGNITE-6973
> URL: https://issues.apache.org/jira/browse/IGNITE-6973
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Alexei Scherbakov
>Assignee: Semen Boikov
> Fix For: 2.4
>
>
> Most probably this is caused by deploymentId reassign after grid restart.
> All nodes must have same deploymentId in such case.
> Reproducer:
> {noformat}
> /*
>  * Licensed to the Apache Software Foundation (ASF) under one or more
>  * contributor license agreements.  See the NOTICE file distributed with
>  * this work for additional information regarding copyright ownership.
>  * The ASF licenses this file to You under the Apache License, Version 2.0
>  * (the "License"); you may not use this file except in compliance with
>  * the License.  You may obtain a copy of the License at
>  *
>  *  http://www.apache.org/licenses/LICENSE-2.0
>  *
>  * Unless required by applicable law or agreed to in writing, software
>  * distributed under the License is distributed on an "AS IS" BASIS,
>  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>  * See the License for the specific language governing permissions and
>  * limitations under the License.
>  */
> package org.apache.ignite.internal.processors.cache.persistence;
> import java.util.Arrays;
> import java.util.Collection;
> import java.util.HashMap;
> import java.util.List;
> import java.util.Map;
> import java.util.concurrent.Callable;
> import java.util.concurrent.atomic.AtomicInteger;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.cache.CacheAtomicityMode;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
> import org.apache.ignite.cluster.ClusterNode;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.MemoryConfiguration;
> import org.apache.ignite.configuration.MemoryPolicyConfiguration;
> import org.apache.ignite.configuration.PersistentStoreConfiguration;
> import org.apache.ignite.configuration.WALMode;
> import org.apache.ignite.internal.IgniteEx;
> import org.apache.ignite.internal.IgniteInternalFuture;
> import org.apache.ignite.internal.IgniteKernal;
> import org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion;
> import org.apache.ignite.internal.processors.cache.CacheGroupDescriptor;
> import org.apache.ignite.internal.processors.cache.IgniteInternalCache;
> import org.apache.ignite.internal.util.typedef.G;
> import org.apache.ignite.internal.util.typedef.internal.U;
> import org.apache.ignite.lang.IgniteUuid;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.TcpDiscoveryIpFinder;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
> import org.apache.ignite.testframework.GridTestUtils;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
> import static org.apache.ignite.cache.CacheMode.PARTITIONED;
> import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
> import static 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.IGNITE_PDS_CHECKPOINT_TEST_SKIP_SYNC;
> /**
>  * The test validates assignment after nodes restart with enabled persistence.
>  */
> public class IgnitePdsCacheAssignmentNodeRestartsTest extends 
> GridCommonAbstractTest {
> /** */
> private static TcpDiscoveryIpFinder ipFinder = new 
> TcpDiscoveryVmIpFinder(true);
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String 
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> cfg.setMemoryConfiguration(new 
> MemoryConfiguration().setDefaultMemoryPolicyName("d").
> setPageSize(1024).setMemoryPolicies(new 
> MemoryPolicyConfiguration().setName("d").
> setInitialSize(50 * 1024 * 1024L).setMaxSize(50 * 1024 * 
> 1024)));
> cfg.setPersistentStoreConfiguration(new 
> PersistentStoreConfiguration().setWalMode(WALMode.LOG_ONLY));
> 

[jira] [Assigned] (IGNITE-6973) Node restarts with enabled persistence lead to affinity assignment mismatch on different nodes.

[Semen Boikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov reassigned IGNITE-6973:


Assignee: (was: Semen Boikov)

> Node restarts with enabled persistence lead to affinity assignment mismatch 
> on different nodes.
> ---
>
> Key: IGNITE-6973
> URL: https://issues.apache.org/jira/browse/IGNITE-6973
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Alexei Scherbakov
> Fix For: 2.4
>
>
> Most probably this is caused by deploymentId reassign after grid restart.
> All nodes must have same deploymentId in such case.
> Reproducer:
> {noformat}
> /*
>  * Licensed to the Apache Software Foundation (ASF) under one or more
>  * contributor license agreements.  See the NOTICE file distributed with
>  * this work for additional information regarding copyright ownership.
>  * The ASF licenses this file to You under the Apache License, Version 2.0
>  * (the "License"); you may not use this file except in compliance with
>  * the License.  You may obtain a copy of the License at
>  *
>  *  http://www.apache.org/licenses/LICENSE-2.0
>  *
>  * Unless required by applicable law or agreed to in writing, software
>  * distributed under the License is distributed on an "AS IS" BASIS,
>  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>  * See the License for the specific language governing permissions and
>  * limitations under the License.
>  */
> package org.apache.ignite.internal.processors.cache.persistence;
> import java.util.Arrays;
> import java.util.Collection;
> import java.util.HashMap;
> import java.util.List;
> import java.util.Map;
> import java.util.concurrent.Callable;
> import java.util.concurrent.atomic.AtomicInteger;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.cache.CacheAtomicityMode;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
> import org.apache.ignite.cluster.ClusterNode;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.MemoryConfiguration;
> import org.apache.ignite.configuration.MemoryPolicyConfiguration;
> import org.apache.ignite.configuration.PersistentStoreConfiguration;
> import org.apache.ignite.configuration.WALMode;
> import org.apache.ignite.internal.IgniteEx;
> import org.apache.ignite.internal.IgniteInternalFuture;
> import org.apache.ignite.internal.IgniteKernal;
> import org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion;
> import org.apache.ignite.internal.processors.cache.CacheGroupDescriptor;
> import org.apache.ignite.internal.processors.cache.IgniteInternalCache;
> import org.apache.ignite.internal.util.typedef.G;
> import org.apache.ignite.internal.util.typedef.internal.U;
> import org.apache.ignite.lang.IgniteUuid;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.TcpDiscoveryIpFinder;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
> import org.apache.ignite.testframework.GridTestUtils;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
> import static org.apache.ignite.cache.CacheMode.PARTITIONED;
> import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
> import static 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.IGNITE_PDS_CHECKPOINT_TEST_SKIP_SYNC;
> /**
>  * The test validates assignment after nodes restart with enabled persistence.
>  */
> public class IgnitePdsCacheAssignmentNodeRestartsTest extends 
> GridCommonAbstractTest {
> /** */
> private static TcpDiscoveryIpFinder ipFinder = new 
> TcpDiscoveryVmIpFinder(true);
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String 
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> cfg.setMemoryConfiguration(new 
> MemoryConfiguration().setDefaultMemoryPolicyName("d").
> setPageSize(1024).setMemoryPolicies(new 
> MemoryPolicyConfiguration().setName("d").
> setInitialSize(50 * 1024 * 1024L).setMaxSize(50 * 1024 * 
> 1024)));
> cfg.setPersistentStoreConfiguration(new 
> PersistentStoreConfiguration().setWalMode(WALMode.LOG_ONLY));
> ((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(ipFinder);
> return cfg;
> }
> /** {@inheritDoc} */
> @Override 

[jira] [Commented] (IGNITE-6955) Update com.google.code.simple-spring-memcached:spymemcached to 2.8.4

[Nikolay Tikhonov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262236#comment-16262236
 ] 

Nikolay Tikhonov commented on IGNITE-6955:
--

[~avinogradov],
I don't have any expertise in this area. AFAIK you're committer and PMC too. 
Please, do it yourself.

> Update com.google.code.simple-spring-memcached:spymemcached to 2.8.4
> 
>
> Key: IGNITE-6955
> URL: https://issues.apache.org/jira/browse/IGNITE-6955
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Minor
> Fix For: 2.4
>
>
> Please update com.google.code.simple-spring-memcached:spymemcached to 2.8.4 
> version.
> This version does not have "netty" dependencies



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6955) Update com.google.code.simple-spring-memcached:spymemcached to 2.8.4

[Anton Vinogradov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262233#comment-16262233
 ] 

Anton Vinogradov commented on IGNITE-6955:
--

[~alexey.tank2]
Thanks.

[~ntikho...@apache.org]
Please merge to appropriate branches.

> Update com.google.code.simple-spring-memcached:spymemcached to 2.8.4
> 
>
> Key: IGNITE-6955
> URL: https://issues.apache.org/jira/browse/IGNITE-6955
> Project: Ignite
>  Issue Type: Improvement
>  Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Minor
> Fix For: 2.4
>
>
> Please update com.google.code.simple-spring-memcached:spymemcached to 2.8.4 
> version.
> This version does not have "netty" dependencies



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-6979) Race in GridClientPartitionTopology may cause NPE and partition map exchange hang.

[Alexei Scherbakov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexei Scherbakov resolved IGNITE-6979.
---
Resolution: Won't Fix

Already fixed by commit 788adc0d00e0455e06cc9acabfe9ad425fdcd65b

> Race in GridClientPartitionTopology may cause NPE and partition map exchange 
> hang.
> --
>
> Key: IGNITE-6979
> URL: https://issues.apache.org/jira/browse/IGNITE-6979
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Alexei Scherbakov
> Fix For: 2.4
>
>
> Was reproduced on TC and locally using test
> {{org.apache.ignite.internal.processors.cache.IgniteCachePartitionMapUpdateTest#testRandom}}
> Reason: discoCache is not initalized due to race before calling  
> {{GridClientPartitionTopology#nodes(int, AffinityTopologyVersion, 
> GridDhtPartitionState, GridDhtPartitionState...)}}
> Stacktrace on coordinator:
> {noformat}
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridClientPartitionTopology.nodes(GridClientPartitionTopology.java:538)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridClientPartitionTopology.owners(GridClientPartitionTopology.java:577)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridClientPartitionTopology.owners(GridClientPartitionTopology.java:582)
> at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$22.applyx(CacheAffinitySharedManager.java:2117)
> at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$22.applyx(CacheAffinitySharedManager.java:2043)
> at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllRegisteredCacheGroups(CacheAffinitySharedManager.java:1059)
> at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.initAffinityOnNodeLeft0(CacheAffinitySharedManager.java:2043)
> at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onServerLeftWithExchangeMergeProtocol(CacheAffinitySharedManager.java:1383)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:2239)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:2199)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:1936)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:116)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:1793)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:1781)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:353)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:1781)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1483)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1000(GridCachePartitionExchangeManager.java:131)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:327)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:307)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:2626)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:2605)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at 

[jira] [Updated] (IGNITE-6986) .NET: Some exceptions can't be serialized

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-6986:
---
Description: 
{{System.Exception}} may include some data that is not handled properly by 
Ignite.

For example, below is an error caused by calling {{GetCache}} from compute job 
for a cache that does not exist.

Client-side error:
{code}
System.AggregateException - One or more errors occurred.
Apache.Ignite.Core.Common.IgniteException - Remote job threw user exception 
(override or implement IComputeTask.result(..) method if you would like to have 
automatic failover for this exception).
Apache.Ignite.Core.Common.IgniteException - Compute job has failed on remote 
node, examine InnerException for details.
Apache.Ignite.Core.Common.IgniteException - Call completed with error, but 
error serialization failed [errType=ArgumentException, 
serializationErrMsg=Field type mismatch detected [fieldName=WatsonBuckets, 
expectedType=103, actualType=12]]
Apache.Ignite.Core.Common.JavaException - class 
org.apache.ignite.IgniteException: Call completed with error, but error 
serialization failed [errType=ArgumentException, serializationErrMsg=Field type 
mismatch detected [fieldName=WatsonBuckets, expectedType=103, actualType=12]]
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
at 
org.apache.ignite.internal.processors.platform.compute.PlatformAbstractJob.execute(PlatformAbstractJob.java:83)
at 
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6629)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1181)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1908)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1097)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: Call completed with 
error, but error serialization failed [errType=ArgumentException, 
serializationErrMsg=Field type mismatch detected [fieldName=WatsonBuckets, 
expectedType=103, actualType=12]]
at 
org.apache.ignite.internal.processors.platform.utils.PlatformUtils.readInvocationResult(PlatformUtils.java:834)
at 
org.apache.ignite.internal.processors.platform.compute.PlatformFullJob.execute0(PlatformFullJob.java:134)
at 
org.apache.ignite.internal.processors.platform.compute.PlatformAbstractJob.execute(PlatformAbstractJob.java:80)
... 14 more (edited)
{code}

Server-side error:
{code}
at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.Error(Void* target, I
nt32 errType, SByte* errClsChars, Int32 errClsCharsLen, SByte* errMsgChars, Int3
2 errMsgCharsLen, SByte* stackTraceChars, Int32 stackTraceCharsLen, Void* errDat
a, Int32 errDataLen)
   at Apache.Ignite.Core.Impl.Unmanaged.IgniteJniNativeMethods.ProcessorCache(Vo
id* ctx, Void* obj, SByte* name)
   at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.ProcessorCache(IUnmanaged
Target target, String name)
   at Apache.Ignite.Core.Impl.Ignite.GetCache[TK,TV](String name)
   at To.ProductEngine.Service.Framework.Ignite.Caches.BaseCacheObject`2.GetCach
e(IIgnite ignite) in C:\Users\mgriggs\Source\Repos\development\To.ProductEngine.
Service.Framework\Ignite\Caches\BaseCacheObject.cs:line 71
   at To.ProductEngine.Service.Closures.Flight.CheapestFlightComputeJob.Execute(
) in C:\Users\mgriggs\Source\Repos\development\To.ProductEngine.Service.Closures
\Flight\CheapestFlightComputeJob.cs:line 57
System.ArgumentException: Cache doesn't exist: Flight_FlightComponent_Cache --->
 Apache.Ignite.Core.Common.JavaException: java.lang.IllegalArgumentException: Ca
che doesn't exist: Flight_FlightComponent_Cache
at org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.
cache(PlatformProcessorImpl.java:225)
at org.apache.ignite.internal.processors.platform.callback.PlatformCallb

[jira] [Created] (IGNITE-6986) .NET: Some exceptions can't be serialized

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-6986:
--

 Summary: .NET: Some exceptions can't be serialized
 Key: IGNITE-6986
 URL: https://issues.apache.org/jira/browse/IGNITE-6986
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 2.3
Reporter: Pavel Tupitsyn
 Fix For: 2.4


{{System.Exception}} may include some data that is not handled properly by 
Ignite.

For example, below is an error caused by calling {{GetCache}} from compute job 
for a cache that does not exist.

Client-side error:
{code}
System.AggregateException - One or more errors occurred.
Apache.Ignite.Core.Common.IgniteException - Remote job threw user exception 
(override or implement IComputeTask.result(..) method if you would like to have 
automatic failover for this exception).
Apache.Ignite.Core.Common.IgniteException - Compute job has failed on remote 
node, examine InnerException for details.
Apache.Ignite.Core.Common.IgniteException - Call completed with error, but 
error serialization failed [errType=ArgumentException, 
serializationErrMsg=Field type mismatch detected [fieldName=WatsonBuckets, 
expectedType=103, actualType=12]]
Apache.Ignite.Core.Common.JavaException - class 
org.apache.ignite.IgniteException: Call completed with error, but error 
serialization failed [errType=ArgumentException, serializationErrMsg=Field type 
mismatch detected [fieldName=WatsonBuckets, expectedType=103, actualType=12]]
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
at 
org.apache.ignite.internal.processors.platform.compute.PlatformAbstractJob.execute(PlatformAbstractJob.java:83)
at 
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6629)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1181)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1908)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1097)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: Call completed with 
error, but error serialization failed [errType=ArgumentException, 
serializationErrMsg=Field type mismatch detected [fieldName=WatsonBuckets, 
expectedType=103, actualType=12]]
at 
org.apache.ignite.internal.processors.platform.utils.PlatformUtils.readInvocationResult(PlatformUtils.java:834)
at 
org.apache.ignite.internal.processors.platform.compute.PlatformFullJob.execute0(PlatformFullJob.java:134)
at 
org.apache.ignite.internal.processors.platform.compute.PlatformAbstractJob.execute(PlatformAbstractJob.java:80)
... 14 more (edited)
{code}

Server-side error:
{code}
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-4452) Web console: add execution time to results panel on Queries screen

[Alexander Kalinin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Kalinin reassigned IGNITE-4452:
-

Assignee: Pavel Konstantinov  (was: Alexander Kalinin)

Adjusted colums width. Please test

> Web console: add execution time to results panel on Queries screen
> --
>
> Key: IGNITE-4452
> URL: https://issues.apache.org/jira/browse/IGNITE-4452
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Trivial
> Attachments: screenshot-1.png
>
>
> I think it may be useful to know query last execution time, especially if we 
> have a Refresh rate possibility.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (IGNITE-6802) NullPointerException when WAL store and WAL archive paths are same

[Ryabov Dmitrii (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryabov Dmitrii updated IGNITE-6802:
---
Comment: was deleted

(was: Misclick - from In progress it should be moved to patch available.)

> NullPointerException when WAL store and WAL archive paths are same 
> ---
>
> Key: IGNITE-6802
> URL: https://issues.apache.org/jira/browse/IGNITE-6802
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Alexey Kukushkin
>Assignee: Ryabov Dmitrii
>  Labels: newbie, usability
> Fix For: 2.4
>
>
> Configuring WAL store and WAL archive paths to be the same results in 
> NullPointerException. We should display a meaningful error about the 
> misconfiguration instead.
> See 
> http://apache-ignite-users.70518.x6.nabble.com/NullPointerException-in-FileWriteAheadLogManager-java-1313-tc17860.html
> The thread includes the reproducer code and stack trace. I was able to 
> reproduce the issue with today's (31-Oct-2017) Apache master.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6711) DataRegionMetrics#totalAllocatedPages is not valid after node restart

[Andrey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Kuznetsov reassigned IGNITE-6711:


Assignee: Andrey Kuznetsov

> DataRegionMetrics#totalAllocatedPages is not valid after node restart
> -
>
> Key: IGNITE-6711
> URL: https://issues.apache.org/jira/browse/IGNITE-6711
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.2
>Reporter: Alexey Goncharuk
>Assignee: Andrey Kuznetsov
>  Labels: newbie
> Fix For: 2.4
>
>
> Currently, data region metric tracks total allocated pages by a callback on 
> page allocation. However, when a node with enabled persistence is started, 
> some of the pages are already allocated, which leads to an incorrect metric 
> value.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6985) Wrong value of RebalancingStartTime cache metric

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262202#comment-16262202
 ] 

ASF GitHub Bot commented on IGNITE-6985:


GitHub user alex-plekhanov opened a pull request:

https://github.com/apache/ignite/pull/3080

IGNITE-6985 Wrong value of RebalancingStartTime cache metric



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/alex-plekhanov/ignite ignite-6985

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3080.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 #3080


commit 64f07ce774e88d7bb83c5fddfdcaf59ef28a7f79
Author: Aleksey Plekhanov 
Date:   2017-11-22T09:24:50Z

IGNITE-6985 Wrong value of RebalancingStartTime cache metric




> Wrong value of RebalancingStartTime cache metric
> 
>
> Key: IGNITE-6985
> URL: https://issues.apache.org/jira/browse/IGNITE-6985
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>  Labels: jmx
>
> If "rebalance delay" property is set in the cache configuration and more then 
> one nodes are joined cluster in a period of rebalance delay then cache metric 
> RebalancingStartTime has wrong value (for example, metric value is 
> 4534024989722 when currentTimeMillis is 1511341657692 and rebalance delay is 
> 5000).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6985) Wrong value of RebalancingStartTime cache metric

[Aleksey Plekhanov (JIRA)]

Aleksey Plekhanov created IGNITE-6985:
-

 Summary: Wrong value of RebalancingStartTime cache metric
 Key: IGNITE-6985
 URL: https://issues.apache.org/jira/browse/IGNITE-6985
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.3
Reporter: Aleksey Plekhanov
Assignee: Aleksey Plekhanov


If "rebalance delay" property is set in the cache configuration and more then 
one nodes are joined cluster in a period of rebalance delay then cache metric 
RebalancingStartTime has wrong value (for example, metric value is 
4534024989722 when currentTimeMillis is 1511341657692 and rebalance delay is 
5000).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-4398) Web console: incorrect authentication under IE 11 (windows 10)

[Alexander Kalinin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Kalinin reassigned IGNITE-4398:
-

Assignee: Pavel Konstantinov  (was: Alexander Kalinin)

Fixed. Please test

> Web console: incorrect authentication under IE 11 (windows 10)
> --
>
> Key: IGNITE-4398
> URL: https://issues.apache.org/jira/browse/IGNITE-4398
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>  Time Spent: 0.1m
>  Remaining Estimate: 0h
>
> To reproduce:
> 1) log in as User1
> 2) create some cluster and save
> 3) log out
> 4) log in as User2
> You will see the cluster from User1.
> Note: IE specific only



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6984) Make cache creation slightly more verbose.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-6984:
-
Description: 
For now we do not print cacheId on cache start, but use cacheId instead of name 
everywhere in logs.
So, it is hard to investigate issues in production.
Also actual number of backups can be helpful when restoring cache from 
persistence.

Lets, add cacheId and number of backups to the "cache start" message.

  was:
For now we do not print cacheId on cache start, but use cacheId instead of name 
everywhere in logs.
So, it is hard to investigate issues in production.

Lets, add cacheId to the "cache start" message.


> Make cache creation slightly more verbose.
> --
>
> Key: IGNITE-6984
> URL: https://issues.apache.org/jira/browse/IGNITE-6984
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.4
>
>
> For now we do not print cacheId on cache start, but use cacheId instead of 
> name everywhere in logs.
> So, it is hard to investigate issues in production.
> Also actual number of backups can be helpful when restoring cache from 
> persistence.
> Lets, add cacheId and number of backups to the "cache start" message.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6984) Make cache creation slightly more verbose.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262131#comment-16262131
 ] 

ASF GitHub Bot commented on IGNITE-6984:


GitHub user AMashenkov opened a pull request:

https://github.com/apache/ignite/pull/3078

IGNITE-6984: Make cache creation slightly more verbose.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-6984

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3078.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 #3078


commit bb89ad4d90f4da79eba3e5170f71499c6700ee96
Author: Andrey V. Mashenkov 
Date:   2017-11-22T08:19:32Z

IGNITE-6984: Make cache creation slightly more verbose.




> Make cache creation slightly more verbose.
> --
>
> Key: IGNITE-6984
> URL: https://issues.apache.org/jira/browse/IGNITE-6984
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.4
>
>
> For now we do not print cacheId on cache start, but use cacheId instead of 
> name everywhere in logs.
> So, it is hard to investigate issues in production.
> Lets, add cacheId to the "cache start" message.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6984) Make cache creation slightly more verbose.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov reassigned IGNITE-6984:


Assignee: Andrew Mashenkov

> Make cache creation slightly more verbose.
> --
>
> Key: IGNITE-6984
> URL: https://issues.apache.org/jira/browse/IGNITE-6984
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.4
>
>
> For now we do not print cacheId on cache start, but use cacheId instead of 
> name everywhere in logs.
> So, it is hard to investigate issues in production.
> Lets, add cacheId to the "cache start" message.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6984) Make cache creation slightly more verbose.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-6984:
-
Fix Version/s: 2.4

> Make cache creation slightly more verbose.
> --
>
> Key: IGNITE-6984
> URL: https://issues.apache.org/jira/browse/IGNITE-6984
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Andrew Mashenkov
> Fix For: 2.4
>
>
> For now we do not print cacheId on cache start, but use cacheId instead of 
> name everywhere in logs.
> So, it is hard to investigate issues in production.
> Lets, add cacheId to the "cache start" message.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6984) Make cache creation slightly more verbose.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-6984:


 Summary: Make cache creation slightly more verbose.
 Key: IGNITE-6984
 URL: https://issues.apache.org/jira/browse/IGNITE-6984
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Reporter: Andrew Mashenkov


For now we do not print cacheId on cache start, but use cacheId instead of name 
everywhere in logs.
So, it is hard to investigate issues in production.

Lets, add cacheId to the "cache start" message.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)