[jira] [Comment Edited] (IGNITE-1146) Implement summary page with configuration downloads.
[
https://issues.apache.org/jira/browse/IGNITE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939376#comment-14939376
]
Pavel Konstantinov edited comment on IGNITE-1146 at 10/2/15 4:50 AM:
-
1) I think we should rename generated java factory class 'ConfigurationFactory'
to 'IgniteConfigurationFactory' because 'IgniteConfiguration' is returned.
2) currently we set gridName using incorrect syntax 'cfg.gridName("aaa");'
should be 'cfg.setGridName("aaa");'
3) we should hide Server and Client preview in case of no clusters are matched
the filter
4) I scrolled the page up so that Client section was at the top of the screen.
Then switched Client preview to Java view - the page is scrolling down.
5) Java view doesn't display drop down triangle for field 'Generate'
was (Author: pkonstantinov):
1) I think we should rename generated java factory class 'ConfigurationFactory'
to 'IgniteConfigurationFactory' because 'IgniteConfiguration' is returned.
2) currently we set gridName using incorrect syntax 'cfg.gridName("aaa");'
should be 'cfg.setGridName("aaa");'
3) we should hide Server and Client preview in case of no clusters are matched
the filter
4) I scrolled the page up so that Client section was at the top of the screen.
Then switched Client preview to Java view - the page is scrolling down.
> Implement summary page with configuration downloads.
>
>
> Key: IGNITE-1146
> URL: https://issues.apache.org/jira/browse/IGNITE-1146
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
> Fix For: ignite-1.5
>
> Attachments: summary - client.png, summary - server.png,
> test-cluster-2.xml
>
>
> Generate:
> * sprint xml configuration;
> * Java class with configuration;
> * Java snippet with configuration;
> * docker file for run with this configuration.
> Download all generated files as zip archive, generate client configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1146) Implement summary page with configuration downloads.
[
https://issues.apache.org/jira/browse/IGNITE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939376#comment-14939376
]
Pavel Konstantinov edited comment on IGNITE-1146 at 10/2/15 4:48 AM:
-
1) I think we should rename generated java factory class 'ConfigurationFactory'
to 'IgniteConfigurationFactory' because 'IgniteConfiguration' is returned.
2) currently we set gridName using incorrect syntax 'cfg.gridName("aaa");'
should be 'cfg.setGridName("aaa");'
3) we should hide Server and Client preview in case of no clusters are matched
the filter
4) I scrolled the page up so that Client section was at the top of the screen.
Then switched Client preview to Java view - the page is scrolling down.
was (Author: pkonstantinov):
1) I think we should rename generated java factory class 'ConfigurationFactory'
to 'IgniteConfigurationFactory' because 'IgniteConfiguration' is returned.
2) currently we set gridName using incorrect syntax 'cfg.gridName("aaa");'
should be 'cfg.setGridName("aaa");'
3) we should hide Server and Client preview in case of no clusters are matched
the filter
4) Page is scrolling down after I've clicked 'Java' preview in 'Client'
configuration.
> Implement summary page with configuration downloads.
>
>
> Key: IGNITE-1146
> URL: https://issues.apache.org/jira/browse/IGNITE-1146
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
> Fix For: ignite-1.5
>
> Attachments: summary - client.png, summary - server.png,
> test-cluster-2.xml
>
>
> Generate:
> * sprint xml configuration;
> * Java class with configuration;
> * Java snippet with configuration;
> * docker file for run with this configuration.
> Download all generated files as zip archive, generate client configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1146) Implement summary page with configuration downloads.
[
https://issues.apache.org/jira/browse/IGNITE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939376#comment-14939376
]
Pavel Konstantinov edited comment on IGNITE-1146 at 10/2/15 4:43 AM:
-
1) I think we should rename generated java factory class 'ConfigurationFactory'
to 'IgniteConfigurationFactory' because 'IgniteConfiguration' is returned.
2) currently we set gridName using incorrect syntax 'cfg.gridName("aaa");'
should be 'cfg.setGridName("aaa");'
3) we should hide Server and Client preview in case of no clusters are matched
the filter
4) Page is scrolling down after I've clicked 'Java' preview in 'Client'
configuration.
was (Author: pkonstantinov):
1) I think we should rename generated java factory class 'ConfigurationFactory'
to 'IgniteConfigurationFactory' because 'IgniteConfiguration' is returned.
2) currently we set gridName using incorrect syntax 'cfg.gridName("aaa");'
should be 'cfg.setGridName("aaa");'
3) we should hide Server and Client preview in case of no clusters are matched
the filter
> Implement summary page with configuration downloads.
>
>
> Key: IGNITE-1146
> URL: https://issues.apache.org/jira/browse/IGNITE-1146
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
> Fix For: ignite-1.5
>
> Attachments: summary - client.png, summary - server.png,
> test-cluster-2.xml
>
>
> Generate:
> * sprint xml configuration;
> * Java class with configuration;
> * Java snippet with configuration;
> * docker file for run with this configuration.
> Download all generated files as zip archive, generate client configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (IGNITE-1146) Implement summary page with configuration downloads.
[ https://issues.apache.org/jira/browse/IGNITE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1146: --- Comment: was deleted (was: Page is scrolling down after I've clicked 'Java' preview in 'Client' configuration. ) > Implement summary page with configuration downloads. > > > Key: IGNITE-1146 > URL: https://issues.apache.org/jira/browse/IGNITE-1146 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Andrey Novikov >Assignee: Andrey Novikov > Fix For: ignite-1.5 > > Attachments: summary - client.png, summary - server.png, > test-cluster-2.xml > > > Generate: > * sprint xml configuration; > * Java class with configuration; > * Java snippet with configuration; > * docker file for run with this configuration. > Download all generated files as zip archive, generate client configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (IGNITE-1146) Implement summary page with configuration downloads.
[ https://issues.apache.org/jira/browse/IGNITE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reopened IGNITE-1146: Assignee: Andrey Novikov (was: Pavel Konstantinov) Page is scrolling down after I've clicked 'Java' preview in 'Client' configuration. > Implement summary page with configuration downloads. > > > Key: IGNITE-1146 > URL: https://issues.apache.org/jira/browse/IGNITE-1146 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Andrey Novikov >Assignee: Andrey Novikov > Fix For: ignite-1.5 > > Attachments: summary - client.png, summary - server.png, > test-cluster-2.xml > > > Generate: > * sprint xml configuration; > * Java class with configuration; > * Java snippet with configuration; > * docker file for run with this configuration. > Download all generated files as zip archive, generate client configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1219) Add ssl configuration
[
https://issues.apache.org/jira/browse/IGNITE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940756#comment-14940756
]
Pavel Konstantinov edited comment on IGNITE-1219 at 10/2/15 4:27 AM:
-
Is it correct to set array of objects like you done for 'trustManagers'?
I suspect that '' will be an
array of String.
May be need to do something like this because trustManager should be an
instance of TrustManager
{code}
{code}
was (Author: pkonstantinov):
Is it correct to set array of objects like you done for 'trustManagers'?
I suspect that '' will be an
array of String.
May be something like this because trustManager should be an instance of
TrustManager
{code}
{code}
> Add ssl configuration
> -
>
> Key: IGNITE-1219
> URL: https://issues.apache.org/jira/browse/IGNITE-1219
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Affects Versions: ignite-1.4
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: ignite-1.5
>
>
> We need to add ssl configuration to cluster screen
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1219) Add ssl configuration
[
https://issues.apache.org/jira/browse/IGNITE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940756#comment-14940756
]
Pavel Konstantinov edited comment on IGNITE-1219 at 10/2/15 4:27 AM:
-
Is it correct to set array of objects like you done for 'trustManagers'?
I suspect that '' will be an
array of String.
May be something like this because trustManager should be an instance of
TrustManager
{code}
{code}
was (Author: pkonstantinov):
Is it correct to set array of objects like you done for 'trustManagers'?
May be something like this because trustManager should be an instance of
TrustManager
{code}
{code}
> Add ssl configuration
> -
>
> Key: IGNITE-1219
> URL: https://issues.apache.org/jira/browse/IGNITE-1219
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Affects Versions: ignite-1.4
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: ignite-1.5
>
>
> We need to add ssl configuration to cluster screen
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1219) Add ssl configuration
[
https://issues.apache.org/jira/browse/IGNITE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940756#comment-14940756
]
Pavel Konstantinov commented on IGNITE-1219:
Is it correct to set array of objects like you done for 'trustManagers'?
May be something like this because trustManager should be an instance of
TrustManager
{code}
{code}
> Add ssl configuration
> -
>
> Key: IGNITE-1219
> URL: https://issues.apache.org/jira/browse/IGNITE-1219
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Affects Versions: ignite-1.4
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: ignite-1.5
>
>
> We need to add ssl configuration to cluster screen
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1594) Home page for web console
[ https://issues.apache.org/jira/browse/IGNITE-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939884#comment-14939884 ] Vasiliy Sisko edited comment on IGNITE-1594 at 10/2/15 3:37 AM: Changed: # Title of the page shortened, # Description added, # Changed carousel: navigation arrows showed all time, removed gradient for navigation arrows, navigation arrows shifted inside of image, removed shadows on image description. # The clicker left and right arrows stay on current height for better usability. was (Author: vsisko): Changed: # Title of the page shortened, # Description added, # Changed carousel: navigation arrows showed all time, removed gradient for navigation arrows, navigation arrows shifted inside of image and stay on current height for better usability, removed shadows on image description. > Home page for web console > - > > Key: IGNITE-1594 > URL: https://issues.apache.org/jira/browse/IGNITE-1594 > Project: Ignite > Issue Type: Sub-task > Components: UI >Reporter: Dmitriy Setrakyan >Assignee: Pavel Konstantinov > Fix For: ignite-1.5 > > > Home page should look as following: > # Logo with Apache Ignite Web Console up top > # Explanation of what web console is immediately below. > # Login on the left > # screenshots on the right -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1594) Home page for web console
[ https://issues.apache.org/jira/browse/IGNITE-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-1594: - Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Home page for web console > - > > Key: IGNITE-1594 > URL: https://issues.apache.org/jira/browse/IGNITE-1594 > Project: Ignite > Issue Type: Sub-task > Components: UI >Reporter: Dmitriy Setrakyan >Assignee: Pavel Konstantinov > Fix For: ignite-1.5 > > > Home page should look as following: > # Logo with Apache Ignite Web Console up top > # Explanation of what web console is immediately below. > # Login on the left > # screenshots on the right -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1609) New value should be copied when cache interceptor is called
Valentin Kulichenko created IGNITE-1609: --- Summary: New value should be copied when cache interceptor is called Key: IGNITE-1609 URL: https://issues.apache.org/jira/browse/IGNITE-1609 Project: Ignite Issue Type: Bug Components: cache Reporter: Valentin Kulichenko Currently we copy old value that is stored in cache, but not new value - this is inconsistent. Also there are scenarios when interceptor is called more than once and if the value is mutated, issues are possible. Example can be found in this thread: http://apache-ignite-users.70518.x6.nabble.com/CacheStore-implementation-using-Hibernate-td1423.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-638) Implement IgniteSemaphore data structure
[
https://issues.apache.org/jira/browse/IGNITE-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940180#comment-14940180
]
Vladisav Jelisavcic commented on IGNITE-638:
Thanks for the comments!
Everything should be okay now (regarding the formatting issues).
System.out.println is only used in IgniteSemaphoreExample (same as in other
examples).
> Implement IgniteSemaphore data structure
>
>
> Key: IGNITE-638
> URL: https://issues.apache.org/jira/browse/IGNITE-638
> Project: Ignite
> Issue Type: Sub-task
> Components: data structures
>Reporter: Dmitriy Setrakyan
>Assignee: Vladisav Jelisavcic
>
> We need to add {{IgniteSemaphore}} data structure in addition to other data
> structures provided by Ignite. {{IgniteSemaphore}} should have similar API to
> {{java.util.concurrent.IgniteSemaphore}} class in JDK.
> As an example, you can see how
> [IgniteCountDownLatch|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/IgniteCountDownLatch.java]
> is implemented in
> [GridCacheCountDownLatchImpl|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/datastructures/GridCacheCountDownLatchImpl.java]
> class.
> In general we need to have an entity in ATOMIC cache storing number of
> permits and allow user threads to block whenever no more permits are
> available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1246) Exception in thread "main" javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: Failed to validate cache configuration. Cache store factory is not
[
https://issues.apache.org/jira/browse/IGNITE-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-1246:
Assignee: kcheng.mvp (was: Valentin Kulichenko)
> Exception in thread "main" javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Failed to validate cache
> configuration. Cache store factory is not serializable. Cache name: XXX
> ---
>
> Key: IGNITE-1246
> URL: https://issues.apache.org/jira/browse/IGNITE-1246
> Project: Ignite
> Issue Type: Bug
>Reporter: kcheng.mvp
>Assignee: kcheng.mvp
> Labels: user-request
> Attachments: ignite-01.png, ignite-02.png
>
>
> Here is my configuration
> {code:xml}
>
> class="org.springframework.jdbc.datasource.DriverManagerDataSource">
>value="oracle.jdbc.driver.OracleDriver" />
> value="jdbc:oracle:thin:@//192.168.2.39:1521/db" />
>
>
>
> class="org.apache.ignite.configuration.CacheConfiguration" scope="prototype">
>
>
>
>
>
>
>class="javax.cache.configuration.FactoryBuilder$SingletonFactory">
>
>class="org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStore">
>ref="dataSource"/>
>
>
>
>
>
> {code}
> When I try to load data to the cache I got the exception.
> here is he stack from client node
> {code}
> Exception in thread "main" javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Failed to validate cache
> configuration. Cache store factory is not serializable. Cache name:
> T_HTLPRO_PRICEPLAN
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1581)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2311)
> at
> org.apache.ignite.IgniteSpringBean.getOrCreateCache(IgniteSpringBean.java:246)
> at com.fangcang.cache.client.Grid.getCacheByCfg(Grid.java:30)
> at com.fangcang.cache.client.InitLoader.main(InitLoader.java:16)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to validate
> cache configuration. Cache store factory is not serializable. Cache name:
> T_HTLPRO_PRICEPLAN
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.checkSerializable(GridCacheProcessor.java:3038)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:1958)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:1927)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2306)
> ... 3 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
> serialize object:
> javax.cache.configuration.FactoryBuilder$SingletonFactory@55dfebeb
> at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.marshal(JdkMarshaller.java:78)
> at
> org.apache.ignite.marshaller.AbstractMarshaller.marshal(AbstractMarshaller.java:51)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.checkSerializable(GridCacheProcessor.java:3034)
> ... 6 more
> Caused by: java.io.NotSerializableException:
> org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStore
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
> at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
> at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
> at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.marshal(JdkMarshaller.java:73)
> ... 8 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1608) Platform .Net: Optimize PortableWriterImpl.WritePrimitive
Pavel Tupitsyn created IGNITE-1608: --- Summary: Platform .Net: Optimize PortableWriterImpl.WritePrimitive Key: IGNITE-1608 URL: https://issues.apache.org/jira/browse/IGNITE-1608 Project: Ignite Issue Type: Task Components: interop Affects Versions: ignite-1.5 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: ignite-1.5 Huge "if" tree can be replaced with dynamic dispatch. Need to investigate if performance can be improved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1607) Implement deadlock-free optimistic serializable mode
Alexey Goncharuk created IGNITE-1607: Summary: Implement deadlock-free optimistic serializable mode Key: IGNITE-1607 URL: https://issues.apache.org/jira/browse/IGNITE-1607 Project: Ignite Issue Type: Bug Components: cache Affects Versions: ignite-1.4 Reporter: Alexey Goncharuk There is an idea of optimistic serializable mode which will provide better scalability on relatively large transactions and large topologies when no heavy contention is experienced. * When transactional read is performed, we need to store the version of read entry. * When transaction prepare is performed, we can send prepare requests simultaneously on all nodes. There is no need to preserve the order of locks and create a queue of tx mappings for this mode. * When we add local MVCC candidates on a primary node, two checks are performed: that the current entry version matches the one transaction read (if read was performed), and that currently there are no other local MVCC candidates. If any of these checks fails, prepare step fails and transaction is failed with optimistic conflict exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1605) Provide stronger data loss check
[ https://issues.apache.org/jira/browse/IGNITE-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yakov Zhdanov updated IGNITE-1605: -- Description: Need to provide stronger data loss check. Currently node can fire event - EVT_CACHE_REBALANCE_PART_DATA_LOST However, this is not enough since if there is strong requirement on application behavior on data loss e.g. further cache updates should throw exception - this requirement cannot currently be met even with use of cache interceptor. Suggestions: * Introduce CacheDataLossPolicy enum: FAIL_OPS, NOOP and put it to configuration * If node fires PART_LOST_EVT then any update to lost partition will throw (or will not throw) exception according to DataLossPolicy * ForceKeysRequest should be completed with exception (if plc == FAIL) if all nodes to request from are gone. So, all gets/puts/txs should fail. * Add a public API method in order to allow a recovery from a failed state. Another solution is to detect partition loss at the time partition exchange completes. Since we hold topology lock during the exchange, we can easily check that there are no owners for a partition and act as a topology validator in case FAIL policy is configured. There is one thing needed to be carefully analyzed: demand worker should not park partition as owning in case last owner leaves grid before the corresponding exchange completes. was: Need to provide stronger data loss check. Currently node can fire event - EVT_CACHE_REBALANCE_PART_DATA_LOST However, this is not enough since if there is strong requirement on application behavior on data loss e.g. further cache updates should throw exception - this requirement cannot currently be met even with use of cache interceptor. Suggestions: * Introduce CacheDataLossPolicy enum: FAIL_OPS, NOOP and put it to configuration * If node fires PART_LOST_EVT then any update to lost partition will throw (or will not throw) exception according to DataLossPolicy * ForceKeysRequest should be completed with exception (if plc == FAIL) if all nodes to request from are gone. So, all gets/puts/txs should fail. We also may want to add a public API method in order to allow a recovery from a failed state. > Provide stronger data loss check > > > Key: IGNITE-1605 > URL: https://issues.apache.org/jira/browse/IGNITE-1605 > Project: Ignite > Issue Type: Task >Reporter: Yakov Zhdanov >Assignee: Alexey Goncharuk > > Need to provide stronger data loss check. > Currently node can fire event - EVT_CACHE_REBALANCE_PART_DATA_LOST > However, this is not enough since if there is strong requirement on > application behavior on data loss e.g. further cache updates should throw > exception - this requirement cannot currently be met even with use of cache > interceptor. > Suggestions: > * Introduce CacheDataLossPolicy enum: FAIL_OPS, NOOP and put it to > configuration > * If node fires PART_LOST_EVT then any update to lost partition will throw > (or will not throw) exception according to DataLossPolicy > * ForceKeysRequest should be completed with exception (if plc == FAIL) if all > nodes to request from are gone. So, all gets/puts/txs should fail. > * Add a public API method in order to allow a recovery from a failed state. > Another solution is to detect partition loss at the time partition exchange > completes. Since we hold topology lock during the exchange, we can easily > check that there are no owners for a partition and act as a topology > validator in case FAIL policy is configured. There is one thing needed to be > carefully analyzed: demand worker should not park partition as owning in case > last owner leaves grid before the corresponding exchange completes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1604) Provide ability to get notification on rebalancing finish
[ https://issues.apache.org/jira/browse/IGNITE-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yakov Zhdanov updated IGNITE-1604: -- Description: It would be nice if user have ability to wait until rebalancing is finished across whole topology on current topology version. Need to add method: * Future IgniteCache.rebalanceFuture(); * Future IgniteCache.localRebalanceFuture(); If currently no rebalancing is running, finished future is returned. was: It would be nice if user have ability to wait until rebalancing is finished across whole topology on current topology version. Need to add method: * Future IgniteCache.rebalanceFuture(); * Future IgniteCache.globalRebalanceFuture(); If currently no rebalancing is running, finished future is returned. > Provide ability to get notification on rebalancing finish > - > > Key: IGNITE-1604 > URL: https://issues.apache.org/jira/browse/IGNITE-1604 > Project: Ignite > Issue Type: Task >Reporter: Yakov Zhdanov >Assignee: Anton Vinogradov > > It would be nice if user have ability to wait until rebalancing is finished > across whole topology on current topology version. > Need to add method: > * Future IgniteCache.rebalanceFuture(); > * Future IgniteCache.localRebalanceFuture(); > If currently no rebalancing is running, finished future is returned. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1605) Provide stronger data loss check
[ https://issues.apache.org/jira/browse/IGNITE-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940051#comment-14940051 ] Alexey Goncharuk commented on IGNITE-1605: -- Another solution is to detect partition loss at the time partition exchange completes. Since we hold topology lock during the exchange, we can easily check that there are no owners for a partition and act as a topology validator in case FAIL policy is configured. There is one thing needed to be carefully analyzed: demand worker should not park partition as owning in case last owner leaves grid before the corresponding exchange completes. > Provide stronger data loss check > > > Key: IGNITE-1605 > URL: https://issues.apache.org/jira/browse/IGNITE-1605 > Project: Ignite > Issue Type: Task >Reporter: Yakov Zhdanov >Assignee: Alexey Goncharuk > > Need to provide stronger data loss check. > Currently node can fire event - EVT_CACHE_REBALANCE_PART_DATA_LOST > However, this is not enough since if there is strong requirement on > application behavior on data loss e.g. further cache updates should throw > exception - this requirement cannot currently be met even with use of cache > interceptor. > Suggestions: > * Introduce CacheDataLossPolicy enum: FAIL_OPS, NOOP and put it to > configuration > * If node fires PART_LOST_EVT then any update to lost partition will throw > (or will not throw) exception according to DataLossPolicy > * ForceKeysRequest should be completed with exception (if plc == FAIL) if all > nodes to request from are gone. So, all gets/puts/txs should fail. > We also may want to add a public API method in order to allow a recovery from > a failed state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1605) Provide stronger data loss check
[ https://issues.apache.org/jira/browse/IGNITE-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-1605: - Description: Need to provide stronger data loss check. Currently node can fire event - EVT_CACHE_REBALANCE_PART_DATA_LOST However, this is not enough since if there is strong requirement on application behavior on data loss e.g. further cache updates should throw exception - this requirement cannot currently be met even with use of cache interceptor. Suggestions: * Introduce CacheDataLossPolicy enum: FAIL_OPS, NOOP and put it to configuration * If node fires PART_LOST_EVT then any update to lost partition will throw (or will not throw) exception according to DataLossPolicy * ForceKeysRequest should be completed with exception (if plc == FAIL) if all nodes to request from are gone. So, all gets/puts/txs should fail. We also may want to add a public API method in order to allow a recovery from a failed state. was: Need to provide stronger data loss check. Currently node can fire event - EVT_CACHE_REBALANCE_PART_DATA_LOST However, this is not enough since if there is strong requirement on application behavior on data loss e.g. further cache updates should throw exception - this requirement cannot currently be met even with use of cache interceptor. Suggestions: * Introduce CacheDataLossPolicy enum: FAIL_OPS, NOOP and put it to configuration * If node fires PART_LOST_EVT then any update to lost partition will throw (or will not throw) exception according to DataLossPolicy * ForceKeysRequest should be completed with exception (if plc == FAIL) if all nodes to request from are gone. So, all gets/puts/txs should fail. > Provide stronger data loss check > > > Key: IGNITE-1605 > URL: https://issues.apache.org/jira/browse/IGNITE-1605 > Project: Ignite > Issue Type: Task >Reporter: Yakov Zhdanov >Assignee: Alexey Goncharuk > > Need to provide stronger data loss check. > Currently node can fire event - EVT_CACHE_REBALANCE_PART_DATA_LOST > However, this is not enough since if there is strong requirement on > application behavior on data loss e.g. further cache updates should throw > exception - this requirement cannot currently be met even with use of cache > interceptor. > Suggestions: > * Introduce CacheDataLossPolicy enum: FAIL_OPS, NOOP and put it to > configuration > * If node fires PART_LOST_EVT then any update to lost partition will throw > (or will not throw) exception according to DataLossPolicy > * ForceKeysRequest should be completed with exception (if plc == FAIL) if all > nodes to request from are gone. So, all gets/puts/txs should fail. > We also may want to add a public API method in order to allow a recovery from > a failed state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1606) NPE during node stop due to nullified logger in TcpCommunicationSpi
Valentin Kulichenko created IGNITE-1606:
---
Summary: NPE during node stop due to nullified logger in
TcpCommunicationSpi
Key: IGNITE-1606
URL: https://issues.apache.org/jira/browse/IGNITE-1606
Project: Ignite
Issue Type: Bug
Components: general
Reporter: Valentin Kulichenko
Fix For: ignite-1.5
Probably we should check other components as well. Not sure why we need to
nullify logger.
{noformat}
Exception in thread "ignite-#101%sys-t1-1%" java.lang.NullPointerException
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1896)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1880)
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1066)
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1214)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1071)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1034)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1017)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processNotification(GridContinuousProcessor.java:851)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$1500(GridContinuousProcessor.java:85)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$8.onMessage(GridContinuousProcessor.java:556)
at
org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2302)
at
org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:992)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:106)
at
org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:961)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1605) Provide stronger data loss check
[ https://issues.apache.org/jira/browse/IGNITE-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-1605: - Assignee: Alexey Goncharuk > Provide stronger data loss check > > > Key: IGNITE-1605 > URL: https://issues.apache.org/jira/browse/IGNITE-1605 > Project: Ignite > Issue Type: Task >Reporter: Yakov Zhdanov >Assignee: Alexey Goncharuk > > Need to provide stronger data loss check. > Currently node can fire event - EVT_CACHE_REBALANCE_PART_DATA_LOST > However, this is not enough since if there is strong requirement on > application behavior on data loss e.g. further cache updates should throw > exception - this requirement cannot currently be met even with use of cache > interceptor. > Suggestions: > * Introduce CacheDataLossPolicy enum: FAIL_OPS, NOOP and put it to > configuration > * If node fires PART_LOST_EVT then any update to lost partition will throw > (or will not throw) exception according to DataLossPolicy > * ForceKeysRequest should be completed with exception (if plc == FAIL) if all > nodes to request from are gone. So, all gets/puts/txs should fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1605) Provide stronger data loss check
Yakov Zhdanov created IGNITE-1605: - Summary: Provide stronger data loss check Key: IGNITE-1605 URL: https://issues.apache.org/jira/browse/IGNITE-1605 Project: Ignite Issue Type: Task Reporter: Yakov Zhdanov Need to provide stronger data loss check. Currently node can fire event - EVT_CACHE_REBALANCE_PART_DATA_LOST However, this is not enough since if there is strong requirement on application behavior on data loss e.g. further cache updates should throw exception - this requirement cannot currently be met even with use of cache interceptor. Suggestions: * Introduce CacheDataLossPolicy enum: FAIL_OPS, NOOP and put it to configuration * If node fires PART_LOST_EVT then any update to lost partition will throw (or will not throw) exception according to DataLossPolicy * ForceKeysRequest should be completed with exception (if plc == FAIL) if all nodes to request from are gone. So, all gets/puts/txs should fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1604) Provide ability to get notification on rebalancing finish
[ https://issues.apache.org/jira/browse/IGNITE-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov reassigned IGNITE-1604: Assignee: Anton Vinogradov > Provide ability to get notification on rebalancing finish > - > > Key: IGNITE-1604 > URL: https://issues.apache.org/jira/browse/IGNITE-1604 > Project: Ignite > Issue Type: Task >Reporter: Yakov Zhdanov >Assignee: Anton Vinogradov > > It would be nice if user have ability to wait until rebalancing is finished > across whole topology on current topology version. > Need to add method: > * Future IgniteCache.rebalanceFuture(); > * Future IgniteCache.globalRebalanceFuture(); > If currently no rebalancing is running, finished future is returned. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1604) Provide ability to get notification on rebalancing finish
Yakov Zhdanov created IGNITE-1604: - Summary: Provide ability to get notification on rebalancing finish Key: IGNITE-1604 URL: https://issues.apache.org/jira/browse/IGNITE-1604 Project: Ignite Issue Type: Task Reporter: Yakov Zhdanov It would be nice if user have ability to wait until rebalancing is finished across whole topology on current topology version. Need to add method: * Future IgniteCache.rebalanceFuture(); * Future IgniteCache.globalRebalanceFuture(); If currently no rebalancing is running, finished future is returned. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1571) .Net: Improve Guid and DateTime reader/writer interface.
[ https://issues.apache.org/jira/browse/IGNITE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940019#comment-14940019 ] Pavel Tupitsyn commented on IGNITE-1571: - I'm not sure if I understand your point with readers. * We can't separate type ids for non-nullable DateTime & Guid because of Java * For single value methods like ReadDate() we just call ReadNullableDate().Value * For arrays methods we have to create separate read methods that create arrays of non-nullable items Now, ReadObject is a different story: * for single value methods it should not be a problem since cast works between nullable/nonnullable value types and we do not have to do anything. * for arrays, we have a problem since we do not know what the user expects. We can try to examine generic argument, but it can be "object". > .Net: Improve Guid and DateTime reader/writer interface. > > > Key: IGNITE-1571 > URL: https://issues.apache.org/jira/browse/IGNITE-1571 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn >Priority: Critical > Fix For: ignite-1.5 > > > Currently we force user to write Guid and DateTime as nullables. We do this > to be more compatible with Java. > But user is more likely to operate on plain types: Guid, Guid[], DateTime, > DateTime[]. > We need to add these methods to API, and rename existing ones to > "ReadNullableDateTime", etc.. > Note that while trivial to on writer side, it will be harder to implement for > readers. Currently we lookup by type ID, which will be equal for the type and > it's nullable counterpart. For this reason we probably must lookup by type ID > + type or simply by type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (IGNITE-1571) .Net: Improve Guid and DateTime reader/writer interface.
[ https://issues.apache.org/jira/browse/IGNITE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1571: Comment: was deleted (was: We don't have methods for nullable primitives, so I think we should either remove methods for nullable Guid and DateTime or add them for all other types.) > .Net: Improve Guid and DateTime reader/writer interface. > > > Key: IGNITE-1571 > URL: https://issues.apache.org/jira/browse/IGNITE-1571 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn >Priority: Critical > Fix For: ignite-1.5 > > > Currently we force user to write Guid and DateTime as nullables. We do this > to be more compatible with Java. > But user is more likely to operate on plain types: Guid, Guid[], DateTime, > DateTime[]. > We need to add these methods to API, and rename existing ones to > "ReadNullableDateTime", etc.. > Note that while trivial to on writer side, it will be harder to implement for > readers. Currently we lookup by type ID, which will be equal for the type and > it's nullable counterpart. For this reason we probably must lookup by type ID > + type or simply by type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1571) .Net: Improve Guid and DateTime reader/writer interface.
[ https://issues.apache.org/jira/browse/IGNITE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939996#comment-14939996 ] Pavel Tupitsyn commented on IGNITE-1571: - We don't have methods for nullable primitives, so I think we should either remove methods for nullable Guid and DateTime or add them for all other types. > .Net: Improve Guid and DateTime reader/writer interface. > > > Key: IGNITE-1571 > URL: https://issues.apache.org/jira/browse/IGNITE-1571 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn >Priority: Critical > Fix For: ignite-1.5 > > > Currently we force user to write Guid and DateTime as nullables. We do this > to be more compatible with Java. > But user is more likely to operate on plain types: Guid, Guid[], DateTime, > DateTime[]. > We need to add these methods to API, and rename existing ones to > "ReadNullableDateTime", etc.. > Note that while trivial to on writer side, it will be harder to implement for > readers. Currently we lookup by type ID, which will be equal for the type and > it's nullable counterpart. For this reason we probably must lookup by type ID > + type or simply by type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1571) .Net: Improve Guid and DateTime reader/writer interface.
[ https://issues.apache.org/jira/browse/IGNITE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1571: Description: Currently we force user to write Guid and DateTime as nullables. We do this to be more compatible with Java. But user is more likely to operate on plain types: Guid, Guid[], DateTime, DateTime[]. We need to add these methods to API, and rename existing ones to "ReadNullableDateTime", etc.. Note that while trivial to on writer side, it will be harder to implement for readers. Currently we lookup by type ID, which will be equal for the type and it's nullable counterpart. For this reason we probably must lookup by type ID + type or simply by type. was: Currently we force user to write Guid and DateTime as nullables. We do this to be more compatible with Java. But user is more likely to operate on plain types: Guid, Guid[], DateTime, DateTime[]. We need to ass these methods to API, and rename existing ones to "ReadNullableDateTime", etc.. Note that while trivial to on writer side, it will be harder to implement for readers. Currently we lookup by type ID, which will be equal for the type and it's nullable counterpart. For this reason we probably must lookup by type ID + type or simply by type. > .Net: Improve Guid and DateTime reader/writer interface. > > > Key: IGNITE-1571 > URL: https://issues.apache.org/jira/browse/IGNITE-1571 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn >Priority: Critical > Fix For: ignite-1.5 > > > Currently we force user to write Guid and DateTime as nullables. We do this > to be more compatible with Java. > But user is more likely to operate on plain types: Guid, Guid[], DateTime, > DateTime[]. > We need to add these methods to API, and rename existing ones to > "ReadNullableDateTime", etc.. > Note that while trivial to on writer side, it will be harder to implement for > readers. Currently we lookup by type ID, which will be equal for the type and > it's nullable counterpart. For this reason we probably must lookup by type ID > + type or simply by type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1454) CPP: Review all std:: usages in public API.
[ https://issues.apache.org/jira/browse/IGNITE-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-1454: --- Assignee: Igor Sapego > CPP: Review all std:: usages in public API. > --- > > Key: IGNITE-1454 > URL: https://issues.apache.org/jira/browse/IGNITE-1454 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Igor Sapego >Priority: Critical > Fix For: ignite-1.5 > > > 1) All std:: usages in public API must reside in headers. > 2) Consider getting rid of char* and use std::string instead in public API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1573) IGFS: mkdirs operations should be truly thread-safe
[ https://issues.apache.org/jira/browse/IGNITE-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939921#comment-14939921 ] Ivan Veselovsky commented on IGNITE-1573: - done. > IGFS: mkdirs operations should be truly thread-safe > --- > > Key: IGNITE-1573 > URL: https://issues.apache.org/jira/browse/IGNITE-1573 > Project: Ignite > Issue Type: Bug > Components: hadoop >Affects Versions: ignite-1.4 >Reporter: Ivan Veselovsky >Assignee: Ivan Veselovsky > Fix For: ignite-1.5 > > > Need to lock all the existing parents and try to add the missing path in one > transaction. > If failed due to concurrent creation, retry from the beginning. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1572) .Net: Check if we can get rid of "WritePortableOrSerializable" method.
[ https://issues.apache.org/jira/browse/IGNITE-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939912#comment-14939912 ] Pavel Tupitsyn commented on IGNITE-1572: - PortableOrSerializable methods replaced with Write/ReadObject > .Net: Check if we can get rid of "WritePortableOrSerializable" method. > -- > > Key: IGNITE-1572 > URL: https://issues.apache.org/jira/browse/IGNITE-1572 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn >Priority: Critical > Fix For: ignite-1.5 > > > We have lots of places where "WritePortableOrSerializable" routine is > invoked. It is not clear why do we need it provided that we already handle > [Serializable] classes properly. > Looks like we are able to get rid of it safely, aren't we? Need to > double-check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1123) Instability and broken topology when multiple server and client nodes are restarted
[
https://issues.apache.org/jira/browse/IGNITE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-1123:
-
Labels: Muted_test (was: )
> Instability and broken topology when multiple server and client nodes are
> restarted
> ---
>
> Key: IGNITE-1123
> URL: https://issues.apache.org/jira/browse/IGNITE-1123
> Project: Ignite
> Issue Type: Sub-task
> Components: clients, general
>Affects Versions: sprint-7
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Labels: Muted_test
> Fix For: ignite-1.5
>
>
> The bug is always reproduced with
> TcpDiscoveryMultiThreadedTest.testMultiThreadedClientsServersRestart.
> The test starts multiple servers and clients and then restarts them from
> multiple thread. At some point it will lead to one or all of the following:
> 1) Broken topology on a client side:
> {noformat}
> java.lang.AssertionError: TcpDiscoveryNodeAddFinishedMessage
> [nodeId=70576075-b528-43f4-b490-33d079dc7007,
> super=TcpDiscoveryAbstractMessage [sndNodeId=null,
> id=8f7e19c8e41-10b88275-1868-4faf-9ae0-d61d627b1001,
> verifierNodeId=10b88275-1868-4faf-9ae0-d61d627b1001, topVer=89, pendingIdx=0,
> isClient=false]]
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl.updateTopologyHistory(ClientImpl.java:589)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl.access$2500(ClientImpl.java:48)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:1370)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1227)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processClientReconnectMessage(ClientImpl.java:1552)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1235)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1197)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {noformat}
> 2) Clients segmentation that is not properly processed by
> GridCachePartionExchangeManager and that leads to the test hang:
> {noformat}
> Still waiting for initial partition map exchange
> [fut=GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false,
> reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=60b736c0-a2ad-4465-a3c1-7656e1fa9006, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:0], discPort=0, order=255, intOrder=0, loc=true,
> ver=1.4.1#19700101-sha1:, isClient=true], topVer=255,
> nodeId8=60b736c0, msg=null, type=NODE_JOINED, tstamp=1436877471568],
> rcvdIds=GridConcurrentHashSet
> [elements=[7098ffd9-f81b-40bf-9b9e-b0935d394007,
> 30b30924-a9e7-45fb-9aeb-361bbb482003, 00d7e953-ce8b-45e0-a1f3-be7a6dea1000,
> 301559de-a129-4b85-852f-f8325649f003, 7078cd7a-e6b9-4bed-b829-a2e792a0c007,
> 20de002e-7e98-4e55-b25f-d873e25db002, 00c444ad-b221-4695-9a6d-5ea529779000,
> 40dc3691-7b20-41d7-a436-65ad27f74004, 308f0e4a-507a-4da6-b086-bdecc08e1003,
> 20b1d488-7aa1-41d7-ac0b-e8730002, 00da0ab2-9441-4cc2-b787-c34dcf6a2000,
> 4096e7dd-e3fe-4704-9d11-3b267430e004, 1059ba84-4ca7-4d8f-9563-b90334d48001]],
> rmtIds=[30b30924-a9e7-45fb-9aeb-361bbb482003,
> 20de002e-7e98-4e55-b25f-d873e25db002, 4096e7dd-e3fe-4704-9d11-3b267430e004,
> 00c444ad-b221-4695-9a6d-5ea529779000], exchId=GridDhtPartitionExchangeId
> [topVer=AffinityTopologyVersion [topVer=255, minorTopVer=0], nodeId=60b736c0,
> evt=NODE_JOINED], init=true, ready=false, replied=false, added=true,
> initFut=GridFutureAdapter [resFlag=2, res=true, startTime=1436877471578,
> endTime=1436877471578, ignoreInterrupts=false, lsnr=null, state=DONE],
> topSnapshot=null, lastVer=null, partReleaseFut=null, skipPreload=true,
> clientOnlyExchange=true, oldest=20de002e-7e98-4e55-b25f-d873e25db002,
> oldestOrder=254, evtLatch=0, remaining=[], super=GridFutureAdapter
> [resFlag=0, res=null, startTime=1436877471578, endTime=0,
> ignoreInterrupts=false, lsnr=null, state=INIT]]]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1377) Portable metadata update on changing topology causes hangs in tests
[
https://issues.apache.org/jira/browse/IGNITE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-1377:
-
Labels: Muted_test (was: )
> Portable metadata update on changing topology causes hangs in tests
> ---
>
> Key: IGNITE-1377
> URL: https://issues.apache.org/jira/browse/IGNITE-1377
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Alexey Goncharuk
>Assignee: Semen Boikov
> Labels: Muted_test
> Fix For: ignite-1.5
>
>
> I removed metadata update on for objects not defined in configuration (this
> is not an introduced bug, it existed before) because it causes portable
> failover suite to hang.
> Need to investigate further the cause of the hang and unmute
> {{testNoConfiguration}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-705) [Test] Complete implementation of BaseH2CompareQueryTest.
[ https://issues.apache.org/jira/browse/IGNITE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-705: Labels: Muted_test (was: ) > [Test] Complete implementation of BaseH2CompareQueryTest. > - > > Key: IGNITE-705 > URL: https://issues.apache.org/jira/browse/IGNITE-705 > Project: Ignite > Issue Type: Task >Reporter: Artem Shutak >Assignee: Artem Shutak > Labels: Muted_test > > At BaseH2CompareQueryTest: > - complete implementation of testAllExamples > - improve testing data content (People with the same names for grouping > testing and etc.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-996) IgniteMessagingWithClientTest hangs on TC
[ https://issues.apache.org/jira/browse/IGNITE-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-996: Labels: Muted_test (was: ) > IgniteMessagingWithClientTest hangs on TC > - > > Key: IGNITE-996 > URL: https://issues.apache.org/jira/browse/IGNITE-996 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Semen Boikov >Assignee: Semen Boikov > Labels: Muted_test > > Test IgniteMessagingWithClientTest sometimes hangs on TC. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1386) IPC semaphores are not released on server endpoint abrupt stop
[
https://issues.apache.org/jira/browse/IGNITE-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-1386:
-
Labels: Muted_test (was: )
> IPC semaphores are not released on server endpoint abrupt stop
> --
>
> Key: IGNITE-1386
> URL: https://issues.apache.org/jira/browse/IGNITE-1386
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Priority: Critical
> Labels: Muted_test
>
> {{IpcSharedMemoryCrashDetectionSelfTest.testIgfsClientServerInteractionsUponServerKilling}}
> stops a server endpoint abruptly with 'kill' command and right after that
> start a new endpoint.
> The test expects that such a flow will release all previously allocated
> memory segments and semaphores.
> In fact, only memory segments are released while semaphores stay in the
> system. However, the test successfully ends.
> Steps to reproduce:
> - check existing semaphores with {{ipcs -s}};
> - start the test on Linux or Mac OS;
> - call {{ipcs -s}} and you will see that semaphores hasn't been released.
> In addition, TeamCity agents fail a test suite because of this reason from
> time to time
> {noformat}
> [16:14:03][Step 7/7] Failing build because of remaining IPC resources.
> [16:14:03][Step 7/7] Process exited with code 1
> [16:14:03][Step 7/7] Step Check IPC / Clean up (Command Line) failed
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1541) IGFS: mkdirs operation should be truly thread-safe.
[ https://issues.apache.org/jira/browse/IGNITE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-1541: - Labels: Muted_test (was: ) > IGFS: mkdirs operation should be truly thread-safe. > --- > > Key: IGNITE-1541 > URL: https://issues.apache.org/jira/browse/IGNITE-1541 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Veselovsky >Assignee: Ivan Veselovsky > Labels: Muted_test > > In IGNITE-1515 we made delete thread-safe. > But experience shows that concurrent delete + mkdirs operations nevertheless > cause file system structure corruption, see test > org.apache.ignite.internal.processors.igfs.IgfsAbstractSelfTest#testDeadlocksDeleteMkdirs > . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-404) Rework external execution to use regular Ignite node instead of custom bootstraper.
[ https://issues.apache.org/jira/browse/IGNITE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-404: Labels: Muted_test (was: ) > Rework external execution to use regular Ignite node instead of custom > bootstraper. > --- > > Key: IGNITE-404 > URL: https://issues.apache.org/jira/browse/IGNITE-404 > Project: Ignite > Issue Type: Task > Components: hadoop >Affects Versions: sprint-1 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Labels: Muted_test > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1107) Full Api Milti-JVM testLocalClearKeys test doesn't work for OFFHEAP_TIERED.
[
https://issues.apache.org/jira/browse/IGNITE-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-1107:
-
Labels: Muted_test (was: )
> Full Api Milti-JVM testLocalClearKeys test doesn't work for OFFHEAP_TIERED.
> ---
>
> Key: IGNITE-1107
> URL: https://issues.apache.org/jira/browse/IGNITE-1107
> Project: Ignite
> Issue Type: Bug
>Reporter: Artem Shutak
> Labels: Muted_test
>
> Full Api Milti-JVM testLocalClearKeys test doesn't work for OFFHEAP_TIERED.
> Failures of these tests cause another failures.
> {noformat}
> org.apache.ignite.IgniteException: Failed to deserialize object with given
> class loader: IsolatedClassLoader{roleName='test'}
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:684)
> at
> org.apache.ignite.internal.IgniteComputeImpl.call(IgniteComputeImpl.java:335)
> at
> org.apache.ignite.testframework.junits.multijvm.IgniteCacheProcessProxy.localEntries(IgniteCacheProcessProxy.java:191)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAbstractSelfTest.afterTest(GridCacheAbstractSelfTest.java:113)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.afterTest(GridCacheAbstractFullApiSelfTest.java:233)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.tearDown(GridAbstractTest.java:1278)
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.tearDown(GridCommonAbstractTest.java:343)
> at junit.framework.TestCase.runBare(TestCase.java:146)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82)
> at
> org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.runSuitesInProcess(InPluginVMSurefireStarter.java:82)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:951)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:831)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:729)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
[jira] [Updated] (IGNITE-648) Implement framework for multi JVM unit tests
[ https://issues.apache.org/jira/browse/IGNITE-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-648: Labels: Muted_test (was: ) > Implement framework for multi JVM unit tests > > > Key: IGNITE-648 > URL: https://issues.apache.org/jira/browse/IGNITE-648 > Project: Ignite > Issue Type: Bug >Reporter: Yakov Zhdanov >Assignee: Artem Shutak >Priority: Critical > Labels: Muted_test > Fix For: sprint-7 > > > Now, Ignite test framework runs tests with multi ignite instances in one JVM. > Need to improve Ignite test framework to have ability run different ignite > instances in separate JVMs. > Ideally, it should be isMultiJvm() method, and if isMultiJvm() returns true, > then framework will run new grids by startGrid(...) methods in separate JVMs > and existng tests have not to be fully rewritten. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-518) TTL is not updated for reader when entry is accessed on backup
[
https://issues.apache.org/jira/browse/IGNITE-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-518:
Labels: Muted_test (was: )
> TTL is not updated for reader when entry is accessed on backup
> --
>
> Key: IGNITE-518
> URL: https://issues.apache.org/jira/browse/IGNITE-518
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-2
>Reporter: Alexey Goncharuk
> Labels: Muted_test
>
> When ttl is updated, readers are recorded locally and update is then sent
> based on collected data. When get is performed on backup, readers are empty,
> so near readers are not updated.
> {{IgniteCacheAtomicExpiryPolicyTest.testNearAccess}} fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1090) GridCachePartitionedOptimisticTxNodeRestartTest hangs when node lefts topology
[
https://issues.apache.org/jira/browse/IGNITE-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-1090:
-
Labels: Muted_test (was: )
> GridCachePartitionedOptimisticTxNodeRestartTest hangs when node lefts topology
> --
>
> Key: IGNITE-1090
> URL: https://issues.apache.org/jira/browse/IGNITE-1090
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Critical
> Labels: Muted_test
> Fix For: ignite-1.5
>
>
> The test hangs with the following errors:
> {noformat}
> [16:26:33] (err) Failed to execute compound future reducer: Compound future
> listener: GridCompoundIdentityFuture [super=GridCompoundFuture [lsnrCalls=0,
> finished=false, rdc=Map reducer: {}, init=true,
> res=java.util.concurrent.atomic.AtomicMarkableReference@3c6fff03, err=null,
> done=false, cancelled=false, err=null, futs=[true]]]class
> org.apache.ignite.IgniteCheckedException: Failed to wait for topology version
> to change: AffinityTopologyVersion [topVer=274, minorTopVer=0]
> at
> org.apache.ignite.internal.processors.cache.distributed.GridFutureRemapTimeoutObject.onTimeout(GridFutureRemapTimeoutObject.java:64)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:158)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class
> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Remote
> node left grid (will retry): 703c58e1-e099-4f22-b5c3-6c3676338007
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.onNodeLeft(GridNearGetFuture.java:215)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:186)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:745)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:730)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:270)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1719)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:1910)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:1758)
> ... 2 more
> {noformat}
> This issue appeared after IGNITE-882 was fixed. Until it wasn't fixed the
> tests hung because of this issue:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: Remote node ID is
> not as expected [expected=9019c94c-84f5-4065-89b1-f16fdf708009,
> rcvd=707ed613-1b65-4771-ac98-5faa6857e007]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeHandshake(TcpCommunicationSpi.java:2203)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2025)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1113) GridCacheAtomicNearOnlyMultiJvmFullApiSelfTest.testEvictExpired fails
[
https://issues.apache.org/jira/browse/IGNITE-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-1113:
-
Labels: Muted_test (was: )
> GridCacheAtomicNearOnlyMultiJvmFullApiSelfTest.testEvictExpired fails
> -
>
> Key: IGNITE-1113
> URL: https://issues.apache.org/jira/browse/IGNITE-1113
> Project: Ignite
> Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Andrey Gura
> Labels: Muted_test
>
> Next tests fail in multi jvm mode:
> GridCacheAtomicNearOnlyMultiJvmFullApiSelfTest.testEvictExpired
> GridCacheAtomicNearOnlyMultiJvmP2PDisabledFullApiSelfTest.testEvictExpired
> Need to investigate.
> Log:
> {noformat}
> /home/ashutak/java/jdk7u75/bin/java
> -agentlib:jdwp=transport=dt_socket,address=127.0.0.1:36703,suspend=y,server=n
> -ea
> -javaagent:/home/ashutak/Programms/idea-IC-139.659.2/plugins/Groovy/lib/agent/gragent.jar
> -Dfile.encoding=UTF-8 -classpath
> /home/ashutak/Programms/idea-IC-139.659.2/lib/idea_rt.jar:/home/ashutak/Programms/idea-IC-139.659.2/plugins/junit/lib/junit-rt.jar:/home/ashutak/java/jdk7u75/jre/lib/management-agent.jar:/home/ashutak/java/jdk7u75/jre/lib/javaws.jar:/home/ashutak/java/jdk7u75/jre/lib/deploy.jar:/home/ashutak/java/jdk7u75/jre/lib/rt.jar:/home/ashutak/java/jdk7u75/jre/lib/jce.jar:/home/ashutak/java/jdk7u75/jre/lib/jsse.jar:/home/ashutak/java/jdk7u75/jre/lib/resources.jar:/home/ashutak/java/jdk7u75/jre/lib/plugin.jar:/home/ashutak/java/jdk7u75/jre/lib/jfxrt.jar:/home/ashutak/java/jdk7u75/jre/lib/jfr.jar:/home/ashutak/java/jdk7u75/jre/lib/charsets.jar:/home/ashutak/java/jdk7u75/jre/lib/ext/zipfs.jar:/home/ashutak/java/jdk7u75/jre/lib/ext/dnsns.jar:/home/ashutak/java/jdk7u75/jre/lib/ext/sunjce_provider.jar:/home/ashutak/java/jdk7u75/jre/lib/ext/sunec.jar:/home/ashutak/java/jdk7u75/jre/lib/ext/localedata.jar:/home/ashutak/java/jdk7u75/jre/lib/ext/sunpkcs11.jar:/home/ashutak/dev/incubator-ignite/modules/core/target/test-classes:/home/ashutak/dev/incubator-ignite/modules/core/target/classes:/home/ashutak/.m2/repository/javax/cache/cache-api/1.0.0/cache-api-1.0.0.jar:/home/ashutak/.m2/repository/mx4j/mx4j-tools/3.0.1/mx4j-tools-3.0.1.jar:/home/ashutak/.m2/repository/commons-dbcp/commons-dbcp/1.4/commons-dbcp-1.4.jar:/home/ashutak/.m2/repository/commons-pool/commons-pool/1.5.4/commons-pool-1.5.4.jar:/home/ashutak/.m2/repository/com/thoughtworks/xstream/xstream/1.4.8/xstream-1.4.8.jar:/home/ashutak/.m2/repository/xmlpull/xmlpull/1.1.3.1/xmlpull-1.1.3.1.jar:/home/ashutak/.m2/repository/xpp3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.jar:/home/ashutak/.m2/repository/commons-cli/commons-cli/1.2/commons-cli-1.2.jar:/home/ashutak/.m2/repository/org/hsqldb/hsqldb/1.8.0.10/hsqldb-1.8.0.10.jar:/home/ashutak/.m2/repository/com/h2database/h2/1.3.175/h2-1.3.175.jar:/home/ashutak/.m2/repository/org/mockito/mockito-all/1.9.5/mockito-all-1.9.5.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-servlets/9.2.11.v20150529/jetty-servlets-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-continuation/9.2.11.v20150529/jetty-continuation-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-http/9.2.11.v20150529/jetty-http-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-util/9.2.11.v20150529/jetty-util-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-io/9.2.11.v20150529/jetty-io-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-webapp/9.2.11.v20150529/jetty-webapp-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-xml/9.2.11.v20150529/jetty-xml-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-servlet/9.2.11.v20150529/jetty-servlet-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-security/9.2.11.v20150529/jetty-security-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-server/9.2.11.v20150529/jetty-server-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar:/home/ashutak/.m2/repository/com/esotericsoftware/kryo/kryo/2.20/kryo-2.20.jar:/home/ashutak/.m2/repository/com/esotericsoftware/reflectasm/reflectasm/1.07/reflectasm-1.07-shaded.jar:/home/ashutak/.m2/repository/org/ow2/asm/asm/4.0/asm-4.0.jar:/home/ashutak/.m2/repository/com/esotericsoftware/minlog/minlog/1.2/minlog-1.2.jar:/home/ashutak/.m2/repository/org/objenesis/objenesis/1.2/objenesis-1.2.jar:/home/ashutak/.m2/repository/c3p0/c3p0/0.9.1/c3p0-0.9.1.jar:/home/ashutak/.m2/repository/com/google/guava/guava/14.0.1/guava-14.0.1.jar:/home/ashutak/.m2/repository/net/sf/json-lib/json-lib/2.4/json-lib-2.4-jdk15.jar:/home/ashutak/.m2/repository/commons-beanutils/commons-beanutils/1.8.0/commons-beanutils-1.8.0.jar
[jira] [Assigned] (IGNITE-1219) Add ssl configuration
[ https://issues.apache.org/jira/browse/IGNITE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-1219: - Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Add ssl configuration > - > > Key: IGNITE-1219 > URL: https://issues.apache.org/jira/browse/IGNITE-1219 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: ignite-1.4 >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov > Fix For: ignite-1.5 > > > We need to add ssl configuration to cluster screen -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-835) IgniteCache.lock is broken for PARTITIONED cache without near cache.
[
https://issues.apache.org/jira/browse/IGNITE-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-835:
Labels: Muted_test (was: )
> IgniteCache.lock is broken for PARTITIONED cache without near cache.
>
>
> Key: IGNITE-835
> URL: https://issues.apache.org/jira/browse/IGNITE-835
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-2
>Reporter: Vladimir Ozerov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Labels: Muted_test
>
> Steps to reproduce:
> 1) Go to GridCacheLockAbstractTest
> 2) Add the test source below.
> 3) Make sure to disable near cache
> (GridCacheLockAbstractTest.cacheConfiguration() ->
> setNearConfiguration(null)).
> 4) Run GridCachePartitionedLockSelfTest.testLockReentrancy() and observe
> assertion failure.
> 5) Enable near cache back and re-run the test. Observe that now it pass.
> {code}
> public void testLockReentrancy() throws Throwable {
> for (int i = 10; i < 100; i++) {
> System.out.println("Key: " + i);
> final int i0 = i;
> final Lock lock = cache1.lock(i);
> lock.lockInterruptibly();
> try {
> final AtomicReference err = new AtomicReference<>();
> Thread t = new Thread(new Runnable() {
> @Override public void run() {
> try {
> assert !lock.tryLock();
> assert !lock.tryLock(100, TimeUnit.MILLISECONDS);
> assert !cache1.lock(i0).tryLock();
> assert !cache1.lock(i0).tryLock(100,
> TimeUnit.MILLISECONDS);
> }
> catch (Throwable e) {
> err.set(e);
> }
> }
> });
> t.start();
> t.join();
> if (err.get() != null)
> throw err.get();
> lock.lock();
> lock.unlock();
> t = new Thread(new Runnable() {
> @Override public void run() {
> try {
> assert !lock.tryLock();
> assert !lock.tryLock(100, TimeUnit.MILLISECONDS);
> assert !cache1.lock(i0).tryLock();
> assert !cache1.lock(i0).tryLock(100,
> TimeUnit.MILLISECONDS);
> }
> catch (Throwable e) {
> err.set(e);
> }
> }
> });
> t.start();
> t.join();
> if (err.get() != null)
> throw err.get();
> }
> finally {
> lock.unlock();
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1219) Add ssl configuration
[ https://issues.apache.org/jira/browse/IGNITE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939588#comment-14939588 ] Vasiliy Sisko edited comment on IGNITE-1219 at 10/1/15 2:26 PM: # Added configuration of SSL trust managers. # Fixed showing of empty properties in java code generation. # Fixed validation of trust configuration selection. was (Author: vsisko): # Added configuration of SSL trust managers. # Fixed showing of empty properties in java code generation. > Add ssl configuration > - > > Key: IGNITE-1219 > URL: https://issues.apache.org/jira/browse/IGNITE-1219 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: ignite-1.4 >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko > Fix For: ignite-1.5 > > > We need to add ssl configuration to cluster screen -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-614) Race in preloading/unswapping
[ https://issues.apache.org/jira/browse/IGNITE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-614: Labels: Muted_test (was: ) > Race in preloading/unswapping > - > > Key: IGNITE-614 > URL: https://issues.apache.org/jira/browse/IGNITE-614 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Semen Boikov >Assignee: Anton Vinogradov >Priority: Critical > Labels: Muted_test > Fix For: ignite-1.5 > > > During unswap entry is removed from swap then unswap listener is notified, > and this logic in preload supply worker: > - register unswap listener > - iterater over heap > - iterate over swap > - remove unswap listener > - iterate over entries recorded by unswap listener > There is a race: entry is removed from unswap, listener is not notified yet, > at this moment supply worker removes unswap listener. > These tests fail from time to time because entry can be missed during > preloading: > GridCacheSwapPreloadSelfTest.testSwapPartitionedMultithreaded > GridCacheSwapPreloadSelfTest.testSwapReplicatedMultithreaded -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-500) GridCacheLoadingConcurrentGridStartTest fails
[ https://issues.apache.org/jira/browse/IGNITE-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-500: Labels: Muted_test user-request (was: user-request) > GridCacheLoadingConcurrentGridStartTest fails > - > > Key: IGNITE-500 > URL: https://issues.apache.org/jira/browse/IGNITE-500 > Project: Ignite > Issue Type: Sub-task >Reporter: Yakov Zhdanov >Assignee: Alexey Goncharuk > Labels: Muted_test, user-request > Fix For: ignite-1.5 > > Attachments: ignite-500.log > > > http://apacheignite.readme.io/v1.0/discuss/550865a8e35e9c3b0083af3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-114) Value is not loaded from store for invoke in transactional cache
[ https://issues.apache.org/jira/browse/IGNITE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-114: Labels: Muted_test (was: ) > Value is not loaded from store for invoke in transactional cache > > > Key: IGNITE-114 > URL: https://issues.apache.org/jira/browse/IGNITE-114 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: sprint-1 >Reporter: Semen Boikov >Assignee: Alexey Goncharuk > Labels: Muted_test > Fix For: ignite-1.5 > > > Added test IgniteCacheInvokeReadThroughTest. Value is not in cache but exists > in store, when invoke EntryProcessor is executed on backup it gets null value > instead of value loaded from store. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1594) Home page for web console
[ https://issues.apache.org/jira/browse/IGNITE-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939884#comment-14939884 ] Vasiliy Sisko commented on IGNITE-1594: --- Changed: # Title of the page shortened, # Description added, # Changed carousel: navigation arrows showed all time, removed gradient for navigation arrows, navigation arrows shifted inside of image and stay on current height for better usability, removed shadows on image description. > Home page for web console > - > > Key: IGNITE-1594 > URL: https://issues.apache.org/jira/browse/IGNITE-1594 > Project: Ignite > Issue Type: Sub-task > Components: UI >Reporter: Dmitriy Setrakyan >Assignee: Vasiliy Sisko > Fix For: ignite-1.5 > > > Home page should look as following: > # Logo with Apache Ignite Web Console up top > # Explanation of what web console is immediately below. > # Login on the left > # screenshots on the right -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1094) Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization
[ https://issues.apache.org/jira/browse/IGNITE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-1094: - Labels: Muted_test (was: ) > Ignite.createCache(CacheConfiguration) hangs if some exception occurs during > cache initialization > - > > Key: IGNITE-1094 > URL: https://issues.apache.org/jira/browse/IGNITE-1094 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: sprint-7 >Reporter: Sergey Evdokimov >Assignee: Alexey Goncharuk > Labels: Muted_test > > User can pass broken configuration, for example, store factory that throws > exception from create() method. I created test to demonstrate the problem. > See IgniteDynamicCacheStartSelfTest#testBrokenStoreFactory in 'ignite-1094' > branch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1088) [Multi jvm] Full api test which test store.
[
https://issues.apache.org/jira/browse/IGNITE-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-1088:
-
Labels: Muted_test (was: )
> [Multi jvm] Full api test which test store.
> ---
>
> Key: IGNITE-1088
> URL: https://issues.apache.org/jira/browse/IGNITE-1088
> Project: Ignite
> Issue Type: Task
>Reporter: Artem Shutak
> Labels: Muted_test
>
> Next tests use a store which actually is {{ConcurrentMap}}. Need to use some
> place for storage which will be available from several jvms (file, db or
> etc.).
> testRemoveAllSkipStore
> testWithSkipStore
> testWithSkipStoreRemoveAll
> See also all tests which use {{putToStore}} method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1393) AssertionError when stop node executing transaction
[
https://issues.apache.org/jira/browse/IGNITE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-1393:
-
Labels: Muted_test (was: )
> AssertionError when stop node executing transaction
> ---
>
> Key: IGNITE-1393
> URL: https://issues.apache.org/jira/browse/IGNITE-1393
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Semen Boikov
> Labels: Muted_test
>
> I fixed GridCacheStopSelfTest which was disabled for long time, now it fails
> because of asserts:
> {noformat}
> [10:53:02,362][ERROR][async-runner-1][GridNearTxLocal] Heuristic transaction
> failure.
> class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Failed to locally write to cache (all transaction entries will be
> invalidated, however there was a window when entries for this transaction
> were visible to others): GridNearTxLocal [nearLocallyMapped=false,
> colocatedLocallyMapped=true, hasRemoteLocks=false,
> mappings=[009f5238-db3d-426f-b787-9a4a156e8000], super=GridDhtTxLocalAdapter
> [dhtThreadId=101, needsCompletedVers=false, nearNodes=[], dhtNodes=[],
> explicitLock=false, super=IgniteTxLocalAdapter [txMap={IgniteTxKey
> [key=KeyCacheObjectImpl [val=22, hasValBytes=true], cacheId=1]=IgniteTxEntry
> [key=KeyCacheObjectImpl [val=22, hasValBytes=true], cacheId=1,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=22, hasValBytes=true],
> cacheId=1], val=[op=CREATE, val=UserCacheObjectImpl [val=22,
> hasValBytes=true]], prevVal=[op=CREATE, val=UserCacheObjectImpl [val=22,
> hasValBytes=true]], entryProcessorsCol=null, entryProcessorCalcVal=null,
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=GridCacheVersion [topVer=53261582, nodeOrderDrId=1,
> globalTime=1441781582327, order=1441781581691], filters=[],
> filtersPassed=false, filtersSet=true, entry=GridDhtColocatedCacheEntry
> [super=GridDhtCacheEntry [rdrs=[], locPart=GridDhtLocalPartition [id=22,
> mapPubSize=1, rmvQueue=GridCircularBuffer [sizeMask=31, idxGen=0],
> state=OWNING, reservations=0, empty=false, createTime=09/09/2015 10:53:02,
> mapPubSize=1], super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [val=22, hasValBytes=true], val=CacheObjectImpl
> [val=22, hasValBytes=true], startVer=1441781581658, ver=GridCacheVersion
> [topVer=53261582, nodeOrderDrId=1, globalTime=1441781582327,
> order=1441781581691], hash=2018242870, extras=null, flags=2,
> prepared=false, locked=true, nodeId=009f5238-db3d-426f-b787-9a4a156e8000,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> xidVer=GridCacheVersion [topVer=53261582, nodeOrderDrId=1,
> globalTime=1441781582217, order=1441781581591]]}, completedBase=null,
> sndTransformedVals=false, super=IgniteTxAdapter [xidVer=GridCacheVersion
> [topVer=53261582, nodeOrderDrId=1, globalTime=1441781582217,
> order=1441781581591], writeVer=GridCacheVersion [topVer=53261582,
> nodeOrderDrId=1, globalTime=1441781582327, order=1441781581691],
> implicit=false, implicitSingle=false, loc=true, threadId=101,
> startTime=1441781582212, nodeId=009f5238-db3d-426f-b787-9a4a156e8000,
> startVer=GridCacheVersion [topVer=53261582, nodeOrderDrId=1,
> globalTime=1441781582218, order=1441781581611], endVer=GridCacheVersion
> [topVer=53261582, nodeOrderDrId=1, globalTime=1441781582336,
> order=1441781581738], isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
> timeout=0, sysInvalidate=false, sys=false, plc=2, commitVer=GridCacheVersion
> [topVer=53261582, nodeOrderDrId=1, globalTime=1441781582217,
> order=1441781581591], finalizing=NONE, preparing=false, state=COMMITTED,
> timedOut=false, topVer=AffinityTopologyVersion [topVer=1, minorTopVer=0],
> duration=138ms, onePhaseCommit=true], size=1]]]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:1036)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.finish(GridNearTxLocal.java:654)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$3.apply(GridNearTxLocal.java:749)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$3.apply(GridNearTxLocal.java:741)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:225)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commitAsync(GridNearTxLocal.java:741)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.commitTxAsync(GridCacheAdapter.java:4024)
>
[jira] [Assigned] (IGNITE-1571) .Net: Improve Guid and DateTime reader/writer interface.
[ https://issues.apache.org/jira/browse/IGNITE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-1571: --- Assignee: Pavel Tupitsyn > .Net: Improve Guid and DateTime reader/writer interface. > > > Key: IGNITE-1571 > URL: https://issues.apache.org/jira/browse/IGNITE-1571 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn >Priority: Critical > Fix For: ignite-1.5 > > > Currently we force user to write Guid and DateTime as nullables. We do this > to be more compatible with Java. > But user is more likely to operate on plain types: Guid, Guid[], DateTime, > DateTime[]. > We need to ass these methods to API, and rename existing ones to > "ReadNullableDateTime", etc.. > Note that while trivial to on writer side, it will be harder to implement for > readers. Currently we lookup by type ID, which will be equal for the type and > it's nullable counterpart. For this reason we probably must lookup by type ID > + type or simply by type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-592) [Test] Null can be erroneously passed to filter in optimistic transaction
[ https://issues.apache.org/jira/browse/IGNITE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-592: Labels: Muted_test (was: failedtest) > [Test] Null can be erroneously passed to filter in optimistic transaction > - > > Key: IGNITE-592 > URL: https://issues.apache.org/jira/browse/IGNITE-592 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > For optimsitic transaction filter is applied in > GridCacheTxLocalAdapter.enlistWrite, and there are two issues: > - when put is started from backup node we pass to filter detached entry > without value, so that GridCacheEntry.peek returns null even if we have value > locally > - when offheap is enabled then entry is unswapped before it is passed to > filter, but there is a race so that another thread can swap it again before > filter is applied > (GridCacheOffHeapMultiThreadedUpdateSelfTest.testPutWithFilterTx) > see GG-8118 > Next test(s) should be unmuted on TC: > GridCacheOffHeapMultiThreadedUpdateSelfTest # testPutTxOptimistic and > testPutxIfAbsentTxOptimistic -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-821) [Test] IgniteCacheExpiryPolicyWithStoreAbstractTest # testReadThrough was disabled
[ https://issues.apache.org/jira/browse/IGNITE-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-821: Labels: Muted_test (was: failedtest) > [Test] IgniteCacheExpiryPolicyWithStoreAbstractTest # testReadThrough was > disabled > -- > > Key: IGNITE-821 > URL: https://issues.apache.org/jira/browse/IGNITE-821 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > IgniteCacheExpiryPolicyWithStoreAbstractTest # testReadThrough was disabled. > It has to be fixed or removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1089) [Multi jvm] Need to rewrite Full Api ttl tests.
[ https://issues.apache.org/jira/browse/IGNITE-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-1089: - Labels: Muted_test (was: ) > [Multi jvm] Need to rewrite Full Api ttl tests. > --- > > Key: IGNITE-1089 > URL: https://issues.apache.org/jira/browse/IGNITE-1089 > Project: Ignite > Issue Type: Task >Reporter: Artem Shutak > Labels: Muted_test > > GridCacheAbstractFullApiSelfTest#checkTtl > and > GridCacheNearOnlyMultiNodeFullApiSelfTest#checkReaderTtl > should be rewritten for multi jvm. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-433) Add async message processing in grid thin client and fix deadlock in TcpRoute
[
https://issues.apache.org/jira/browse/IGNITE-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-433:
Labels: Muted_test (was: )
> Add async message processing in grid thin client and fix deadlock in TcpRoute
> --
>
> Key: IGNITE-433
> URL: https://issues.apache.org/jira/browse/IGNITE-433
> Project: Ignite
> Issue Type: Bug
>Reporter: Yakov Zhdanov
>Priority: Minor
> Labels: Muted_test
>
> # Router receives message from server/client and forwards it to client/server
> in the same thread which is NIO worker thread which wrong (see dumps below)
> # Also need to check if client futures returned to user are completed in NIO
> threads. If so, it is wrong, since listeners will be executed (if any) in the
> same thread which slows down IO.
> # uncomment test {{TcpSslRouterSelfTest}}
> {code}
> [11:50:48]W: [org.apache.ignite:ignite-clients] Thread
> [name="grid-nio-worker-0-#10203%routerClient%", id=102408, state=WAITING,
> blockCnt=2, waitCnt=3]
> [11:50:48]W: [org.apache.ignite:ignite-clients] Lock
> [object=java.util.concurrent.locks.ReentrantLock$NonfairSync@3732762,
> ownerName=grid-nio-worker-1-#10196%router-77155b53-a9a1-44ab-b675-16371b760033%,
> ownerId=102400]
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> sun.misc.Unsafe.park(Native Method)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:867)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:214)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:290)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> o.a.i.i.util.nio.ssl.GridNioSslFilter.onSessionWrite(GridNioSslFilter.java:242)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> o.a.i.i.util.nio.GridNioFilterAdapter.proceedSessionWrite(GridNioFilterAdapter.java:114)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> o.a.i.i.util.nio.GridNioCodecFilter.onSessionWrite(GridNioCodecFilter.java:86)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> o.a.i.i.util.nio.GridNioFilterAdapter.proceedSessionWrite(GridNioFilterAdapter.java:114)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> o.a.i.i.util.nio.GridNioFilterChain$TailFilter.onSessionWrite(GridNioFilterChain.java:259)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> o.a.i.i.util.nio.GridNioFilterChain.onSessionWrite(GridNioFilterChain.java:184)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> o.a.i.i.util.nio.GridNioSessionImpl.send(GridNioSessionImpl.java:102)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> o.a.i.i.client.router.impl.GridTcpRouterNioListenerAdapter$1.onDone(GridTcpRouterNioListenerAdapter.java:111)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> o.a.i.i.client.impl.GridClientFutureAdapter$DoneCallback.proceed(GridClientFutureAdapter.java:291)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> o.a.i.i.client.impl.GridClientFutureAdapter.fireDone(GridClientFutureAdapter.java:244)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> o.a.i.i.client.impl.GridClientFutureAdapter.onDone(GridClientFutureAdapter.java:178)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> o.a.i.i.client.impl.GridClientFutureAdapter.onDone(GridClientFutureAdapter.java:140)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> o.a.i.i.client.impl.connection.GridClientNioTcpConnection.handleResponse(GridClientNioTcpConnection.java:479)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> o.a.i.i.client.impl.connection.GridClientConnectionManagerAdapter$NioListener.onMessage(GridClientConnectionManagerAdapter.java:601)
> [11:50:48]W: [org.apache.ignite:ignite-clients] at
> o.a.i.i.util.nio.GridNioF
[jira] [Updated] (IGNITE-588) [Test] GridCacheAbstractFieldsQuerySelfTest #testComplexKeys and #testNoPrimitives tests fail
[ https://issues.apache.org/jira/browse/IGNITE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-588: Labels: Muted_test (was: failedtest) > [Test] GridCacheAbstractFieldsQuerySelfTest #testComplexKeys and > #testNoPrimitives tests fail > - > > Key: IGNITE-588 > URL: https://issues.apache.org/jira/browse/IGNITE-588 > Project: Ignite > Issue Type: Bug >Affects Versions: sprint-3 >Reporter: Artem Shutak > Labels: Muted_test > > Next tests failed by unknown reason (should be unmuted on TC after fix) > - GridCacheAbstractFieldsQuerySelfTest #testComplexKeys and #testNoPrimitives -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-803) [Test] DataStructures failover tests fail with partitioned cache
[ https://issues.apache.org/jira/browse/IGNITE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-803: Labels: Muted_test (was: failedtest) > [Test] DataStructures failover tests fail with partitioned cache > > > Key: IGNITE-803 > URL: https://issues.apache.org/jira/browse/IGNITE-803 > Project: Ignite > Issue Type: Sub-task > Environment: See GG-2699 >Reporter: Artem Shutak >Assignee: Denis Magda > Labels: Muted_test > > See GG-2699 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-605) [Test] TODO in GridAbstractTest w/ comment "propose another way to avoid network overhead in tests"
[ https://issues.apache.org/jira/browse/IGNITE-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-605: Labels: Muted_test (was: failedtest) > [Test] TODO in GridAbstractTest w/ comment "propose another way to avoid > network overhead in tests" > --- > > Key: IGNITE-605 > URL: https://issues.apache.org/jira/browse/IGNITE-605 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > See GG-4048 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-808) invokeAll fails with ClassCastException on unstable topology
[ https://issues.apache.org/jira/browse/IGNITE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-808: Labels: Muted_test (was: failedtest) > invokeAll fails with ClassCastException on unstable topology > > > Key: IGNITE-808 > URL: https://issues.apache.org/jira/browse/IGNITE-808 > Project: Ignite > Issue Type: Sub-task >Reporter: Artem Shutak >Assignee: Semen Boikov > Labels: Muted_test > Fix For: ignite-1.5 > > > GridReplicatedTxPreloadTest fails. > See gg-7434 already fixed, but tests fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-807) [Test] Need to fix transaction order in topology change self test
[ https://issues.apache.org/jira/browse/IGNITE-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-807: Labels: Muted_test (was: failedtest) > [Test] Need to fix transaction order in topology change self test > - > > Key: IGNITE-807 > URL: https://issues.apache.org/jira/browse/IGNITE-807 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > See test GridCachePartitionedTopologyChangeSelfTest (GG issue is gg-5489). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-584) Need to make sure that scan query returns consistent results on topology changes
[ https://issues.apache.org/jira/browse/IGNITE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-584: Labels: Muted_test (was: failedtest) > Need to make sure that scan query returns consistent results on topology > changes > > > Key: IGNITE-584 > URL: https://issues.apache.org/jira/browse/IGNITE-584 > Project: Ignite > Issue Type: Sub-task >Reporter: Artem Shutak > Labels: Muted_test > > Consistent results on topology changes was implemented for sql queries, but > looks like it still does not work for scan queries. > This affects 'cache set' tests since set uses scan query for set iteration > (to be unmuted on TC): > GridCacheSetAbstractSelfTest testNodeJoinsAndLeaves and > testNodeJoinsAndLeavesCollocated; > Also see todos here GridCacheSetFailoverAbstractSelfTest -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-583) [Test] Need to create test that checks cache queue contents for consistency.
[ https://issues.apache.org/jira/browse/IGNITE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-583: Labels: Muted_test (was: failedtest) > [Test] Need to create test that checks cache queue contents for consistency. > > > Key: IGNITE-583 > URL: https://issues.apache.org/jira/browse/IGNITE-583 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > See SPT-2 support ticket, we need to add test for customer scenario to make > sure queue contents obtained by different methods are consistent across > nodes. > Ask Alexey Zlobin for details. > see GG-4807 > Next test(s) should be unmuted on TC: GridCacheQueueMultiNodeAbstractSelfTest > # testIterator -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-792) [Test] DR: GridDrHandlerFullStateTransferFailoverSelfTest.testFullStateTransferFailureOnReplicationPause hanged.
[ https://issues.apache.org/jira/browse/IGNITE-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-792: Labels: Muted_test (was: failedtest) > [Test] DR: > GridDrHandlerFullStateTransferFailoverSelfTest.testFullStateTransferFailureOnReplicationPause > hanged. > > > Key: IGNITE-792 > URL: https://issues.apache.org/jira/browse/IGNITE-792 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Artem Shutak >Priority: Critical > Labels: Muted_test > Fix For: sprint-5 > > > Root cause: state transfer was not completed during DR stop. > see GG-8010 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-824) [Test] GridRandomSelfTest # testPerformance was disabled.
[ https://issues.apache.org/jira/browse/IGNITE-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-824: Labels: Muted_test (was: failedtest) > [Test] GridRandomSelfTest # testPerformance was disabled. > - > > Key: IGNITE-824 > URL: https://issues.apache.org/jira/browse/IGNITE-824 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > GridRandomSelfTest # testPerformance was disabled. It has to be fixed or > removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-607) [Test] Extra read events and reads in metrics for PARTITIONED_ONLY cache
[
https://issues.apache.org/jira/browse/IGNITE-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-607:
Labels: Muted_test (was: failedtest)
> [Test] Extra read events and reads in metrics for PARTITIONED_ONLY cache
>
>
> Key: IGNITE-607
> URL: https://issues.apache.org/jira/browse/IGNITE-607
> Project: Ignite
> Issue Type: Bug
>Reporter: Artem Shutak
> Labels: Muted_test
>
> See GG-7578.
> Need to check, may be issue have been already fixed, because linked tests
> pass now (failed before):
> - GridCacheEventAbstractTest #testGetPutRemove and #testGetPutRemoveAsync
> ===Origin text===
> To reproduce run GridCachePartitionedMetricsSelfTest and
> GridCachePartitionedEventSelfTest with PARTITIONED_ONLY cache.
> GridCachePartitionedMetricsSelfTest:
> {noformat}
> junit.framework.AssertionFailedError:
> Expected :75
> Actual :150
>
> at
> org.gridgain.grid.kernal.processors.cache.GridCacheAbstractMetricsSelfTest.testMisses(GridCacheAbstractMetricsSelfTest.java:164)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> org.gridgain.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1253)
> at
> org.gridgain.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:60)
> at
> org.gridgain.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1198)
> {noformat}
> GridCachePartitionedEventSelfTest:
> {noformat}
> class org.gridgain.grid.GridException: Wrong event count
> [evtName=CACHE_OBJECT_READ, evtType=64, expCnt=3, actCnt=7, partitioned=true]
> For more information see:
> Troubleshooting: http://bit.ly/GridGain-Troubleshooting
> Documentation Center: http://bit.ly/GridGain-Documentation
> at
> org.gridgain.grid.kernal.processors.cache.distributed.GridCacheEventAbstractTest$EventTypeFuture.onEvent(GridCacheEventAbstractTest.java:942)
> at
> org.gridgain.grid.kernal.processors.cache.distributed.GridCacheEventAbstractTest$TestEventListener.waitForEventCount(GridCacheEventAbstractTest.java:863)
> at
> org.gridgain.grid.kernal.processors.cache.distributed.GridCacheEventAbstractTest$TestEventListener.access$300(GridCacheEventAbstractTest.java:759)
> at
> org.gridgain.grid.kernal.processors.cache.distributed.GridCacheEventAbstractTest.waitForEvents(GridCacheEventAbstractTest.java:109)
> at
> org.gridgain.grid.kernal.processors.cache.distributed.GridCacheEventAbstractTest.runTest(GridCacheEventAbstractTest.java:165)
> at
> org.gridgain.grid.kernal.processors.cache.distributed.GridCacheEventAbstractTest.testGetPutRemove(GridCacheEventAbstractTest.java:224)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-600) [Test] Set remove leaves orphaned set items in cache when topology changes
[ https://issues.apache.org/jira/browse/IGNITE-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-600: Labels: Muted_test (was: failedtest) > [Test] Set remove leaves orphaned set items in cache when topology changes > -- > > Key: IGNITE-600 > URL: https://issues.apache.org/jira/browse/IGNITE-600 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > Now there is a race when remove operation is running before preloading > finished. > See GridCacheSetFailoverAbstractSelfTest # testNodeRestart test when issue > will be fixed (and unmute on TC). > See GG-8962. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-591) [Test] GridCacheJtaSelfTest # testJtaTwoCaches disabled
[ https://issues.apache.org/jira/browse/IGNITE-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-591: Labels: Muted_test (was: failedtest) > [Test] GridCacheJtaSelfTest # testJtaTwoCaches disabled > --- > > Key: IGNITE-591 > URL: https://issues.apache.org/jira/browse/IGNITE-591 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Sergey Evdokimov > Labels: Muted_test > Fix For: sprint-7 > > > see GG-9141 (it had been closed) > Next test(s) should be unmuted on TC: GridCacheJtaSelfTest # testJtaTwoCaches -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-608) [Test] Fix cache with portableEnabled=true
[ https://issues.apache.org/jira/browse/IGNITE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-608: Labels: Muted_test (was: failedtest) > [Test] Fix cache with portableEnabled=true > -- > > Key: IGNITE-608 > URL: https://issues.apache.org/jira/browse/IGNITE-608 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > 1. Portable object must be deserialized before return to user (see cache > 'get' implementation), looks like now it is not implemented for put/remove > return value, peek, reload (need check all cache public API). > 2. Need to make sure that all tests in GridCachePortableEnabledSelfTestSuite > pass (add suite to TC after that). > Comment from GG-8743: > - Fixed all found issues with portables except metadata update inside > explicit transaction. If metadata is updated then method > GridEntPortableProcessor.addMeta is called which can execute 'invoke' on > system cache. For now just changed it to execute invoke in another thread > (using 'CU.outTx'). Is it possible to add internal method to execute 'invoke' > without enlisting system cache in transaction? If this is not easy to add I > think we can leave it as is since metadata update is not expecte to happen > frequently. > See GG-9271 and GG-8743. Also see TODOs in java-code for this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-580) [Test] Grid cannot stop with ongoing cache operations
[ https://issues.apache.org/jira/browse/IGNITE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-580: Labels: Muted_test (was: failedtest) > [Test] Grid cannot stop with ongoing cache operations > - > > Key: IGNITE-580 > URL: https://issues.apache.org/jira/browse/IGNITE-580 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > org.gridgain.grid.kernal.GridStartStopSelfTest#testStopWhileInUse > see GG-7704 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-820) [Test] GridCacheEvictionFilterSelfTest # testPartitionedMixed was disabled
[ https://issues.apache.org/jira/browse/IGNITE-820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-820: Labels: Muted_test (was: failedtest) > [Test] GridCacheEvictionFilterSelfTest # testPartitionedMixed was disabled > -- > > Key: IGNITE-820 > URL: https://issues.apache.org/jira/browse/IGNITE-820 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Andrey Gura > Labels: Muted_test > Fix For: sprint-7 > > > GridCacheEvictionFilterSelfTest # testPartitionedMixed was disabled. It has > to be fixed or removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-603) [Test] GridP2PMissedResourceCacheSizeSelfTest has commented tests
[ https://issues.apache.org/jira/browse/IGNITE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-603: Labels: Muted_test (was: failedtest) > [Test] GridP2PMissedResourceCacheSizeSelfTest has commented tests > - > > Key: IGNITE-603 > URL: https://issues.apache.org/jira/browse/IGNITE-603 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > Test have to be uncommented and fixed or the commented code have to be > removed. > See comments at GG-3804. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-827) [Test] GridCacheCrossCacheQuerySelfTest # testLoop and # testTwoStep were disabled
[ https://issues.apache.org/jira/browse/IGNITE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-827: Labels: Muted_test (was: failedtest) > [Test] GridCacheCrossCacheQuerySelfTest # testLoop and # testTwoStep were > disabled > -- > > Key: IGNITE-827 > URL: https://issues.apache.org/jira/browse/IGNITE-827 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > GridCacheCrossCacheQuerySelfTest # testLoop and # testTwoStep were disabled. > They has to be fixed or removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-810) [Test] GridWebSessionFilter does not retry update when transactional cache is used
[ https://issues.apache.org/jira/browse/IGNITE-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-810: Labels: Muted_test (was: failedtest) > [Test] GridWebSessionFilter does not retry update when transactional cache is > used > -- > > Key: IGNITE-810 > URL: https://issues.apache.org/jira/browse/IGNITE-810 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > When transactional cache is used for web sessions then GridWebSessionFilter > does not retry updates (for atomic cache updates are retried, see > GridWebSessionListener.updateAttributes). > In current implementation we cannot retry transaction since all filter's code > is executed inside transaction (see GridWebSessionFilter.doFilter). > Issue is reproduced by WebSessionTransactionalSelfTest. > See gg-8166. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-582) [Test] Unexpected behavior for OPTIMISTIC SERIALIZABLE transaction
[ https://issues.apache.org/jira/browse/IGNITE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-582: Labels: Muted_test (was: failedtest) > [Test] Unexpected behavior for OPTIMISTIC SERIALIZABLE transaction > -- > > Key: IGNITE-582 > URL: https://issues.apache.org/jira/browse/IGNITE-582 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Alexey Goncharuk >Priority: Blocker > Labels: Muted_test > Fix For: ignite-1.5 > > > Ticket is related to this issue > http://stackoverflow.com/questions/22936749/optimistic-mode-for-gridgain-transactions. > I added more simple test to the GridCacheTxMultiThreadedAbstractTest. > Original test is also attached to the ticket. Sometimes commit fails with > GridCacheTxOptimisticException, but two threads still can commit duplicated > values so that increment is lost. > see GG-8063 > Next test(s) should be unmuted on TC: testOptimisticSerializableConsistency -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-599) [Test] File swap SPI does not support evictions
[ https://issues.apache.org/jira/browse/IGNITE-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-599: Labels: Muted_test (was: failedtest) > [Test] File swap SPI does not support evictions > --- > > Key: IGNITE-599 > URL: https://issues.apache.org/jira/browse/IGNITE-599 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > Please unmute test GridCacheSwapSelfTest.testSwapEviction when fixed. > see GG-7341 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-604) [Test] To create tests which validate exceptions at IpcSharedMemoryUtils.cpp
[
https://issues.apache.org/jira/browse/IGNITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-604:
Labels: Muted_test (was: failedtest)
> [Test] To create tests which validate exceptions at IpcSharedMemoryUtils.cpp
>
>
> Key: IGNITE-604
> URL: https://issues.apache.org/jira/browse/IGNITE-604
> Project: Ignite
> Issue Type: Bug
>Reporter: Artem Shutak
> Labels: Muted_test
>
> Steps to reproduce:
> # Create a local class (or take one from extdata) - the remote nodes
> shouldn't have this class in their classpath - and put some entries with that
> class to REPLICATED cache with several nodes (you can use class instances as
> either keys or values).
> # Stop local node.
> # Increase the user version in META-INF/gridgain.xml.
> # Start a local node an put some more entries with a local class. The current
> entries are not undeployed.
> When local class's code changes, things are even more dramatic: when local
> node with modified class in classpath (and updated user version) joins the
> grid, remote nodes start sending him entries (preloading) with an old class
> version, and the marshaller throws exception due to class bytecode checksum
> mismatch. The fact that user version has changed is completely ignored.
> Reproduced with
> {{GridP2PUserVersionChangeSelfTest.testCacheRedeployVersionChangeContinuousMode()}}
> in the ticket branch.
> See GG-5678. Comment from original issue:
> - Consulted with Yakov. The issue seems complex and will take much effort,
> we've decided to assign it to you for the moment.
> Test have to be unmuted on TC after fix
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-801) [Test] GridCacheReplicatedDataStructuresFailoverSelfTest hangs on TC
[
https://issues.apache.org/jira/browse/IGNITE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-801:
Labels: Muted_test (was: failedtest)
> [Test] GridCacheReplicatedDataStructuresFailoverSelfTest hangs on TC
>
>
> Key: IGNITE-801
> URL: https://issues.apache.org/jira/browse/IGNITE-801
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Artem Shutak
>Assignee: Denis Magda
> Labels: Muted_test
> Fix For: ignite-1.5
>
> Attachments: ignite-801.patch
>
>
> See GG-5306
> http://94.72.60.102/viewLog.html?buildId=113217&buildTypeId=bt6&tab=buildResultsDiv
> {noformat}
> 2013-05-31 10:39:07
> Full thread dump Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode):
> "Attach Listener" daemon prio=10 tid=0x03a94800 nid=0x648 waiting on
> condition [0x]
>java.lang.Thread.State: RUNNABLE
> "tcp-disco-sock-reader-#2408%a940475f-1965-484a-8a43-0a1fcc3bf292" prio=10
> tid=0x7f06f8b1a000 nid=0x42d runnable [0x7f0702d84000]
>java.lang.Thread.State: RUNNABLE
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:150)
> at java.net.SocketInputStream.read(SocketInputStream.java:121)
> at
> org.gridgain.grid.marshaller.jdk.GridJdkMarshallerInputStreamWrapper.read(GridJdkMarshallerInputStreamWrapper.java:47)
> at
> java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2308)
> at
> java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2321)
> at
> java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2792)
> at
> java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:799)
> at java.io.ObjectInputStream.(ObjectInputStream.java:299)
> at
> org.gridgain.grid.marshaller.jdk.GridJdkMarshallerObjectInputStream.(GridJdkMarshallerObjectInputStream.java:30)
> at
> org.gridgain.grid.marshaller.jdk.GridJdkMarshaller.unmarshal(GridJdkMarshaller.java:115)
> at
> org.gridgain.grid.spi.discovery.tcp.GridTcpDiscoverySpi$SocketReader.body(GridTcpDiscoverySpi.java:3985)
> at org.gridgain.grid.spi.GridSpiThread.run(GridSpiThread.java:56)
> "Thread-1905" prio=10 tid=0x7f06f8268000 nid=0x428 waiting on condition
> [0x7f06e1f29000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.gridgain.grid.kernal.GridKernalGatewayImpl.writeLock(GridKernalGatewayImpl.java:89)
> at org.gridgain.grid.kernal.GridKernal.stop0(GridKernal.java:1629)
> - locked <0x00078a53c600> (a
> org.gridgain.grid.util.GridBreaker)
> at org.gridgain.grid.kernal.GridKernal.stop(GridKernal.java:1605)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance.stop0(GridFactory.java:2295)
> - locked <0x00078a473b60> (a
> org.gridgain.grid.GridFactory$GridNamedInstance)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance.stop(GridFactory.java:2256)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance$2.run(GridFactory.java:2223)
> "Thread-1911" prio=10 tid=0x026b1000 nid=0x420 waiting on condition
> [0x7f06e6af4000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.gridgain.grid.kernal.GridKernalGatewayImpl.writeLock(GridKernalGatewayImpl.java:89)
> at org.gridgain.grid.kernal.GridKernal.stop0(GridKernal.java:1629)
> - locked <0x000789b76068> (a
> org.gridgain.grid.util.GridBreaker)
> at org.gridgain.grid.kernal.GridKernal.stop(GridKernal.java:1605)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance.stop0(GridFactory.java:2295)
> - locked <0x00078a4738f8> (a
> org.gridgain.grid.GridFactory$GridNamedInstance)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance.stop(GridFactory.java:2256)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance$2.run(GridFactory.java:2223)
> "SIGTERM handler" daemon prio=10 tid=0x01ec2800 nid=0x41e in
> Object.wait() [0x7f06e8316000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Thread.join(Thread.java:1258)
> - locked <0x00078a473948> (a
> org.gridgain.grid.GridFactory$GridNamedInstance$2)
> at java.lang.Thread.join(Thread.java:1332)
> at
> java.lang.ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:106)
> at
> java.lang.ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:46)
> at java.lang.Shutdown.runHooks(Shutdown.java:123)
> at java.lang.Shutdown.sequence(Shutdown.j
[jira] [Updated] (IGNITE-806) [Test] GridCachePartitionedTxMultiThreadedSelfTest hangs
[ https://issues.apache.org/jira/browse/IGNITE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-806: Labels: Muted_test (was: failedtest) > [Test] GridCachePartitionedTxMultiThreadedSelfTest hangs > > > Key: IGNITE-806 > URL: https://issues.apache.org/jira/browse/IGNITE-806 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > See gg-4066. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-802) [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue
[ https://issues.apache.org/jira/browse/IGNITE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-802: Labels: Muted_test (was: failedtest) > [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue > --- > > Key: IGNITE-802 > URL: https://issues.apache.org/jira/browse/IGNITE-802 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Denis Magda > Labels: Muted_test > Fix For: ignite-1.4 > > Attachments: ignite-802.patch > > > The test had been already fixed (see GG-5620), but it was not uncommented > after. Now it fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-829) [Test] BaseH2CompareQueryTest # testCrossCache was disabled.
[ https://issues.apache.org/jira/browse/IGNITE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-829: Labels: Muted_test (was: failedtest) > [Test] BaseH2CompareQueryTest # testCrossCache was disabled. > > > Key: IGNITE-829 > URL: https://issues.apache.org/jira/browse/IGNITE-829 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Artem Shutak > Labels: Muted_test > > BaseH2CompareQueryTest # testCrossCache was disabled. It has to be fixed or > removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-805) [Test] Need to create multi-threaded tests for full API on GridCache
[ https://issues.apache.org/jira/browse/IGNITE-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-805: Labels: Muted_test (was: failedtest) > [Test] Need to create multi-threaded tests for full API on GridCache > > > Key: IGNITE-805 > URL: https://issues.apache.org/jira/browse/IGNITE-805 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Anton Vinogradov > Labels: Muted_test > > See GG-708 > We have multi-node tesgts, but are there multi-threaded tests? Multi-threaded > tests should be for both, one node and multiple nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-817) [Test] Disabled tests of GridCacheOffHeapTest
[ https://issues.apache.org/jira/browse/IGNITE-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-817: Labels: Muted_test (was: failedtest) > [Test] Disabled tests of GridCacheOffHeapTest > - > > Key: IGNITE-817 > URL: https://issues.apache.org/jira/browse/IGNITE-817 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > GridCacheOffHeapTest had next disabled tests (they have to be fixed or > deleted): > - testOffHeapPartitionedPerformance > - testOffHeapPartitionedPerformanceMultithreaded > - testOffHeapReplicatedPerformance > - testOnHeapPartitionedPerformance > - testOnHeapPartitionedPerformanceMultithreaded > - testOnHeapReplicatedPerformance > - testOnHeapReplicatedPerformanceMultithreaded -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion
[ https://issues.apache.org/jira/browse/IGNITE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-602: Labels: Muted_test (was: failedtest) > [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by > infinite recursion > > > Key: IGNITE-602 > URL: https://issues.apache.org/jira/browse/IGNITE-602 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > See test > org.gridgain.grid.util.tostring.GridToStringBuilderSelfTest#_testToStringCheckAdvancedRecursionPrevention > and related TODO in same source file. > Also take a look at > http://stackoverflow.com/questions/11300203/most-efficient-way-to-prevent-an-infinite-recursion-in-tostring > Test should be unmuted on TC after fix. > see GG-5000. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-606) [Test] Need to fix iterators for GridConcurrentLinkedHashMap in perSegment mode
[ https://issues.apache.org/jira/browse/IGNITE-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-606: Labels: Muted_test (was: failedtest) > [Test] Need to fix iterators for GridConcurrentLinkedHashMap in perSegment > mode > --- > > Key: IGNITE-606 > URL: https://issues.apache.org/jira/browse/IGNITE-606 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > Fix and uncomment test: > GridConcurrentLinkedHashMapMultiThreadedSelfTest.testEvictPerSegment() > Remove all TODOs: > Fix all toString() methods: > * GridBoundedConcurrentLinkedHashMap > * GridBoundedConcurrentLinkedHashSet > * GridConcurrentLinkedHashMap > * GridConcurrentLinkedHashSet > See GG-4788. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-823) [Test] GridUnsafeMemorySelfTest # testGuardedOpsPerformance was disabled.
[ https://issues.apache.org/jira/browse/IGNITE-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-823: Labels: Muted_test (was: failedtest) > [Test] GridUnsafeMemorySelfTest # testGuardedOpsPerformance was disabled. > - > > Key: IGNITE-823 > URL: https://issues.apache.org/jira/browse/IGNITE-823 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > GridUnsafeMemorySelfTest # testGuardedOpsPerformance was disabled. It has to > be fixed or removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-581) [Test] Need to make sure that value is not sent from primary node to client node for implicit transform() calls
[ https://issues.apache.org/jira/browse/IGNITE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-581: Labels: Muted_test (was: failedtest) > [Test] Need to make sure that value is not sent from primary node to client > node for implicit transform() calls > --- > > Key: IGNITE-581 > URL: https://issues.apache.org/jira/browse/IGNITE-581 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > When transform(All) is called outside of explicit transaction we should not > send previous value in lock response to originating node. > see gg-8273 > Next tests have to be unmuted on TC: GridCacheReturnValueTransferSelfTest # > testTransformTransactionalNoBackups and testTransformTransactionalOneBackup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-590) [Test] Idle check probably missbehaves in java client
[ https://issues.apache.org/jira/browse/IGNITE-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-590: Labels: Muted_test (was: failedtest) > [Test] Idle check probably missbehaves in java client > - > > Key: IGNITE-590 > URL: https://issues.apache.org/jira/browse/IGNITE-590 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > It looks like idle check only happens when a new connection is requested by > user. So old idle connections is closed and a new one created immediately > after it. We need to write tests for idle connection close behavior and fix > it if needed. > see GG-3789 > Next test(s) should be unmuted on TC: ClientReconnectionSelfTest # > testIdleConnection -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-585) [Test] Need to test and fix continuous processor on discovery data exchange with P2P deployment
[ https://issues.apache.org/jira/browse/IGNITE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-585: Labels: Muted_test (was: failedtest) > [Test] Need to test and fix continuous processor on discovery data exchange > with P2P deployment > --- > > Key: IGNITE-585 > URL: https://issues.apache.org/jira/browse/IGNITE-585 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > see GG-6730 > Next test(s) should be unmuted on TC: GridEventConsumeSelfTest # > testNodeJoinWithP2P -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-825) [Test] HadoopIgfs20FileSystemAbstractSelfTest # testRenameDirectoryIfDstPathExists was disabled.
[ https://issues.apache.org/jira/browse/IGNITE-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-825: Labels: Muted_test (was: failedtest) > [Test] HadoopIgfs20FileSystemAbstractSelfTest # > testRenameDirectoryIfDstPathExists was disabled. > > > Key: IGNITE-825 > URL: https://issues.apache.org/jira/browse/IGNITE-825 > Project: Ignite > Issue Type: Bug > Components: hadoop >Reporter: Artem Shutak >Assignee: Ivan Veselovsky > Labels: Muted_test > Fix For: ignite-1.5 > > > HadoopIgfs20FileSystemAbstractSelfTest # testRenameDirectoryIfDstPathExists > was disabled. It has to be fixed or removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-613) [Test] IgniteCacheReplicatedQuerySelfTest # testNodeLeft fails
[ https://issues.apache.org/jira/browse/IGNITE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-613: Labels: Muted_test (was: failedtest) > [Test] IgniteCacheReplicatedQuerySelfTest # testNodeLeft fails > -- > > Key: IGNITE-613 > URL: https://issues.apache.org/jira/browse/IGNITE-613 > Project: Ignite > Issue Type: Bug >Affects Versions: ignite-1.4 >Reporter: Artem Shutak >Assignee: Sergi Vladykin >Priority: Critical > Labels: Muted_test > Attachments: ignite-613.patch > > > IgniteCacheReplicatedQuerySelfTest #testNodeLeft test fails by unknown > reason (should be unmuted on TC after fix). > Test works long and fails after. Should be enabled after fix. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-819) [Test] GridCachePartitionedNearDisabledMetricsSelfTest # testGettingRemovedKey was disabled
[ https://issues.apache.org/jira/browse/IGNITE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-819: Labels: Muted_test (was: failedtest) > [Test] GridCachePartitionedNearDisabledMetricsSelfTest # > testGettingRemovedKey was disabled > --- > > Key: IGNITE-819 > URL: https://issues.apache.org/jira/browse/IGNITE-819 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > GridCachePartitionedNearDisabledMetricsSelfTest # testGettingRemovedKey was > disabled. It has to be fixed or removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-804) [Test] Synchronous evicts may cause a deadlock
[
https://issues.apache.org/jira/browse/IGNITE-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-804:
Labels: Muted_test (was: failedtest)
> [Test] Synchronous evicts may cause a deadlock
> --
>
> Key: IGNITE-804
> URL: https://issues.apache.org/jira/browse/IGNITE-804
> Project: Ignite
> Issue Type: Bug
>Reporter: Artem Shutak
> Labels: Muted_test
>
> See gg-5276
> {noformat}
> [20:22:49,442][INFO ][start-stop-thread-1][GridDataLoaderProcessorSelfTest]
> >>> Started node: 2ed6cd2e-f581-4831-81e5-7e8063e020c4
> java.lang.Exception:
> <20:22:49,911>
> >>>
> at org.gridgain.grid.util.GridUtils.dumpStack(GridUtils.java:661)
> at
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.wLock(GridDhtPartitionTopologyImpl.java:179)
> at
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.onEvicted(GridDhtPartitionTopologyImpl.java:1105)
> at
> org.gridgain.grid.kernal.processors.cache.distributed.dht.preloader.GridDhtPreloader.onPartitionEvicted(GridDhtPreloader.java:475)
> at
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtLocalPartition.tryEvict(GridDhtLocalPartition.java:393)
> at
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtLocalPartition.onRemoved(GridDhtLocalPartition.java:188)
> at
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.onRemoved(GridDhtPartitionTopologyImpl.java:567)
> at
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtCacheEntry.onMarkedObsolete(GridDhtCacheEntry.java:97)
> at
> org.gridgain.grid.kernal.processors.cache.GridCacheMapEntry.evictInternal(GridCacheMapEntry.java:2187)
> at
> org.gridgain.grid.kernal.processors.cache.GridCacheEvictionManager.evict0(GridCacheEvictionManager.java:693)
> at
> org.gridgain.grid.kernal.processors.cache.GridCacheEvictionManager.access$2200(GridCacheEvictionManager.java:49)
> at
> org.gridgain.grid.kernal.processors.cache.GridCacheEvictionManager$EvictionFuture.prepare0(GridCacheEvictionManager.java:1678)
> at
> org.gridgain.grid.kernal.processors.cache.GridCacheEvictionManager$EvictionFuture.prepare(GridCacheEvictionManager.java:1591)
> at
> org.gridgain.grid.kernal.processors.cache.GridCacheEvictionManager.addToCurrentFuture(GridCacheEvictionManager.java:1052)
> at
> org.gridgain.grid.kernal.processors.cache.GridCacheEvictionManager.checkEvictionQueue(GridCacheEvictionManager.java:1008)
> at
> org.gridgain.grid.kernal.processors.cache.GridCacheEvictionManager.unwind(GridCacheEvictionManager.java:1278)
> at
> org.gridgain.grid.kernal.processors.cache.GridCacheUtils.unwindEvicts(GridCacheUtils.java:1402)
> at
> org.gridgain.grid.kernal.processors.cache.GridCacheIoManager.processUnordered(GridCacheIoManager.java:210)
> at
> org.gridgain.grid.kernal.processors.cache.GridCacheIoManager.access$500(GridCacheIoManager.java:35)
> at
> org.gridgain.grid.kernal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:113)
> at
> org.gridgain.grid.kernal.managers.communication.GridIoManager$GridFilteredMessageListener.onMessage(GridIoManager.java:1612)
> at
> org.gridgain.grid.kernal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:675)
> at
> org.gridgain.grid.kernal.managers.communication.GridIoManager.access$1900(GridIoManager.java:50)
> at
> org.gridgain.grid.kernal.managers.communication.GridIoManager$6.body(GridIoManager.java:636)
> at org.gridgain.grid.util.worker.GridWorker.run(GridWorker.java:139)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> {noformat}
> To debug this, I have added a check before write lock acquisition:
> {noformat}
> private void wLock() {
> int cnt0 = cnt.get();
> if (cnt0 > 0)
> U.dumpStack(">>>");
> lock.writeLock().lock();
> }
> {noformat}
> cnt here is a thread local that holds count of read locks hold by current
> thread.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-826) [Test] HadoopHashMapSelfTest # testAllocation was disabled.
[ https://issues.apache.org/jira/browse/IGNITE-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-826: Labels: Muted_test (was: failedtest) > [Test] HadoopHashMapSelfTest # testAllocation was disabled. > --- > > Key: IGNITE-826 > URL: https://issues.apache.org/jira/browse/IGNITE-826 > Project: Ignite > Issue Type: Bug > Components: hadoop >Reporter: Artem Shutak > Labels: Muted_test > > HadoopHashMapSelfTest # testAllocation was disabled. It has to be fixed or > removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-601) IgniteCache.isLocalLocked is broken
[ https://issues.apache.org/jira/browse/IGNITE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-601: Labels: Muted_test (was: failedtest) > IgniteCache.isLocalLocked is broken > --- > > Key: IGNITE-601 > URL: https://issues.apache.org/jira/browse/IGNITE-601 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Semen Boikov > Labels: Muted_test > > To reproduce change GridCachePartitionedBasicApiTest to use PARTITIONED_ONLY > cache instead of NEAR_PARTITIONED. > See GG-7437. Comments from origin Jira: > - Fixed in gg-7434-1 > - Reopening since there are left TODOs in data grid test suite. > Now, see GridCacheReplicatedNearOnlyMultiNodeFullApiSelfTest # lockingEnabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1463) GridCacheClientNodePortableMetadataMultinodeTest.testFailoverOnStart fails on TC
[ https://issues.apache.org/jira/browse/IGNITE-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-1463: - Labels: Muted_test (was: failedtest) > GridCacheClientNodePortableMetadataMultinodeTest.testFailoverOnStart fails on > TC > > > Key: IGNITE-1463 > URL: https://issues.apache.org/jira/browse/IGNITE-1463 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Semen Boikov > Labels: Muted_test > > Test GridCacheClientNodePortableMetadataMultinodeTest.testFailoverOnStart > sometimes fails on TC. For some reason client node does not load all expected > portable metadata. > http://94.72.60.102/viewLog.html?buildId=535726&tab=buildResultsDiv&buildTypeId=Ignite_IgnitePortablesBasic -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-822) [Test] IgfsModesSelfTest # testPropagationDualAsync was disabled
[ https://issues.apache.org/jira/browse/IGNITE-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-822: Labels: Muted_test (was: failedtest) > [Test] IgfsModesSelfTest # testPropagationDualAsync was disabled > > > Key: IGNITE-822 > URL: https://issues.apache.org/jira/browse/IGNITE-822 > Project: Ignite > Issue Type: Bug > Components: hadoop >Reporter: Artem Shutak > Labels: Muted_test > > IgfsModesSelfTest # testPropagationDualAsync was disabled. It has to be fixed > or removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-818) [Test] GridSuppressedExceptionSelfTest # testStackTrace was disabled
[ https://issues.apache.org/jira/browse/IGNITE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-818: Labels: Muted_test (was: failedtest) > [Test] GridSuppressedExceptionSelfTest # testStackTrace was disabled > > > Key: IGNITE-818 > URL: https://issues.apache.org/jira/browse/IGNITE-818 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: Muted_test > > GridSuppressedExceptionSelfTest # testStackTrace was disabled. It has to be > fixed or deleted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
