[JBoss JIRA] (ISPN-11959) Add custom NonBlockingStore test
by Will Burns (Jira)
Will Burns created ISPN-11959:
---------------------------------
Summary: Add custom NonBlockingStore test
Key: ISPN-11959
URL: https://issues.redhat.com/browse/ISPN-11959
Project: Infinispan
Issue Type: Task
Reporter: Will Burns
Assignee: Will Burns
Fix For: 11.0.0.Final
We have the new SPI with ISPN-10373. We should add a test that verifies this works in the infinispan-server-tests module.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (ISPN-11679) Bad uneven segment distributions can happen after the rebalancing with SyncConsistentHashFactory
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11679?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-11679:
------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Bad uneven segment distributions can happen after the rebalancing with SyncConsistentHashFactory
> ------------------------------------------------------------------------------------------------
>
> Key: ISPN-11679
> URL: https://issues.redhat.com/browse/ISPN-11679
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.4.19.Final, 10.1.6.Final
> Reporter: Masafumi Miura
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> Uneven segment distribution can happen after rebalancing with SyncConsistentHashFactory.
> Even if a larger number of segments than "20 * number of nodes" is configured, some nodes have only around 50-60% number of segments than other nodes after the rebalance in the worst case.
> I understand the documentation (like the following) states about the possibility of slight uneven distribution as a potential drawback of SyncConsistentHashFactory.
> [Infinispan 10 configuration guide|https://infinispan.org/docs/stable/titles/configuring/configuring.h...] says:
> {quote}
> This implementation does have some negative points in that the load distribution is slightly uneven. It also moves more segments than strictly necessary on a join or leave.
> {quote}
> [JDG 7 Developer Guide|https://access.redhat.com/documentation/en-us/red_hat_data_grid/7.2...] says:
> {quote}
> It has a potential drawback in that it can move a greater number of segments than necessary during re-balancing. This can be mitigated by using a larger number of segments.
> Another potential drawback is that the segments are not distributed as evenly as possible, and actually using a very large number of segments can make the distribution of segments worse.
> {quote}
> However, only half segments than others is not a slight uneven.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (ISPN-11953) Create client archetype
by Ryan Emerson (Jira)
Ryan Emerson created ISPN-11953:
-----------------------------------
Summary: Create client archetype
Key: ISPN-11953
URL: https://issues.redhat.com/browse/ISPN-11953
Project: Infinispan
Issue Type: Sub-task
Components: Demos and Tutorials
Affects Versions: 11.0.0.CR1
Reporter: Ryan Emerson
We should create an archetype that allows users to create a HotRod client application.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (ISPN-11951) Component annotation processor should use javax.annotation.processing.Generated
by Dan Berindei (Jira)
Dan Berindei created ISPN-11951:
-----------------------------------
Summary: Component annotation processor should use javax.annotation.processing.Generated
Key: ISPN-11951
URL: https://issues.redhat.com/browse/ISPN-11951
Project: Infinispan
Issue Type: Task
Affects Versions: 11.0.0.CR1
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 11.0.0.Final
The component annotation processor currently uses {{javax.annotation.Generated}} in the source files. Since the annotation only has source retention, we can switch to the JDK 9+ {{javax.annotation.processing.Generated}} annotation and remove the {{javax.annotation-api-1.3.1}} dependency.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months