[JBoss JIRA] (ISPN-9748) Default transport for the test suite should be same except if it was activated by another profile
by Diego Lovison (Jira)
Diego Lovison created ISPN-9748:
-----------------------------------
Summary: Default transport for the test suite should be same except if it was activated by another profile
Key: ISPN-9748
URL: https://issues.jboss.org/browse/ISPN-9748
Project: Infinispan
Issue Type: Bug
Affects Versions: 9.4.1.Final
Reporter: Diego Lovison
The pom.xml configuration should be:
{code:xml}
<default.transport.stack>udp</default.transport.stack>
<infinispan.test.jgroups.protocol>${default.transport.stack}</infinispan.test.jgroups.protocol>
<transport.stack>-Djboss.default.jgroups.stack=${infinispan.test.jgroups.protocol}</transport.stack>
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9699) Cluster member owning no data
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9699?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9699:
----------------------------------
Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Beta1 (was: Sprint 10.0.0.Alpha1)
> Cluster member owning no data
> -----------------------------
>
> Key: ISPN-9699
> URL: https://issues.jboss.org/browse/ISPN-9699
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 9.4.1.Final
> Reporter: Thomas Segismont
> Assignee: Katia Aresti
> Priority: Major
> Fix For: 10.0.0.Alpha2, 9.4.3.Final
>
>
> Currently, you can set {{capacity-factor}} to zero on a cache if you don't want a node to own any segment.
> If you want a node to own no data at all, you could set this property on all declared cached. But this wouldn't work for internal caches anyway (locks, counters).
> It would be nice to have a global switch.
> This would be useful when your app needs to be a cluster member for discovery/membership but is deployed mostly for processing. Indeed, when such nodes are added/removed from the cluster:
> * there would be no data loss
> * the cluster would be back in healthy state faster as no data would be moved around.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9708) Expose threadpool executors via JMX
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9708?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9708:
----------------------------------
Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Beta1 (was: Sprint 10.0.0.Alpha1)
> Expose threadpool executors via JMX
> -----------------------------------
>
> Key: ISPN-9708
> URL: https://issues.jboss.org/browse/ISPN-9708
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core, JMX, reporting and management, Server
> Affects Versions: 9.4.1.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 9.4.2.Final, 10.0.0.Alpha1
>
>
> We should expose executors over JMX so that threadpools can be monitored.
> This includes all the global threadpools as well as any protocol server thread pools.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months