August 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3390) SingleFileCacheStore.start() fails if cache name contains File.separator

by Paul Ferraro (JIRA)

Paul Ferraro created ISPN-3390: ---------------------------------- Summary: SingleFileCacheStore.start() fails if cache name contains File.separator Key: ISPN-3390 URL: https://issues.jboss.org/browse/ISPN-3390 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 6.0.0.Alpha1 Reporter: Paul Ferraro Assignee: Paul Ferraro Using the old FileCacheStore, if the cache name contained File.separator, then the location of the file cache store included corresponding subdirectories. e.g. If my cache name is "myhost/mydeployment.war", then the file cache store includes a subdirectory "myhost". In the new SingleFileCacheStore implementation, however, start() fails because only the directories contained within the location are created. When the File object is constructed using the cache name, if the cache name contains a File.separator, those subdirectories are *not* created, and start() fails with the following message: "Directory ... does not exist and cannot be created!" As I see it, this can be fixed in 1 of 2 ways: 1. Escape any file separators in the cache name when constructing the file name 2. Create the necessary subdirectories on the File object created using the cache name -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3366) Data loss when entry forwarding to primary owner and primary owner shutdown

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-3366?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-3366: ----------------------------------- I have a test-case in library mode (ispn 5.2.4) showing this bug - 4 nodes up, 3 of them loading data (100000 entries in total) via normal PUT operations. During the loading one of the nodes is restarted. If the put operation on some of the loading nodes gets exception, the put is repeated, but even with that in the end I end up with few keys returning null on one of the nodes. [~dan.berindei]: please let me know as you'll have some fix for this issue, I'll try to test it. > Data loss when entry forwarding to primary owner and primary owner shutdown > --------------------------------------------------------------------------- > > Key: ISPN-3366 > URL: https://issues.jboss.org/browse/ISPN-3366 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.4.Final, 6.0.0.Alpha1 > Reporter: Takayoshi Kimura > Assignee: Dan Berindei > Priority: Critical > Attachments: ISPN-3366-logs.zip > > > Looks like a problem in entry forwarding. > Here is test scenario: > * DIST numOwners=2, start with 4 nodes cluster then normal shutdown 1 node during load > * HotRod putIfAbsent accesses from 40 threads (1 process, 1 remote cache instance), 40000 entries total > After the test run, the numberOfEntries on each node are: > * node1: 26608 > * node2: 26622 > * node3: 26746 > * node4: 0 > Total is 79976 and HotRod client received 11 errors, so 79976 + (11 * 2) = 79998. It means 1 entry is completely missing. > Let's take a look at the missing entry, hash(thread16key59) = 574ff563. > Current CH: owners(574ff563) are [node4, node1] > The events sequence is: > * hotrod -> node1 > * node1 forwarding it to primary owner node4 > * node4 doesn't process the forwarded entry, shutdown > Result owners(7c29bccb) is [] empty. This entry is completely lost without any errors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3333) Implement the new Query DSL in embedded mode

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3333?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-3333: ------------------------------------- Some features not implemented yet because they depend on missing features in hibernate-hql-parser: https://hibernate.atlassian.net/browse/HQLPARSER-17 > Implement the new Query DSL in embedded mode > -------------------------------------------- > > Key: ISPN-3333 > URL: https://issues.jboss.org/browse/ISPN-3333 > Project: Infinispan > Issue Type: Sub-task > Components: Querying > Reporter: Mircea Markus > Assignee: Adrian Nistor > Priority: Blocker > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > The output of this: all the sample queries defined in the DSL[1] should be runnable(unit test). > [1] https://github.com/anistor/infinispan/blob/t_3169_m/query/src/main/java/o... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3169) Define a Query API that will be common for library mode + remote

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3169?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3169: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1994 > Define a Query API that will be common for library mode + remote > ---------------------------------------------------------------- > > Key: ISPN-3169 > URL: https://issues.jboss.org/browse/ISPN-3169 > Project: Infinispan > Issue Type: Sub-task > Reporter: Mircea Markus > Assignee: Adrian Nistor > Priority: Blocker > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > Some notes on the query API: > - fluent, supporting a predefined set of filters (equality, range, etc). No user pluggable filter will be supported as this API will be available both embedded and *remotely* by the Java HR client > - the filters accept the schema(protobuf) primitive types as arguments (int, string, byte, etc..) > - should support paging: start page + pageSize > - projections are not supported > For an overview on the remote query design refer to: https://community.jboss.org/wiki/QueryingDesignInInfinispan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3333) Implement the new Query DSL in embedded mode

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3333?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3333: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/1994 > Implement the new Query DSL in embedded mode > -------------------------------------------- > > Key: ISPN-3333 > URL: https://issues.jboss.org/browse/ISPN-3333 > Project: Infinispan > Issue Type: Sub-task > Components: Querying > Reporter: Mircea Markus > Assignee: Adrian Nistor > Priority: Blocker > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > The output of this: all the sample queries defined in the DSL[1] should be runnable(unit test). > [1] https://github.com/anistor/infinispan/blob/t_3169_m/query/src/main/java/o... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3276) Remove usages of CacheLoaderConfig

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3276?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3276: ---------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/infinispan/infinispan/pull/1993, https://github.com/infinispan/infinispan-server/pull/128 (was: https://github.com/infinispan/infinispan/pull/1993) > Remove usages of CacheLoaderConfig > ---------------------------------- > > Key: ISPN-3276 > URL: https://issues.jboss.org/browse/ISPN-3276 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 6.0.0.Alpha1 > Reporter: Navin Surtani > Assignee: Navin Surtani > > As part of the Configuration migration, we need to remove all usages of CacheLoaderConfig and change them to CacheLoaderConfiguration usages. > This will involve making changes to how implementations of org.infinispan.loaders.CacheLoader work along with their respective constructors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3322) Use UNICAST3

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3322?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3322: ------------------------------- Issue Type: Task (was: Enhancement) Assignee: Mircea Markus Fix Version/s: 6.0.0.Alpha3 Affects Version/s: 6.0.0.Alpha1 5.3.0.Final One more reason for the upgrade: JGRP-1658 is already fixed for UNICAST3, but the fix won't be backported to UNICAST2. > Use UNICAST3 > ------------ > > Key: ISPN-3322 > URL: https://issues.jboss.org/browse/ISPN-3322 > Project: Infinispan > Issue Type: Task > Components: RPC > Affects Versions: 5.3.0.Final, 6.0.0.Alpha1 > Reporter: Sanne Grinovero > Assignee: Mircea Markus > Fix For: 6.0.0.Alpha3 > > > As suggested by Bela: it seems UNICAST3 is generally better than previous versions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3366) Data loss when entry forwarding to primary owner and primary owner shutdown

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3366?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-3366: --------------------------------------- [~nekop], you can get strictPeerToPeer working modifying the infinispan-defaults.xml within the infinispan subsystem jar (org.jboss.as.clustering.infinispan) > Data loss when entry forwarding to primary owner and primary owner shutdown > --------------------------------------------------------------------------- > > Key: ISPN-3366 > URL: https://issues.jboss.org/browse/ISPN-3366 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.4.Final, 6.0.0.Alpha1 > Reporter: Takayoshi Kimura > Assignee: Dan Berindei > Priority: Critical > Attachments: ISPN-3366-logs.zip > > > Looks like a problem in entry forwarding. > Here is test scenario: > * DIST numOwners=2, start with 4 nodes cluster then normal shutdown 1 node during load > * HotRod putIfAbsent accesses from 40 threads (1 process, 1 remote cache instance), 40000 entries total > After the test run, the numberOfEntries on each node are: > * node1: 26608 > * node2: 26622 > * node3: 26746 > * node4: 0 > Total is 79976 and HotRod client received 11 errors, so 79976 + (11 * 2) = 79998. It means 1 entry is completely missing. > Let's take a look at the missing entry, hash(thread16key59) = 574ff563. > Current CH: owners(574ff563) are [node4, node1] > The events sequence is: > * hotrod -> node1 > * node1 forwarding it to primary owner node4 > * node4 doesn't process the forwarded entry, shutdown > Result owners(7c29bccb) is [] empty. This entry is completely lost without any errors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3366) Data loss when entry forwarding to primary owner and primary owner shutdown

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3366?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3366: ---------------------------------- Description: Looks like a problem in entry forwarding. Here is test scenario: * DIST numOwners=2, start with 4 nodes cluster then normal shutdown 1 node during load * HotRod putIfAbsent accesses from 40 threads (1 process, 1 remote cache instance), 40000 entries total After the test run, the numberOfEntries on each node are: * node1: 26608 * node2: 26622 * node3: 26746 * node4: 0 Total is 79976 and HotRod client received 11 errors, so 79976 + (11 * 2) = 79998. It means 1 entry is completely missing. Let's take a look at the missing entry, hash(thread16key59) = 574ff563. Current CH: owners(574ff563) are [node4, node1] The events sequence is: * hotrod -> node1 * node1 forwarding it to primary owner node4 * node4 doesn't process the forwarded entry, shutdown Result owners(7c29bccb) is [] empty. This entry is completely lost without any errors. was: Looks like a problem in entry forwarding. Here is test scenario: * DIST numOwners=2, start with 4 nodes cluster then normal shutdown 1 node during load * HotRod putIfAbsent accesses from 40 threads (1 process, 1 remote cache instance), 40000 entries total After the test run, the numberOfEntries on each node are: * node1: 26608 * node2: 26622 * node3: 26746 * node4: 0 Total is 79976 and HotRod client received 11 errors, so 79976 + (11 * 2) = 79998. It means 1 entry is completely missing. Let's take a look at the missing entry, hash(thread16key59) = 574ff563. Current CH: owners(574ff563) are [node4, node1] The events sequence is: * hotrod -> node1 * node1 forwarding it to primary owner node4 * node4 doesn't process the forwarded entry, shutdown Result owners(7c29bccb) is [] empty. This entry is completely lost without any errors. > Data loss when entry forwarding to primary owner and primary owner shutdown > --------------------------------------------------------------------------- > > Key: ISPN-3366 > URL: https://issues.jboss.org/browse/ISPN-3366 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.4.Final, 6.0.0.Alpha1 > Reporter: Takayoshi Kimura > Assignee: Dan Berindei > Priority: Critical > Attachments: ISPN-3366-logs.zip > > > Looks like a problem in entry forwarding. > Here is test scenario: > * DIST numOwners=2, start with 4 nodes cluster then normal shutdown 1 node during load > * HotRod putIfAbsent accesses from 40 threads (1 process, 1 remote cache instance), 40000 entries total > After the test run, the numberOfEntries on each node are: > * node1: 26608 > * node2: 26622 > * node3: 26746 > * node4: 0 > Total is 79976 and HotRod client received 11 errors, so 79976 + (11 * 2) = 79998. It means 1 entry is completely missing. > Let's take a look at the missing entry, hash(thread16key59) = 574ff563. > Current CH: owners(574ff563) are [node4, node1] > The events sequence is: > * hotrod -> node1 > * node1 forwarding it to primary owner node4 > * node4 doesn't process the forwarded entry, shutdown > Result owners(7c29bccb) is [] empty. This entry is completely lost without any errors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3373) HotRod topology cache should allow disabling awaitInitialTransfer

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3373?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3373: ---------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/1991, https://github.com/infinispan/infinispan-server/pull/126, https://github.com/infinispan/infinispan-server/pull/127 (was: https://github.com/infinispan/infinispan/pull/1991, https://github.com/infinispan/infinispan-server/pull/126) > HotRod topology cache should allow disabling awaitInitialTransfer > ----------------------------------------------------------------- > > Key: ISPN-3373 > URL: https://issues.jboss.org/browse/ISPN-3373 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols, Server > Affects Versions: 6.0.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha2 > > > When a server with a hotrod endpoint joins a cluster where state transfer has been disabled (ISPN-3140), waiting for initial state transfer should also be disabled on the topology cache, otherwise failures occur. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2013