[JBoss JIRA] (JGRP-1428) UnicastRequest and GroupRequest should mark a target as suspected if the target has already left the cluster at creation time
11:19 a.m.
Dan Berindei created JGRP-1428:
----------------------------------
Summary: UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Fix For: 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark its
response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
2:47 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
Bela Ban updated JGRP-1428:
---------------------------
Fix Version/s: 3.0.6
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Fix For: 3.0.6, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
5:11 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
Manik Surtani updated JGRP-1428:
--------------------------------
Priority: Critical (was: Major)
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.6, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
5:58 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1428:
--------------------------------
Use case:
- The view is {A,B,C,D}
- A invokes a group request on the cluster
- The GroupRequest is created with targets A, B, C and D
- In RequestCorrelator.sendRequest(), we add the request to the requests hashmap: whenever
a view is received, we mark non-members in the request as suspected and potentially cause
the request to return (if it is blocking)
- However, if a new view {A,B,C} is received *after* creation of the request, but *before*
the request is registered for view changes, the request will *not* mark D in its requests
hashmap as suspected
--> The request will block until (1) another view change (e.g. {A,B,C,F}) is received
or (2) until it times out
SOLUTION:
- In RequestCorrelator.sendRequest(), after registering the request for view changes, we
simply call Request.viewChange(View) with the current view. This will cause D to be marked
as suspected
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.6, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
6:29 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
Bela Ban resolved JGRP-1428.
----------------------------
Resolution: Done
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.6, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
3:04 p.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
Dan Berindei reopened JGRP-1428:
--------------------------------
We have reproduced the issue again with JGroups 3.0.6 and 500 threads doing unicast
requests at the time of the leave.
The problem could be that RequestCorrelator first runs the suspect check on all requests
and only then updates the view reference. Since the ConcurrentHashMap iterator ignores
updates, it's possible for our request thread to add the request to the map and check
the view membership between the start of the iteration and the view update.
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.6, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
4:32 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration updated JGRP-1428:
------------------------------------------
Bugzilla Update: Perform
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.6, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
4:32 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration updated JGRP-1428:
------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=801734
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.6, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
4:32 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on JGRP-1428:
-----------------------------------------------
Michal Linhard <mlinhard(a)redhat.com> made a comment on [bug
801734|https://bugzilla.redhat.com/show_bug.cgi?id=801734]
JGRP-1428 was probably meant instead of JGRP-1424.
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.6, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
6:23 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1428:
--------------------------------
After the request is created, even if it misses the new view installed at the same time
the request is added, it will get called viewChange(), so its membership should be
correct. After this, view change notifications will be handled the normal way.
Can you show me a timing scenario which causes a request to have an incorrect target set
?
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.6, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
7:09 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
Bela Ban updated JGRP-1428:
---------------------------
Fix Version/s: 3.0.7
(was: 3.0.6)
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=801734 (was:
https://bugzilla.redhat.com/show_bug.cgi?id=801734)
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.7, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
7:27 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1428:
--------------------------------
Here's a scenario which could still reproduce the bug:
- The current view is is V1
- RequestCorrelator.receiveView() installs a new view V2 and starts iterating over
requests
- A new Request is added to 'requests'. Because the iterator above iterates on a
ConcurrentHashmap, it will iterate over a copy and *not* call viewChange(V2) on the
request !
- RequestCorrelator.send(Unicast)Request() now calls viewChange(V1) on the request. V1 is
used because the assignment of V2 to RequestCorrelator.view has *not* yet happened !
- RequestCorrelator.receiveView() now assigns V2 to this.view
--> In this scenario, we do *not* call viewChange(V2) on the request, but only use the
old view V1 !
==> Moving the assignment of V2 to this.view *before* the iteration should fix the
issue
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.7, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
7:29 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
Bela Ban resolved JGRP-1428.
----------------------------
Resolution: Done
Feel free to re-open should the issue persist
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.7, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
7:40 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on JGRP-1428:
-----------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
801734|https://bugzilla.redhat.com/show_bug.cgi?id=801734]
Bela Ban <bela(a)jboss.com> made a comment on jira JGRP-1428
After the request is created, even if it misses the new view installed at the same time
the request is added, it will get called viewChange(), so its membership should be
correct. After this, view change notifications will be handled the normal way.
Can you show me a timing scenario which causes a request to have an incorrect target set
?
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.7, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
7:40 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on JGRP-1428:
-----------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
801734|https://bugzilla.redhat.com/show_bug.cgi?id=801734]
Bela Ban <bela(a)jboss.com> made a comment on jira JGRP-1428
Here's a scenario which could still reproduce the bug:
- The current view is is V1
- RequestCorrelator.receiveView() installs a new view V2 and starts iterating over
requests
- A new Request is added to 'requests'. Because the iterator above iterates on a
ConcurrentHashmap, it will iterate over a copy and *not* call viewChange(V2) on the
request !
- RequestCorrelator.send(Unicast)Request() now calls viewChange(V1) on the request. V1 is
used because the assignment of V2 to RequestCorrelator.view has *not* yet happened !
- RequestCorrelator.receiveView() now assigns V2 to this.view
--> In this scenario, we do *not* call viewChange(V2) on the request, but only use the
old view V1 !
==> Moving the assignment of V2 to this.view *before* the iteration should fix the
issue
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.7, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
7:40 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on JGRP-1428:
-----------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
801734|https://bugzilla.redhat.com/show_bug.cgi?id=801734]
Bela Ban <bela(a)jboss.com> made a comment on jira JGRP-1428
Feel free to re-open should the issue persist
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.7, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
7:40 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on JGRP-1428:
-----------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
801734|https://bugzilla.redhat.com/show_bug.cgi?id=801734]
Bela Ban <bela(a)jboss.com> updated the status of jira JGRP-1428 to Resolved
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.7, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
7:40 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on JGRP-1428:
-----------------------------------------------
Dan Berindei <dberinde(a)redhat.com> made a comment on [bug
801734|https://bugzilla.redhat.com/show_bug.cgi?id=801734]
I created ISPN-1904 to upgrade Infinispan to JGroups 3.0.7.
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.7, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
4:12 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on JGRP-1428:
-----------------------------------------------
Michal Linhard <mlinhard(a)redhat.com> made a comment on [bug
801734|https://bugzilla.redhat.com/show_bug.cgi?id=801734]
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.7, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
4:14 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on JGRP-1428:
-----------------------------------------------
Michal Linhard <mlinhard(a)redhat.com> changed the Status of [bug
801734|https://bugzilla.redhat.com/show_bug.cgi?id=801734] from NEW to VERIFIED
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.7, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
4:14 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on JGRP-1428:
-----------------------------------------------
Michal Linhard <mlinhard(a)redhat.com> made a comment on [bug
801734|https://bugzilla.redhat.com/show_bug.cgi?id=801734]
http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-RESILIENCE/j...
In ER4 the state transfer no longer takes 1min.
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.7, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
4:40 a.m.
[
https://issues.jboss.org/browse/JGRP-1428?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on JGRP-1428:
-----------------------------------------------
Michal Linhard <mlinhard(a)redhat.com> made a comment on [bug
801734|https://bugzilla.redhat.com/show_bug.cgi?id=801734]
Another confirmation of this is 4node elasticity test on hyperion:
http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-QE/job/edg-60-resili...
http://www.qa.jboss.com/~mlinhard/hyperion/run27-elasticity4/report/stats...
UnicastRequest and GroupRequest should mark a target as suspected if
the target has already left the cluster at creation time
-----------------------------------------------------------------------------------------------------------------------------
Key: JGRP-1428
URL: https://issues.jboss.org/browse/JGRP-1428
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.5, 3.1
Reporter: Dan Berindei
Assignee: Bela Ban
Priority: Critical
Fix For: 3.0.7, 3.1
UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark
its response as "suspected".
However, if the node has already left the cluster by the time the request is created, its
response is not marked as "suspected" and the request never properly finishes.
--
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
4620
days inactive
4642
days old
21 comments
4 participants
participants (4)
-
Bela Ban (JIRA) -
Dan Berindei (JIRA)
-
Manik Surtani (JIRA)
-
RH Bugzilla Integration (JIRA)