October 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4906) Test subject externalizers in clustered mode

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-4906?page=com.atlassian.jira.plugin.... ] Vojtech Juranek commented on ISPN-4906: --------------------------------------- related commit: https://github.com/infinispan/infinispan/commit/0cef39de7b75ec6d408b4745f... > Test subject externalizers in clustered mode > -------------------------------------------- > > Key: ISPN-4906 > URL: https://issues.jboss.org/browse/ISPN-4906 > Project: Infinispan > Issue Type: Feature Request > Components: Test Suite - Server > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > Verify that authorization mask is properly transferred between the node, i.e. subject externalizers work. > The test scenario could be as follows: > 1. start HR server, 2. client authenticates itself to the server, 3. another server joins the cluster, 4. the first server is turned off, 5. HR client authenticate to the second server 6. verify HR client is properly authorized on second server. > Should be done for different subjects to verify different subject externalizers. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4906) Test subject externalizers in clustered mode

by Vojtech Juranek (JIRA)

Vojtech Juranek created ISPN-4906: ------------------------------------- Summary: Test subject externalizers in clustered mode Key: ISPN-4906 URL: https://issues.jboss.org/browse/ISPN-4906 Project: Infinispan Issue Type: Feature Request Components: Test Suite - Server Reporter: Vojtech Juranek Assignee: Vojtech Juranek Verify that authorization mask is properly transferred between the node, i.e. subject externalizers work. The test scenario could be as follows: 1. start HR server, 2. client authenticates itself to the server, 3. another server joins the cluster, 4. the first server is turned off, 5. HR client authenticate to the second server 6. verify HR client is properly authorized on second server. Should be done for different subjects to verify different subject externalizers. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4850) Allow for filter and conversion to be done in one step for cache listeners

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4850?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4850: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1154044|https://bugzilla.redhat.com/show_bug.cgi?id=1154044] from NEW to MODIFIED > Allow for filter and conversion to be done in one step for cache listeners > -------------------------------------------------------------------------- > > Key: ISPN-4850 > URL: https://issues.jboss.org/browse/ISPN-4850 > Project: Infinispan > Issue Type: Enhancement > Components: Listeners > Affects Versions: 7.0.0.CR1 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Final > > > Currently the cache listeners can install a CacheEventFilter and CacheEventConverter to be used. However each one requires separate invocations. It would be desireable to have this done as a single invocation akin to what we did for ISPN-4640. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3701) In HotRod client topologyId is shared for all caches

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3701?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3701: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1029615|https://bugzilla.redhat.com/show_bug.cgi?id=1029615] from ASSIGNED to MODIFIED > In HotRod client topologyId is shared for all caches > ---------------------------------------------------- > > Key: ISPN-3701 > URL: https://issues.jboss.org/browse/ISPN-3701 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 6.0.0.CR1 > Reporter: Radim Vansa > Assignee: Galder Zamarreño > > The AtomicInteger with topologyId is stored in RemoteCacheManager, therefore, shared for all caches. This can lead to performance problems when accessing two caches with non-synchronized topology ids. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3530) The HotRod client should support a separate CH for each cache

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3530?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3530: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1029615|https://bugzilla.redhat.com/show_bug.cgi?id=1029615] from ASSIGNED to MODIFIED > The HotRod client should support a separate CH for each cache > ------------------------------------------------------------- > > Key: ISPN-3530 > URL: https://issues.jboss.org/browse/ISPN-3530 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Affects Versions: 6.0.0.Alpha4 > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Labels: hotrod, hotrod-java-client > Fix For: 7.0.0.Alpha5 > > > With asymmetric clusters, each cache can have its own consistent hash, so the primary owner of a key in one cache is not necessarily the owner in all the caches. Even with a symmetric cluster, the same client may be used to access both distributed and replicated caches, and those would certainly have a different CH. > In order to send the operations to the correct owner, the HotRod client should use a different CH for each cache. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4882) HotRod authentication fails with an authorization-enabled clustered container

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4882?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4882: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1156318|https://bugzilla.redhat.com/show_bug.cgi?id=1156318] from POST to MODIFIED > HotRod authentication fails with an authorization-enabled clustered container > ----------------------------------------------------------------------------- > > Key: ISPN-4882 > URL: https://issues.jboss.org/browse/ISPN-4882 > Project: Infinispan > Issue Type: Feature Request > Components: Security, Server > Affects Versions: 7.0.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Blocker > Fix For: 7.0.0.Final > > > If authorization is enabled on a clustered container, the hotrod server silently fails when attempting to retrieve the topology information without using a privileged action. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4874) Cross-site replication - allow defining custom backup cache name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4874?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4874: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1156088|https://bugzilla.redhat.com/show_bug.cgi?id=1156088] from POST to MODIFIED > Cross-site replication - allow defining custom backup cache name > ---------------------------------------------------------------- > > Key: ISPN-4874 > URL: https://issues.jboss.org/browse/ISPN-4874 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication, Server > Affects Versions: 7.0.0.CR2 > Reporter: Matej Čimbora > Assignee: Pedro Ruivo > Fix For: 7.0.0.Final > > > Using client-server mode, it's currently not possible to specify custom name for backup cache (different from the name of the main cache), as "backup-for" setting is missing. The issue can be workarounded by using the same name for the main & backup cache. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4882) HotRod authentication fails with an authorization-enabled clustered container

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4882?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4882: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1158121|https://bugzilla.redhat.com/show_bug.cgi?id=1158121] from POST to MODIFIED > HotRod authentication fails with an authorization-enabled clustered container > ----------------------------------------------------------------------------- > > Key: ISPN-4882 > URL: https://issues.jboss.org/browse/ISPN-4882 > Project: Infinispan > Issue Type: Feature Request > Components: Security, Server > Affects Versions: 7.0.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Blocker > Fix For: 7.0.0.Final > > > If authorization is enabled on a clustered container, the hotrod server silently fails when attempting to retrieve the topology information without using a privileged action. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4166) useSynchronization should be disabled by default

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4166?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-4166: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > useSynchronization should be disabled by default > ------------------------------------------------ > > Key: ISPN-4166 > URL: https://issues.jboss.org/browse/ISPN-4166 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration, Transactions > Affects Versions: 6.0.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.0.0.Final > > > When Infinispan registers with the transaction manager as a synchronization, failures during commit are not reported to the user. > Even if registering as a synchronization is faster in some cases, the default should be the safe version. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4890) Entry iterator should throw AvailabilityException in degraded mode

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4890?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-4890: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3014 > Entry iterator should throw AvailabilityException in degraded mode > ------------------------------------------------------------------ > > Key: ISPN-4890 > URL: https://issues.jboss.org/browse/ISPN-4890 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite - Core > Affects Versions: 7.0.0.CR2 > Reporter: Dan Berindei > Assignee: William Burns > Priority: Blocker > Labels: testsuite_stability > Fix For: 7.0.0.Final > > > When the distributed entry iterator gets a suspect exception, it assumes that the CH will be soon updated to remove the leaver, and retries to contact the primary owner of the segment. > But if the cache is in degraded mode, the consistent hash is no longer updated, and the entry iterator enters an infinite loop. > {noformat} > 11:58:35,622 TRACE (testng-DelayedAvailabilityUpdateTest:) [DistributedEntryRetriever] Request to NodeC-51013=[50, 51, 20, 52, 21, 53, 22, 54, 23, 24, 25, 26, 27, 28, 29] for cd886604-960b-431a-81a0-efbb51eed57f was suspect, must resend to a new node! > 11:58:35,622 TRACE (testng-DelayedAvailabilityUpdateTest:) [DistributedEntryRetriever] Request to NodeC-51013=[50, 51, 20, 52, 21, 53, 22, 54, 23, 24, 25, 26, 27, 28, 29] for cd886604-960b-431a-81a0-efbb51eed57f was suspect, must resend to a new node! > 11:58:35,622 TRACE (testng-DelayedAvailabilityUpdateTest:) [DistributedEntryRetriever] Request to NodeC-51013=[50, 51, 20, 52, 21, 53, 22, 54, 23, 24, 25, 26, 27, 28, 29] for cd886604-960b-431a-81a0-efbb51eed57f was suspect, must resend to a new node! > ... > {noformat} > This is visible when running the partition handling tests (e.g. DelayedAvailabilityUpdateTest) with trace logging enabled, as {{TestingUtil.killCaches()}} logs the cache contents at trace level. As an aside, {{TestingUtil.killCaches()}} should probably use {{Flag.CACHE_MODE_LOCAL}} to print only the entries on each node. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2014