[jira] [Updated] (IGNITE-7818) Incorrect assertion in PDS page eviction method

[Aleksey Plekhanov (JIRA)]

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

Aleksey Plekhanov updated IGNITE-7818:
--
Description: 
There is an assertion in the method 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.Segment#removePageForReplacement:

 
{code:java}
assert relRmvAddr != INVALID_REL_PTR;{code}
Which seems potentially dangerous. In some rare cases, when count of 
interations more then 40% of allocated pages and all processed pages are 
aquired, the {{relRmvAddr}} variable will be uninitialized and 
{{AssertionException}} will be thrown. But it's a correct case and page to 
evict can be found later in the method {{tryToFindSequentially.}}

 

  was:
There is assertion in the method 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.Segment#removePageForReplacement:

 
{code:java}
assert relRmvAddr != INVALID_REL_PTR;{code}
Which seems potentially dangerous. In some rare cases, when count of 
interations more then 40% of allocated pages and all processed pages are 
aquired, the {{relRmvAddr}} variable will be uninitialized and 
{{AssertionException}} will be thrown. But it's a correct case and page to 
evict can be found later in the method {{tryToFindSequentially.}}

 


> Incorrect assertion in PDS page eviction method
> ---
>
> Key: IGNITE-7818
> URL: https://issues.apache.org/jira/browse/IGNITE-7818
> Project: Ignite
>  Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Priority: Major
>
> There is an assertion in the method 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.Segment#removePageForReplacement:
>  
> {code:java}
> assert relRmvAddr != INVALID_REL_PTR;{code}
> Which seems potentially dangerous. In some rare cases, when count of 
> interations more then 40% of allocated pages and all processed pages are 
> aquired, the {{relRmvAddr}} variable will be uninitialized and 
> {{AssertionException}} will be thrown. But it's a correct case and page to 
> evict can be found later in the method {{tryToFindSequentially.}}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7818) Incorrect assertion in PDS page eviction method

[Aleksey Plekhanov (JIRA)]

Aleksey Plekhanov created IGNITE-7818:
-

 Summary: Incorrect assertion in PDS page eviction method
 Key: IGNITE-7818
 URL: https://issues.apache.org/jira/browse/IGNITE-7818
 Project: Ignite
  Issue Type: Bug
Reporter: Aleksey Plekhanov


There is assertion in the method 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.Segment#removePageForReplacement:

 
{code:java}
assert relRmvAddr != INVALID_REL_PTR;{code}
Which seems potentially dangerous. In some rare cases, when count of 
interations more then 40% of allocated pages and all processed pages are 
aquired, the {{relRmvAddr}} variable will be uninitialized and 
{{AssertionException}} will be thrown. But it's a correct case and page to 
evict can be found later in the method {{tryToFindSequentially.}}

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7817) Spark 'close' API call hangs when executed within ignite service grid component

[Akshay Mhetre (JIRA)]

Akshay Mhetre created IGNITE-7817:
-

 Summary: Spark 'close' API call hangs when executed within ignite 
service grid component
 Key: IGNITE-7817
 URL: https://issues.apache.org/jira/browse/IGNITE-7817
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Akshay Mhetre


I am running a sprak job within ignite service grid. After job is done I am 
calling close() on spark session. This is working for stable version of 
ignite i.e. 2.3.0. However, its not working with 2.5.0-SNAPSHOT version. 
Please check detailed logs on this link : 

[http://apache-ignite-users.70518.x6.nabble.com/Spark-close-API-call-hangs-within-ignite-service-grid-td20252.html|http://example.com]
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7774) Missing Google Cloud libraries at binary release

[Roman Guseinov (JIRA)]

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

Roman Guseinov commented on IGNITE-7774:


[~dmitry.pavlov], could you take a look at this PR 
[https://github.com/apache/ignite/pull/3567], please?

Test results from TC: 
[https://ci.ignite.apache.org/viewLog.html?buildId=1110578=IgniteTests24Java8_IgniteGce=buildResultsDiv]

Thanks.

> Missing Google Cloud libraries at binary release
> 
>
> Key: IGNITE-7774
> URL: https://issues.apache.org/jira/browse/IGNITE-7774
> Project: Ignite
>  Issue Type: Bug
>  Components: build
> Environment: * Ubuntu 16.04.3 LTS
> * Apache Ignite 2.3.0
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
>  Labels: build
>
> It looks like following libraries aren't included in the build:
>  * google-http-client-1.22.0.jar
>  * google-http-client-jackson2-1.22.0.jar
>  * google-oauth-client-1.22.0.jar
> Steps to reproduce:
> 1. Download apache-ignite-fabric-2.3.0-bin.zip 
> ([http://apache-mirror.rbc.ru/pub/apache//ignite/2.3.0/apache-ignite-fabric-2.3.0-bin.zip]).
> 2. Unzip archive.
> 3. Move ignite-rest-http from /libs/optional to /libs
> 4. Move ignite-gce from /libs/optional to /libs
> 5. Update IgniteConfiguration in default-config.xml:
> {code:xml}
> 
>   
> 
>class="org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder">
> 
> 
> 
>  value="discovery-sp...@apache-ignite.iam.gserviceaccount.com"/>
>   
> 
>   
> 
> {code}
> 6. Copy  into $IGNITE_HOME
> 7. Run bin/ignite.sh
> 8. Log:
> {code:java}
> class org.apache.ignite.IgniteException: Failed to instantiate Spring XML 
> application context (make sure all classes used in Spring configuration are 
> present at CLASSPATH) 
> [springUrl=file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]
>  at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
>  at org.apache.ignite.Ignition.start(Ignition.java:350)
>  at 
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to 
> instantiate Spring XML application context (make sure all classes used in 
> Spring configuration are present at CLASSPATH) 
> [springUrl=file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]
>  at 
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:387)
>  at 
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:104)
>  at 
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:98)
>  at 
> org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:673)
>  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:874)
>  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
>  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
>  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
>  at org.apache.ignite.Ignition.start(Ignition.java:347)
>  ... 1 more
> Caused by: org.springframework.beans.factory.BeanCreationException: Error 
> creating bean with name 
> 'org.apache.ignite.configuration.IgniteConfiguration#0' defined in URL 
> [file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
>  Cannot create inner bean 
> 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#65e2dbf3' of type 
> [org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] while setting bean 
> property 'discoverySpi'; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#65e2dbf3' 
> defined in URL 
> [file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
>  Cannot create inner bean 
> 'org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder#1d16f93d'
>  of type 
> [org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder]
>  while setting bean property 'ipFinder'; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 
> 'org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder#1d16f93d'
>  defined in URL 
> [file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
>  Instantiation of bean failed; nested exception is 
> 

[jira] [Created] (IGNITE-7816) DataFrame examples: wrong folder, hidden on TeamCity

[Nikolay Izhikov (JIRA)]

Nikolay Izhikov created IGNITE-7816:
---

 Summary: DataFrame examples: wrong folder, hidden on TeamCity
 Key: IGNITE-7816
 URL: https://issues.apache.org/jira/browse/IGNITE-7816
 Project: Ignite
  Issue Type: Sub-task
  Components: documentation
Reporter: Nikolay Izhikov
Assignee: Nikolay Izhikov
 Fix For: 2.4


1. Spark DataFrame examples are in 
{{examples/src/main/spark/org/apache/ignite/examples/spark}} folder. Should be 
moved to {{examples/src/main/scala/org/apache/ignite/scalar/examples/spark}}.

2. Spark DataFrame examples not tested on Team City under Ignite Examples. 

https://issues.apache.org/jira/browse/IGNITE-7655?focusedCommentId=16377875=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16377875



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-7655:
-

> Also, we need to have examples of Java API usage. If you don't have anything 
> ready, then Akmal can create Java versions of the Scala example for 2.5.

I don't have ready java examples. It would be great, ff Akmal can help with it.

> Spark Data Frames: saving data frames into Ignite needs to be documented
> 
>
> Key: IGNITE-7655
> URL: https://issues.apache.org/jira/browse/IGNITE-7655
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.4
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-7655:
-

[~dmagda] [~abchaudhri]

> Could you have a look and update the doc one more time?

I tried to merge my edits with current Akmal version of the page.
Please, check it.

> Please make sure this option below is documented: {{SaveMode.Append + 
> OPTION_STREAMER_ALLOW_OVERWRITE=true}}

Done.

> The problem with the existing Scala examples is that they are added to the 
> folder of Java examples:

It's interesting, actually.
I've checked it locally and it works with scala examples in spark folder.
Anyway, I will move examples to the right folder and make sure it tested on TC.

> If it's not late to merge the changes to 2.4, please fix it.

OK. I will fix it in master and mail to dev-list.

> Spark Data Frames: saving data frames into Ignite needs to be documented
> 
>
> Key: IGNITE-7655
> URL: https://issues.apache.org/jira/browse/IGNITE-7655
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.4
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-6489) Expiration Policies and Durable Memory Doc

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-6489:
---

Assignee: Denis Magda  (was: Alexey Goncharuk)

> Expiration Policies and Durable Memory Doc
> --
>
> Key: IGNITE-6489
> URL: https://issues.apache.org/jira/browse/IGNITE-6489
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: 2.5
>
>
> We must make sure that the existing expiration policies documentation [1] 
> makes sense for the off-heap space of the durable memory:
> https://apacheignite.readme.io/docs/expiry-policies



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-6489) Expiration Policies and Durable Memory Doc

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-6489:

Component/s: documentation

> Expiration Policies and Durable Memory Doc
> --
>
> Key: IGNITE-6489
> URL: https://issues.apache.org/jira/browse/IGNITE-6489
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 2.5
>
>
> We must make sure that the existing expiration policies documentation [1] 
> makes sense for the off-heap space of the durable memory:
> https://apacheignite.readme.io/docs/expiry-policies



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-6489) Expiration Policies and Durable Memory Doc

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-6489:

Fix Version/s: 2.5

> Expiration Policies and Durable Memory Doc
> --
>
> Key: IGNITE-6489
> URL: https://issues.apache.org/jira/browse/IGNITE-6489
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 2.5
>
>
> We must make sure that the existing expiration policies documentation [1] 
> makes sense for the off-heap space of the durable memory:
> https://apacheignite.readme.io/docs/expiry-policies



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6489) Expiration Policies and Durable Memory Doc

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-6489:
-

Relevant for 2.4 release, no need to create a hidden copy for 2.5 release.

> Expiration Policies and Durable Memory Doc
> --
>
> Key: IGNITE-6489
> URL: https://issues.apache.org/jira/browse/IGNITE-6489
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 2.5
>
>
> We must make sure that the existing expiration policies documentation [1] 
> makes sense for the off-heap space of the durable memory:
> https://apacheignite.readme.io/docs/expiry-policies



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-6816) Webconsole: investigate/integrate Webpack dll-plugin

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-6816:


Assignee: Alexander Kalinin  (was: Dmitriy Shabalin)

Lets try Web Pack 4 also.

> Webconsole: investigate/integrate Webpack dll-plugin
> 
>
> Key: IGNITE-6816
> URL: https://issues.apache.org/jira/browse/IGNITE-6816
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Alexander Kalinin
>Priority: Trivial
>
> As the webconsole frontend app size grows, it takes more and more time to 
> incrementally rebuild after each source code change in development 
> environment. Let's investigate this plugin 
> https://webpack.js.org/plugins/dll-plugin/ and integrate it into webpack 
> build pipeline if it offers measureable performance improvements.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6400) Document ClientConnectorConfiguration

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-6400:
-

[~pgarg] , please update the parameters table from this section

[https://apacheignite-sql.readme.io/docs/jdbc-driver#section-cluster-configuration]

 

with the new parameters that were added in 2.4:

[https://github.com/apache/ignite/blob/ignite-2.4/modules/core/src/main/java/org/apache/ignite/configuration/ClientConnectorConfiguration.java]

 

Briefly comparing 1 to 2, I see the following changes:
{code:java}
/** Idle timeout. */
private long idleTimeout = DFLT_IDLE_TIMEOUT;
/** JDBC connections enabled flag. */
private boolean jdbcEnabled = true;
/** ODBC connections enabled flag. */
private boolean odbcEnabled = true;
/** JDBC connections enabled flag. */
private boolean thinCliEnabled = true;{code}
 

Check up the ODBC counterpart that needs to be updated too:

[https://apacheignite-sql.readme.io/docs/odbc-driver#cluster-configuration]

 

> Document ClientConnectorConfiguration
> -
>
> Key: IGNITE-6400
> URL: https://issues.apache.org/jira/browse/IGNITE-6400
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, thin client
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-6400) Document ClientConnectorConfiguration

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-6400:
---

Assignee: Prachi Garg  (was: Vladimir Ozerov)

> Document ClientConnectorConfiguration
> -
>
> Key: IGNITE-6400
> URL: https://issues.apache.org/jira/browse/IGNITE-6400
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, thin client
>Reporter: Vladimir Ozerov
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7720) Update ODBC cluster configuration: replace OdbcConfiguration with ClientConnectorConfiguration

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-7720:
-

[~isapego] , thanks a lot. Looks good.

> Update ODBC cluster configuration: replace OdbcConfiguration with 
> ClientConnectorConfiguration
> --
>
> Key: IGNITE-7720
> URL: https://issues.apache.org/jira/browse/IGNITE-7720
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.4
>
>
> https://apacheignite-sql.readme.io/docs/odbc-driver#section-cluster-configuration
> Please note that ODBC configuration is depricated. It is better to update 
> this page with 
> ClientConnectorConfiguration
> BTW, https://apacheignite-sql.readme.io/docs/jdbc-driver is already updated )
> {quote}
> /**
>  * ODBC configuration.
>  * 
>  * Deprecated as of Apache Ignite 2.1. Please use {@link 
> ClientConnectorConfiguration} and
>  * {@link 
> IgniteConfiguration#setClientConnectorConfiguration(ClientConnectorConfiguration)}
>  instead.
>  */
> @Deprecated
> public class OdbcConfiguration {
> {quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-7720) Update ODBC cluster configuration: replace OdbcConfiguration with ClientConnectorConfiguration

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-7720.
---

> Update ODBC cluster configuration: replace OdbcConfiguration with 
> ClientConnectorConfiguration
> --
>
> Key: IGNITE-7720
> URL: https://issues.apache.org/jira/browse/IGNITE-7720
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.4
>
>
> https://apacheignite-sql.readme.io/docs/odbc-driver#section-cluster-configuration
> Please note that ODBC configuration is depricated. It is better to update 
> this page with 
> ClientConnectorConfiguration
> BTW, https://apacheignite-sql.readme.io/docs/jdbc-driver is already updated )
> {quote}
> /**
>  * ODBC configuration.
>  * 
>  * Deprecated as of Apache Ignite 2.1. Please use {@link 
> ClientConnectorConfiguration} and
>  * {@link 
> IgniteConfiguration#setClientConnectorConfiguration(ClientConnectorConfiguration)}
>  instead.
>  */
> @Deprecated
> public class OdbcConfiguration {
> {quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-7655:
-

[~NIzhikov] , thanks for the explanation! It helped. Unfortunately, I don't see 
the changes (plus there are some TODOs left on the page). Akmal told me he had 
troubles with the same page earlier today. Probably, that's because you both 
might have been editing it at the same time. 

Could you have a look and update the doc one more time? Please make sure this 
option below is documented:

{{SaveMode.Append}} + {{OPTION_STREAMER_ALLOW_OVERWRITE=true}}

The problem with the existing Scala examples is that they are added to the 
folder of Java examples:

[https://github.com/apache/ignite/tree/master/examples/src/main/spark/org/apache/ignite/examples/spark]

while they need to be here:

[https://github.com/apache/ignite/tree/master/examples/src/main/scala/org/apache/ignite/scalar/examples/spark]

If it's not late to merge the changes to 2.4, please fix it. Ask the community 
for permission. Otherwise, create a ticket for 2.5.

Also, we need to have examples of Java API usage. If you don't have anything 
ready, then Akmal can create Java versions of the Scala example for 2.5.

> Spark Data Frames: saving data frames into Ignite needs to be documented
> 
>
> Key: IGNITE-7655
> URL: https://issues.apache.org/jira/browse/IGNITE-7655
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.4
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7815) IgniteSpringBean implements SmartInitializingSingleton in version 2.3.2+

[Valeri Chibaev (JIRA)]

Valeri Chibaev created IGNITE-7815:
--

 Summary: IgniteSpringBean implements SmartInitializingSingleton in 
version 2.3.2+
 Key: IGNITE-7815
 URL: https://issues.apache.org/jira/browse/IGNITE-7815
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3
Reporter: Valeri Chibaev


IgniteSpringBean changed the way it starts Ignite grid:
 * implements InitializingBean#afterPropertiesSet in version 2.3.1
 * implements SmartInitializingSingleton#afterSingletonsInstantiated in version 
2.3.2+

This cause problem in my code that uses spring cache 
@org.springframework.cache.annotation.Cacheable via 
org.apache.ignite.cache.spring.SpringCacheManager throwing error from spring 
bean initialisation:

 
{code:java}
Caused by: org.springframework.beans.factory.BeanCreationException: Error 
creating bean with name 'cacheManager' defined in class path resource 
[spring-inc-cache.xml]: Invocation of init method failed; nested exception is 
class org.apache.ignite.IgniteIllegalStateException: Ignite instance with 
provided name doesn't exist. Did you call Ignition.start(..) to start an Ignite 
instance? [name=mktrsk-ignite-grid]
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1628)
 ~[spring-beans-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555)
 ~[spring-beans-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
 ~[spring-beans-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at 
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
 ~[spring-beans-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at 
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
 ~[spring-beans-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at 
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
 ~[spring-beans-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at 
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
 ~[spring-beans-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at 
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:351)
 ~[spring-beans-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
... 27 common frames omitted
Caused by: org.apache.ignite.IgniteIllegalStateException: Ignite instance with 
provided name doesn't exist. Did you call Ignition.start(..) to start an Ignite 
instance? [name=mktrsk-ignite-grid]
at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1312) 
~[ignite-core-2.3.3.jar!/:2.3.3]
at org.apache.ignite.Ignition.ignite(Ignition.java:530) 
~[ignite-core-2.3.3.jar!/:2.3.3]
at 
org.apache.ignite.cache.spring.SpringCacheManager.afterPropertiesSet(SpringCacheManager.java:328)
 ~[ignite-spring-2.3.3.jar!/:2.3.3]
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1687)
 ~[spring-beans-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1624)
 ~[spring-beans-4.3.9.RELEASE.jar!/:4.3.9.RELEASE]
... 34 common frames omitted
{code}
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7329) .NET: Thin client: SSL

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7329:


Github user asfgit closed the pull request at:

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


> .NET: Thin client: SSL
> --
>
> Key: IGNITE-7329
> URL: https://issues.apache.org/jira/browse/IGNITE-7329
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.5
>
>
> Allow secure .NET thin client connection.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7329) .NET: Thin client: SSL

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7329:


Merged to master: {{853cd7a4c69195bc0b6806051c161f0a8443e5ac}}.

> .NET: Thin client: SSL
> --
>
> Key: IGNITE-7329
> URL: https://issues.apache.org/jira/browse/IGNITE-7329
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.5
>
>
> Allow secure .NET thin client connection.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-6846) Add metrics for entry processor invocations

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov edited comment on IGNITE-6846 at 2/26/18 8:14 PM:
---

[~vkulichenko] , hi !

Sorry, for delay. I have resolved conflicts, and rerun 
[tests|https://ci.ignite.apache.org/viewLog.html?buildId=1110794=buildResultsDiv=IgniteTests24Java8_RunAll]

Please, review the ticket.

 


was (Author: alexey kuznetsov):
[~vkulichenko] , hi !

Sorry, for delay. I have resolved conflicts, and rerun tests.

Please, review the ticket.

 

> Add metrics for entry processor invocations
> ---
>
> Key: IGNITE-6846
> URL: https://issues.apache.org/jira/browse/IGNITE-6846
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Alexey Kuznetsov
>Priority: Critical
>  Labels: iep-6
> Fix For: 2.5
>
>
> {{CacheMetrics}} object has multiple metrics for various cache operations 
> like {{get}}, {{put}} and {{remove}}, but nothing for 
> {{invoke}}/{{EntryProcessor}}. It makes sense to add such metrics, for 
> example:
> * Total number of `invoke` operations executed.
> * Number of `invoke` operations that included updates.
> * Number of read-only `invoke` operations.
> * Min/max/avg execution time.
> * ...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-7655:
-

Hello, [~abchaudhri].

> The GitHub examples are in Scala, but I will try and build the project and 
> run the code to test that it works.

Actually, all examples should be tested in Ignite Example plan.
I checked it and found that {{IgniteExamplesSparkSelfTestSuite}} doesn't 
included in "Ignite Example" run.
I will fix it, so all Spark examples will be tested.

> Spark Data Frames: saving data frames into Ignite needs to be documented
> 
>
> Key: IGNITE-7655
> URL: https://issues.apache.org/jira/browse/IGNITE-7655
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.4
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

[Akmal Chaudhri (JIRA)]

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

Akmal Chaudhri commented on IGNITE-7655:


[~NIzhikov]

I have done some minor edits throughout the document to improve readability. 
The GitHub examples are in Scala, but I will try and build the project and run 
the code to test that it works.

> Spark Data Frames: saving data frames into Ignite needs to be documented
> 
>
> Key: IGNITE-7655
> URL: https://issues.apache.org/jira/browse/IGNITE-7655
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.4
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-4648) IgniteInternalTx.prepare() does not wait for async operations to complete

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4648:


Github user SomeFire closed the pull request at:

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


> IgniteInternalTx.prepare() does not wait for async operations to complete
> -
>
> Key: IGNITE-4648
> URL: https://issues.apache.org/jira/browse/IGNITE-4648
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Fix For: 2.3
>
>
> {{commit}} and {{rollback}} wait for async operations by calling 
> {{tx.txState().awaitLastFut();}} (see {{GridCacheSharedContext}}).
> There is no such thing in {{IgniteInternalTx.prepare()}} implementations.
> Since {{prepare}} is an internal method, this is not an issue mostly, except 
> for two things:
> * JTA. {{CacheJtaResource}} calls {{prepare()}} explicitly. 
> * .NET {{TransactionScope}} API. Same thing as JTA, basically. 
> {{PlatformTransactions}} call {{prepare()}} as well.
> As a result, if user starts an async operation within JTA transaction and 
> then completes the tx, undefined behavior is possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7720) Update ODBC cluster configuration: replace OdbcConfiguration with ClientConnectorConfiguration

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-7720:
---

Assignee: Denis Magda  (was: Igor Sapego)

> Update ODBC cluster configuration: replace OdbcConfiguration with 
> ClientConnectorConfiguration
> --
>
> Key: IGNITE-7720
> URL: https://issues.apache.org/jira/browse/IGNITE-7720
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.4
>
>
> https://apacheignite-sql.readme.io/docs/odbc-driver#section-cluster-configuration
> Please note that ODBC configuration is depricated. It is better to update 
> this page with 
> ClientConnectorConfiguration
> BTW, https://apacheignite-sql.readme.io/docs/jdbc-driver is already updated )
> {quote}
> /**
>  * ODBC configuration.
>  * 
>  * Deprecated as of Apache Ignite 2.1. Please use {@link 
> ClientConnectorConfiguration} and
>  * {@link 
> IgniteConfiguration#setClientConnectorConfiguration(ClientConnectorConfiguration)}
>  instead.
>  */
> @Deprecated
> public class OdbcConfiguration {
> {quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7814) Lost scala211.library.version parameter

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7814:


GitHub user akalash opened a pull request:

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

IGNITE-7814 returned scala211.library.version parameter



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

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

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

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


commit 6ed05a814a84f6501dcd515ba6a89edba5303778
Author: Anton Kalashnikov 
Date:   2018-02-26T17:08:07Z

IGNITE-7814 returned scala211.library.version parameter




> Lost scala211.library.version parameter
> ---
>
> Key: IGNITE-7814
> URL: https://issues.apache.org/jira/browse/IGNITE-7814
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> How we can see in test 
> https://ci.ignite.apache.org/viewLog.html?buildId=1109854#testNameId451522206339372479.
>  We use
> scala211.library.version but I see that some time ago it was renamed to 
> scala.library.version at determination place.
> I think we can't use scala.library.version parameter and we will should 
> return scala211.library.version parameter because it is using at specific 
> place for scala2.11 .



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7814) Lost scala211.library.version parameter

[Anton Kalashnikov (JIRA)]

Anton Kalashnikov created IGNITE-7814:
-

 Summary: Lost scala211.library.version parameter
 Key: IGNITE-7814
 URL: https://issues.apache.org/jira/browse/IGNITE-7814
 Project: Ignite
  Issue Type: Bug
Reporter: Anton Kalashnikov
Assignee: Anton Kalashnikov


How we can see in test 
https://ci.ignite.apache.org/viewLog.html?buildId=1109854#testNameId451522206339372479.
 We use

scala211.library.version but I see that some time ago it was renamed to 
scala.library.version at determination place.

I think we can't use scala.library.version parameter and we will should return 
scala211.library.version parameter because it is using at specific place for 
scala2.11 .



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7813) Method org/apache/ignite/cache/hibernate/HibernateRegionFactory.start(Lorg/hibernate/boot/spi/SessionFactoryOptions;Ljava/util/Properties;)V is abstract

[Pavan Jadda (JIRA)]

Pavan Jadda created IGNITE-7813:
---

 Summary:  Method 
org/apache/ignite/cache/hibernate/HibernateRegionFactory.start(Lorg/hibernate/boot/spi/SessionFactoryOptions;Ljava/util/Properties;)V
 is abstract
 Key: IGNITE-7813
 URL: https://issues.apache.org/jira/browse/IGNITE-7813
 Project: Ignite
  Issue Type: Bug
  Components: hibernate
Affects Versions: 2.3
Reporter: Pavan Jadda


I am trying to implement Hibernate 2nd level cache with Apache Ignite. For 
this, I used following maven dependency in pom.xml based on Apache Ignite 
[official 
documentation|https://apacheignite-mix.readme.io/docs/hibernate-l2-cache]. I 
get the following exception when I run the application. I use this JHipster, 
Docker, and Apache Ignite. Code uploaded to 
[github|https://github.com/pavankjadda/ApacheIgnite-JHipster-Docker]

 

*Method 
org/apache/ignite/cache/hibernate/HibernateRegionFactory.start(Lorg/hibernate/boot/spi/SessionFactoryOptions;Ljava/util/Properties;)V
 is abstract*



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (IGNITE-7801) Missing artifact org.apache.ignite:ignite-hibernate_5.1

[Pavan Jadda (JIRA)]

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

Pavan Jadda resolved IGNITE-7801.
-
Resolution: Fixed

Downloaded jar files from here

 

https://stackoverflow.com/questions/48955499/missing-artifact-org-apache-igniteignite-hibernate-5-1jar2-3-0/48967057#48967057

> Missing artifact org.apache.ignite:ignite-hibernate_5.1
> ---
>
> Key: IGNITE-7801
> URL: https://issues.apache.org/jira/browse/IGNITE-7801
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: 2.3
>Reporter: Pavan Jadda
>Priority: Blocker
>
> I am trying to implement Hibernate 2nd level cache with Apache Ignite. For 
> this, I used following maven dependency in pom.xml based on Apache Ignite 
> [official 
> documentation|https://apacheignite-mix.readme.io/docs/hibernate-l2-cache]. I 
> got following excepti[on 
> |https://apacheignite-mix.readme.io/docs/hibernate-l2-cache]*Missing artifact 
> org.apache.ignite:ignite-hibernate_5.1:jar:2.3.0* when I build the project. 
> Code uploaded to 
> [#https://github.com/pavankjadda/ApacheIgnite-JHipster-Docker]. I am using 
> Apache Ignite 2.3.0 version. I tried other versions too and nothing worked



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-7756) Streamer fails if IgniteUuid is indexed

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov edited comment on IGNITE-7756 at 2/26/18 4:20 PM:
--

Hello, [~vozerov].

Can you, please, take a look at my changes?
It, literally, 1 line of production code.

Upsource - https://reviews.ignite.apache.org/ignite/review/IGNT-CR-499
TC - https://ci.ignite.apache.org/viewLog.html?buildId=1108157;

Dev list discussion - 
http://apache-ignite-developers.2346864.n4.nabble.com/IgniteDataStreamer-silently-fails-on-a-server-node-td27239.html


was (Author: nizhikov):
Hello, [~vozerov].

Can you, please, take a look at my changes?
It, literally, 1 line of production code.

Upsource - https://reviews.ignite.apache.org/ignite/review/IGNT-CR-499
TC - https://ci.ignite.apache.org/viewLog.html?buildId=1108157;

> Streamer fails if IgniteUuid is indexed
> ---
>
> Key: IGNITE-7756
> URL: https://issues.apache.org/jira/browse/IGNITE-7756
> Project: Ignite
>  Issue Type: Bug
>  Components: streaming
>Affects Versions: 2.3
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> IgniteDataStreamer are failed to put data to the cache if IgniteUuid is 
> IndexedType.
> Spark tests in IGNITE-7227 are failed because of this issue.
> Reproducer:
> {code:java}
> public void testStreamer() throws Exception {
> Ignite client = grid("client");
> CacheConfiguration ccfg = new CacheConfiguration("UUID_CACHE");
> ccfg.setIndexedTypes(IgniteUuid.class, String.class);
> client.createCache(ccfg);
> try(IgniteDataStreamer cache =
> client.dataStreamer("UUID_CACHE")) {
> for(Integer i=0; i<2; i++)
> cache.addData(IgniteUuid.randomUuid(), i.toString());
> }
> }
> {code}
> Exception stack trace:
> {noformat}
> [23:43:35] (err) Failed to execute compound future reducer: 
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false, 
> cancelled=false, err=null, futs=[true, true]][23:43:35] (err) Failed to 
> execute compound future reducer: GridCompoundFuture [rdc=null, initFlag=1, 
> lsnrCalls=0, done=false, cancelled=false, err=null, futs=[true, true]]class 
> org.apache.ignite.IgniteCheckedException: DataStreamer request failed 
> [node=57961924-82ec-4d56-81eb-1a4109a0]
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:1900)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:344)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1554)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1182)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1089)
>   at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:499)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteException: Failed to set initial 
> value for cache entry
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:2135)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:397)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:302)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:59)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:89)
>   ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update 
> index, incorrect key class [expCls=org.apache.ignite.lang.IgniteUuid, 
> actualCls=org.apache.ignite.internal.binary.BinaryObjectImpl]
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.typeByValue(GridQueryProcessor.java:1954)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1877)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:403)
>  

[jira] [Commented] (IGNITE-7531) SQL: Create data load benchmarks

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7531:


GitHub user pavel-kuznetsov opened a pull request:

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

IGNITE-7531: Implemented copy, insert, batched insert benchmarks

https://issues.apache.org/jira/browse/IGNITE-7531

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

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

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

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


commit 4b2078a06230b921e19e9ac6912d93f48adae037
Author: Pavel Kuznetsov 
Date:   2018-02-07T14:39:18Z

IGNITE-7253: Implemented total time probe

commit ef4ac90ffa1141e80462aea7b6024477583e52b0
Author: Pavel Kuznetsov 
Date:   2018-02-08T16:12:59Z

IGNITE-7253: Implemented simple insert benchmark for upload

commit 31056439f36b5ffeebd45f2140c3750afb9a104e
Author: Pavel Kuznetsov 
Date:   2018-02-09T18:58:50Z

IGNITE-7253: Assert results of TotalTimeProbe is correct

commit d6e1e3f7d76cf612574d5b7e756fd01d0c161c90
Author: Pavel Kuznetsov 
Date:   2018-02-09T18:59:47Z

IGNITE-7253: Batch insert upload benchmark draft

commit 5175d69e5cbb6bc050dd87ccc213d526a40d61fa
Author: Pavel Kuznetsov 
Date:   2018-02-09T19:01:15Z

IGNITE-7253: Add missed configs for upload benchmarks

commit 53e3e58f69261361f7d50695f72aa42c91bfcbd7
Author: Pavel Kuznetsov 
Date:   2018-02-12T11:11:34Z

IGNITE-7253: add batch size parameter (sqlRange);
renamed total size parameter (sqlRange -> range)

commit 998c8f44a432f92c595d37ccacd160d007048311
Author: Pavel Kuznetsov 
Date:   2018-02-12T16:01:32Z

IGNITE-7253: moved queries to separated class; changed table schema

commit 400f564c011362acf151ecdc304ab5a021a69be6
Author: Pavel Kuznetsov 
Date:   2018-02-12T18:47:46Z

IGNITE-7253: renamed configuration names

commit 8727fc47e8dd7796e3df5e070bd9890708664e66
Author: Pavel Kuznetsov 
Date:   2018-02-13T14:10:24Z

Merge remote-tracking branch 'origin/master' into IGNITE-7531

commit 056e97c512ac35ef826eddcb360dd97bf41917be
Author: Pavel Kuznetsov 
Date:   2018-02-13T15:27:12Z

IGNITE-7253: added init method, added comment

commit eae7018b17f7dfc626b7159a38afcf95ac585913
Author: Pavel Kuznetsov 
Date:   2018-02-14T11:39:15Z

IGNITE-7253: added csv copy benchmark, updated comments

commit 3029cb55faeddcb4fa940a9f1592653d90853b7d
Author: Pavel Kuznetsov 
Date:   2018-02-14T14:56:54Z

IGNITE-7253: use full sync and 10M inserts, added configuration for csv
benchmark

commit f1f2f53837e52f4ca5400c94f8131878724419f5
Author: Pavel Kuznetsov 
Date:   2018-02-14T16:21:57Z

Merge remote-tracking branch 'origin/master' into IGNITE-7531

commit e1a91f9547c82ac622a2392e4b352de82d062d67
Author: Pavel Kuznetsov 
Date:   2018-02-15T14:31:58Z

IGNITE-7253: Don't place csv file in tmpfs; Added comments

commit 8ae1e8b95a7d4beb58af25bb08d26c60dfb7c6f2
Author: Pavel Kuznetsov 
Date:   2018-02-15T14:33:27Z

IGNITE-7253: Create table using thin driver

commit db68c889f9673543508f75b1d3470cbf6869f37f
Author: Pavel Kuznetsov 
Date:   2018-02-15T14:44:53Z

Merge remote-tracking branch 'origin/master' into IGNITE-7531
brings fixes for COPY command can't find table

commit 801cb9c6293308508c5929096ad5448e8c20fdff
Author: Pavel Kuznetsov 
Date:   2018-02-15T17:06:55Z

IGNITE-7253: updated configuration

commit b834f43bcdcaa08d501a512bc1d74974e82e7331
Author: Pavel Kuznetsov 
Date:   2018-02-20T11:22:32Z

IGNITE-7253: added persistence config;
added activation in base class

commit 0250b365384cab0ad8fdd581c6c7d6286f823aed
Author: Pavel Kuznetsov 
Date:   2018-02-20T12:08:43Z

IGNITE-7253: added combo configurations

commit 2b798df53160b66fc1e83708169349520b029f81
Author: Pavel Kuznetsov 
Date:   2018-02-20T12:10:09Z

IGNITE-7253: cosmetic changes

commit 934ea7275fc54b3f0e98665e3325b97aa6ce23bf
Author: Pavel Kuznetsov 
Date:   2018-02-20T13:52:42Z

IGNITE-7253: force drop and create table before test

commit 2a1580c88bcec009773c9aa9f5ae4c7b10767a9f
Author: Pavel Kuznetsov 
Date:   2018-02-20T18:45:13Z

IGNITE-7253: option to temporally disable wall while uploading;
fixed configuration

commit 7194461a25c1dfa4da37b8030f1a434395418849
Author: Pavel Kuznetsov 
Date:   

[jira] [Commented] (IGNITE-7756) Streamer fails if IgniteUuid is indexed

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-7756:
-

Hello, [~vozerov].

Can you, please, take a look at my changes?
It, literally, 1 line of production code.

Upsource - https://reviews.ignite.apache.org/ignite/review/IGNT-CR-499
TC - https://ci.ignite.apache.org/viewLog.html?buildId=1108157;

> Streamer fails if IgniteUuid is indexed
> ---
>
> Key: IGNITE-7756
> URL: https://issues.apache.org/jira/browse/IGNITE-7756
> Project: Ignite
>  Issue Type: Bug
>  Components: streaming
>Affects Versions: 2.3
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> IgniteDataStreamer are failed to put data to the cache if IgniteUuid is 
> IndexedType.
> Spark tests in IGNITE-7227 are failed because of this issue.
> Reproducer:
> {code:java}
> public void testStreamer() throws Exception {
> Ignite client = grid("client");
> CacheConfiguration ccfg = new CacheConfiguration("UUID_CACHE");
> ccfg.setIndexedTypes(IgniteUuid.class, String.class);
> client.createCache(ccfg);
> try(IgniteDataStreamer cache =
> client.dataStreamer("UUID_CACHE")) {
> for(Integer i=0; i<2; i++)
> cache.addData(IgniteUuid.randomUuid(), i.toString());
> }
> }
> {code}
> Exception stack trace:
> {noformat}
> [23:43:35] (err) Failed to execute compound future reducer: 
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false, 
> cancelled=false, err=null, futs=[true, true]][23:43:35] (err) Failed to 
> execute compound future reducer: GridCompoundFuture [rdc=null, initFlag=1, 
> lsnrCalls=0, done=false, cancelled=false, err=null, futs=[true, true]]class 
> org.apache.ignite.IgniteCheckedException: DataStreamer request failed 
> [node=57961924-82ec-4d56-81eb-1a4109a0]
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:1900)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:344)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1554)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1182)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1089)
>   at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:499)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteException: Failed to set initial 
> value for cache entry
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:2135)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:397)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:302)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:59)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:89)
>   ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update 
> index, incorrect key class [expCls=org.apache.ignite.lang.IgniteUuid, 
> actualCls=org.apache.ignite.internal.binary.BinaryObjectImpl]
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.typeByValue(GridQueryProcessor.java:1954)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1877)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:403)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:1343)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1207)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:345)
>   at 
> 

[jira] [Commented] (IGNITE-4706) Rewrite test GridTaskExecutionSelfTest::testJobIdCollision to use multiple JVMs

[Maxim Muzafarov (JIRA)]

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

Maxim Muzafarov commented on IGNITE-4706:
-

[~sergey-chugunov], Hi

 
I'm triyng to clarify for myseft issue [1] of rewriting this test case to use 
multiple JVMs. I'm trying to reproduce it using steps described here [2]: 
As I correct understand issue description, I'm runing testJobIdCollision and 
expecting to get exception:
"Received computation request with duplicate job ID"
, but I've got:
"Job has already been hold [ctx=GridJobContextImpl 
[jobId=f7e74a1d161-08edbe47-9b65-4ed2-8d0c-a8a1a673, timeoutObj=null, 
attrs={}]]"


So, does this test-case actual or can be removed? Or we should use another 
IgniteCallable like othis one: IgniteWalRecoveryTest.LoadRunnable [4]?
 
Also, IgniteClusterProcessProxy#forNodeId [3] doesn't implemented yet. Brief 
search for some JIRA's of implementation this method doesn't return anything. 
What should we do with this?

[1] https://issues.apache.org/jira/browse/IGNITE-4706
[2] https://issues.apache.org/jira/browse/IGNITE-1384  
[3] 
[https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/testframework/junits/multijvm/IgniteClusterProcessProxy.java#L204]
[4] 
[https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/persistence/db/wal/IgniteWalRecoveryTest.java#L1552]

> Rewrite test GridTaskExecutionSelfTest::testJobIdCollision to use multiple 
> JVMs
> ---
>
> Key: IGNITE-4706
> URL: https://issues.apache.org/jira/browse/IGNITE-4706
> Project: Ignite
>  Issue Type: Test
>Reporter: Sergey Chugunov
>Priority: Major
>
> h2. Notes
> Test emulates ID collision by tricks with *IgniteUuid* local counter which 
> leads to failures of important components like discovery messaging.
> It makes test unstable; sometimes it hangs or fails in a various ways.
> h2. Acceptance Criteria
> Test exploits multiple JVMs to execute its logic, all tricks with IgniteUuid 
> are removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6005) [Test failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-6005:
-

[~agura] Thank you, for paying attention to my PR!

> [Test failed] 
> GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
> -
>
> Key: IGNITE-6005
> URL: https://issues.apache.org/jira/browse/IGNITE-6005
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Example of fail
> https://ci.ignite.apache.org/viewLog.html?buildId=762788=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures
> Typical problem is 
> {code}
> org.apache.ignite.IgniteInterruptedException: Failed to wait for asynchronous 
> operation permit (thread got interrupted).
> at 
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:805)
> at 
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:803)
> at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:961)
> at 
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1026)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.InterruptedException: null
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1301)
> at java.util.concurrent.Semaphore.acquire(Semaphore.java:317)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOpAcquire(GridCacheAdapter.java:4314)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4177)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:196)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4509)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4490)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1324)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:329)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$5.applyx(DataStructuresProcessor.java:635)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.retryTopologySafe(DataStructuresProcessor.java:1519)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeDataStructure(DataStructuresProcessor.java:629)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeSemaphore(DataStructuresProcessor.java:1188)
> at 
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1023)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> 

[jira] [Commented] (IGNITE-6005) [Test failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6005:


Github user nizhikov closed the pull request at:

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


> [Test failed] 
> GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
> -
>
> Key: IGNITE-6005
> URL: https://issues.apache.org/jira/browse/IGNITE-6005
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Example of fail
> https://ci.ignite.apache.org/viewLog.html?buildId=762788=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures
> Typical problem is 
> {code}
> org.apache.ignite.IgniteInterruptedException: Failed to wait for asynchronous 
> operation permit (thread got interrupted).
> at 
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:805)
> at 
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:803)
> at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:961)
> at 
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1026)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.InterruptedException: null
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1301)
> at java.util.concurrent.Semaphore.acquire(Semaphore.java:317)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOpAcquire(GridCacheAdapter.java:4314)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4177)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:196)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4509)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4490)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1324)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:329)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$5.applyx(DataStructuresProcessor.java:635)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.retryTopologySafe(DataStructuresProcessor.java:1519)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeDataStructure(DataStructuresProcessor.java:629)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeSemaphore(DataStructuresProcessor.java:1188)
> at 
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1023)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> 

[jira] [Created] (IGNITE-7812) Slow rebalancing in case of enabled persistence

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-7812:


 Summary: Slow rebalancing in case of enabled persistence
 Key: IGNITE-7812
 URL: https://issues.apache.org/jira/browse/IGNITE-7812
 Project: Ignite
  Issue Type: Task
Reporter: Alexey Goncharuk


A user reported that rebalancing take significantly larger amounts of time when 
persistence is enabled even in LOG_ONLY mode.

Need to investigate how the performance of rebalancing may be increased.

Also, it would be great to estimate the benefit of file transfer for 
rebalancing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7811) ODBC: Implement connection failover

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-7811:

Description: 
Currently user has to manually connect to some specific Ignite server.
Implement some kind of automatic failover where ODBC driver knows about 
multiple nodes.

> ODBC: Implement connection failover
> ---
>
> Key: IGNITE-7811
> URL: https://issues.apache.org/jira/browse/IGNITE-7811
> Project: Ignite
>  Issue Type: New Feature
>  Components: odbc
>Affects Versions: 2.4
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.5
>
>
> Currently user has to manually connect to some specific Ignite server.
> Implement some kind of automatic failover where ODBC driver knows about 
> multiple nodes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7811) ODBC: Implement connection fail over

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-7811:

Component/s: odbc

> ODBC: Implement connection fail over
> 
>
> Key: IGNITE-7811
> URL: https://issues.apache.org/jira/browse/IGNITE-7811
> Project: Ignite
>  Issue Type: New Feature
>  Components: odbc
>Affects Versions: 2.4
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7811) ODBC: Implement connection failover

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-7811:

Summary: ODBC: Implement connection failover  (was: ODBC: Implement 
connection fail over)

> ODBC: Implement connection failover
> ---
>
> Key: IGNITE-7811
> URL: https://issues.apache.org/jira/browse/IGNITE-7811
> Project: Ignite
>  Issue Type: New Feature
>  Components: odbc
>Affects Versions: 2.4
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7811) ODBC: Implement connection fail over

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-7811:

Issue Type: New Feature  (was: Bug)

> ODBC: Implement connection fail over
> 
>
> Key: IGNITE-7811
> URL: https://issues.apache.org/jira/browse/IGNITE-7811
> Project: Ignite
>  Issue Type: New Feature
>  Components: odbc
>Affects Versions: 2.4
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7811) ODBC: Implement connection fail over

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-7811:

Affects Version/s: 2.4

> ODBC: Implement connection fail over
> 
>
> Key: IGNITE-7811
> URL: https://issues.apache.org/jira/browse/IGNITE-7811
> Project: Ignite
>  Issue Type: Bug
>  Components: odbc
>Affects Versions: 2.4
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7811) ODBC: Implement connection fail over

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-7811:

Fix Version/s: 2.5

> ODBC: Implement connection fail over
> 
>
> Key: IGNITE-7811
> URL: https://issues.apache.org/jira/browse/IGNITE-7811
> Project: Ignite
>  Issue Type: Bug
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7811) ODBC: Implement connection fail over

[Igor Sapego (JIRA)]

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

Igor Sapego reassigned IGNITE-7811:
---

Assignee: Igor Sapego

> ODBC: Implement connection fail over
> 
>
> Key: IGNITE-7811
> URL: https://issues.apache.org/jira/browse/IGNITE-7811
> Project: Ignite
>  Issue Type: Bug
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7811) ODBC: Implement connection fail over

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-7811:
---

 Summary: ODBC: Implement connection fail over
 Key: IGNITE-7811
 URL: https://issues.apache.org/jira/browse/IGNITE-7811
 Project: Ignite
  Issue Type: Bug
Reporter: Igor Sapego






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7809) Ignite PDS 2 & PDS 2 Direct IO: stable failures of IgniteWalFlushDefaultSelfTest

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7809:


GitHub user ilantukh opened a pull request:

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

IGNITE-7809 : Fixed tests.



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

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

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

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


commit 4925ffc10ce8e8287980eaec38b587512568a302
Author: Alexey Goncharuk 
Date:   2018-01-17T12:26:03Z

IGNITE-7453 Use GridUnsafe.cleanDirectBuffer in PageSnapshot

commit bcd68a058683b2f17b7ac60471b6e7aab3e4f6de
Author: Pavel Tupitsyn 
Date:   2018-01-17T12:38:20Z

IGNITE-7301 .NET: Baseline topology

This closes #3352

commit 66b96316a7775ce8a6e2ff4475185d5929e4998b
Author: devozerov 
Date:   2018-01-17T12:54:17Z

Merge branch 'master' into ignite-2.4

commit 268481c1cf7fe57df24be130eb67c3e3a13afe01
Author: Alexey Goncharuk 
Date:   2018-01-17T13:50:34Z

IGNITE-7453 Use GridUnsafe.cleanDirectBuffer in WalStat

commit db0cd105719c8ae713b13b34d9dca0a8cd45d377
Author: Pavel Tupitsyn 
Date:   2018-01-17T14:05:25Z

IGNITE-6776 .NET: Thin client: Add SQL & LINQ example

This closes #3390

commit c214db879101aa5660e2a50b11cd20964c0bc114
Author: Andrey Gura 
Date:   2018-01-17T12:42:41Z

ignite-7450 FileWriteAheadLogManager always uses RandomAccessFileIOFactory 
now

commit 75c27d5e49d7458e46eb46e6f87a445c3f1320ea
Author: Alexey Kuznetsov 
Date:   2018-01-18T02:25:19Z

IGNITE-7274 Web Console: Support multiple statements on Queries screen.
(cherry picked from commit 1926783)

commit 36cc822935387b2150e690c29bc6992dca0563f7
Author: Dmitriy Shabalin 
Date:   2018-01-18T04:49:08Z

IGNITE-7306 Web Console: Fixed export data from tables.
(cherry picked from commit 1bb60ec)

commit d753298b4012894b56f5c9218325211cd84a21d5
Author: Peter Ivanov 
Date:   2018-01-18T06:18:53Z

IGNITE-7107 Apache Ignite RPM packages

* added changelog to package specification

This closes #3396

commit 63445893f1bc75dc9777184499f7eabc1d4e51b1
Author: Denis Mekhanikov 
Date:   2018-01-18T08:36:18Z

IGNITE-3935 Use PeerDeployAware for streamer transformer - Fixes #3378.

Signed-off-by: Alexey Goncharuk 

commit f3f9f2a24b23027cf0c835140322e41a788932ae
Author: Pavel Tupitsyn 
Date:   2018-01-18T09:05:12Z

IGNITE-7413 Fix SqlDmlExample

This closes #3389

commit 1daa7c41bf1460a4d9a2b0c26a7a317f2fca3fb7
Author: Alexey Kuznetsov 
Date:   2018-01-18T10:14:53Z

IGNITE-7461 UI tools: Actualized data storage configuration.
(cherry picked from commit 577e632)

commit cf0080210d24d9dd8b057f959446fac5f8a4ca01
Author: dpavlov 
Date:   2018-01-18T10:53:29Z

IGNITE-7380 Implemented pluggable Direct IO - Fixes #3226.

Signed-off-by: Alexey Goncharuk 

commit dd06d0bd7ef266bfbe156e858b312d1ac86e8982
Author: Pavel Tupitsyn 
Date:   2018-01-18T12:55:49Z

IGNITE-7465 .NET: Fix SqlDdlExample failure with standalone node

commit 57479ec564e1761716da3d5f9feb7a64c396a9f9
Author: Pavel Tupitsyn 
Date:   2018-01-18T13:45:54Z

.NET: Fix CacheLocalTest.TestTxDeadlockDetection

commit bd6be8a4653322905a3b63850c7e033ce3801ce5
Author: Pavel Tupitsyn 
Date:   2018-01-18T18:25:05Z

.NET: Thin client: Fix OP_BINARY_TYPE_GET schema passing format

commit 97564d160586d6d57d300937e6b8877994e35fc7
Author: rkondakov 
Date:   2018-01-19T08:24:51Z

IGNITE-6456: Ability to separately enable or disable JDBC, ODBC and thin 
client endpoints. This closes #3309.

commit d50274ca8875c9680c12e8786ac355a787ba95e0
Author: Yakov Zhdanov 
Date:   2018-01-18T17:57:17Z

Javadoc enhancements - added @see

commit cb2d3cf22388ab19fb2d34ae5bdfc8f1b608db75
Author: Dmitriy Govorukhin 
Date:   2018-01-18T14:14:26Z

IGNITE-7471 Use soft reference for checkpoint entry contents to avoid 
excessive memory usage

commit 3965923369870bb4e8e57e3332c1a1eb1e5f5ed3
Author: rkondakov 
Date:   2018-01-19T09:00:55Z

IGNITE-6772: SQL exception messages became more informative. This closes 
#3342.

commit ba68cb0fa87f776fcd0499d030c333f182611f41
Author: devozerov 
Date:   2018-01-19T09:03:52Z

Merge 

[jira] [Commented] (IGNITE-7329) .NET: Thin client: SSL

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-7329:
-

[~ptupitsyn], looks good to me.

> .NET: Thin client: SSL
> --
>
> Key: IGNITE-7329
> URL: https://issues.apache.org/jira/browse/IGNITE-7329
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.5
>
>
> Allow secure .NET thin client connection.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7329) .NET: Thin client: SSL

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7329:


Merged with recent master.

[~vozerov], if you have no objections, I'm going to merge this tomorrow.

> .NET: Thin client: SSL
> --
>
> Key: IGNITE-7329
> URL: https://issues.apache.org/jira/browse/IGNITE-7329
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.5
>
>
> Allow secure .NET thin client connection.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7594) Tx performance drop after WAL optimization

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh commented on IGNITE-7594:
--

Temporary resolved performance drop by restoring old WAL implementation (before 
IGNITE-6339) and using it in FSYNC WAL mode.

> Tx performance drop after WAL optimization 
> ---
>
> Key: IGNITE-7594
> URL: https://issues.apache.org/jira/browse/IGNITE-7594
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Aleksey Chetaev
>Assignee: Andrey Gura
>Priority: Critical
> Fix For: 2.4
>
>
> Perfomance dropes in tx-putAll benchmarks after commit with WAL optimization.
> WAL Mode: Default
> First bad commit: 
> [https://github.com/apache/ignite/commit/a5ffd4eb18e6e9eab30c176a7bb4008a51b3d59d]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6400) Document ClientConnectorConfiguration

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-6400:
-

[~dmagda], [~pgarg],
You can consult to JavaDocs of this class which are pretty self-explanatory 
[1]. This needs to be documented in thin client section. Let me know if any 
additional inputs are required.

[1] 
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/configuration/ClientConnectorConfiguration.java

> Document ClientConnectorConfiguration
> -
>
> Key: IGNITE-6400
> URL: https://issues.apache.org/jira/browse/IGNITE-6400
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, thin client
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7648) Revert IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-7648:
--

The main reason why this property was introduced is that under some 
circumstances nodes were trying to kick each other from the cluster leading to 
a whole cluster falling apart. 

Until it's proven that new changes are stable enough, I would leave this 
behavior disabled by default.

> Revert IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.
> 
>
> Key: IGNITE-7648
> URL: https://issues.apache.org/jira/browse/IGNITE-7648
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.3
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>Priority: Major
> Fix For: 2.5
>
>
> IGNITE_ENABLE_FORCIBLE_NODE_KILL system property was introduced in 
> IGNITE-5718 as a way to prevent unnecessary node drops in case of short 
> network problems.
> I suppose it's wrong decision to fix it in such way.
> We had faced some issues in our production due to lack of automatic kicking 
> of ill-behaving nodes (on example, hanging due to long GC pauses) until we 
> realised the necessity of changing default behavior via property.
> Right solution is to kick nodes only if failure threshold is reached. Such 
> behavior should be always enabled.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7692) affinityCall and affinityRun may execute code on backup partitions

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-7692:
---
Labels: MakeTeamcityGreenAgain Muted_test usability  (was: usability)

> affinityCall and affinityRun may execute code on backup partitions
> --
>
> Key: IGNITE-7692
> URL: https://issues.apache.org/jira/browse/IGNITE-7692
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test, usability
> Fix For: 2.5
>
>
> Apparently, the affinityCall and affinityRun methods reserve partitions and 
> check their state to be OWNING, however, if topology changes and partition 
> role is changed to backup from primary, the code is still executed.
> This can be an issue if a user executes a local SQL query inside the 
> affinityCall runnable. In this case, the query result may return null.
> This can be observed in the 
> IgniteCacheLockPartitionOnAffinityRunTest#getPersonsCountSingleCache - note 
> an additional check I've added to make the test pass.
> I think it is ok to have an old semantics for the API, because in some cases 
> (scan query, local gets) a backup OWNER is enough. However, it looks like we 
> need to add another API method to enforce that affinity run be executed on 
> primary nodes and forbid primary role change.
> Another option is to detect a topology version of the affinity run and use 
> that version for local SQL queries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7594) Tx performance drop after WAL optimization

[Andrey Gura (JIRA)]

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

Andrey Gura reassigned IGNITE-7594:
---

Assignee: Andrey Gura  (was: Ilya Lantukh)

> Tx performance drop after WAL optimization 
> ---
>
> Key: IGNITE-7594
> URL: https://issues.apache.org/jira/browse/IGNITE-7594
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Aleksey Chetaev
>Assignee: Andrey Gura
>Priority: Critical
> Fix For: 2.4
>
>
> Perfomance dropes in tx-putAll benchmarks after commit with WAL optimization.
> WAL Mode: Default
> First bad commit: 
> [https://github.com/apache/ignite/commit/a5ffd4eb18e6e9eab30c176a7bb4008a51b3d59d]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-7655:
-

[~dmagda]

I fixed all issues, please, take a look.

https://dash.readme.io/project/apacheignite-fs/v2.3/docs/ignite-data-frame

> Spark Data Frames: saving data frames into Ignite needs to be documented
> 
>
> Key: IGNITE-7655
> URL: https://issues.apache.org/jira/browse/IGNITE-7655
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.4
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7398) InstanceNotFoundException appears in the log when a cache is closed and MBeans are disabled

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7398:


Github user asfgit closed the pull request at:

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


> InstanceNotFoundException appears in the log when a cache is closed and 
> MBeans are disabled
> ---
>
> Key: IGNITE-7398
> URL: https://issues.apache.org/jira/browse/IGNITE-7398
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Stanislav Lukyanov
>Assignee: Pavel Vinokurov
>Priority: Minor
> Fix For: 2.5
>
>
> If IGNITE_MBEANS_DISABLED is set to true, whenever a cache is started the 
> following error is logged:
> javax.management.InstanceNotFoundException: 
> org.apache:clsLdr=18b4aac2,igniteInstanceName=mbeans.GridMBeanDisableSelfTest0,group=Cache
>  groups,name=MyCache
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1095)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:427)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:415)
>   at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:546)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.cleanup(GridCacheProcessor.java:606)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2264)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2253)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCaches(GridCacheProcessor.java:907)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stop(GridCacheProcessor.java:872)
>   at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2316)
>   at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2182)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2512)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2475)
>   at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:362)
>   at org.apache.ignite.Ignition.stop(Ignition.java:224)
>   at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3509)
>   at 
> org.apache.ignite.util.mbeans.GridMBeanDisableSelfTest.testCorrectMBeanInfo(GridMBeanDisableSelfTest.java:101)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
>   at java.lang.Thread.run(Thread.java:748)
> That's because GridCacheProcessor::cleanup unconditionally attempts to 
> unregister cache's MBean, not checking whether or not the cache actually has 
> an MBean registered for it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6005) [Test failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-6005:
-

[~NIzhikov] Merged to master branch. Thanks for your contribution!

> [Test failed] 
> GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
> -
>
> Key: IGNITE-6005
> URL: https://issues.apache.org/jira/browse/IGNITE-6005
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Example of fail
> https://ci.ignite.apache.org/viewLog.html?buildId=762788=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures
> Typical problem is 
> {code}
> org.apache.ignite.IgniteInterruptedException: Failed to wait for asynchronous 
> operation permit (thread got interrupted).
> at 
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:805)
> at 
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:803)
> at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:961)
> at 
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1026)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.InterruptedException: null
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1301)
> at java.util.concurrent.Semaphore.acquire(Semaphore.java:317)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOpAcquire(GridCacheAdapter.java:4314)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4177)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:196)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4509)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4490)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1324)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:329)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$5.applyx(DataStructuresProcessor.java:635)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.retryTopologySafe(DataStructuresProcessor.java:1519)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeDataStructure(DataStructuresProcessor.java:629)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeSemaphore(DataStructuresProcessor.java:1188)
> at 
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1023)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> 

[jira] [Commented] (IGNITE-7632) NPE in IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.updateIgfsMetrics()

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7632:


Github user asfgit closed the pull request at:

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


> NPE in IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.updateIgfsMetrics()
> ---
>
> Key: IGNITE-7632
> URL: https://issues.apache.org/jira/browse/IGNITE-7632
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Alexandr Kuramshin
>Priority: Major
> Fix For: 2.5
>
>
> Occurs on destroying cache while rebuilding indices in progress
> {noformat}
> Partition eviction failed, this can cause grid hang.
> java.lang.NullPointerException: null
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.updateIgfsMetrics(IgniteCacheOffheapManagerImpl.java:1576)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishRemove(IgniteCacheOffheapManagerImpl.java:1403)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:1368)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.remove(GridCacheOffheapManager.java:1312)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:368)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:3224)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.clearInternal(GridDhtCacheEntry.java:588)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.clearAll(GridDhtLocalPartition.java:895)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.tryEvict(GridDhtLocalPartition.java:753)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:593)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:580)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6639)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
> ...
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-7655:
-

[~dmagda] 

As far as I can see you edited my explanation of {{Overwrite}} mode. I think it 
incorrect now.
{{Overwrite}} mode means we will do next steps:

1. Drop table from Ignite if it already exists.

2. Create table. We will use schema from Data frame we need to save.

3. Inserts data from data frame to new table.

I wrote this changes in page. Does it look right for you?

> Spark Data Frames: saving data frames into Ignite needs to be documented
> 
>
> Key: IGNITE-7655
> URL: https://issues.apache.org/jira/browse/IGNITE-7655
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.4
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov edited comment on IGNITE-7655 at 2/26/18 12:20 PM:
---

[~dmagda]

> What does appending mean here? As far as I understand, you're just going to 
> insert new data ignoring the data which keys are already in the table.

Appends mean we will not execute {{DROP TABLE}}/{{CREATE TABLE}}.
Since all inserts are executed through IgniteDataStreamer behaviour will be 
like this:

* {{OPTION_STREAMER_ALLOW_OVERWRITE=false}} - if key already exists in Ignite 
cache then no insert will be execute.
* {{OPTION_STREAMER_ALLOW_OVERWRITE=true}} - if a key already exists in Ignite 
cache then it will be overwritten with data frame content.

> which mode is a default? 

ErrorIfExsists

> Is there a mode that updates existing rows, inserts new from the data frame 
> and does NOT delete the rows that were in the table initially?

{{SaveMode.Append}} + {{OPTION_STREAMER_ALLOW_OVERWRITE=true}}

> How do I set a mode? You start talking about the data frames right away but 
> do not explain how to use them.

One can use {{dataFrame.write.mode(SaveMode.Append)}}.  It's a part of Spark 
API. 
OK, I will add an example to the page.

> I would start "Saving Data Frame" section with the explanation of how all 
> this works

OK. Will do.


was (Author: nizhikov):
[~dmagda]

> What does appending mean here? As far as I understand, you're just going to 
> insert new data ignoring the data which keys are already in the table.

Appends mean we will not execute {{DROP TABLE}}/{{CREATE TABLE}}.
Since all inserts are executed through IgniteDataStreamer behaviour will be 
like this:

* {{OPTION_STREAMER_ALLOW_OVERWRITE=false}} - existing keys will be ignored.
* {{OPTION_STREAMER_ALLOW_OVERWRITE=true}} - existing key/value will 
overwritten with DataFrame data.

> which mode is a default? 

ErrorIfExsists

> Is there a mode that updates existing rows, inserts new from the data frame 
> and does NOT delete the rows that were in the table initially?

{{SaveMode.Append}} + {{OPTION_STREAMER_ALLOW_OVERWRITE=true}}

> How do I set a mode? You start talking about the data frames right away but 
> do not explain how to use them.

One can use {{dataFrame.write.mode(SaveMode.Append)}}.  It's a part of Spark 
API. 
OK, I will add an example to the page.

> I would start "Saving Data Frame" section with the explanation of how all 
> this works

OK. Will do.

> Spark Data Frames: saving data frames into Ignite needs to be documented
> 
>
> Key: IGNITE-7655
> URL: https://issues.apache.org/jira/browse/IGNITE-7655
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.4
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7632) NPE in IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.updateIgfsMetrics()

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-7632:
---
Fix Version/s: (was: 2.4)
   2.5

> NPE in IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.updateIgfsMetrics()
> ---
>
> Key: IGNITE-7632
> URL: https://issues.apache.org/jira/browse/IGNITE-7632
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Alexandr Kuramshin
>Priority: Major
> Fix For: 2.5
>
>
> Occurs on destroying cache while rebuilding indices in progress
> {noformat}
> Partition eviction failed, this can cause grid hang.
> java.lang.NullPointerException: null
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.updateIgfsMetrics(IgniteCacheOffheapManagerImpl.java:1576)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishRemove(IgniteCacheOffheapManagerImpl.java:1403)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:1368)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.remove(GridCacheOffheapManager.java:1312)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:368)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:3224)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.clearInternal(GridDhtCacheEntry.java:588)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.clearAll(GridDhtLocalPartition.java:895)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.tryEvict(GridDhtLocalPartition.java:753)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:593)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:580)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6639)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
> ...
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7398) InstanceNotFoundException appears in the log when a cache is closed and MBeans are disabled

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-7398:
---
Fix Version/s: (was: 2.4)
   2.5

> InstanceNotFoundException appears in the log when a cache is closed and 
> MBeans are disabled
> ---
>
> Key: IGNITE-7398
> URL: https://issues.apache.org/jira/browse/IGNITE-7398
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Stanislav Lukyanov
>Assignee: Pavel Vinokurov
>Priority: Minor
> Fix For: 2.5
>
>
> If IGNITE_MBEANS_DISABLED is set to true, whenever a cache is started the 
> following error is logged:
> javax.management.InstanceNotFoundException: 
> org.apache:clsLdr=18b4aac2,igniteInstanceName=mbeans.GridMBeanDisableSelfTest0,group=Cache
>  groups,name=MyCache
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1095)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:427)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:415)
>   at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:546)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.cleanup(GridCacheProcessor.java:606)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2264)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2253)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCaches(GridCacheProcessor.java:907)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stop(GridCacheProcessor.java:872)
>   at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2316)
>   at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2182)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2512)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2475)
>   at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:362)
>   at org.apache.ignite.Ignition.stop(Ignition.java:224)
>   at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3509)
>   at 
> org.apache.ignite.util.mbeans.GridMBeanDisableSelfTest.testCorrectMBeanInfo(GridMBeanDisableSelfTest.java:101)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
>   at java.lang.Thread.run(Thread.java:748)
> That's because GridCacheProcessor::cleanup unconditionally attempts to 
> unregister cache's MBean, not checking whether or not the cache actually has 
> an MBean registered for it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7398) InstanceNotFoundException appears in the log when a cache is closed and MBeans are disabled

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7398:


Hi [~pvinokurov], TC looks acceptable, fix looks good to me

[~agoncharuk], could you confirm?

> InstanceNotFoundException appears in the log when a cache is closed and 
> MBeans are disabled
> ---
>
> Key: IGNITE-7398
> URL: https://issues.apache.org/jira/browse/IGNITE-7398
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Stanislav Lukyanov
>Assignee: Pavel Vinokurov
>Priority: Minor
> Fix For: 2.5
>
>
> If IGNITE_MBEANS_DISABLED is set to true, whenever a cache is started the 
> following error is logged:
> javax.management.InstanceNotFoundException: 
> org.apache:clsLdr=18b4aac2,igniteInstanceName=mbeans.GridMBeanDisableSelfTest0,group=Cache
>  groups,name=MyCache
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1095)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:427)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:415)
>   at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:546)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.cleanup(GridCacheProcessor.java:606)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2264)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2253)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCaches(GridCacheProcessor.java:907)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stop(GridCacheProcessor.java:872)
>   at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2316)
>   at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2182)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2512)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2475)
>   at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:362)
>   at org.apache.ignite.Ignition.stop(Ignition.java:224)
>   at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3509)
>   at 
> org.apache.ignite.util.mbeans.GridMBeanDisableSelfTest.testCorrectMBeanInfo(GridMBeanDisableSelfTest.java:101)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
>   at java.lang.Thread.run(Thread.java:748)
> That's because GridCacheProcessor::cleanup unconditionally attempts to 
> unregister cache's MBean, not checking whether or not the cache actually has 
> an MBean registered for it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-5936) Cleanup of not needed and committed versions

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5936:
---

Assignee: Roman Kondakov

> Cleanup of not needed and committed versions
> 
>
> Key: IGNITE-5936
> URL: https://issues.apache.org/jira/browse/IGNITE-5936
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Roman Kondakov
>Priority: Major
> Fix For: 2.5
>
>
> At first committed data is stored in separate data structure.Need implement 
> some procedure to remove from mvcc storage versions which are not needed 
> anymore and flush committed versions in main storage. Version which is safe 
> to remove (there are not readers using this version) should be somehow passed 
> from coordinator to servers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-6938) SQL TX: Reads should see own's previous writes

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-6938:
---

Assignee: Igor Seliverstov

> SQL TX: Reads should see own's previous writes
> --
>
> Key: IGNITE-6938
> URL: https://issues.apache.org/jira/browse/IGNITE-6938
> Project: Ignite
>  Issue Type: Task
>  Components: cache, sql
>Reporter: Vladimir Ozerov
>Assignee: Igor Seliverstov
>Priority: Major
>  Labels: iep-3
> Fix For: 2.5
>
>
> If transaction modified a row, subsequent {{SELECT}} statements in the same 
> TX must return latest pending update instead of last matching committed 
> version.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7362) ODBC: Third party libraries truncate any inserted varlen data to ColumnSize

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7362:


Github user isapego closed the pull request at:

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


> ODBC: Third party libraries truncate any inserted varlen data to ColumnSize
> ---
>
> Key: IGNITE-7362
> URL: https://issues.apache.org/jira/browse/IGNITE-7362
> Project: Ignite
>  Issue Type: Bug
>  Components: odbc
>Affects Versions: 2.3
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.5
>
>
> Third-party frameworks and ODBC bindings for different languages use metadata 
> requests results for columns (such as {{SQL_COLUMN_PRECISION}}) to truncate 
> varlen data, inserted by the user, which is only 64 by default.
> {code:java}
>  ini_set("display_errors", 1);
> error_reporting(E_ALL);
> try {
> $ignite = new PDO('odbc:Apache Ignite');
> $ignite->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
> $sql = 'DROP TABLE IF EXISTS test';
> $ignite->exec($sql);
> $sql = 'CREATE TABLE IF NOT EXISTS test (id int PRIMARY KEY, userkey 
> VARCHAR(1000))';
> $ignite->exec($sql);
> $id = 1;
> $varval = 'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed 
> do elit, sed';
> $dbs = $ignite->prepare("INSERT INTO test (id, userkey) VALUES ($id, 
> '$varval')");
> $dbs->execute();
> $dbs = $ignite->prepare("SELECT userkey from test where id=$id");
> $dbs->execute();
> $res = $dbs->fetchColumn();
> assert($varval == $res);
> } catch (PDOException $e) {
> print "Error!: " . $e->getMessage() . "\n";
> die();
> }
> ?>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7300) Allow expressions in SQL INSERTs within transactions

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-7300:
---

Assignee: Sergey Kalashnikov  (was: Igor Seliverstov)

> Allow expressions in SQL INSERTs within transactions
> 
>
> Key: IGNITE-7300
> URL: https://issues.apache.org/jira/browse/IGNITE-7300
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexander Paschenko
>Assignee: Sergey Kalashnikov
>Priority: Major
> Fix For: 2.5
>
>
> The problem is related to IGNITE-7267 - the latter honors raw rows, but drops 
> support for inserts with expressions which yield local subqueries. To fix 
> this, {{UpdatePlan.isLocalSubquery()}} must be honored.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-6846) Add metrics for entry processor invocations

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov edited comment on IGNITE-6846 at 2/26/18 11:48 AM:


[~vkulichenko] , hi !

Sorry, for delay. I have resolved conflicts, and rerun tests.

Please, review the ticket.

 


was (Author: alexey kuznetsov):
[~vkulichenko] , hi !

Sorry, for delay. I have resolved conflicts, and rerun tests.

This new metric test was added : GridCacheNearAtomicMetricsSelfTest, and it 
shows "cache read" metric works incorrect(see testNearRead()). So, my question 
is, should i file a ticket for fixing this test?("cache read" metric in atomic 
cache)

 

Please, review the ticket.

 

> Add metrics for entry processor invocations
> ---
>
> Key: IGNITE-6846
> URL: https://issues.apache.org/jira/browse/IGNITE-6846
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Alexey Kuznetsov
>Priority: Critical
>  Labels: iep-6
> Fix For: 2.5
>
>
> {{CacheMetrics}} object has multiple metrics for various cache operations 
> like {{get}}, {{put}} and {{remove}}, but nothing for 
> {{invoke}}/{{EntryProcessor}}. It makes sense to add such metrics, for 
> example:
> * Total number of `invoke` operations executed.
> * Number of `invoke` operations that included updates.
> * Number of read-only `invoke` operations.
> * Min/max/avg execution time.
> * ...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6005) [Test failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-6005:


Hi [~NIzhikov], I've checked your run and din't find any suspicious test 
(except that I mentioned on dev-list, RDD*). 

So TC looks acceptable.

[~agura], can we proceed and merge?

> [Test failed] 
> GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
> -
>
> Key: IGNITE-6005
> URL: https://issues.apache.org/jira/browse/IGNITE-6005
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Example of fail
> https://ci.ignite.apache.org/viewLog.html?buildId=762788=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures
> Typical problem is 
> {code}
> org.apache.ignite.IgniteInterruptedException: Failed to wait for asynchronous 
> operation permit (thread got interrupted).
> at 
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:805)
> at 
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:803)
> at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:961)
> at 
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1026)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.InterruptedException: null
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1301)
> at java.util.concurrent.Semaphore.acquire(Semaphore.java:317)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOpAcquire(GridCacheAdapter.java:4314)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4177)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:196)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4509)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4490)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1324)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:329)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$5.applyx(DataStructuresProcessor.java:635)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.retryTopologySafe(DataStructuresProcessor.java:1519)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeDataStructure(DataStructuresProcessor.java:629)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeSemaphore(DataStructuresProcessor.java:1188)
> at 
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1023)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> 

[jira] [Commented] (IGNITE-7718) Collections.singleton() and Collections.singletonMap() are not properly serialized by binary marshaller

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7718:


Suspicious tests which not failed in master:
{noformat}
   Ignite Cache 3 [ tests 9 ]  
 IgniteBinaryObjectsCacheTestSuite3: 
CacheInterceptorPartitionCounterRandomOperationsTest.testAtomic (fail rate 
0,0%) 
 IgniteBinaryObjectsCacheTestSuite3: 
CacheInterceptorPartitionCounterRandomOperationsTest.testAtomicNoBackups (fail 
rate 0,0%) 
 IgniteBinaryObjectsCacheTestSuite3: 
CacheInterceptorPartitionCounterRandomOperationsTest.testAtomicReplicated (fail 
rate 0,0%) 
 IgniteBinaryObjectsCacheTestSuite3: 
CacheInterceptorPartitionCounterRandomOperationsTest.testAtomicWithStore (fail 
rate 0,0%) 
 IgniteBinaryObjectsCacheTestSuite3: 
CacheInterceptorPartitionCounterRandomOperationsTest.testTxNoBackups (fail rate 
0,0%) 
 IgniteBinaryObjectsCacheTestSuite3: 
CacheInterceptorPartitionCounterRandomOperationsTest.testTxNoBackupsWithStore 
(fail rate 0,0%) 
 IgniteBinaryObjectsCacheTestSuite3: 
CacheInterceptorPartitionCounterRandomOperationsTest.testTxReplicatedWithStore 
(fail rate 0,0%) 
 IgniteBinaryObjectsCacheTestSuite3: 
CacheInterceptorPartitionCounterRandomOperationsTest.testTxWithStore (fail rate 
0,0%) 
 IgniteBinaryObjectsCacheTestSuite3: 
FifoEvictionPolicySelfTest.testMaxMemSizePolicy (fail rate 0,0%) 

   Ignite Cache Restarts [ tests 9 ]  
 IgniteCacheRestartTestSuite: 
GridCachePartitionedNearDisabledOptimisticTxNodeRestartTest.testRestartWithTxFourNodesNoBackups
 (fail rate 0,0%) 
 IgniteCacheRestartTestSuite: 
GridCachePartitionedNearDisabledOptimisticTxNodeRestartTest.testRestartWithTxFourNodesOneBackupsOffheapEvict
 (fail rate 0,0%) 
 IgniteCacheRestartTestSuite: 
GridCachePartitionedNearDisabledOptimisticTxNodeRestartTest.testRestartWithTxSixNodesTwoBackups
 (fail rate 0,0%) 
 IgniteCacheRestartTestSuite: 
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutEightNodesTwoBackups 
(fail rate 0,0%) 
 IgniteCacheRestartTestSuite: 
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesOneBackupsOffheapEvict
 (fail rate 0,0%) 
 IgniteCacheRestartTestSuite: 
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutSixNodesTwoBackups 
(fail rate 0,0%) 
 IgniteCacheRestartTestSuite: 
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxEightNodesTwoBackups 
(fail rate 0,0%) 
 IgniteCacheRestartTestSuite: 
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackups 
(fail rate 0,0%) 
 IgniteCacheRestartTestSuite: 
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxPutAllTenNodesTwoBackups
 (fail rate 0,0%) 
{noformat}

> Collections.singleton() and Collections.singletonMap() are not properly 
> serialized by binary marshaller
> ---
>
> Key: IGNITE-7718
> URL: https://issues.apache.org/jira/browse/IGNITE-7718
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Pavel Vinokurov
>Assignee: Pavel Vinokurov
>Priority: Major
>
> After desialization collections obtained by Collections.singleton() and  
> Collections.singletonMap() does not return collection of binary objects, but 
> rather collection of deserialized objects. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-7716) Red selftest in ML examples

[Peter Ivanov (JIRA)]

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

Peter Ivanov edited comment on IGNITE-7716 at 2/26/18 11:22 AM:


Fixed: https://ci.ignite.apache.org/viewLog.html?buildId=1110388


was (Author: vveider):
Починил: https://ci.ignite.apache.org/viewLog.html?buildId=1110388

> Red selftest in ML examples
> ---
>
> Key: IGNITE-7716
> URL: https://issues.apache.org/jira/browse/IGNITE-7716
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Reporter: Yury Babak
>Assignee: Peter Ivanov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> https://ci.ignite.apache.org/project.html?tab=testDetails=IgniteTests24Java8=1447870893775475761



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (IGNITE-7716) Red selftest in ML examples

[Peter Ivanov (JIRA)]

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

Peter Ivanov resolved IGNITE-7716.
--
   Resolution: Fixed
Fix Version/s: (was: 2.5)

Починил: https://ci.ignite.apache.org/viewLog.html?buildId=1110388

> Red selftest in ML examples
> ---
>
> Key: IGNITE-7716
> URL: https://issues.apache.org/jira/browse/IGNITE-7716
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Reporter: Yury Babak
>Assignee: Peter Ivanov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> https://ci.ignite.apache.org/project.html?tab=testDetails=IgniteTests24Java8=1447870893775475761



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7718) Collections.singleton() and Collections.singletonMap() are not properly serialized by binary marshaller

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7718:


[~pvinokurov], could you please check results first? Is it ok from point of 
view of tests?

Also you can merge master into your branch to reduce failed tests count.

> Collections.singleton() and Collections.singletonMap() are not properly 
> serialized by binary marshaller
> ---
>
> Key: IGNITE-7718
> URL: https://issues.apache.org/jira/browse/IGNITE-7718
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Pavel Vinokurov
>Assignee: Pavel Vinokurov
>Priority: Major
>
> After desialization collections obtained by Collections.singleton() and  
> Collections.singletonMap() does not return collection of binary objects, but 
> rather collection of deserialized objects. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7716) Red selftest in ML examples

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7716:


[~vveider] could you provide assisance?

> Red selftest in ML examples
> ---
>
> Key: IGNITE-7716
> URL: https://issues.apache.org/jira/browse/IGNITE-7716
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Reporter: Yury Babak
>Assignee: Peter Ivanov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> https://ci.ignite.apache.org/project.html?tab=testDetails=IgniteTests24Java8=1447870893775475761



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7716) Red selftest in ML examples

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko commented on IGNITE-7716:


hi [~dpavlov], have you checked the explanation in [above 
comment|https://issues.apache.org/jira/browse/IGNITE-7716?focusedCommentId=16365599=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16365599]?
 In brief, we believe this issue is caused by misconfiguration of TeamCity and 
we asked [~vveider] to check this.

> Red selftest in ML examples
> ---
>
> Key: IGNITE-7716
> URL: https://issues.apache.org/jira/browse/IGNITE-7716
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Reporter: Yury Babak
>Assignee: Peter Ivanov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> https://ci.ignite.apache.org/project.html?tab=testDetails=IgniteTests24Java8=1447870893775475761



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7716) Red selftest in ML examples

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7716:


Hi [~chief], are there any news about this issue?

> Red selftest in ML examples
> ---
>
> Key: IGNITE-7716
> URL: https://issues.apache.org/jira/browse/IGNITE-7716
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Reporter: Yury Babak
>Assignee: Peter Ivanov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> https://ci.ignite.apache.org/project.html?tab=testDetails=IgniteTests24Java8=1447870893775475761



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7362) ODBC: Third party libraries truncate any inserted varlen data to ColumnSize

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov commented on IGNITE-7362:


[~isapego], Looks good to me. Thanks!

> ODBC: Third party libraries truncate any inserted varlen data to ColumnSize
> ---
>
> Key: IGNITE-7362
> URL: https://issues.apache.org/jira/browse/IGNITE-7362
> Project: Ignite
>  Issue Type: Bug
>  Components: odbc
>Affects Versions: 2.3
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.5
>
>
> Third-party frameworks and ODBC bindings for different languages use metadata 
> requests results for columns (such as {{SQL_COLUMN_PRECISION}}) to truncate 
> varlen data, inserted by the user, which is only 64 by default.
> {code:java}
>  ini_set("display_errors", 1);
> error_reporting(E_ALL);
> try {
> $ignite = new PDO('odbc:Apache Ignite');
> $ignite->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
> $sql = 'DROP TABLE IF EXISTS test';
> $ignite->exec($sql);
> $sql = 'CREATE TABLE IF NOT EXISTS test (id int PRIMARY KEY, userkey 
> VARCHAR(1000))';
> $ignite->exec($sql);
> $id = 1;
> $varval = 'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed 
> do elit, sed';
> $dbs = $ignite->prepare("INSERT INTO test (id, userkey) VALUES ($id, 
> '$varval')");
> $dbs->execute();
> $dbs = $ignite->prepare("SELECT userkey from test where id=$id");
> $dbs->execute();
> $res = $dbs->fetchColumn();
> assert($varval == $res);
> } catch (PDOException $e) {
> print "Error!: " . $e->getMessage() . "\n";
> die();
> }
> ?>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7810) Web console: replace Roboto slab font with Roboto regular

[Ilya Borisov (JIRA)]

Ilya Borisov created IGNITE-7810:


 Summary: Web console: replace Roboto slab font with Roboto regular
 Key: IGNITE-7810
 URL: https://issues.apache.org/jira/browse/IGNITE-7810
 Project: Ignite
  Issue Type: Improvement
  Components: wizards
Reporter: Ilya Borisov
Assignee: Ilya Borisov


Since the Roboto slab font is considered deprecated, it should be replaced with 
Roboto regular.

What to do:
1. Replace global font on  with Roboto.
2. Look for Roboto slab in other place and remove it too.
3. Remove Roboto slab from dependencies, if applicable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7809) Ignite PDS 2 & PDS 2 Direct IO: stable failures of IgniteWalFlushDefaultSelfTest

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-7809:
--

 Summary: Ignite PDS 2 & PDS 2 Direct IO: stable failures of 
IgniteWalFlushDefaultSelfTest
 Key: IGNITE-7809
 URL: https://issues.apache.org/jira/browse/IGNITE-7809
 Project: Ignite
  Issue Type: Task
  Components: persistence
Affects Versions: 2.4
Reporter: Dmitriy Pavlov
Assignee: Ilya Lantukh
 Fix For: 2.5


Probably after last WAL default changes 'IGNITE-7594 Fixed performance drop 
after WAL optimization for FSYNC' 2 tests in 2 build configs began to fail

   Ignite PDS 2 (Direct IO) [ tests 2 ]  
 IgnitePdsNativeIoTestSuite2: 
IgniteWalFlushDefaultSelfTest.testFailAfterStart (fail rate 13,0%) 
 IgnitePdsNativeIoTestSuite2: 
IgniteWalFlushDefaultSelfTest.testFailWhileStart (fail rate 13,0%) 

   Ignite PDS 2 [ tests 2 ]  
 IgnitePdsTestSuite2: IgniteWalFlushDefaultSelfTest.testFailAfterStart 
(fail rate 8,4%) 
 IgnitePdsTestSuite2: IgniteWalFlushDefaultSelfTest.testFailWhileStart 
(fail rate 8,4%) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7640) Refactor DiscoveryDataClusterState to be immutable

[Alexander Menshikov (JIRA)]

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

Alexander Menshikov commented on IGNITE-7640:
-

*[~agoncharuk]*

*Done. Please review.*

 

*Details:*

1) I removed field _DiscoveryDataClusterState.transitionError_ because there is 
no place in the project where setter was called, so it always was null.

2) Replaced _DiscoveryDataClusterState.transitionRes_ with 
_DiscoveryDataClusterState.transitionFut_ to avoid concurrent passing result 
from _GridClusterStateProcessor#onStateFinishMessage_ to 
_GridClusterStateProcessor#publicApiActiveState_ . It also allows me to remove 
_GridClusterStateProcessor.transitionFuts_. See details in code.

3) Optimized _DiscoveryDataClusterState#setTransitionResult_ using because in 
all cases except one we don't need comparison of request id. See details in 
code.

> Refactor DiscoveryDataClusterState to be immutable
> --
>
> Key: IGNITE-7640
> URL: https://issues.apache.org/jira/browse/IGNITE-7640
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.4
>Reporter: Alexey Goncharuk
>Assignee: Alexander Menshikov
>Priority: Major
> Fix For: 2.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7362) ODBC: Third party libraries truncate any inserted varlen data to ColumnSize

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-7362:
-

[~skalashnikov], fixed issues you have found in review. Can you take a look 
again please?

> ODBC: Third party libraries truncate any inserted varlen data to ColumnSize
> ---
>
> Key: IGNITE-7362
> URL: https://issues.apache.org/jira/browse/IGNITE-7362
> Project: Ignite
>  Issue Type: Bug
>  Components: odbc
>Affects Versions: 2.3
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.5
>
>
> Third-party frameworks and ODBC bindings for different languages use metadata 
> requests results for columns (such as {{SQL_COLUMN_PRECISION}}) to truncate 
> varlen data, inserted by the user, which is only 64 by default.
> {code:java}
>  ini_set("display_errors", 1);
> error_reporting(E_ALL);
> try {
> $ignite = new PDO('odbc:Apache Ignite');
> $ignite->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
> $sql = 'DROP TABLE IF EXISTS test';
> $ignite->exec($sql);
> $sql = 'CREATE TABLE IF NOT EXISTS test (id int PRIMARY KEY, userkey 
> VARCHAR(1000))';
> $ignite->exec($sql);
> $id = 1;
> $varval = 'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed 
> do elit, sed';
> $dbs = $ignite->prepare("INSERT INTO test (id, userkey) VALUES ($id, 
> '$varval')");
> $dbs->execute();
> $dbs = $ignite->prepare("SELECT userkey from test where id=$id");
> $dbs->execute();
> $res = $dbs->fetchColumn();
> assert($varval == $res);
> } catch (PDOException $e) {
> print "Error!: " . $e->getMessage() . "\n";
> die();
> }
> ?>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-5553) Ignite PDS 2: IgnitePersistentStoreDataStructuresTest testSet assertion error

[Pavel Pereslegin (JIRA)]

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

Pavel Pereslegin reassigned IGNITE-5553:


Assignee: Pavel Pereslegin  (was: Andrey Kuznetsov)

> Ignite PDS 2: IgnitePersistentStoreDataStructuresTest testSet assertion error
> -
>
> Key: IGNITE-5553
> URL: https://issues.apache.org/jira/browse/IGNITE-5553
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures, persistence
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Pavel Pereslegin
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test, test-fail
> Fix For: 2.5
>
>
> h2. Notes-4435
> When IgniteSet is restored from persistence, size of set is always 0, [link 
> to test 
> history|http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-7043871603266099589=testDetails].
> h2. Detailed description
> Unlike *IgniteQueue* which uses separate cache key to store its size 
> *IgniteSet* stores it in a field of some class.
> Test from the link above shows very clearly that after restoring memory state 
> from PDS all set values are restored correctly but size is lost.
> h2. Proposed solution
> One possible solution might be to do the same thing as *IgniteQueue* does: 
> size of *IgniteSet* must be stored is cache instead of volatile in-memory 
> fields of random classes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7808) Automate Docker images build

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7808:


 Summary: Automate Docker images build
 Key: IGNITE-7808
 URL: https://issues.apache.org/jira/browse/IGNITE-7808
 Project: Ignite
  Issue Type: Improvement
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Introduce and document process and tools for automated Docked images build 
based on release tag. Include both Ignite and Web Console images.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7807) SQL TX: Store lock info inside tuples

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov reassigned IGNITE-7807:


Assignee: Igor Seliverstov

> SQL TX: Store lock info inside tuples
> -
>
> Key: IGNITE-7807
> URL: https://issues.apache.org/jira/browse/IGNITE-7807
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Igor Seliverstov
>Priority: Major
>
> We need to store lock info inside tuples. Otherwise, touching a lot of 
> entries would lead to OOME. Also we should rework our locking logic - instead 
> of trying to enlist ourselves in every entry, we should stop on the very 
> first locked entry and wait for it's release.
> Suggested fix: 
> 1) Check for {{lock_id}} field of an entry
> 2) If it is empty, CAS own XID
> 3) If it is not empty, check fo TX LOG to see if transaction is still active; 
> if not - CAS itself
> 4) If failed to install own version - stop locking and wait for release
> 5) When transaction commits, no locks are released explicilty. Instead, it is 
> responsibility of the next locker to check TX LOG and undesrantnad whether 
> entry could be locked or not
> 6) When lock is acquired, create new version of an entry with lock info



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-7697) Update maven-javadoc-plugin version

[Peter Ivanov (JIRA)]

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

Peter Ivanov closed IGNITE-7697.


> Update maven-javadoc-plugin version
> ---
>
> Key: IGNITE-7697
> URL: https://issues.apache.org/jira/browse/IGNITE-7697
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.4
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> Update version of {{maven-javadoc-plugin}} in order to try to overcome 
> following error:
> {code}
> javadoc: warning - Error fetching URL: 
> http://hadoop.apache.org/docs/current/api/
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (IGNITE-7697) Update maven-javadoc-plugin version

[Peter Ivanov (JIRA)]

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

Peter Ivanov resolved IGNITE-7697.
--
Resolution: Won't Fix

> Update maven-javadoc-plugin version
> ---
>
> Key: IGNITE-7697
> URL: https://issues.apache.org/jira/browse/IGNITE-7697
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.4
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> Update version of {{maven-javadoc-plugin}} in order to try to overcome 
> following error:
> {code}
> javadoc: warning - Error fetching URL: 
> http://hadoop.apache.org/docs/current/api/
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-7729) Add usage of Roles for Web Console E2E tests

[Andrey Novikov (JIRA)]

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

Andrey Novikov closed IGNITE-7729.
--

> Add usage of Roles for Web Console E2E tests
> 
>
> Key: IGNITE-7729
> URL: https://issues.apache.org/jira/browse/IGNITE-7729
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Andrey Novikov
>Priority: Major
> Fix For: 2.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7729) Add usage of Roles for Web Console E2E tests

[Andrey Novikov (JIRA)]

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

Andrey Novikov updated IGNITE-7729:
---
Fix Version/s: 2.5

> Add usage of Roles for Web Console E2E tests
> 
>
> Key: IGNITE-7729
> URL: https://issues.apache.org/jira/browse/IGNITE-7729
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Andrey Novikov
>Priority: Major
> Fix For: 2.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7729) Add usage of Roles for Web Console E2E tests

[Andrey Novikov (JIRA)]

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

Andrey Novikov commented on IGNITE-7729:


Reviewed. Merged to master.

> Add usage of Roles for Web Console E2E tests
> 
>
> Key: IGNITE-7729
> URL: https://issues.apache.org/jira/browse/IGNITE-7729
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Andrey Novikov
>Priority: Major
> Fix For: 2.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7807) SQL TX: Store lock info inside tuples

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7807:
---

 Summary: SQL TX: Store lock info inside tuples
 Key: IGNITE-7807
 URL: https://issues.apache.org/jira/browse/IGNITE-7807
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov


We need to store lock info inside tuples. Otherwise, touching a lot of entries 
would lead to OOME. Also we should rework our locking logic - instead of trying 
to enlist ourselves in every entry, we should stop on the very first locked 
entry and wait for it's release.

Suggested fix: 
1) Check for {{lock_id}} field of an entry
2) If it is empty, CAS own XID
3) If it is not empty, check fo TX LOG to see if transaction is still active; 
if not - CAS itself
4) If failed to install own version - stop locking and wait for release
5) When transaction commits, no locks are released explicilty. Instead, it is 
responsibility of the next locker to check TX LOG and undesrantnad whether 
entry could be locked or not
6) When lock is acquired, create new version of an entry with lock info



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7774) Missing Google Cloud libraries at binary release

[Roman Guseinov (JIRA)]

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

Roman Guseinov commented on IGNITE-7774:


[~avinogradov] , could you take a look at this PR 
[https://github.com/apache/ignite/pull/3567], please? I made a build locally 
and now it contains all necessary Google Cloud libraries. Also, I tested 
TcpDiscoveryGoogleStorageIpFinder and it works out of the box.

Thanks. 

> Missing Google Cloud libraries at binary release
> 
>
> Key: IGNITE-7774
> URL: https://issues.apache.org/jira/browse/IGNITE-7774
> Project: Ignite
>  Issue Type: Bug
>  Components: build
> Environment: * Ubuntu 16.04.3 LTS
> * Apache Ignite 2.3.0
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
>  Labels: build
>
> It looks like following libraries aren't included in the build:
>  * google-http-client-1.22.0.jar
>  * google-http-client-jackson2-1.22.0.jar
>  * google-oauth-client-1.22.0.jar
> Steps to reproduce:
> 1. Download apache-ignite-fabric-2.3.0-bin.zip 
> ([http://apache-mirror.rbc.ru/pub/apache//ignite/2.3.0/apache-ignite-fabric-2.3.0-bin.zip]).
> 2. Unzip archive.
> 3. Move ignite-rest-http from /libs/optional to /libs
> 4. Move ignite-gce from /libs/optional to /libs
> 5. Update IgniteConfiguration in default-config.xml:
> {code:xml}
> 
>   
> 
>class="org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder">
> 
> 
> 
>  value="discovery-sp...@apache-ignite.iam.gserviceaccount.com"/>
>   
> 
>   
> 
> {code}
> 6. Copy  into $IGNITE_HOME
> 7. Run bin/ignite.sh
> 8. Log:
> {code:java}
> class org.apache.ignite.IgniteException: Failed to instantiate Spring XML 
> application context (make sure all classes used in Spring configuration are 
> present at CLASSPATH) 
> [springUrl=file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]
>  at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
>  at org.apache.ignite.Ignition.start(Ignition.java:350)
>  at 
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to 
> instantiate Spring XML application context (make sure all classes used in 
> Spring configuration are present at CLASSPATH) 
> [springUrl=file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]
>  at 
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:387)
>  at 
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:104)
>  at 
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:98)
>  at 
> org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:673)
>  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:874)
>  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
>  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
>  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
>  at org.apache.ignite.Ignition.start(Ignition.java:347)
>  ... 1 more
> Caused by: org.springframework.beans.factory.BeanCreationException: Error 
> creating bean with name 
> 'org.apache.ignite.configuration.IgniteConfiguration#0' defined in URL 
> [file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
>  Cannot create inner bean 
> 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#65e2dbf3' of type 
> [org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] while setting bean 
> property 'discoverySpi'; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#65e2dbf3' 
> defined in URL 
> [file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
>  Cannot create inner bean 
> 'org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder#1d16f93d'
>  of type 
> [org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder]
>  while setting bean property 'ipFinder'; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 
> 'org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder#1d16f93d'
>  defined in URL 
> [file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
>  Instantiation of bean failed; nested exception is 
> 

[jira] [Created] (IGNITE-7806) SQL TX: Backup update protocol

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7806:
---

 Summary: SQL TX: Backup update protocol
 Key: IGNITE-7806
 URL: https://issues.apache.org/jira/browse/IGNITE-7806
 Project: Ignite
  Issue Type: Task
  Components: cache, sql
Reporter: Vladimir Ozerov


Currently TX SQL protocol works as follows:
1) Lock request is sent to {{PRIMARY}} node where updates are applied 
immediately.
2) Updated values are stored in-memory
3) When commit command is issued, updates are propagated to {{BACKUP}}s.

This requires data to be stored in memory at some point. We should design 
better protocol which will allow for updates to be propagated to backups 
efficiently.

Ticket is related (or may be even duplicates) to IGNITE-7186.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)