[JBoss JIRA] (ISPN-11199) Remove AffinityIndexManager
by Gustavo Fernandes (Jira)
Gustavo Fernandes created ISPN-11199:
----------------------------------------
Summary: Remove AffinityIndexManager
Key: ISPN-11199
URL: https://issues.redhat.com/browse/ISPN-11199
Project: Infinispan
Issue Type: Bug
Components: Embedded Querying
Affects Versions: 10.1.1.Final
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
Fix For: 11.0.0.Alpha1
This Index Manager is marked as experimental and since we are giving priority to local indexes, it will be discontinued
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-11129) High Availability for non-shared indexes on DIST caches
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-11129?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-11129:
-------------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/7768
> High Availability for non-shared indexes on DIST caches
> -------------------------------------------------------
>
> Key: ISPN-11129
> URL: https://issues.redhat.com/browse/ISPN-11129
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 9.4.17.Final, 10.1.1.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> 'Non-shared indexes' is a setup when each node has a local index backed by the file system, using either the near-real-time or the FS index managers.
> For REPL caches, a full copy of the index is kept in each node. As long as at least on node is up the queries hit the local index which represents the full index of the data.
> But non-shared indexes has some drawbacks for DIST caches: each node only indexes data that the node is the primary owner. If a node goes down, there is no redundancy. This issue aims to solve this issue at two levels:
> * Indexing: replicated entries should be indexed for redundancy purposes. If a primary owner goes down, the entry is indexed in the backup owner. This should follow exactly the data distribution on the cache in terms of number of replicas and rebalancing
> * Querying: query broadcast is currently used for non-shared indexes. If replicated entries start to be indexed, a mechanism will have to be used to avoid retuning repeated results, since currently the broadcast simply queries all the entries in each node and join the result.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-11129) High Availability for non-shared indexes on DIST caches
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-11129?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-11129:
-------------------------------------
Affects Version/s: 10.1.1.Final
9.4.17.Final
> High Availability for non-shared indexes on DIST caches
> -------------------------------------------------------
>
> Key: ISPN-11129
> URL: https://issues.redhat.com/browse/ISPN-11129
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 9.4.17.Final, 10.1.1.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> 'Non-shared indexes' is a setup when each node has a local index backed by the file system, using either the near-real-time or the FS index managers.
> For REPL caches, a full copy of the index is kept in each node. As long as at least on node is up the queries hit the local index which represents the full index of the data.
> But non-shared indexes has some drawbacks for DIST caches: each node only indexes data that the node is the primary owner. If a node goes down, there is no redundancy. This issue aims to solve this issue at two levels:
> * Indexing: replicated entries should be indexed for redundancy purposes. If a primary owner goes down, the entry is indexed in the backup owner. This should follow exactly the data distribution on the cache in terms of number of replicas and rebalancing
> * Querying: query broadcast is currently used for non-shared indexes. If replicated entries start to be indexed, a mechanism will have to be used to avoid retuning repeated results, since currently the broadcast simply queries all the entries in each node and join the result.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-11129) High Availability for non-shared indexes on DIST caches
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-11129?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-11129:
-------------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/7768, https://github.com/infinispan/infinispan/pull/7762 (was: https://github.com/infinispan/infinispan/pull/7768)
> High Availability for non-shared indexes on DIST caches
> -------------------------------------------------------
>
> Key: ISPN-11129
> URL: https://issues.redhat.com/browse/ISPN-11129
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 9.4.17.Final, 10.1.1.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> 'Non-shared indexes' is a setup when each node has a local index backed by the file system, using either the near-real-time or the FS index managers.
> For REPL caches, a full copy of the index is kept in each node. As long as at least on node is up the queries hit the local index which represents the full index of the data.
> But non-shared indexes has some drawbacks for DIST caches: each node only indexes data that the node is the primary owner. If a node goes down, there is no redundancy. This issue aims to solve this issue at two levels:
> * Indexing: replicated entries should be indexed for redundancy purposes. If a primary owner goes down, the entry is indexed in the backup owner. This should follow exactly the data distribution on the cache in terms of number of replicas and rebalancing
> * Querying: query broadcast is currently used for non-shared indexes. If replicated entries start to be indexed, a mechanism will have to be used to avoid retuning repeated results, since currently the broadcast simply queries all the entries in each node and join the result.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-11197) Server Docs: JMX Monitoring
by Donald Naro (Jira)
[ https://issues.redhat.com/browse/ISPN-11197?page=com.atlassian.jira.plugi... ]
Donald Naro updated ISPN-11197:
-------------------------------
Description: Need to update server docs for JMX monitoring. (was: Configuring authentication and encryption.
As a user, I need to understand auth mechanisms (BASIC, DIGEST-MD5, OAUTH [KeyCloak], SCRAM, SPNEGO and CERT)
Authentication: Hot Rod > SASL, REST > HTTP Auth
Auth methods
SASL: PLAIN <> HTTP: Basic
SASL: DIGEST-MD5 <> HTTP: Digest
SASL: EXTERNAL <> HTTP: ClientCert
As an admin, I can enable memcached even though it does not support authentication.
As a user, I need to create and manage credentials.
As a user, I need to set up encryption. Adding CA-signed server certs. Creating and adding self-signed certs.)
> Server Docs: JMX Monitoring
> ---------------------------
>
> Key: ISPN-11197
> URL: https://issues.redhat.com/browse/ISPN-11197
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> Need to update server docs for JMX monitoring.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-11197) Server Docs: Auth and Encryption
by Donald Naro (Jira)
Donald Naro created ISPN-11197:
----------------------------------
Summary: Server Docs: Auth and Encryption
Key: ISPN-11197
URL: https://issues.redhat.com/browse/ISPN-11197
Project: Infinispan
Issue Type: Enhancement
Components: Documentation
Reporter: Donald Naro
Assignee: Donald Naro
Configuring authentication and encryption.
As a user, I need to understand auth mechanisms (BASIC, DIGEST-MD5, OAUTH [KeyCloak], SCRAM, SPNEGO and CERT)
Authentication: Hot Rod > SASL, REST > HTTP Auth
Auth methods
SASL: PLAIN <> HTTP: Basic
SASL: DIGEST-MD5 <> HTTP: Digest
SASL: EXTERNAL <> HTTP: ClientCert
As an admin, I can enable memcached even though it does not support authentication.
As a user, I need to create and manage credentials.
As a user, I need to set up encryption. Adding CA-signed server certs. Creating and adding self-signed certs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-11197) Server Docs: JMX Monitoring
by Donald Naro (Jira)
[ https://issues.redhat.com/browse/ISPN-11197?page=com.atlassian.jira.plugi... ]
Donald Naro updated ISPN-11197:
-------------------------------
Summary: Server Docs: JMX Monitoring (was: Server Docs: Auth and Encryption)
> Server Docs: JMX Monitoring
> ---------------------------
>
> Key: ISPN-11197
> URL: https://issues.redhat.com/browse/ISPN-11197
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> Configuring authentication and encryption.
> As a user, I need to understand auth mechanisms (BASIC, DIGEST-MD5, OAUTH [KeyCloak], SCRAM, SPNEGO and CERT)
> Authentication: Hot Rod > SASL, REST > HTTP Auth
> Auth methods
> SASL: PLAIN <> HTTP: Basic
> SASL: DIGEST-MD5 <> HTTP: Digest
> SASL: EXTERNAL <> HTTP: ClientCert
> As an admin, I can enable memcached even though it does not support authentication.
> As a user, I need to create and manage credentials.
> As a user, I need to set up encryption. Adding CA-signed server certs. Creating and adding self-signed certs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-10725) Server Docs: Auth and Encryption
by Donald Naro (Jira)
[ https://issues.redhat.com/browse/ISPN-10725?page=com.atlassian.jira.plugi... ]
Donald Naro updated ISPN-10725:
-------------------------------
Summary: Server Docs: Auth and Encryption (was: Server Docs: Authentication Mechanisms + Encryption)
> Server Docs: Auth and Encryption
> --------------------------------
>
> Key: ISPN-10725
> URL: https://issues.redhat.com/browse/ISPN-10725
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> Configuring authentication and encryption.
> As a user, I need to understand auth mechanisms (BASIC, DIGEST-MD5, OAUTH [KeyCloak], SCRAM, SPNEGO and CERT)
> Authentication: Hot Rod > SASL, REST > HTTP Auth
> Auth methods
> SASL: PLAIN <> HTTP: Basic
> SASL: DIGEST-MD5 <> HTTP: Digest
> SASL: EXTERNAL <> HTTP: ClientCert
> As an admin, I can enable memcached even though it does not support authentication.
> As a user, I need to create and manage credentials.
> As a user, I need to set up encryption. Adding CA-signed server certs. Creating and adding self-signed certs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months