November 2014 - infinispan-issues

[JBoss JIRA] (ISPN-4792) RemoteClusterListener still invokes filter/converter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4792?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4792: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1154044 > RemoteClusterListener still invokes filter/converter > ---------------------------------------------------- > > Key: ISPN-4792 > URL: https://issues.jboss.org/browse/ISPN-4792 > Project: Infinispan > Issue Type: Enhancement > Components: Listeners > Affects Versions: 7.0.0.Beta2 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.CR1 > > > When using a distributed cluster listener it installs a listener on each of the nodes to receive notifications. Cluster listeners only raise post events, but on remote nodes (ones where the listener wasn't originally installed) they invoke the filter and converter even on pre events which is not needed. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4904) PartitionHandlingInterceptor should not do checks when Flag.CACHE_MODE_LOCAL is supplied

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4904?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4904: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1161783 > PartitionHandlingInterceptor should not do checks when Flag.CACHE_MODE_LOCAL is supplied > ---------------------------------------------------------------------------------------- > > Key: ISPN-4904 > URL: https://issues.jboss.org/browse/ISPN-4904 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.CR2 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Final > > > The PartitionHandlingInterceptor currently checks every key irrespective of flags. Since CACHE_MODE_LOCAL flag doesn't involve other nodes we should ignore these checks as the user must know what they are doing. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4890?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4890: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1161783 > 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.8#6338)

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: ----------------------------------------------- William Burns <wburns(a)redhat.com> changed the Status of [bug 1154044|https://bugzilla.redhat.com/show_bug.cgi?id=1154044] from ASSIGNED to POST > 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.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2678) Security needs to be implemented for HotRod

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2678?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-2678. --------------------------------- Fix Version/s: 7.0.0.Final Resolution: Done > Security needs to be implemented for HotRod > ------------------------------------------- > > Key: ISPN-2678 > URL: https://issues.jboss.org/browse/ISPN-2678 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration, Server > Reporter: Joel Tosi > Labels: security > Fix For: 7.0.0.Final > > > Breakdown of ISPN-143 - https://issues.jboss.org/browse/ISPN-143 > This is implementing security for the HotRod client -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4956) Task Management

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-4956: ------------------------------------- Summary: Task Management Key: ISPN-4956 URL: https://issues.jboss.org/browse/ISPN-4956 Project: Infinispan Issue Type: Feature Request Reporter: Tristan Tarrant Task Management: - job metadata (type, start, elapsed time, subject, caches involved, status: RUNNING, FINISHED, CANCELLED) - see running jobs and allow cancelling them - maintain a history of executed jobs - once we have a repository of named tasks, allow launching them -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4955) JCache implementation over HotRod

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-4955: ------------------------------------- Summary: JCache implementation over HotRod Key: ISPN-4955 URL: https://issues.jboss.org/browse/ISPN-4955 Project: Infinispan Issue Type: Feature Request Components: Remote Protocols Reporter: Tristan Tarrant Fix For: 7.1.0.Final -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4953) Review quickstart README metadata to optimize it for the Google search

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/ISPN-4953?page=com.atlassian.jira.plugin.... ] Sande Gilda updated ISPN-4953: ------------------------------ Description: See JDF-787. The jboss.org development team plans to do the following: - Parse the first line of each README file to remove the quickstart name prefix and use the rest for Google SEO title. That field is limited to ~55 characters. - Use the 'Summary:' metadata for the description. This field is limited to 155 characters. This information is what shows up on the search result page, so the better it better describes the example. I went through all the JBoss EAP quickstart README files to shorten the title and lengthen the Summary to be more descriptive. We need to do this for all of the other quickstarts, including: * JDG: https://github.com/jboss-developer/jboss-jdg-quickstarts See related JBoss EAP bugs for details: * https://bugzilla.redhat.com/show_bug.cgi?id=1160776 * https://bugzilla.redhat.com/show_bug.cgi?id=1159374 was: The jboss.org development team plans to do the following: - Parse the first line of each README file to remove the quickstart name prefix and use the rest for Google SEO title. That field is limited to ~55 characters. - Use the 'Summary:' metadata for the description. This field is limited to 155 characters. This information is what shows up on the search result page, so the better it better describes the example. I went through all the JBoss EAP quickstart README files to shorten the title and lengthen the Summary to be more descriptive. We need to do this for all of the other quickstarts, including: * JDG: https://github.com/jboss-developer/jboss-jdg-quickstarts See related JBoss EAP bugs for details: * https://bugzilla.redhat.com/show_bug.cgi?id=1160776 * https://bugzilla.redhat.com/show_bug.cgi?id=1159374 > Review quickstart README metadata to optimize it for the Google search > ---------------------------------------------------------------------- > > Key: ISPN-4953 > URL: https://issues.jboss.org/browse/ISPN-4953 > Project: Infinispan > Issue Type: Bug > Components: Demos and Tutorials > Reporter: Sande Gilda > > See JDF-787. > The jboss.org development team plans to do the following: > - Parse the first line of each README file to remove the quickstart name prefix and use the rest for Google SEO title. That field is limited to ~55 characters. > - Use the 'Summary:' metadata for the description. This field is limited to 155 characters. > This information is what shows up on the search result page, so the better it better describes the example. > I went through all the JBoss EAP quickstart README files to shorten the title and lengthen the Summary to be more descriptive. We need to do this for all of the other quickstarts, including: > * JDG: https://github.com/jboss-developer/jboss-jdg-quickstarts > See related JBoss EAP bugs for details: > * https://bugzilla.redhat.com/show_bug.cgi?id=1160776 > * https://bugzilla.redhat.com/show_bug.cgi?id=1159374 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4954) Entry Iterator can block transport thread if closed while trying to put wait into queue

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4954?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-4954: -------------------------------- Description: This can happen if an iterator is only partially iterated on and is then closed. See https://developer.jboss.org/message/909509 for more details. was: This will happen if an iterator is only partially iterated on and is then closed. See https://developer.jboss.org/message/909509 for more details. > Entry Iterator can block transport thread if closed while trying to put wait into queue > --------------------------------------------------------------------------------------- > > Key: ISPN-4954 > URL: https://issues.jboss.org/browse/ISPN-4954 > Project: Infinispan > Issue Type: Bug > Affects Versions: 7.0.0.Final > Reporter: William Burns > Assignee: William Burns > Priority: Blocker > Fix For: 7.1.0.Alpha1 > > > This can happen if an iterator is only partially iterated on and is then closed. > See https://developer.jboss.org/message/909509 for more details. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3561) A joining cache should receive the rebalancedEnabled flag from the coordinator.

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3561?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-3561: ---------------------------------- Assignee: Dan Berindei (was: Mircea Markus) > A joining cache should receive the rebalancedEnabled flag from the coordinator. > ------------------------------------------------------------------------------- > > Key: ISPN-3561 > URL: https://issues.jboss.org/browse/ISPN-3561 > Project: Infinispan > Issue Type: Feature Request > Components: State Transfer > Affects Versions: 5.2.7.Final, 5.3.0.Final, 6.0.0.Beta1 > Reporter: Erik Salter > Assignee: Dan Berindei > > There is an issue when starting up a set of nodes in a cluster where the coordinator has told the surviving members that state transfer has been disabled. If rebalancing is disabled while the cluster is running it's disabled on all the > However, if a new set of nodes join afterwards, they don't know that rebalancing was disabled. > This has consequences if there is a new coordinator elected (like during a MERGE) from the set of newly-started nodes. > To prevent this and ensure the greatest probablility of success, a node joining should get the state of this flag from the response from the coordinator. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

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 November 2014