[jira] [Commented] (IGNITE-7292) Optimize Ignite main page load performance

[Prachi Garg (JIRA)]

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

Prachi Garg commented on IGNITE-7292:
-

1. Updated css version and merged the patch. 
2. Updated index.html and javascript (use data-src attribute) to lazy-load 
youtube videos.


> Optimize Ignite main page load performance
> --
>
> Key: IGNITE-7292
> URL: https://issues.apache.org/jira/browse/IGNITE-7292
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Blocker
> Fix For: 2.4
>
> Attachments: Screen Shot 2017-12-22 at 9.49.02 AM.png
>
>
> Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
> it completely. That might affect the SEO optimizations we've done so far. 
> These are immediate actions to alleviate the situation: 
> # Reduce banner and all the images size to 72 ppi resolution and save in the 
> JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
> screencasts were already changed, just need to regenerate the CSS and merge 
> the patch.
> # The next fierce contributors to the poor performance are screencasts 
> youtube videos. It takes 700ms for each screencast to make a roundtrip to 
> YouTube. See the screenshot attached where 3 base.js calls are triggered by 
> the video links. This has to be done asynchronously.
> # Preload GitHub, Twitter butten and feed asynchronously too.
> The overall goal of this optimization is to speed up the loading at least to 
> 2.0 seconds.



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

[jira] [Commented] (IGNITE-7291) Apache Ignite "in use at" section

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan commented on IGNITE-7291:
---

https://www.youtube.com/watch?v=RxWLt3x_yBk

> Apache Ignite "in use at" section
> -
>
> Key: IGNITE-7291
> URL: https://issues.apache.org/jira/browse/IGNITE-7291
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.4
>
>
> Put together a list of publicly disclosed Apache Ignite use cases and present 
> them on the main page right below the benefits. The "Ignite is in use at" 
> section might be like Cassandra's "PROVEN" section:
> http://cassandra.apache.org
> A list of the known use cases:
> * 
> https://www.imcsummit.org/us/sessions/implementation-investment-book-record-ibor-using-apache-ignitegridgain
> * 
> https://www.imcsummit.org/us/sessions/high-availability-and-disaster-recovery-imdg
> * https://www.imcsummit.org/us/sessions/ignite-compute-grid-in-cloud
> * https://youtu.be/1D8hyLWMtfM
> * 
> https://www.imcsummit.org/us/sessions/how-in-memory-solutions-can-assist-saas-integrations
> * https://www.youtube.com/watch?v=RxWLt3x_yBk



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

[jira] [Updated] (IGNITE-7291) Apache Ignite "in use at" section

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-7291:

Description: 
Put together a list of publicly disclosed Apache Ignite use cases and present 
them on the main page right below the benefits. The "Ignite is in use at" 
section might be like Cassandra's "PROVEN" section:
http://cassandra.apache.org

A list of the known use cases:
* 
https://www.imcsummit.org/us/sessions/implementation-investment-book-record-ibor-using-apache-ignitegridgain
* 
https://www.imcsummit.org/us/sessions/high-availability-and-disaster-recovery-imdg
* https://www.imcsummit.org/us/sessions/ignite-compute-grid-in-cloud
* https://youtu.be/1D8hyLWMtfM
* 
https://www.imcsummit.org/us/sessions/how-in-memory-solutions-can-assist-saas-integrations
* https://www.youtube.com/watch?v=RxWLt3x_yBk

  was:
Put together a list of publicly disclosed Apache Ignite use cases and present 
them on the main page right below the benefits. The "Ignite is in use at" 
section might be like Cassandra's "PROVEN" section:
http://cassandra.apache.org

A list of the known use cases:
* 
https://www.imcsummit.org/us/sessions/implementation-investment-book-record-ibor-using-apache-ignitegridgain
* 
https://www.imcsummit.org/us/sessions/high-availability-and-disaster-recovery-imdg
* https://www.imcsummit.org/us/sessions/ignite-compute-grid-in-cloud
* https://youtu.be/1D8hyLWMtfM
* 
https://www.imcsummit.org/us/sessions/how-in-memory-solutions-can-assist-saas-integrations



> Apache Ignite "in use at" section
> -
>
> Key: IGNITE-7291
> URL: https://issues.apache.org/jira/browse/IGNITE-7291
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.4
>
>
> Put together a list of publicly disclosed Apache Ignite use cases and present 
> them on the main page right below the benefits. The "Ignite is in use at" 
> section might be like Cassandra's "PROVEN" section:
> http://cassandra.apache.org
> A list of the known use cases:
> * 
> https://www.imcsummit.org/us/sessions/implementation-investment-book-record-ibor-using-apache-ignitegridgain
> * 
> https://www.imcsummit.org/us/sessions/high-availability-and-disaster-recovery-imdg
> * https://www.imcsummit.org/us/sessions/ignite-compute-grid-in-cloud
> * https://youtu.be/1D8hyLWMtfM
> * 
> https://www.imcsummit.org/us/sessions/how-in-memory-solutions-can-assist-saas-integrations
> * https://www.youtube.com/watch?v=RxWLt3x_yBk



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

[jira] [Updated] (IGNITE-7292) Optimize Ignite main page load performance

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-7292:

Description: 
Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
it completely. That might affect the SEO optimizations we've done so far. These 
are immediate actions to alleviate the situation: 
# Reduce banner and all the images size to 72 ppi resolution and save in the 
JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
screencasts were already changed, just need to regenerate the CSS and merge the 
patch.
# The next fierce contributors to the poor performance are screencasts youtube 
videos. It takes 700ms for each screencast to make a roundtrip to YouTube. See 
the screenshot attached where 3 base.js calls are triggered by the video links. 
This has to be done asynchronously.
# Preload GitHub, Twitter butten and feed asynchronously too.

The overall goal of this optimization is to speed up the loading at least to 
2.0 seconds.


  was:
Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
it completely. That might affect the SEO optimizations we've done so far. These 
are immediate actions to alleviate the situation: 
# Reduce banner and all the images size to 72 ppi resolution and save in the 
JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
screencasts were already changed, just need to regenerate the CSS and merge the 
patch.
# The next fierce contributors to the poor performance are screencasts youtube 
videos. It takes 700ms for each screencast to make a roundtrip to YouTube. See 
the screenshot attached where 3 base.js calls are triggered by the video links. 
This has to be done asynchronously.
# Preload GitHub, Twitter butten and feed asynchronously too.

The overall goal of this optimization is to speed up the loading at least to 
2.5 seconds (no more).



> Optimize Ignite main page load performance
> --
>
> Key: IGNITE-7292
> URL: https://issues.apache.org/jira/browse/IGNITE-7292
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Blocker
> Fix For: 2.4
>
> Attachments: Screen Shot 2017-12-22 at 9.49.02 AM.png
>
>
> Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
> it completely. That might affect the SEO optimizations we've done so far. 
> These are immediate actions to alleviate the situation: 
> # Reduce banner and all the images size to 72 ppi resolution and save in the 
> JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
> screencasts were already changed, just need to regenerate the CSS and merge 
> the patch.
> # The next fierce contributors to the poor performance are screencasts 
> youtube videos. It takes 700ms for each screencast to make a roundtrip to 
> YouTube. See the screenshot attached where 3 base.js calls are triggered by 
> the video links. This has to be done asynchronously.
> # Preload GitHub, Twitter butten and feed asynchronously too.
> The overall goal of this optimization is to speed up the loading at least to 
> 2.0 seconds.



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

[jira] [Updated] (IGNITE-7292) Optimize Ignite main page load performance

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-7292:

Description: 
Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
it completely. That might affect the SEO optimizations we've done so far. These 
are immediate actions to alleviate the situation: 
# Reduce banner and all the images size to 72 ppi resolution and save in the 
JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
screencasts were already changed, just need to regenerate the CSS and merge the 
patch.
# The next fierce contributors to the poor performance are screencasts youtube 
videos. It takes 700ms for each screencast to make a roundtrip to YouTube. See 
the screenshot attached where 3 base.js calls are triggered by the video links. 
This has to be done asynchronously.
# Preload GitHub, Twitter butten and feed asynchronously too.

The overall goal of this optimization is to speed up the loading at least to 
2.5 seconds (no more).


  was:
Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
it completely. That might affect the SEO optimizations we've done so far. These 
are immediate actions to alleviate the situation: 
# Reduce banner and all the images size to 72 ppi resolution and save in the 
JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
screencasts were already changed, just need to regenerate the CSS and merge the 
patch.
# The next fierce contributors to the poor performance are screencasts youtube 
videos. It takes 700ms for each screencast to make a roundtrip to YouTube. See 
the screenshot attached where 3 base.js calls are triggered by the video links. 
This has to be done asynchronously.
# Preload GitHub, Twitter butten and feed asynchronously too.

The overall goal of this optimization is to speed up the loading to 2.5 seconds 
(no more).



> Optimize Ignite main page load performance
> --
>
> Key: IGNITE-7292
> URL: https://issues.apache.org/jira/browse/IGNITE-7292
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Blocker
> Fix For: 2.4
>
> Attachments: Screen Shot 2017-12-22 at 9.49.02 AM.png
>
>
> Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
> it completely. That might affect the SEO optimizations we've done so far. 
> These are immediate actions to alleviate the situation: 
> # Reduce banner and all the images size to 72 ppi resolution and save in the 
> JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
> screencasts were already changed, just need to regenerate the CSS and merge 
> the patch.
> # The next fierce contributors to the poor performance are screencasts 
> youtube videos. It takes 700ms for each screencast to make a roundtrip to 
> YouTube. See the screenshot attached where 3 base.js calls are triggered by 
> the video links. This has to be done asynchronously.
> # Preload GitHub, Twitter butten and feed asynchronously too.
> The overall goal of this optimization is to speed up the loading at least to 
> 2.5 seconds (no more).



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

[jira] [Updated] (IGNITE-7292) Optimize Ignite main page load performance

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-7292:

Description: 
Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
it completely. That might affect the SEO optimizations we've done so far. These 
are immediate actions to alleviate the situation: 
# Reduce banner and all the images size to 72 ppi resolution and save in the 
JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
screencasts were already changed, just need to regenerate the CSS and merge the 
patch.
# The next fierce contributors to the poor performance are screencasts youtube 
videos. It takes 700ms for each screencast to make a roundtrip to YouTube. See 
the screenshot attached where 3 base.js calls are triggered by the video links. 
This has to be done asynchronously.
# Preload GitHub, Twitter butter and feed asynchronously too.

The overall goal of this optimization is to speed up the loading to 2.5 seconds 
(no more).


  was:
Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
it completely. That might affect the SEO optimizations we've done so far. These 
are immediate actions to alleviate the situation: 
# Reduce banner and all the images size to 72 ppi resolution and save in the 
JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
screencasts were already changed, just need to regenerate the CSS and merge the 
patch.
# The next fierce contributors to the poor performance are screencasts youtube 
video. It takes 700ms for each screencast to make a roundtrip to YouTube. See 
the screenshot attached where 3 base.js calls are triggered by the video links. 
This has to be done asynchronously.
# Preload GitHub, Twitter butter and feed asynchronously too.

The overall goal of this optimization is to speed up the loading to 2.5 seconds 
(no more).



> Optimize Ignite main page load performance
> --
>
> Key: IGNITE-7292
> URL: https://issues.apache.org/jira/browse/IGNITE-7292
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Blocker
> Fix For: 2.4
>
> Attachments: Screen Shot 2017-12-22 at 9.49.02 AM.png
>
>
> Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
> it completely. That might affect the SEO optimizations we've done so far. 
> These are immediate actions to alleviate the situation: 
> # Reduce banner and all the images size to 72 ppi resolution and save in the 
> JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
> screencasts were already changed, just need to regenerate the CSS and merge 
> the patch.
> # The next fierce contributors to the poor performance are screencasts 
> youtube videos. It takes 700ms for each screencast to make a roundtrip to 
> YouTube. See the screenshot attached where 3 base.js calls are triggered by 
> the video links. This has to be done asynchronously.
> # Preload GitHub, Twitter butter and feed asynchronously too.
> The overall goal of this optimization is to speed up the loading to 2.5 
> seconds (no more).



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

[jira] [Updated] (IGNITE-7292) Optimize Ignite main page load performance

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-7292:

Description: 
Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
it completely. That might affect the SEO optimizations we've done so far. These 
are immediate actions to alleviate the situation: 
# Reduce banner and all the images size to 72 ppi resolution and save in the 
JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
screencasts were already changed, just need to regenerate the CSS and merge the 
patch.
# The next fierce contributors to the poor performance are screencasts youtube 
videos. It takes 700ms for each screencast to make a roundtrip to YouTube. See 
the screenshot attached where 3 base.js calls are triggered by the video links. 
This has to be done asynchronously.
# Preload GitHub, Twitter butten and feed asynchronously too.

The overall goal of this optimization is to speed up the loading to 2.5 seconds 
(no more).


  was:
Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
it completely. That might affect the SEO optimizations we've done so far. These 
are immediate actions to alleviate the situation: 
# Reduce banner and all the images size to 72 ppi resolution and save in the 
JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
screencasts were already changed, just need to regenerate the CSS and merge the 
patch.
# The next fierce contributors to the poor performance are screencasts youtube 
videos. It takes 700ms for each screencast to make a roundtrip to YouTube. See 
the screenshot attached where 3 base.js calls are triggered by the video links. 
This has to be done asynchronously.
# Preload GitHub, Twitter butter and feed asynchronously too.

The overall goal of this optimization is to speed up the loading to 2.5 seconds 
(no more).



> Optimize Ignite main page load performance
> --
>
> Key: IGNITE-7292
> URL: https://issues.apache.org/jira/browse/IGNITE-7292
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Blocker
> Fix For: 2.4
>
> Attachments: Screen Shot 2017-12-22 at 9.49.02 AM.png
>
>
> Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
> it completely. That might affect the SEO optimizations we've done so far. 
> These are immediate actions to alleviate the situation: 
> # Reduce banner and all the images size to 72 ppi resolution and save in the 
> JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
> screencasts were already changed, just need to regenerate the CSS and merge 
> the patch.
> # The next fierce contributors to the poor performance are screencasts 
> youtube videos. It takes 700ms for each screencast to make a roundtrip to 
> YouTube. See the screenshot attached where 3 base.js calls are triggered by 
> the video links. This has to be done asynchronously.
> # Preload GitHub, Twitter butten and feed asynchronously too.
> The overall goal of this optimization is to speed up the loading to 2.5 
> seconds (no more).



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

[jira] [Updated] (IGNITE-7292) Optimize Ignite main page load performance

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-7292:

Description: 
Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
it completely. That might affect the SEO optimizations we've done so far. These 
are immediate actions to alleviate the situation: 
# Reduce banner and all the images size to 72 ppi resolution and save in the 
JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
screencasts were already changed, just need to regenerate the CSS and merge the 
patch.
# The next fierce contributors to the poor performance are screencasts youtube 
video. It takes 700ms for each screencast to make a roundtrip to YouTube. See 
the screenshot attached where 3 base.js calls are triggered by the video links. 
This has to be done asynchronously.
# Preload GitHub, Twitter butter and feed asynchronously too.

The overall goal of this optimization is to speed up the loading to 2.5 seconds 
(no more).


  was:
Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
in completely. That might affect the SEO optimizations we've done so far. These 
are immediate actions to alleviate the situation: 
# Reduce banner and all the images size to 72 ppi resolution and save in the 
JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
screencasts were already changed, just need to regenerate the CSS and merge the 
patch.
# The next fierce contributors to the poor performance are screencasts youtube 
video. It takes 700ms for each screencast to make a roundtrip to YouTube. See 
the screenshot attached where 3 base.js calls are triggered by the video links. 
This has to be done asynchronously.
# Preload GitHub, Twitter butter and feed asynchronously too.

The overall goal of this optimization is to speed up the loading to 2.5 seconds 
(no more).



> Optimize Ignite main page load performance
> --
>
> Key: IGNITE-7292
> URL: https://issues.apache.org/jira/browse/IGNITE-7292
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Blocker
> Fix For: 2.4
>
> Attachments: Screen Shot 2017-12-22 at 9.49.02 AM.png
>
>
> Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
> it completely. That might affect the SEO optimizations we've done so far. 
> These are immediate actions to alleviate the situation: 
> # Reduce banner and all the images size to 72 ppi resolution and save in the 
> JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
> screencasts were already changed, just need to regenerate the CSS and merge 
> the patch.
> # The next fierce contributors to the poor performance are screencasts 
> youtube video. It takes 700ms for each screencast to make a roundtrip to 
> YouTube. See the screenshot attached where 3 base.js calls are triggered by 
> the video links. This has to be done asynchronously.
> # Preload GitHub, Twitter butter and feed asynchronously too.
> The overall goal of this optimization is to speed up the loading to 2.5 
> seconds (no more).



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

[jira] [Created] (IGNITE-7292) Optimize Ignite main page load performance

[Denis Magda (JIRA)]

Denis Magda created IGNITE-7292:
---

 Summary: Optimize Ignite main page load performance
 Key: IGNITE-7292
 URL: https://issues.apache.org/jira/browse/IGNITE-7292
 Project: Ignite
  Issue Type: Task
Reporter: Denis Magda
Assignee: Prachi Garg
Priority: Blocker
 Fix For: 2.4
 Attachments: Screen Shot 2017-12-22 at 9.49.02 AM.png

Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
in completely. That might affect the SEO optimizations we've done so far. These 
are immediate actions to alleviate the situation: 
# Reduce banner and all the images size to 72 ppi resolution and save in the 
JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
screencasts were already changed, just need to regenerate the CSS and merge the 
patch.
# The next fierce contributors to the poor performance are screencasts youtube 
video. It takes 700ms for each screencast to make a roundtrip to YouTube. See 
the screenshot attached where 3 base.js calls are triggered by the video links. 
This has to be done asynchronously.
# Preload GitHub, Twitter butter and feed asynchronously too.

The overall goal of this optimization is to speed up the loading to 2.5 seconds 
(no more).




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

[jira] [Updated] (IGNITE-7292) Optimize Ignite main page load performance

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-7292:

Component/s: site

> Optimize Ignite main page load performance
> --
>
> Key: IGNITE-7292
> URL: https://issues.apache.org/jira/browse/IGNITE-7292
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Blocker
> Fix For: 2.4
>
> Attachments: Screen Shot 2017-12-22 at 9.49.02 AM.png
>
>
> Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
> in completely. That might affect the SEO optimizations we've done so far. 
> These are immediate actions to alleviate the situation: 
> # Reduce banner and all the images size to 72 ppi resolution and save in the 
> JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
> screencasts were already changed, just need to regenerate the CSS and merge 
> the patch.
> # The next fierce contributors to the poor performance are screencasts 
> youtube video. It takes 700ms for each screencast to make a roundtrip to 
> YouTube. See the screenshot attached where 3 base.js calls are triggered by 
> the video links. This has to be done asynchronously.
> # Preload GitHub, Twitter butter and feed asynchronously too.
> The overall goal of this optimization is to speed up the loading to 2.5 
> seconds (no more).



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

[jira] [Commented] (IGNITE-7291) Apache Ignite "in use at" section

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan commented on IGNITE-7291:
---

https://www.imcsummit.org/2017/eu/sessions/using-memory-grid-compute-achieve-scalability-and-high-performance-legacy-travel

> Apache Ignite "in use at" section
> -
>
> Key: IGNITE-7291
> URL: https://issues.apache.org/jira/browse/IGNITE-7291
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.4
>
>
> Put together a list of publicly disclosed Apache Ignite use cases and present 
> them on the main page right below the benefits. The "Ignite is in use at" 
> section might be like Cassandra's "PROVEN" section:
> http://cassandra.apache.org
> A list of the known use cases:
> * 
> https://www.imcsummit.org/us/sessions/implementation-investment-book-record-ibor-using-apache-ignitegridgain
> * 
> https://www.imcsummit.org/us/sessions/high-availability-and-disaster-recovery-imdg
> * https://www.imcsummit.org/us/sessions/ignite-compute-grid-in-cloud
> * https://youtu.be/1D8hyLWMtfM
> * 
> https://www.imcsummit.org/us/sessions/how-in-memory-solutions-can-assist-saas-integrations



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

[jira] [Updated] (IGNITE-7291) Apache Ignite "in use at" section

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-7291:

Component/s: site

> Apache Ignite "in use at" section
> -
>
> Key: IGNITE-7291
> URL: https://issues.apache.org/jira/browse/IGNITE-7291
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.4
>
>
> Put together a list of publicly disclosed Apache Ignite use cases and present 
> them on the main page right below the benefits. The "Ignite is in use at" 
> section might be like Cassandra's "PROVEN" section:
> http://cassandra.apache.org
> A list of the known use cases:
> * 
> https://www.imcsummit.org/us/sessions/implementation-investment-book-record-ibor-using-apache-ignitegridgain
> * 
> https://www.imcsummit.org/us/sessions/high-availability-and-disaster-recovery-imdg
> * https://www.imcsummit.org/us/sessions/ignite-compute-grid-in-cloud
> * https://youtu.be/1D8hyLWMtfM
> * 
> https://www.imcsummit.org/us/sessions/how-in-memory-solutions-can-assist-saas-integrations



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

[jira] [Updated] (IGNITE-7291) Apache Ignite "in use at" section

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-7291:

Issue Type: Task  (was: Bug)

> Apache Ignite "in use at" section
> -
>
> Key: IGNITE-7291
> URL: https://issues.apache.org/jira/browse/IGNITE-7291
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.4
>
>
> Put together a list of publicly disclosed Apache Ignite use cases and present 
> them on the main page right below the benefits. The "Ignite is in use at" 
> section might be like Cassandra's "PROVEN" section:
> http://cassandra.apache.org
> A list of the known use cases:
> * 
> https://www.imcsummit.org/us/sessions/implementation-investment-book-record-ibor-using-apache-ignitegridgain
> * 
> https://www.imcsummit.org/us/sessions/high-availability-and-disaster-recovery-imdg
> * https://www.imcsummit.org/us/sessions/ignite-compute-grid-in-cloud
> * https://youtu.be/1D8hyLWMtfM
> * 
> https://www.imcsummit.org/us/sessions/how-in-memory-solutions-can-assist-saas-integrations



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

[jira] [Created] (IGNITE-7291) Apache Ignite "in use at" section

[Denis Magda (JIRA)]

Denis Magda created IGNITE-7291:
---

 Summary: Apache Ignite "in use at" section
 Key: IGNITE-7291
 URL: https://issues.apache.org/jira/browse/IGNITE-7291
 Project: Ignite
  Issue Type: Bug
Reporter: Denis Magda
Assignee: Denis Magda
 Fix For: 2.4


Put together a list of publicly disclosed Apache Ignite use cases and present 
them on the main page right below the benefits. The "Ignite is in use at" 
section might be like Cassandra's "PROVEN" section:
http://cassandra.apache.org

A list of the known use cases:
* 
https://www.imcsummit.org/us/sessions/implementation-investment-book-record-ibor-using-apache-ignitegridgain
* 
https://www.imcsummit.org/us/sessions/high-availability-and-disaster-recovery-imdg
* https://www.imcsummit.org/us/sessions/ignite-compute-grid-in-cloud
* https://youtu.be/1D8hyLWMtfM
* 
https://www.imcsummit.org/us/sessions/how-in-memory-solutions-can-assist-saas-integrations




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

[jira] [Commented] (IGNITE-6579) WAL history does not used when node returns to cluster again

[Pavel Pereslegin (JIRA)]

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

Pavel Pereslegin commented on IGNITE-6579:
--

Hello [~v.pyatkov].

Could you provide more details about your configuration and behavior that you 
expect to see (or how to reproduce this bug).

I tried following scenario and I believe it works well.
# Set IGNITE_PDS_WAL_REBALANCE_THRESHOLD to 0 (default threshold = 50).
# Start nodes A, B and C with PDS enabled (1 backup).
# Add data to cache.
# Stop node C.
# Add more data to cache.
# Rejoin node C to cluster (nodeId = 93206ec4-0b0a-4c91-bb55-79b05f12).
# Observing messages from coordinator about outdated update counters 
(haveHistory=true):

{noformat}
Partition has been scheduled for rebalancing due to outdated update counter 
[nodeId=93206ec4-0b0a-4c91-bb55-79b05f12, cacheOrGroupName=default, 
partId=0, haveHistory=true]
Partition has been scheduled for rebalancing due to outdated update counter 
[nodeId=93206ec4-0b0a-4c91-bb55-79b05f12, cacheOrGroupName=default, 
partId=1, haveHistory=true]
Partition has been scheduled for rebalancing due to outdated update counter 
[nodeId=93206ec4-0b0a-4c91-bb55-79b05f12, cacheOrGroupName=default, 
partId=4, haveHistory=true]
...
{noformat}

> WAL history does not used when node returns to cluster again
> 
>
> Key: IGNITE-6579
> URL: https://issues.apache.org/jira/browse/IGNITE-6579
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Reporter: Vladislav Pyatkov
>
> When I have set big enough value to "WAL history size" and stop node on 20 
> minutes, I got the message from coordinator (order=1):
> {noformat}
> 2017-10-06 15:46:33.429 [WARN 
> ][sys-#10740%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl]
>  Partition has been scheduled for rebalancing due to outdated update counter 
> [nodeId=e51a1db2-f49b-44a9-b122-adde4016d9e7,
>  cacheOrGroupName=CACHEGROUP_PARTICLE_DServiceZone, partId=2424, 
> haveHistory=false]
> 2017-10-06 15:46:33.429 [WARN 
> ][sys-#10740%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl]
>  Partition has been scheduled for rebalancing due to outdated update counter 
> [nodeId=e51a1db2-f49b-44a9-b122-adde4016d9e7,
>  cacheOrGroupName=CACHEGROUP_PARTICLE_DServiceZone, partId=2427, 
> haveHistory=false]
> 2017-10-06 15:46:33.429 [WARN 
> ][sys-#10740%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl]
>  Partition has been scheduled for rebalancing due to outdated update counter 
> [nodeId=e51a1db2-f49b-44a9-b122-adde4016d9e7,
>  cacheOrGroupName=CACHEGROUP_PARTICLE_DServiceZone, partId=2426, 
> haveHistory=false]
> {noformat}
> after start node again.
> I think, history size should be enough, but I see it is not by logs 
> (haveHistory=false).



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

[jira] [Created] (IGNITE-7290) Log when partition is moved to a LOST state

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-7290:


 Summary: Log when partition is moved to a LOST state
 Key: IGNITE-7290
 URL: https://issues.apache.org/jira/browse/IGNITE-7290
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
Priority: Critical
 Fix For: 2.4






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

[jira] [Created] (IGNITE-7289) ODBC: add possibility to reconnect to the cluster after node failing

[Evgenii Zhuravlev (JIRA)]

Evgenii Zhuravlev created IGNITE-7289:
-

 Summary: ODBC: add possibility to reconnect to the cluster after 
node failing
 Key: IGNITE-7289
 URL: https://issues.apache.org/jira/browse/IGNITE-7289
 Project: Ignite
  Issue Type: Improvement
Reporter: Evgenii Zhuravlev
Assignee: Igor Sapego






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

[jira] [Commented] (IGNITE-7174) Local MLP

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7174:


Github user asfgit closed the pull request at:

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


> Local MLP
> -
>
> Key: IGNITE-7174
> URL: https://issues.apache.org/jira/browse/IGNITE-7174
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Yury Babak
>Assignee: Artem Malykh
> Fix For: 2.4
>
>
> local version of MLP



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

[jira] [Issue Comment Deleted] (IGNITE-6740) Java 9: rework DirectBuffer.address() usages

[Andrey Kuznetsov (JIRA)]

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

Andrey Kuznetsov updated IGNITE-6740:
-
Comment: was deleted

(was: [~vozerov], when one tries to set {{Buffer.address}} field accessible 
JRE9 fires warnings like

{noformat}
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by ... to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of ...
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
{noformat}

Why can't we always fall back to offset?)

> Java 9: rework DirectBuffer.address() usages
> 
>
> Key: IGNITE-6740
> URL: https://issues.apache.org/jira/browse/IGNITE-6740
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> We have two usages of {{DirectBuffer.address()}} method which is no longer 
> accessible in Java 9: 
> 1) {{DirectByteBufferStreamImplV1}}
> 2) {{DirectByteBufferStreamImplV2}}
> Need to rework this code using reflection and/or {{Unsafe}}, so that it 
> compiles and work on all Java versions.



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

[jira] [Assigned] (IGNITE-7174) Local MLP

[Artem Malykh (JIRA)]

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

Artem Malykh reassigned IGNITE-7174:


Assignee: Artem Malykh

> Local MLP
> -
>
> Key: IGNITE-7174
> URL: https://issues.apache.org/jira/browse/IGNITE-7174
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Yury Babak
>Assignee: Artem Malykh
> Fix For: 2.4
>
>
> local version of MLP



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

[jira] [Commented] (IGNITE-7021) IgniteOOM is not propogated to client in case of implicit transaction

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-7021:
-

LGTM. Merged to master branch.

> IgniteOOM is not propogated to client  in case of implicit transaction
> --
>
> Key: IGNITE-7021
> URL: https://issues.apache.org/jira/browse/IGNITE-7021
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Mikhail Cherkasov
>Priority: Critical
> Fix For: 2.4
>
>
> it's related to https://issues.apache.org/jira/browse/IGNITE-7019
> when transaction fails due IgniteOOM,  ignite tries to rollback transaction 
> and it fails too, because can't add free pages to free list due a new 
> IgniteOOM:
> [2017-11-27 
> 12:47:37,539][ERROR][sys-stripe-2-#4%cache.IgniteOutOfMemoryPropagationTest0%][GridNearTxLocal]
>  Heuristic transaction failure.
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:835)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:774)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:555)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:441)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:489)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitAsync(GridDhtTxLocal.java:498)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.onDone(GridDhtTxPrepareFuture.java:727)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.onDone(GridDhtTxPrepareFuture.java:104)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:451)
>   at 
> org.apache.ignite.internal.util.future.GridCompoundFuture.checkComplete(GridCompoundFuture.java:285)
>   at 
> org.apache.ignite.internal.util.future.GridCompoundFuture.markInitialized(GridCompoundFuture.java:276)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1246)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:666)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1040)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:398)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:519)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest0(IgniteTxHandler.java:150)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest(IgniteTxHandler.java:135)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$000(IgniteTxHandler.java:97)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:177)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:175)
>   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 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1183)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
>   at 
> 

[jira] [Updated] (IGNITE-7288) Thin client: partial cache configuration

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-7288:
---
Summary: Thin client: partial cache configuration  (was: Thin client: Allow 
partial cache configuration)

> Thin client: partial cache configuration
> 
>
> Key: IGNITE-7288
> URL: https://issues.apache.org/jira/browse/IGNITE-7288
> Project: Ignite
>  Issue Type: Improvement
>  Components: thin client
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 2.4
>
>
> {{OP_CACHE_CREATE_WITH_CONFIGURATION}} and 
> {{OP_CACHE_GET_OR_CREATE_WITH_CONFIGURATION}} should not require complete 
> {{CacheConfiguration}}. User should be able to specify any combination of 
> properties in any order, leaving others at default state.
> Prefix each property with unique ID, then do a switch in a loop.



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

[jira] [Commented] (IGNITE-6740) Java 9: rework DirectBuffer.address() usages

[Andrey Kuznetsov (JIRA)]

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

Andrey Kuznetsov commented on IGNITE-6740:
--

[~vozerov], when one tries to set {{Buffer.address}} field accessible JRE9 
fires warnings like

{noformat}
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by ... to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of ...
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
{noformat}

Why can't we always fall back to offset?

> Java 9: rework DirectBuffer.address() usages
> 
>
> Key: IGNITE-6740
> URL: https://issues.apache.org/jira/browse/IGNITE-6740
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> We have two usages of {{DirectBuffer.address()}} method which is no longer 
> accessible in Java 9: 
> 1) {{DirectByteBufferStreamImplV1}}
> 2) {{DirectByteBufferStreamImplV2}}
> Need to rework this code using reflection and/or {{Unsafe}}, so that it 
> compiles and work on all Java versions.



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

[jira] [Commented] (IGNITE-7109) .NET: Thin client: Async cache operations

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7109:


Github user asfgit closed the pull request at:

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


> .NET: Thin client: Async cache operations
> -
>
> Key: IGNITE-7109
> URL: https://issues.apache.org/jira/browse/IGNITE-7109
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Add async operations to {{ICacheClient}}.
> Thin client suppots asynchrony with requestId mechanism. Make sure it works 
> with .NET.



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

[jira] [Commented] (IGNITE-7109) .NET: Thin client: Async cache operations

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7109:


Merged to master: {{1c09a923d90987da111f8ac9722e5870bb9f7627}}.

> .NET: Thin client: Async cache operations
> -
>
> Key: IGNITE-7109
> URL: https://issues.apache.org/jira/browse/IGNITE-7109
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Add async operations to {{ICacheClient}}.
> Thin client suppots asynchrony with requestId mechanism. Make sure it works 
> with .NET.



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

[jira] [Created] (IGNITE-7288) Thin client: Allow partial cache configuration

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7288:
--

 Summary: Thin client: Allow partial cache configuration
 Key: IGNITE-7288
 URL: https://issues.apache.org/jira/browse/IGNITE-7288
 Project: Ignite
  Issue Type: Improvement
  Components: thin client
Affects Versions: 2.4
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.4


{{OP_CACHE_CREATE_WITH_CONFIGURATION}} and 
{{OP_CACHE_GET_OR_CREATE_WITH_CONFIGURATION}} should not require complete 
{{CacheConfiguration}}. User should be able to specify any combination of 
properties in any order, leaving others at default state.

Prefix each property with unique ID, then do a switch in a loop.



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

[jira] [Commented] (IGNITE-6740) Java 9: rework DirectBuffer.address() usages

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-6740:
-

I've added new comments to upsource. I should also stress that the problem not 
with {{address}} method (it's public for {{DirectBuffer}} and 
{{DirectByteBuffer}}). Actually {{DirectBuffer}} interface and 
{{DirectByteBuffer}} class are not accessible in Java 9. We should remove all 
castings, instance type checking, etc.

> Java 9: rework DirectBuffer.address() usages
> 
>
> Key: IGNITE-6740
> URL: https://issues.apache.org/jira/browse/IGNITE-6740
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> We have two usages of {{DirectBuffer.address()}} method which is no longer 
> accessible in Java 9: 
> 1) {{DirectByteBufferStreamImplV1}}
> 2) {{DirectByteBufferStreamImplV2}}
> Need to rework this code using reflection and/or {{Unsafe}}, so that it 
> compiles and work on all Java versions.



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

[jira] [Commented] (IGNITE-6743) Java 9: rework DirectBuffer.cleaner().clean() usage in GridNioServer

[Andrey Kuznetsov (JIRA)]

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

Andrey Kuznetsov commented on IGNITE-6743:
--

[~vozerov], do you offer to check Java version every time we need to clean a 
buffer?

> Java 9: rework DirectBuffer.cleaner().clean() usage in GridNioServer
> 
>
> Key: IGNITE-6743
> URL: https://issues.apache.org/jira/browse/IGNITE-6743
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> When session is closed we clean allocated {{DirectByteBuffer}}-s using 
> {{sun.misc.Cleaner}}. Need to rework this piece to reflection-based approach 
> which will work for supported Java versions.



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

[jira] [Comment Edited] (IGNITE-7142) Introduce ability to run Ignite Tests on TeamCity with Java 9

[Peter Ivanov (JIRA)]

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

Peter Ivanov edited comment on IGNITE-7142 at 12/22/17 11:30 AM:
-

There is problem running current configuration on Windows-base agents because 
of hardcoded JAVA_HOME parameter passed to snapshot dependency builds.
Possible fix:
 - either add LinuxOS agent requirement
 - or redesign environmental variables to have os-based variables pointing to 
JAVA_HOME of corresponding version.

Test on 
https://ci.ignite.apache.org/project.html?projectId=Ignite20TestsJava8_Ignite20TestsJava8=__all_branches__
 project.

*Update (I)* Problem fixed by passing corresponding {{JDK_ORA_XX}} 
environmental variable.


was (Author: vveider):
There is problem running current configuration on Windows-base agents because 
of hardcoded JAVA_HOME parameter passed to snapshot dependency builds.
Possible fix:
 - either add LinuxOS agent requirement
 - or redesign environmental variables to have os-based variables pointing to 
JAVA_HOME of corresponding version.

Test on 
https://ci.ignite.apache.org/project.html?projectId=Ignite20TestsJava8_Ignite20TestsJava8=__all_branches__
 project.

> Introduce ability to run Ignite Tests on TeamCity with Java 9
> -
>
> Key: IGNITE-7142
> URL: https://issues.apache.org/jira/browse/IGNITE-7142
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>
> Introduce ability to run Ignite Tests on TeamCity with Java 9 (and Java 1.8 
> as well).



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

[jira] [Commented] (IGNITE-6743) Java 9: rework DirectBuffer.cleaner().clean() usage in GridNioServer

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-6743:
-

[~andrey-kuznetsov], [~ezhuravl], I support Evgenii here that closures (and 
possible lambdas in Java 8 +) is overengineering. All we need is to get three 
fields/methods, and call them ocnditionally based on Java version. No need for 
any abstractions here, this is just small and simple utility method.

> Java 9: rework DirectBuffer.cleaner().clean() usage in GridNioServer
> 
>
> Key: IGNITE-6743
> URL: https://issues.apache.org/jira/browse/IGNITE-6743
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> When session is closed we clean allocated {{DirectByteBuffer}}-s using 
> {{sun.misc.Cleaner}}. Need to rework this piece to reflection-based approach 
> which will work for supported Java versions.



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

[jira] [Created] (IGNITE-7287) Thin client: idle connection timeout

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7287:
--

 Summary: Thin client: idle connection timeout
 Key: IGNITE-7287
 URL: https://issues.apache.org/jira/browse/IGNITE-7287
 Project: Ignite
  Issue Type: Improvement
  Components: thin client
Affects Versions: 2.4
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.4


Add an ability to drop inactive connections on server side, disabled by 
default: introduce {{ClientConnectorConfiguration.idleTimeout}}, default to 
{{long.MAX_VALUE}}.

Currently we set {{GridNioServer.idleTimeout}} to {{MAX_VALUE}} in 
{{ClientListenerProcessor.start()}}.



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

[jira] [Commented] (IGNITE-7217) Add abilities to monitor custom thread pools

[Stanislav Lukyanov (JIRA)]

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

Stanislav Lukyanov commented on IGNITE-7217:


I'll add beans for all the pools that don't have them yet then. The pools are
utilityCachePool
igfsExecSvc
dataStreamExecSvc
affExecSvc
idxExecSvc
callbackExecSvc


> Add abilities to monitor custom thread pools
> 
>
> Key: IGNITE-7217
> URL: https://issues.apache.org/jira/browse/IGNITE-7217
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Stanislav Lukyanov
> Fix For: 2.4
>
>
> We have a periodic metrics logger that prints out different stats including 
> the ones for public and system thread pools:
> {noformat}
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=8, qSize=0]
> {noformat}
> However, if user configures a custom thread pools via 
> {{IgniteConfiguration#setExecutorConfiguration}}, stats for these thread 
> pools are not added. We also do not register MBeans for these pools.



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

[jira] [Assigned] (IGNITE-7217) Add abilities to monitor custom thread pools

[Stanislav Lukyanov (JIRA)]

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

Stanislav Lukyanov reassigned IGNITE-7217:
--

Assignee: Stanislav Lukyanov

> Add abilities to monitor custom thread pools
> 
>
> Key: IGNITE-7217
> URL: https://issues.apache.org/jira/browse/IGNITE-7217
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Stanislav Lukyanov
> Fix For: 2.4
>
>
> We have a periodic metrics logger that prints out different stats including 
> the ones for public and system thread pools:
> {noformat}
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=8, qSize=0]
> {noformat}
> However, if user configures a custom thread pools via 
> {{IgniteConfiguration#setExecutorConfiguration}}, stats for these thread 
> pools are not added. We also do not register MBeans for these pools.



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

[jira] [Resolved] (IGNITE-6715) .NET: DataStorageConfiguration.WalAutoArchiveAfterInactivity

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-6715.

Resolution: Fixed

> .NET: DataStorageConfiguration.WalAutoArchiveAfterInactivity
> 
>
> Key: IGNITE-6715
> URL: https://issues.apache.org/jira/browse/IGNITE-6715
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET, newbie
> Fix For: 2.4
>
>
> Add {{DataStorageConfiguration.WalAutoArchiveAfterInactivity}} property.



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

[jira] [Commented] (IGNITE-6715) .NET: DataStorageConfiguration.WalAutoArchiveAfterInactivity

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-6715:


Merged to master: {{0e8224f9c5ef06c1b1700379be3beb8996443558}}.

> .NET: DataStorageConfiguration.WalAutoArchiveAfterInactivity
> 
>
> Key: IGNITE-6715
> URL: https://issues.apache.org/jira/browse/IGNITE-6715
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET, newbie
> Fix For: 2.4
>
>
> Add {{DataStorageConfiguration.WalAutoArchiveAfterInactivity}} property.



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

[jira] [Assigned] (IGNITE-7264) Caches with forward slash "/" in names cause problems for PDS

[Stanislav Lukyanov (JIRA)]

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

Stanislav Lukyanov reassigned IGNITE-7264:
--

Assignee: Stanislav Lukyanov

> Caches with forward slash "/" in names cause problems for PDS
> -
>
> Key: IGNITE-7264
> URL: https://issues.apache.org/jira/browse/IGNITE-7264
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, persistence
>Affects Versions: 2.3
>Reporter: Ilya Kasnacheev
>Assignee: Stanislav Lukyanov
>
> If I am to create cache with name "caches/1", there's no immediate error, but 
> nodes fail when trying to rejoin topology with storage already initialized.
> I think there should be an immediate exception in case persistence is enabled 
> for such case.
> Moreover, I suggest first trying to create directory, then making sure it was 
> created and that dir.parent == expected parent directory. Because on Windows 
> there are more restrictions on FS file names, etc...



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

[jira] [Commented] (IGNITE-6732) Java 9: Hadoop module should not start on Java 9

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6732:


Github user asfgit closed the pull request at:

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


> Java 9: Hadoop module should not start on Java 9
> 
>
> Key: IGNITE-6732
> URL: https://issues.apache.org/jira/browse/IGNITE-6732
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> Hadoop module heavily relies on the fact that application class loader is 
> {{URLClassLoader}}. It is used to inspect class path and hack it in various 
> ways. But in Java 9 another class loader type is used. 
> Looks like there is no simple solution at the moment. Let's check for Java 
> version during startup and throw an exception if it Java 9 or later.



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

[jira] [Commented] (IGNITE-6735) Java 9: fix Java version resolution/check logic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6735:


Github user asfgit closed the pull request at:

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


> Java 9: fix Java version resolution/check logic
> ---
>
> Key: IGNITE-6735
> URL: https://issues.apache.org/jira/browse/IGNITE-6735
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: of.salakhutdinov
> Fix For: 2.4
>
>
> We have several places in the code where Java version is validated. First, 
> sometimes we do not take in count Java 9 at all. Second, sometimes we rely on 
> old version pattern {{1.x}}, while as of Java 9 it is just {{x}}. 
> Places to fix:
> 1) {{GridDiscoveryManager.nodeJavaMajorVersion}} - add support for new Java 
> version format without {{1.}} prefix.
> 2) {{IgnitionEx.}} - add Java 9 to the list of supported 
> versions.



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

[jira] [Commented] (IGNITE-6735) Java 9: fix Java version resolution/check logic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6735:


Github user devozerov closed the pull request at:

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


> Java 9: fix Java version resolution/check logic
> ---
>
> Key: IGNITE-6735
> URL: https://issues.apache.org/jira/browse/IGNITE-6735
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
> Fix For: 2.4
>
>
> We have several places in the code where Java version is validated. First, 
> sometimes we do not take in count Java 9 at all. Second, sometimes we rely on 
> old version pattern {{1.x}}, while as of Java 9 it is just {{x}}. 
> Places to fix:
> 1) {{GridDiscoveryManager.nodeJavaMajorVersion}} - add support for new Java 
> version format without {{1.}} prefix.
> 2) {{IgnitionEx.}} - add Java 9 to the list of supported 
> versions.



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

[jira] [Assigned] (IGNITE-6735) Java 9: fix Java version resolution/check logic

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-6735:
---

Assignee: of.salakhutdinov

> Java 9: fix Java version resolution/check logic
> ---
>
> Key: IGNITE-6735
> URL: https://issues.apache.org/jira/browse/IGNITE-6735
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: of.salakhutdinov
> Fix For: 2.4
>
>
> We have several places in the code where Java version is validated. First, 
> sometimes we do not take in count Java 9 at all. Second, sometimes we rely on 
> old version pattern {{1.x}}, while as of Java 9 it is just {{x}}. 
> Places to fix:
> 1) {{GridDiscoveryManager.nodeJavaMajorVersion}} - add support for new Java 
> version format without {{1.}} prefix.
> 2) {{IgnitionEx.}} - add Java 9 to the list of supported 
> versions.



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

[jira] [Commented] (IGNITE-6015) Test fail in Ignite Cache 2: GridCachePartitionedGetAndTransformStoreSelfTest.testGetAndTransform

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6015:


Github user andrey-kuznetsov closed the pull request at:

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


> Test fail in Ignite Cache 2: 
> GridCachePartitionedGetAndTransformStoreSelfTest.testGetAndTransform 
> --
>
> Key: IGNITE-6015
> URL: https://issues.apache.org/jira/browse/IGNITE-6015
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 2.1
>Reporter: Dmitriy Govorukhin
>Assignee: Andrey Kuznetsov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.4
>
>
> {code}
> java.util.concurrent.TimeoutException: Test has been timed out 
> [test=testGetAndTransform, timeout=30]
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:1949)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at 
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208)
> at 
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156)
> at 
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82)
> at 
> org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.runSuitesInProcess(InPluginVMSurefireStarter.java:82)
> at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:951)
> at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:831)
> at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:729)
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at 

[jira] [Commented] (IGNITE-7109) .NET: Thin client: Async cache operations

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-7109:
-

[~ptupitsyn], looks good to me.

> .NET: Thin client: Async cache operations
> -
>
> Key: IGNITE-7109
> URL: https://issues.apache.org/jira/browse/IGNITE-7109
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Add async operations to {{ICacheClient}}.
> Thin client suppots asynchrony with requestId mechanism. Make sure it works 
> with .NET.



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

[jira] [Updated] (IGNITE-7286) Web Console: We can't copy from the tables (in old design)

[Vica Abramova (JIRA)]

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

Vica Abramova updated IGNITE-7286:
--
Description: Also can't copy from the tables (in new design). We should fix 
it.

> Web Console: We can't copy from the tables (in old design)
> --
>
> Key: IGNITE-7286
> URL: https://issues.apache.org/jira/browse/IGNITE-7286
> Project: Ignite
>  Issue Type: Bug
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Alexey Kuznetsov
> Attachments: table.png
>
>
> Also can't copy from the tables (in new design). We should fix it.



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

[jira] [Created] (IGNITE-7286) Web Console: We can't copy from the tables (in old design)

[Vica Abramova (JIRA)]

Vica Abramova created IGNITE-7286:
-

 Summary: Web Console: We can't copy from the tables (in old design)
 Key: IGNITE-7286
 URL: https://issues.apache.org/jira/browse/IGNITE-7286
 Project: Ignite
  Issue Type: Bug
  Components: UI, wizards
Reporter: Vica Abramova
Assignee: Alexey Kuznetsov
 Attachments: table.png





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

[jira] [Commented] (IGNITE-6735) Java 9: fix Java version resolution/check logic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6735:


GitHub user devozerov opened a pull request:

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

IGNITE-6735



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

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

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

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


commit 6d35794978c6c84001d16293e78031a4aed7d0da
Author: devozerov 
Date:   2017-12-22T09:18:13Z

Done.




> Java 9: fix Java version resolution/check logic
> ---
>
> Key: IGNITE-6735
> URL: https://issues.apache.org/jira/browse/IGNITE-6735
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
> Fix For: 2.4
>
>
> We have several places in the code where Java version is validated. First, 
> sometimes we do not take in count Java 9 at all. Second, sometimes we rely on 
> old version pattern {{1.x}}, while as of Java 9 it is just {{x}}. 
> Places to fix:
> 1) {{GridDiscoveryManager.nodeJavaMajorVersion}} - add support for new Java 
> version format without {{1.}} prefix.
> 2) {{IgnitionEx.}} - add Java 9 to the list of supported 
> versions.



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

[jira] [Commented] (IGNITE-6735) Java 9: fix Java version resolution/check logic

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-6735:
-

Not merged to master yet.

> Java 9: fix Java version resolution/check logic
> ---
>
> Key: IGNITE-6735
> URL: https://issues.apache.org/jira/browse/IGNITE-6735
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
> Fix For: 2.4
>
>
> We have several places in the code where Java version is validated. First, 
> sometimes we do not take in count Java 9 at all. Second, sometimes we rely on 
> old version pattern {{1.x}}, while as of Java 9 it is just {{x}}. 
> Places to fix:
> 1) {{GridDiscoveryManager.nodeJavaMajorVersion}} - add support for new Java 
> version format without {{1.}} prefix.
> 2) {{IgnitionEx.}} - add Java 9 to the list of supported 
> versions.



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

[jira] [Reopened] (IGNITE-6735) Java 9: fix Java version resolution/check logic

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reopened IGNITE-6735:
-
  Assignee: (was: of.salakhutdinov)

> Java 9: fix Java version resolution/check logic
> ---
>
> Key: IGNITE-6735
> URL: https://issues.apache.org/jira/browse/IGNITE-6735
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
> Fix For: 2.4
>
>
> We have several places in the code where Java version is validated. First, 
> sometimes we do not take in count Java 9 at all. Second, sometimes we rely on 
> old version pattern {{1.x}}, while as of Java 9 it is just {{x}}. 
> Places to fix:
> 1) {{GridDiscoveryManager.nodeJavaMajorVersion}} - add support for new Java 
> version format without {{1.}} prefix.
> 2) {{IgnitionEx.}} - add Java 9 to the list of supported 
> versions.



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

[jira] [Assigned] (IGNITE-5217) Gradient descent for OLS lin reg

[Anton Dmitriev (JIRA)]

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

Anton Dmitriev reassigned IGNITE-5217:
--

Assignee: Anton Dmitriev  (was: Yury Babak)

> Gradient descent for OLS lin reg
> 
>
> Key: IGNITE-5217
> URL: https://issues.apache.org/jira/browse/IGNITE-5217
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Anton Dmitriev
>
> We should implement Gradient Descent for Ignite ML. Current we have only 
> normal equation for linear regression.



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

[jira] [Resolved] (IGNITE-7279) .NET: Compile on Linux

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-7279.

Resolution: Fixed

> .NET: Compile on Linux
> --
>
> Key: IGNITE-7279
> URL: https://issues.apache.org/jira/browse/IGNITE-7279
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, xplat
>
> Make it possible to develop Ignite.NET on Linux.
> * Provide separate .NET Core csproj files for {{Core}} and {{Linq}} projects
> * Make sure we can compile and run tests from scratch on Linux ({{git clone}} 
> -> {{dotnet test}})
> * Update DEVNOTES



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

[jira] [Commented] (IGNITE-7279) .NET: Compile on Linux

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7279:


Merged to master: {{198399bb984c3ff8f63a9eb2bed1a359329f9678}}, 
{{3dc5e531212f4e6a9fd859f55d1d372a81988aa8}}.

> .NET: Compile on Linux
> --
>
> Key: IGNITE-7279
> URL: https://issues.apache.org/jira/browse/IGNITE-7279
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, xplat
>
> Make it possible to develop Ignite.NET on Linux.
> * Provide separate .NET Core csproj files for {{Core}} and {{Linq}} projects
> * Make sure we can compile and run tests from scratch on Linux ({{git clone}} 
> -> {{dotnet test}})
> * Update DEVNOTES



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

[jira] [Commented] (IGNITE-6731) Java 9: remove sun.misc.PerfCounter usages

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6731:


Github user asfgit closed the pull request at:

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


> Java 9: remove sun.misc.PerfCounter usages
> --
>
> Key: IGNITE-6731
> URL: https://issues.apache.org/jira/browse/IGNITE-6731
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> This class is used in Hadoop module only:
> 1) {{HadoopClassLoader}}
> 2) {{HadoopTestClassLoader}}
> Need to understand whether it is safe to simply remove this calls. Most 
> probably - yes.



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

[jira] [Commented] (IGNITE-7279) .NET: Compile on Linux

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7279:


Github user asfgit closed the pull request at:

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


> .NET: Compile on Linux
> --
>
> Key: IGNITE-7279
> URL: https://issues.apache.org/jira/browse/IGNITE-7279
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, xplat
>
> Make it possible to develop Ignite.NET on Linux.
> * Provide separate .NET Core csproj files for {{Core}} and {{Linq}} projects
> * Make sure we can compile and run tests from scratch on Linux ({{git clone}} 
> -> {{dotnet test}})
> * Update DEVNOTES



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