#2184
- Created on2012-06-05 13:04
- Reported by
- StatusFixed
- PriorityNormal (3)
- Assigned to
- Milestone
- Plan Level-
- Due Date-
Test a node that is UP and joins again
What should happen here?
Leave a comment
on 2012-06-05 17:12 *
By Jonas Bonér
If the node is already a member of the cluster then JOIN should be a no-op.
on 2012-06-07 13:11 *
By Patrik Nordwall
Assigned to set to Patrik Nordwall
Status changed from New to Accepted
When looking at another thing I saw that this is not a no-op. I will fix.
on 2012-06-07 13:45 *
By Patrik Nordwall
(In revision:dbac17621f80d62e7cd9aa0d4adbc964ad2e82a6) Node that joins again should be ignored, see #2184
Branch: wip-2184-join-again-patriknw
Branch: wip-2184-join-again-patriknw
on 2012-06-07 15:14 *
By Patrik Nordwall
(In revision:dbac17621f80d62e7cd9aa0d4adbc964ad2e82a6) Node that joins again should be ignored, see #2184
Branch: master
Branch: master
on 2012-06-07 15:14 *
By Patrik Nordwall
(In revision:bd979a8845c6d26cfaf7a9600ad3aa630c0a438d) Merge pull request #522 from akka/wip-2184-join-again-patriknw
Node that joins again should be ignored, see #2184
Branch: master
Node that joins again should be ignored, see #2184
Branch: master
Updating tickets (#620, #679, #725, #750, #752, #753, #754, #763, #789, #870, #893, #922, #953, #954, #971, #977, #983, #985, #987, #991, #1026, #1045, #1051, #1060, #1061, #1084, #1098, #1099, #1133, #1134, #1135, #1136, #1137, #1194, #1225, #1226, #1243, #1245, #1247, #1248, #1254, #1261, #1300, #1317, #1391, #1412, #1791, #1793, #1901, #1908, #1911, #1912, #1913, #1914, #1915, #1916, #1917, #1922, #1983, #1987, #1996, #1997, #1998, #2066, #2077, #2105, #2117, #2133, #2143, #2149, #2151, #2152, #2153, #2155, #2157, #2158, #2159, #2160, #2161, #2162, #2163, #2164, #2165, #2167, #2171, #2175, #2176, #2177, #2180, #2182, #2184, #2185, #2193, #2199, #2202, #2204, #2206, #2207, #2209, #2210)