[JBoss JIRA] (ISPN-9086) Improve logging of topology updates
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-9086?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-9086.
--------------------------------
Resolution: Done
> Improve logging of topology updates
> -----------------------------------
>
> Key: ISPN-9086
> URL: https://issues.jboss.org/browse/ISPN-9086
> Project: Infinispan
> Issue Type: Task
> Components: Core
> Affects Versions: 9.2.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 9.3.0.Beta1
>
>
> Rebalance confirmations are logged with the event logger, but topology updates aren't. It should be the other way around, because the number of confirmations grows with the cluster size, and the number of topology updates only depends on the number of caches and joiners/leavers.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (ISPN-8989) Administration console - Counters don't work in standalone mode
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-8989?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-8989.
--------------------------------
Fix Version/s: 9.3.0.Beta1
Resolution: Done
> Administration console - Counters don't work in standalone mode
> ---------------------------------------------------------------
>
> Key: ISPN-8989
> URL: https://issues.jboss.org/browse/ISPN-8989
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.2.0.Final
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Fix For: 9.3.0.Beta1
>
>
> start the server in standalone clustered mode:
> - bin/standalone.sh -c clustered.xml
> - click on cache container -> Counters tab -> Create new counter -> create counter e.g. (name: new, initial value 5)
> This results in error pop up:
> WFLYCTL0030: No resource definition is registered for address [ ("profile" => "standalone"), ("subsystem" => "datagrid-infinispan"), ("cache-container" => "clustered"), ("counters" => "COUNTERS") ]
> Please note that this works in domain mode.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (ISPN-8989) Administration console - Counters don't work in standalone mode
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-8989?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-8989:
-------------------------------
Sprint: Sprint 9.3.0.Beta1
> Administration console - Counters don't work in standalone mode
> ---------------------------------------------------------------
>
> Key: ISPN-8989
> URL: https://issues.jboss.org/browse/ISPN-8989
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.2.0.Final
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Fix For: 9.3.0.Beta1
>
>
> start the server in standalone clustered mode:
> - bin/standalone.sh -c clustered.xml
> - click on cache container -> Counters tab -> Create new counter -> create counter e.g. (name: new, initial value 5)
> This results in error pop up:
> WFLYCTL0030: No resource definition is registered for address [ ("profile" => "standalone"), ("subsystem" => "datagrid-infinispan"), ("cache-container" => "clustered"), ("counters" => "COUNTERS") ]
> Please note that this works in domain mode.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (ISPN-9113) SITE_UNREACHABLE not handled by JGroupsTransport
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-9113?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9113:
-------------------------------
Fix Version/s: 9.3.0.Beta1
> SITE_UNREACHABLE not handled by JGroupsTransport
> ------------------------------------------------
>
> Key: ISPN-9113
> URL: https://issues.jboss.org/browse/ISPN-9113
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication
> Affects Versions: 9.2.2.Final, 9.3.0.Alpha1
> Reporter: Galder Zamarreño
> Assignee: Dan Berindei
> Fix For: 9.3.0.Beta1
>
>
> If a user defineds a site with SYNC x-site replication and the site is unavailable, requests will timeout instead of quickly failing. See below for a summary discussion:
> {code}
> Galder: @Dan Berindei @Pedro Ruivo @Bela Ban Any thoughts on my dev thread?
> Galder: In essence, @Dan Berindei you made ChannelCallbacks implement UpHandler, but JChannel.invokeCallback()
> won't pass any events to receive instance variable because it doesn't check whether the receiver is UpHandler //cc @Tristan
> Bela Ban: @Galder yes, this won't work
> Bela Ban: @Galder You need to call RELAY2.setRouterStatusListener() directly
> Bela Ban: Implementing this as part of Receiver won't help
> Galder: Don't think RELAY2.setRouterStatusListener() is what I want - I can see RELAY2.handleMessage() passing up the
> stack Event.SITE_UNREACHABLE though, the problem is that there's no handler for that
> Bela Ban: @Galder Yes, but the SITE_UNREACHABLE event is only handled by RequestCorrelator, not by JChannel
> Galder: Ah ok, let me check what that does
> Bela Ban: The thing is that RequestCorrelator is not used anymore (AFAIK), as Infinispan moved from
> MessageDispatcher to JChannel
> Galder: the RequestCorrelator is never called
> Galder: exactly
> Bela Ban: So this is a regression caused by that move then
> Galder: Yeah, that's my feeling too. That's why I was asking Dan about the move to make ChannelCallbacks class an
> UpHandler, because I noticed that happened when the move to JChannel happened
> Galder: The impact of this is the following: if any site in SYNC and the site is unreachable, you'd get a timeout eventually
> instead of a immediate failure
> Galder: I'm trying to implement auto x-site state transfer for protobuf metadata cache and I cannot do it until this is fixed
> Galder: I'll see if I can get something working with ASYNC, but ASYNC is not a good option for protobuf metadata.
> If a node does not succesfully get it, it won't be able to work properly
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (ISPN-9113) SITE_UNREACHABLE not handled by JGroupsTransport
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-9113?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9113:
-------------------------------
Status: Open (was: New)
> SITE_UNREACHABLE not handled by JGroupsTransport
> ------------------------------------------------
>
> Key: ISPN-9113
> URL: https://issues.jboss.org/browse/ISPN-9113
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication
> Affects Versions: 9.2.2.Final, 9.3.0.Alpha1
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
>
> If a user defineds a site with SYNC x-site replication and the site is unavailable, requests will timeout instead of quickly failing. See below for a summary discussion:
> {code}
> Galder: @Dan Berindei @Pedro Ruivo @Bela Ban Any thoughts on my dev thread?
> Galder: In essence, @Dan Berindei you made ChannelCallbacks implement UpHandler, but JChannel.invokeCallback()
> won't pass any events to receive instance variable because it doesn't check whether the receiver is UpHandler //cc @Tristan
> Bela Ban: @Galder yes, this won't work
> Bela Ban: @Galder You need to call RELAY2.setRouterStatusListener() directly
> Bela Ban: Implementing this as part of Receiver won't help
> Galder: Don't think RELAY2.setRouterStatusListener() is what I want - I can see RELAY2.handleMessage() passing up the
> stack Event.SITE_UNREACHABLE though, the problem is that there's no handler for that
> Bela Ban: @Galder Yes, but the SITE_UNREACHABLE event is only handled by RequestCorrelator, not by JChannel
> Galder: Ah ok, let me check what that does
> Bela Ban: The thing is that RequestCorrelator is not used anymore (AFAIK), as Infinispan moved from
> MessageDispatcher to JChannel
> Galder: the RequestCorrelator is never called
> Galder: exactly
> Bela Ban: So this is a regression caused by that move then
> Galder: Yeah, that's my feeling too. That's why I was asking Dan about the move to make ChannelCallbacks class an
> UpHandler, because I noticed that happened when the move to JChannel happened
> Galder: The impact of this is the following: if any site in SYNC and the site is unreachable, you'd get a timeout eventually
> instead of a immediate failure
> Galder: I'm trying to implement auto x-site state transfer for protobuf metadata cache and I cannot do it until this is fixed
> Galder: I'll see if I can get something working with ASYNC, but ASYNC is not a good option for protobuf metadata.
> If a node does not succesfully get it, it won't be able to work properly
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (ISPN-9113) SITE_UNREACHABLE not handled by JGroupsTransport
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-9113?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9113:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/5958
> SITE_UNREACHABLE not handled by JGroupsTransport
> ------------------------------------------------
>
> Key: ISPN-9113
> URL: https://issues.jboss.org/browse/ISPN-9113
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication
> Affects Versions: 9.2.2.Final, 9.3.0.Alpha1
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
>
> If a user defineds a site with SYNC x-site replication and the site is unavailable, requests will timeout instead of quickly failing. See below for a summary discussion:
> {code}
> Galder: @Dan Berindei @Pedro Ruivo @Bela Ban Any thoughts on my dev thread?
> Galder: In essence, @Dan Berindei you made ChannelCallbacks implement UpHandler, but JChannel.invokeCallback()
> won't pass any events to receive instance variable because it doesn't check whether the receiver is UpHandler //cc @Tristan
> Bela Ban: @Galder yes, this won't work
> Bela Ban: @Galder You need to call RELAY2.setRouterStatusListener() directly
> Bela Ban: Implementing this as part of Receiver won't help
> Galder: Don't think RELAY2.setRouterStatusListener() is what I want - I can see RELAY2.handleMessage() passing up the
> stack Event.SITE_UNREACHABLE though, the problem is that there's no handler for that
> Bela Ban: @Galder Yes, but the SITE_UNREACHABLE event is only handled by RequestCorrelator, not by JChannel
> Galder: Ah ok, let me check what that does
> Bela Ban: The thing is that RequestCorrelator is not used anymore (AFAIK), as Infinispan moved from
> MessageDispatcher to JChannel
> Galder: the RequestCorrelator is never called
> Galder: exactly
> Bela Ban: So this is a regression caused by that move then
> Galder: Yeah, that's my feeling too. That's why I was asking Dan about the move to make ChannelCallbacks class an
> UpHandler, because I noticed that happened when the move to JChannel happened
> Galder: The impact of this is the following: if any site in SYNC and the site is unreachable, you'd get a timeout eventually
> instead of a immediate failure
> Galder: I'm trying to implement auto x-site state transfer for protobuf metadata cache and I cannot do it until this is fixed
> Galder: I'll see if I can get something working with ASYNC, but ASYNC is not a good option for protobuf metadata.
> If a node does not succesfully get it, it won't be able to work properly
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (ISPN-9113) SITE_UNREACHABLE not handled by JGroupsTransport
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-9113?page=com.atlassian.jira.plugin.... ]
Dan Berindei reassigned ISPN-9113:
----------------------------------
Assignee: Dan Berindei (was: Galder Zamarreño)
> SITE_UNREACHABLE not handled by JGroupsTransport
> ------------------------------------------------
>
> Key: ISPN-9113
> URL: https://issues.jboss.org/browse/ISPN-9113
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication
> Affects Versions: 9.2.2.Final, 9.3.0.Alpha1
> Reporter: Galder Zamarreño
> Assignee: Dan Berindei
>
> If a user defineds a site with SYNC x-site replication and the site is unavailable, requests will timeout instead of quickly failing. See below for a summary discussion:
> {code}
> Galder: @Dan Berindei @Pedro Ruivo @Bela Ban Any thoughts on my dev thread?
> Galder: In essence, @Dan Berindei you made ChannelCallbacks implement UpHandler, but JChannel.invokeCallback()
> won't pass any events to receive instance variable because it doesn't check whether the receiver is UpHandler //cc @Tristan
> Bela Ban: @Galder yes, this won't work
> Bela Ban: @Galder You need to call RELAY2.setRouterStatusListener() directly
> Bela Ban: Implementing this as part of Receiver won't help
> Galder: Don't think RELAY2.setRouterStatusListener() is what I want - I can see RELAY2.handleMessage() passing up the
> stack Event.SITE_UNREACHABLE though, the problem is that there's no handler for that
> Bela Ban: @Galder Yes, but the SITE_UNREACHABLE event is only handled by RequestCorrelator, not by JChannel
> Galder: Ah ok, let me check what that does
> Bela Ban: The thing is that RequestCorrelator is not used anymore (AFAIK), as Infinispan moved from
> MessageDispatcher to JChannel
> Galder: the RequestCorrelator is never called
> Galder: exactly
> Bela Ban: So this is a regression caused by that move then
> Galder: Yeah, that's my feeling too. That's why I was asking Dan about the move to make ChannelCallbacks class an
> UpHandler, because I noticed that happened when the move to JChannel happened
> Galder: The impact of this is the following: if any site in SYNC and the site is unreachable, you'd get a timeout eventually
> instead of a immediate failure
> Galder: I'm trying to implement auto x-site state transfer for protobuf metadata cache and I cannot do it until this is fixed
> Galder: I'll see if I can get something working with ASYNC, but ASYNC is not a good option for protobuf metadata.
> If a node does not succesfully get it, it won't be able to work properly
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (ISPN-9002) LocalModeNoPassivationTest.testValuesWithEvictedEntries random failures
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-9002?page=com.atlassian.jira.plugin.... ]
Radim Vansa updated ISPN-9002:
------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> LocalModeNoPassivationTest.testValuesWithEvictedEntries random failures
> -----------------------------------------------------------------------
>
> Key: ISPN-9002
> URL: https://issues.jboss.org/browse/ISPN-9002
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 9.2.0.Final
> Reporter: Dan Berindei
> Assignee: William Burns
> Labels: testsuite_stability
> Fix For: 9.3.0.Beta1
>
> Attachments: LocalModeNoPassivationTest_ISPN-8962_preferavailabilitystrategy_20180327.log.gz
>
>
> {noformat}
> 12:59:16,370 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.persistence.LocalModeNoPassivationTest.testValuesWithEvictedEntries
> java.lang.AssertionError: Value: 247 was not found!
> at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.9.9.jar:?]
> at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24) ~[testng-6.9.9.jar:?]
> at org.infinispan.persistence.LocalModePassivationTest.testValuesWithEvictedEntries(LocalModePassivationTest.java:203) ~[test-classes/:?]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (ISPN-9002) LocalModeNoPassivationTest.testValuesWithEvictedEntries random failures
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-9002?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-9002:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/5957
> LocalModeNoPassivationTest.testValuesWithEvictedEntries random failures
> -----------------------------------------------------------------------
>
> Key: ISPN-9002
> URL: https://issues.jboss.org/browse/ISPN-9002
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 9.2.0.Final
> Reporter: Dan Berindei
> Assignee: William Burns
> Labels: testsuite_stability
> Fix For: 9.3.0.Beta1
>
> Attachments: LocalModeNoPassivationTest_ISPN-8962_preferavailabilitystrategy_20180327.log.gz
>
>
> {noformat}
> 12:59:16,370 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.persistence.LocalModeNoPassivationTest.testValuesWithEvictedEntries
> java.lang.AssertionError: Value: 247 was not found!
> at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.9.9.jar:?]
> at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24) ~[testng-6.9.9.jar:?]
> at org.infinispan.persistence.LocalModePassivationTest.testValuesWithEvictedEntries(LocalModePassivationTest.java:203) ~[test-classes/:?]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years