January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5093) Granularity of remote event listener implementations doing the same job

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-5093?page=com.atlassian.jira.plugin... ] Tristan Tarrant reassigned ISPN-5093: ------------------------------------- Assignee: (was: Galder Zamarreño) > Granularity of remote event listener implementations doing the same job > ----------------------------------------------------------------------- > > Key: ISPN-5093 > URL: https://issues.redhat.com/browse/ISPN-5093 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Priority: Major > > Currently, if N clients add the same listener to a cache that does the same job, e.g. keeping a near cache consistent, this results in N server-side cluster listeners created, each potentially installed in different nodes. If one of those nodes fails, all clients that had a listener registered to that node will have to find a different node for this listener. > The downsides of this approach is that there are as many cluster listeners installed as clients have added listeners (or have near cache enabled), which might not very efficient. If a node goes down, all clients that have cluster listeners there need to failover to some other node. > The advantage of this approach is simplicity of the approach to decide where to add the listener and where to failover to. > For this type of scenarios, an alternative set up might be worth exploring: > If all these client side listeners are interested in exactly the same events, and the client ID would be exposed via the RemoteCache API, a server side cluster listener multi-plexing between all these clients could be potentially built. In other words, instead of having N clients register N cluster listeners, the first client would register the cluster listener with a client listener ID, and if more registrations were added with the same client listener ID, the connections would be added to the existing cluster listener implementation. > The maximise the efficiency of this solution, all clients (even running in different JMVs), given the same client listener ID, should agree upon the node to add the listener in. For a distributed cache, hashing on the cache name would work. For replicated caches, since there's no hashing available, the first node of the view could be used. > Since the logic to be executed server-side varies between being the first node adding the client listener vs the others, synchronization would be added to make sure that the first invocation only creates the cluster listener, and the others simply add the channel to the listener. > Failover is a bit more tricky too, because if the node with the cluster listener goes down, all the clients have to failover, which again exposes a 1st vs the others type of logic. > Advantages of this approach is the reduction in number of cluster listeners and potentially efficiency coming from a single cluster listener implementation server side. > The disadvantages come from the server side logic to add/failover a cluster listener, which need to take into account if the listener is present or not. Other disadvantages come from needing the clients to use some specific routing for adding listeners for same node. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9590) ExtendedSearchWorkCreator and SearchWorkCreatorContext are no longer needed

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-9590?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-9590: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > ExtendedSearchWorkCreator and SearchWorkCreatorContext are no longer needed > --------------------------------------------------------------------------- > > Key: ISPN-9590 > URL: https://issues.redhat.com/browse/ISPN-9590 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.1.Final > > > These were introduced in https://issues.jboss.org/browse/ISPN-5346 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11132) Data not indexed during state transfer in server mode

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11132?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11132: ------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Data not indexed during state transfer in server mode > ----------------------------------------------------- > > Key: ISPN-11132 > URL: https://issues.redhat.com/browse/ISPN-11132 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 9.4.17.Final, 10.1.0.Final > Reporter: Gustavo Fernandes > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.1.Final, 9.4.18.Final > > > A REPL cache with index auto-config, during State transfer is skipping index of data. > The order of events observed is: > CACHE_STARTING LIFECYCLE -> ST HAPPENS -> DATA WRITTEN -> CACHE STARTED LIFECYCLE > During data writes, the {{ProtobufValueWrapperIndexingInterceptor}} is activated by Hibernate Search and skips the indexing altogether since the {{ProtobufValueWrapperSearchWorkCreator}} is not used, and thus it cannot extract the descriptor from the entities. That search creator is only installed at cacheStarted phase. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11145) Operator Docs: XSite Replication Updates

by Galder Zamarreño (Jira)

[ https://issues.redhat.com/browse/ISPN-11145?page=com.atlassian.jira.plugi... ] Galder Zamarreño updated ISPN-11145: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Operator Docs: XSite Replication Updates > ---------------------------------------- > > Key: ISPN-11145 > URL: https://issues.redhat.com/browse/ISPN-11145 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Minor > > Making a few changes to be consistent with https://github.com/infinispan/infinispan/pull/7730 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11145) Operator Docs: XSite Replication Updates

by Galder Zamarreño (Jira)

[ https://issues.redhat.com/browse/ISPN-11145?page=com.atlassian.jira.plugi... ] Galder Zamarreño updated ISPN-11145: ------------------------------------ Component/s: Operator > Operator Docs: XSite Replication Updates > ---------------------------------------- > > Key: ISPN-11145 > URL: https://issues.redhat.com/browse/ISPN-11145 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation, Operator > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Minor > > Making a few changes to be consistent with https://github.com/infinispan/infinispan/pull/7730 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8699) REST endpoint doesn't apply Subject to cache ops

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-8699?page=com.atlassian.jira.plugin... ] Tristan Tarrant resolved ISPN-8699. ----------------------------------- Fix Version/s: 10.0.0.Final Resolution: Done > REST endpoint doesn't apply Subject to cache ops > ------------------------------------------------ > > Key: ISPN-8699 > URL: https://issues.redhat.com/browse/ISPN-8699 > Project: Infinispan > Issue Type: Bug > Components: REST, Security, Server > Affects Versions: 9.2.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 10.0.0.Final > > > The REST endpoint is not applying the identity associated with the request to the cache operations, resulting in authorization not working -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10316) Support for Elytron in the REST server

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-10316?page=com.atlassian.jira.plugi... ] Tristan Tarrant reassigned ISPN-10316: -------------------------------------- Assignee: Tristan Tarrant > Support for Elytron in the REST server > -------------------------------------- > > Key: ISPN-10316 > URL: https://issues.redhat.com/browse/ISPN-10316 > Project: Infinispan > Issue Type: Feature Request > Components: REST > Reporter: Gustavo Fernandes > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Final > > > By creating an adapter between our Authenticator and this elytron httpauthenticationmechanism > it will give us BASIC, DIGEST, OAUTH, SPNEGO and CERT authentication -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10316) Support for Elytron in the REST server

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-10316?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-10316: ----------------------------------- Status: Open (was: New) > Support for Elytron in the REST server > -------------------------------------- > > Key: ISPN-10316 > URL: https://issues.redhat.com/browse/ISPN-10316 > Project: Infinispan > Issue Type: Feature Request > Components: REST > Reporter: Gustavo Fernandes > Priority: Major > Fix For: 10.0.0.Final > > > By creating an adapter between our Authenticator and this elytron httpauthenticationmechanism > it will give us BASIC, DIGEST, OAUTH, SPNEGO and CERT authentication -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10316) Support for Elytron in the REST server

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-10316?page=com.atlassian.jira.plugi... ] Tristan Tarrant resolved ISPN-10316. ------------------------------------ Fix Version/s: 10.0.0.Final Resolution: Done > Support for Elytron in the REST server > -------------------------------------- > > Key: ISPN-10316 > URL: https://issues.redhat.com/browse/ISPN-10316 > Project: Infinispan > Issue Type: Feature Request > Components: REST > Reporter: Gustavo Fernandes > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Final > > > By creating an adapter between our Authenticator and this elytron httpauthenticationmechanism > it will give us BASIC, DIGEST, OAUTH, SPNEGO and CERT authentication -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10539) Server Logging management via REST

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-10539?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-10539: ----------------------------------- Description: Interact with the Log4j instance (was: For inspecting, altering the logging configuration by looking at the installed LogManager) > Server Logging management via REST > ---------------------------------- > > Key: ISPN-10539 > URL: https://issues.redhat.com/browse/ISPN-10539 > Project: Infinispan > Issue Type: Feature Request > Components: REST > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > Interact with the Log4j instance -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 January 2020