[JBoss JIRA] (ISPN-10749) Invalidation mode needs a proper key partitioner
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-10749?page=com.atlassian.jira.plugin... ]
Dan Berindei updated ISPN-10749:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/7491
> Invalidation mode needs a proper key partitioner
> ------------------------------------------------
>
> Key: ISPN-10749
> URL: https://issues.jboss.org/browse/ISPN-10749
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.4.16.Final, 10.0.0.CR3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Final, 9.4.17.Final
>
>
> Caches in invalidation mode used to do everything on the local node and only broadcast an invalidation command to all the members. ISPN-10029 changed this, and now transactional invalidation caches acquire locks for affected keys on the primary owners.
> Unfortunately {{KeyPartitionerFactory}} constructs a {{SingleSegmentKeyPartitioner}} in invalidation mode, so there is only one primary owner for all the keys.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (ISPN-10617) Operator Docs: Getting started with k8s/OpenShift
by Donald Naro (Jira)
[ https://issues.jboss.org/browse/ISPN-10617?page=com.atlassian.jira.plugin... ]
Donald Naro updated ISPN-10617:
-------------------------------
Sprint: (was: DataGrid Sprint #36)
> Operator Docs: Getting started with k8s/OpenShift
> -------------------------------------------------
>
> Key: ISPN-10617
> URL: https://issues.jboss.org/browse/ISPN-10617
> Project: Infinispan
> Issue Type: Task
> Components: Documentation-Servers
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> assembly with getting started that includes procedure to setup pull request tokens. this should be done when engineering starts the work to create the cache service and dg service via the operator as well as the different profiles.
> clarify details about creating the operator. requires kubeadmin to install the operator into specific namespaces.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (ISPN-10657) Handle async-xsite in parallel
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-10657?page=com.atlassian.jira.plugin... ]
Dan Berindei updated ISPN-10657:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Handle async-xsite in parallel
> ------------------------------
>
> Key: ISPN-10657
> URL: https://issues.jboss.org/browse/ISPN-10657
> Project: Infinispan
> Issue Type: Enhancement
> Components: Cross-Site Replication
> Affects Versions: 10.0.0.CR2
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> Asynchronous cross-site replication relies on the ordering of the write operation to ensure data consistency. This ordering is provided by JGroups; it only delivers the next request after the first one is completed.
> This order contains updates for multiple caches and keys. What is proposed here is to handle different keys/cache updates in parallel.
> It should improve the response time, however, there is no free lunch. The following is expected:
> * An increase of CPU utilization: it may spawn new threads to handle different keys update in parallel
> * An increase in memory: it chains the updates (queue)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months