4:04 a.m.
Consider staggering remote get requests when using DIST
-------------------------------------------------------
Key: ISPN-825
URL: https://jira.jboss.org/browse/ISPN-825
Project: Infinispan
Issue Type: Feature Request
Components: RPC
Affects Versions: 4.1.0.Final
Reporter: Manik Surtani
Assignee: Manik Surtani
Fix For: 5.0.0.BETA1, 5.0.0.Final
In DIST mode, when a request is made on a key that is not mapped locally, a remote get is
sent to all data owners of that key and the first response is used. This can add
unnecessary load on the network as all nodes still eventually respond, and if values are
large this can cause a lot of unnecessary network traffic.
The purpose of broadcasting to all data owners is so that (1) if one is down, another
could still respond (2) if one is overloaded, others may respond faster.
A solution around this could be based on either (or both) of:
* Provide a configurable stagger timeout, e.g. 100ms. E.g., RPC to (random) Owner1. Wait
for timeout t. If no response, RPC to Owner2. etc.
* Always broadcast to a (configurable) subset of owners, e.g., always 2 even if numOwners
is 5.
Needs careful thought and design.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:17 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-825) Consider staggering remote get requests when using DIST
[
https://jira.jboss.org/browse/ISPN-825?page=com.atlassian.jira.plugin.sys...
]
Mircea Markus commented on ISPN-825:
------------------------------------
for TopologyAwareConsistentHash/server hiting this should always make sure that it goes to
the "closest" server: in this case the first backups are selected as far as
possible from the data owner.
Consider staggering remote get requests when using DIST
-------------------------------------------------------
Key: ISPN-825
URL: https://jira.jboss.org/browse/ISPN-825
Project: Infinispan
Issue Type: Feature Request
Components: RPC
Affects Versions: 4.1.0.Final
Reporter: Manik Surtani
Assignee: Manik Surtani
Labels: optimization, performance
Fix For: 5.0.0.BETA1, 5.0.0.Final
In DIST mode, when a request is made on a key that is not mapped locally, a remote get is
sent to all data owners of that key and the first response is used. This can add
unnecessary load on the network as all nodes still eventually respond, and if values are
large this can cause a lot of unnecessary network traffic.
The purpose of broadcasting to all data owners is so that (1) if one is down, another
could still respond (2) if one is overloaded, others may respond faster.
A solution around this could be based on either (or both) of:
* Provide a configurable stagger timeout, e.g. 100ms. E.g., RPC to (random) Owner1.
Wait for timeout t. If no response, RPC to Owner2. etc.
* Always broadcast to a (configurable) subset of owners, e.g., always 2 even if numOwners
is 5.
Needs careful thought and design.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:05 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-825) Consider staggering remote get requests when using DIST
[
https://issues.jboss.org/browse/ISPN-825?page=com.atlassian.jira.plugin.s...
]
Manik Surtani updated ISPN-825:
-------------------------------
Fix Version/s: 5.1.0.BETA1
5.1.0.Final
(was: 5.0.0.BETA1)
(was: 5.0.0.FINAL)
Consider staggering remote get requests when using DIST
-------------------------------------------------------
Key: ISPN-825
URL: https://issues.jboss.org/browse/ISPN-825
Project: Infinispan
Issue Type: Feature Request
Components: RPC
Affects Versions: 4.1.0.Final
Reporter: Manik Surtani
Assignee: Manik Surtani
Labels: optimization, performance
Fix For: 5.1.0.BETA1, 5.1.0.Final
In DIST mode, when a request is made on a key that is not mapped locally, a remote get is
sent to all data owners of that key and the first response is used. This can add
unnecessary load on the network as all nodes still eventually respond, and if values are
large this can cause a lot of unnecessary network traffic.
The purpose of broadcasting to all data owners is so that (1) if one is down, another
could still respond (2) if one is overloaded, others may respond faster.
A solution around this could be based on either (or both) of:
* Provide a configurable stagger timeout, e.g. 100ms. E.g., RPC to (random) Owner1.
Wait for timeout t. If no response, RPC to Owner2. etc.
* Always broadcast to a (configurable) subset of owners, e.g., always 2 even if numOwners
is 5.
Needs careful thought and design.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:24 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-825) Consider staggering remote get requests when using DIST
[
https://issues.jboss.org/browse/ISPN-825?page=com.atlassian.jira.plugin.s...
]
Manik Surtani updated ISPN-825:
-------------------------------
Priority: Critical (was: Major)
Consider staggering remote get requests when using DIST
-------------------------------------------------------
Key: ISPN-825
URL: https://issues.jboss.org/browse/ISPN-825
Project: Infinispan
Issue Type: Feature Request
Components: RPC
Affects Versions: 4.1.0.Final
Reporter: Manik Surtani
Assignee: Manik Surtani
Priority: Critical
Labels: optimization, performance
Fix For: 5.1.0.BETA1, 5.1.0.Final
In DIST mode, when a request is made on a key that is not mapped locally, a remote get is
sent to all data owners of that key and the first response is used. This can add
unnecessary load on the network as all nodes still eventually respond, and if values are
large this can cause a lot of unnecessary network traffic.
The purpose of broadcasting to all data owners is so that (1) if one is down, another
could still respond (2) if one is overloaded, others may respond faster.
A solution around this could be based on either (or both) of:
* Provide a configurable stagger timeout, e.g. 100ms. E.g., RPC to (random) Owner1.
Wait for timeout t. If no response, RPC to Owner2. etc.
* Always broadcast to a (configurable) subset of owners, e.g., always 2 even if numOwners
is 5.
Needs careful thought and design.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:34 a.m.
New subject: [JBoss JIRA] (ISPN-825) Consider staggering remote get requests when using DIST
[
https://issues.jboss.org/browse/ISPN-825?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño updated ISPN-825:
----------------------------------
Fix Version/s: 5.1.0.BETA2
(was: 5.1.0.BETA1)
Consider staggering remote get requests when using DIST
-------------------------------------------------------
Key: ISPN-825
URL: https://issues.jboss.org/browse/ISPN-825
Project: Infinispan
Issue Type: Feature Request
Components: RPC
Affects Versions: 4.1.0.Final
Reporter: Manik Surtani
Assignee: Manik Surtani
Priority: Critical
Labels: optimization, performance
Fix For: 5.1.0.BETA2, 5.1.0.FINAL
In DIST mode, when a request is made on a key that is not mapped locally, a remote get is
sent to all data owners of that key and the first response is used. This can add
unnecessary load on the network as all nodes still eventually respond, and if values are
large this can cause a lot of unnecessary network traffic.
The purpose of broadcasting to all data owners is so that (1) if one is down, another
could still respond (2) if one is overloaded, others may respond faster.
A solution around this could be based on either (or both) of:
* Provide a configurable stagger timeout, e.g. 100ms. E.g., RPC to (random) Owner1.
Wait for timeout t. If no response, RPC to Owner2. etc.
* Always broadcast to a (configurable) subset of owners, e.g., always 2 even if numOwners
is 5.
Needs careful thought and design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:24 a.m.
New subject: [JBoss JIRA] (ISPN-825) Consider staggering remote get requests when using DIST
[
https://issues.jboss.org/browse/ISPN-825?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño updated ISPN-825:
----------------------------------
Fix Version/s: 5.1.0.BETA3
(was: 5.1.0.BETA2)
Consider staggering remote get requests when using DIST
-------------------------------------------------------
Key: ISPN-825
URL: https://issues.jboss.org/browse/ISPN-825
Project: Infinispan
Issue Type: Feature Request
Components: RPC
Affects Versions: 4.1.0.Final
Reporter: Manik Surtani
Assignee: Manik Surtani
Priority: Critical
Labels: optimization, performance
Fix For: 5.1.0.BETA3, 5.1.0.FINAL
In DIST mode, when a request is made on a key that is not mapped locally, a remote get is
sent to all data owners of that key and the first response is used. This can add
unnecessary load on the network as all nodes still eventually respond, and if values are
large this can cause a lot of unnecessary network traffic.
The purpose of broadcasting to all data owners is so that (1) if one is down, another
could still respond (2) if one is overloaded, others may respond faster.
A solution around this could be based on either (or both) of:
* Provide a configurable stagger timeout, e.g. 100ms. E.g., RPC to (random) Owner1.
Wait for timeout t. If no response, RPC to Owner2. etc.
* Always broadcast to a (configurable) subset of owners, e.g., always 2 even if numOwners
is 5.
Needs careful thought and design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:41 a.m.
New subject: [JBoss JIRA] (ISPN-825) Consider staggering remote get requests when using DIST
[
https://issues.jboss.org/browse/ISPN-825?page=com.atlassian.jira.plugin.s...
]
Manik Surtani updated ISPN-825:
-------------------------------
Fix Version/s: 5.2.0.FINAL
(was: 5.1.0.FINAL)
(was: 5.1.0.BETA3)
Consider staggering remote get requests when using DIST
-------------------------------------------------------
Key: ISPN-825
URL: https://issues.jboss.org/browse/ISPN-825
Project: Infinispan
Issue Type: Feature Request
Components: RPC
Affects Versions: 4.1.0.Final
Reporter: Manik Surtani
Assignee: Manik Surtani
Priority: Critical
Labels: optimization, performance
Fix For: 5.2.0.FINAL
In DIST mode, when a request is made on a key that is not mapped locally, a remote get is
sent to all data owners of that key and the first response is used. This can add
unnecessary load on the network as all nodes still eventually respond, and if values are
large this can cause a lot of unnecessary network traffic.
The purpose of broadcasting to all data owners is so that (1) if one is down, another
could still respond (2) if one is overloaded, others may respond faster.
A solution around this could be based on either (or both) of:
* Provide a configurable stagger timeout, e.g. 100ms. E.g., RPC to (random) Owner1.
Wait for timeout t. If no response, RPC to Owner2. etc.
* Always broadcast to a (configurable) subset of owners, e.g., always 2 even if numOwners
is 5.
Needs careful thought and design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:19 a.m.
New subject: [JBoss JIRA] (ISPN-825) Consider staggering remote get requests when using DIST
[
https://issues.jboss.org/browse/ISPN-825?page=com.atlassian.jira.plugin.s...
]
Mircea Markus reassigned ISPN-825:
----------------------------------
Assignee: Mircea Markus (was: Manik Surtani)
Consider staggering remote get requests when using DIST
-------------------------------------------------------
Key: ISPN-825
URL: https://issues.jboss.org/browse/ISPN-825
Project: Infinispan
Issue Type: Feature Request
Components: RPC
Affects Versions: 4.1.0.Final
Reporter: Manik Surtani
Assignee: Mircea Markus
Priority: Critical
Labels: optimization, performance
Fix For: 5.2.0.FINAL
In DIST mode, when a request is made on a key that is not mapped locally, a remote get is
sent to all data owners of that key and the first response is used. This can add
unnecessary load on the network as all nodes still eventually respond, and if values are
large this can cause a lot of unnecessary network traffic.
The purpose of broadcasting to all data owners is so that (1) if one is down, another
could still respond (2) if one is overloaded, others may respond faster.
A solution around this could be based on either (or both) of:
* Provide a configurable stagger timeout, e.g. 100ms. E.g., RPC to (random) Owner1.
Wait for timeout t. If no response, RPC to Owner2. etc.
* Always broadcast to a (configurable) subset of owners, e.g., always 2 even if numOwners
is 5.
Needs careful thought and design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:07 a.m.
New subject: [JBoss JIRA] (ISPN-825) Consider staggering remote get requests when using DIST
[
https://issues.jboss.org/browse/ISPN-825?page=com.atlassian.jira.plugin.s...
]
Mircea Markus commented on ISPN-825:
------------------------------------
Suggestion from Manik:
numInitialRemoteGets (default 1)
remoteGetTimeout (default 500ms? What's our average remote GET time anyway?)
So with this scheme, we'd:
* Randomly select 'numInitialRemoteGets' from dataOwners
* Send them the remote get
* After remoteGetTimeout, send a remote get to the next data owner, until we run out of
data owners
* Return the first valid response.
Consider staggering remote get requests when using DIST
-------------------------------------------------------
Key: ISPN-825
URL: https://issues.jboss.org/browse/ISPN-825
Project: Infinispan
Issue Type: Feature Request
Components: RPC
Affects Versions: 4.1.0.Final
Reporter: Manik Surtani
Assignee: Mircea Markus
Priority: Critical
Labels: optimization, performance
Fix For: 5.2.0.FINAL
In DIST mode, when a request is made on a key that is not mapped locally, a remote get is
sent to all data owners of that key and the first response is used. This can add
unnecessary load on the network as all nodes still eventually respond, and if values are
large this can cause a lot of unnecessary network traffic.
The purpose of broadcasting to all data owners is so that (1) if one is down, another
could still respond (2) if one is overloaded, others may respond faster.
A solution around this could be based on either (or both) of:
* Provide a configurable stagger timeout, e.g. 100ms. E.g., RPC to (random) Owner1.
Wait for timeout t. If no response, RPC to Owner2. etc.
* Always broadcast to a (configurable) subset of owners, e.g., always 2 even if numOwners
is 5.
Needs careful thought and design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:22 p.m.
New subject: [JBoss JIRA] (ISPN-825) Consider staggering remote get requests when using DIST
[
https://issues.jboss.org/browse/ISPN-825?page=com.atlassian.jira.plugin.s...
]
Mircea Markus updated ISPN-825:
-------------------------------
Priority: Major (was: Critical)
Consider staggering remote get requests when using DIST
-------------------------------------------------------
Key: ISPN-825
URL: https://issues.jboss.org/browse/ISPN-825
Project: Infinispan
Issue Type: Feature Request
Components: RPC
Affects Versions: 4.1.0.Final
Reporter: Manik Surtani
Assignee: Mircea Markus
Labels: optimization, performance
Fix For: 5.2.0.Final
In DIST mode, when a request is made on a key that is not mapped locally, a remote get is
sent to all data owners of that key and the first response is used. This can add
unnecessary load on the network as all nodes still eventually respond, and if values are
large this can cause a lot of unnecessary network traffic.
The purpose of broadcasting to all data owners is so that (1) if one is down, another
could still respond (2) if one is overloaded, others may respond faster.
A solution around this could be based on either (or both) of:
* Provide a configurable stagger timeout, e.g. 100ms. E.g., RPC to (random) Owner1.
Wait for timeout t. If no response, RPC to Owner2. etc.
* Always broadcast to a (configurable) subset of owners, e.g., always 2 even if numOwners
is 5.
Needs careful thought and design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:33 a.m.
New subject: [JBoss JIRA] (ISPN-825) Consider staggering remote get requests when using DIST
[
https://issues.jboss.org/browse/ISPN-825?page=com.atlassian.jira.plugin.s...
]
Mircea Markus updated ISPN-825:
-------------------------------
Fix Version/s: 6.0.0.Final
(was: 5.2.0.Final)
Consider staggering remote get requests when using DIST
-------------------------------------------------------
Key: ISPN-825
URL: https://issues.jboss.org/browse/ISPN-825
Project: Infinispan
Issue Type: Feature Request
Components: RPC
Affects Versions: 4.1.0.Final
Reporter: Manik Surtani
Assignee: Mircea Markus
Labels: optimization, performance
Fix For: 6.0.0.Final
In DIST mode, when a request is made on a key that is not mapped locally, a remote get is
sent to all data owners of that key and the first response is used. This can add
unnecessary load on the network as all nodes still eventually respond, and if values are
large this can cause a lot of unnecessary network traffic.
The purpose of broadcasting to all data owners is so that (1) if one is down, another
could still respond (2) if one is overloaded, others may respond faster.
A solution around this could be based on either (or both) of:
* Provide a configurable stagger timeout, e.g. 100ms. E.g., RPC to (random) Owner1.
Wait for timeout t. If no response, RPC to Owner2. etc.
* Always broadcast to a (configurable) subset of owners, e.g., always 2 even if numOwners
is 5.
Needs careful thought and design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4434
days inactive
5127
days old
infinispan-issues@lists.jboss.org
10 comments
4 participants
participants (4)
-
Galder Zamarreño (Updated) (JIRA) -
Manik Surtani (JIRA)
-
Manik Surtani (Updated) (JIRA)
-
Mircea Markus (JIRA)