[JBoss JIRA] (ISPN-5860) ComponentRegistry should cache the VersionGenerator in a field
by Dan Berindei (JIRA)
Dan Berindei created ISPN-5860:
----------------------------------
Summary: ComponentRegistry should cache the VersionGenerator in a field
Key: ISPN-5860
URL: https://issues.jboss.org/browse/ISPN-5860
Project: Infinispan
Issue Type: Bug
Components: Core, Server
Affects Versions: 8.1.0.Alpha1, 8.0.1.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 8.1.0.Alpha2, 8.1.0.Final
The {{VersionGenerator}} component is read by the HotRod server for each write operation, and we can optimize it by caching the component in a field.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (ISPN-5857) HotRod client should use the consistent hash in replicated mode
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-5857?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-5857:
-------------------------------
Status: Open (was: New)
> HotRod client should use the consistent hash in replicated mode
> ---------------------------------------------------------------
>
> Key: ISPN-5857
> URL: https://issues.jboss.org/browse/ISPN-5857
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.0.1.Final, 8.1.0.Alpha1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Critical
> Labels: hotrod
> Fix For: 8.1.0.Alpha2, 8.1.0.Final
>
>
> The HotRod server assumes that in replicated mode the server accessed by the client doesn't matter, so it doesn't send a consistent hash in the topology updates.
> However, since replicated mode is now implemented on top of distributed mode, hitting the primary owner or another node makes a big difference. We should change the server to send the consistent hash for replicated caches as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (ISPN-5858) ValueMatcher and AvailabilityMode should have externalizers
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-5858?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-5858:
-------------------------------
Status: Open (was: New)
> ValueMatcher and AvailabilityMode should have externalizers
> -----------------------------------------------------------
>
> Key: ISPN-5858
> URL: https://issues.jboss.org/browse/ISPN-5858
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 8.0.1.Final, 8.1.0.Alpha1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 8.1.0.Alpha2, 8.1.0.CR1
>
>
> The default enum serialization is pretty bad, it writes both the enum name and value name as strings.
> {{ValueMatcher}} is needed in each write command, so we should optimize it.
> {{AvailabilityMode}} doesn't matter that much, except when the coordinator changes, and the new coordinator has to retrieve the status of all the caches on all the nodes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (ISPN-5859) HotRod server should not use privileged actions for common stuff
by Dan Berindei (JIRA)
Dan Berindei created ISPN-5859:
----------------------------------
Summary: HotRod server should not use privileged actions for common stuff
Key: ISPN-5859
URL: https://issues.jboss.org/browse/ISPN-5859
Project: Infinispan
Issue Type: Bug
Components: Server
Affects Versions: 8.1.0.Alpha1, 8.0.1.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 8.1.0.Alpha2, 8.1.0.Final
The HotRod server uses privileged actions to perform operations that are needed for each request, like reading the cache mode to decide what kind (if any) topology update to send to the client. Since privileged actions use thread-locals, we should try to avoid them.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (ISPN-5858) ValueMatcher and AvailabilityMode should have externalizers
by Dan Berindei (JIRA)
Dan Berindei created ISPN-5858:
----------------------------------
Summary: ValueMatcher and AvailabilityMode should have externalizers
Key: ISPN-5858
URL: https://issues.jboss.org/browse/ISPN-5858
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 8.1.0.Alpha1, 8.0.1.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 8.1.0.Alpha2, 8.1.0.CR1
The default enum serialization is pretty bad, it writes both the enum name and value name as strings.
{{ValueMatcher}} is needed in each write command, so we should optimize it.
{{AvailabilityMode}} doesn't matter that much, except when the coordinator changes, and the new coordinator has to retrieve the status of all the caches on all the nodes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (ISPN-5857) HotRod client should use the consistent hash in replicated mode
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-5857?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-5857:
-------------------------------
Issue Type: Bug (was: Feature Request)
> HotRod client should use the consistent hash in replicated mode
> ---------------------------------------------------------------
>
> Key: ISPN-5857
> URL: https://issues.jboss.org/browse/ISPN-5857
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.0.1.Final, 8.1.0.Alpha1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Critical
> Labels: hotrod
> Fix For: 8.1.0.Alpha2, 8.1.0.Final
>
>
> The HotRod server assumes that in replicated mode the server accessed by the client doesn't matter, so it doesn't send a consistent hash in the topology updates.
> However, since replicated mode is now implemented on top of distributed mode, hitting the primary owner or another node makes a big difference. We should change the server to send the consistent hash for replicated caches as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (ISPN-5857) HotRod client should use the consistent hash in replicated mode
by Dan Berindei (JIRA)
Dan Berindei created ISPN-5857:
----------------------------------
Summary: HotRod client should use the consistent hash in replicated mode
Key: ISPN-5857
URL: https://issues.jboss.org/browse/ISPN-5857
Project: Infinispan
Issue Type: Feature Request
Components: Server
Affects Versions: 8.1.0.Alpha1, 8.0.1.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Priority: Critical
Fix For: 8.1.0.Alpha2, 8.1.0.Final
The HotRod server assumes that in replicated mode the server accessed by the client doesn't matter, so it doesn't send a consistent hash in the topology updates.
However, since replicated mode is now implemented on top of distributed mode, hitting the primary owner or another node makes a big difference. We should change the server to send the consistent hash for replicated caches as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months