[JBoss JIRA] (ISPN-8670) Add a configuration storage for standalone servers
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-8670:
-------------------------------------
Summary: Add a configuration storage for standalone servers
Key: ISPN-8670
URL: https://issues.jboss.org/browse/ISPN-8670
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Server
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 9.2.0.Final
Introduce a configuration storage that can store permanent caches in the server model for standalone deployments.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-8669) Cache created from RemoteCacheManagerAdmin is not appearing in Administration Console
by Diego Lovison (JIRA)
Diego Lovison created ISPN-8669:
-----------------------------------
Summary: Cache created from RemoteCacheManagerAdmin is not appearing in Administration Console
Key: ISPN-8669
URL: https://issues.jboss.org/browse/ISPN-8669
Project: Infinispan
Issue Type: Feature Request
Components: Console
Reporter: Diego Lovison
Priority: Minor
Create a Hot Rod client and call the method *createCache* using the following example.
{code:java}
Cache<String, String> myCache = manager.administration().createCache("myCache", "myTemplate");
{code}
Open the Administration Console, it is not possible see the cache "myCache".
Additional Info:
The issue is occurring in standalone and domain mode.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-8558) Administration console - some events are not displayed in the console
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-8558?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic edited comment on ISPN-8558 at 1/10/18 4:57 AM:
--------------------------------------------------------------------
[~rmacor] Let's do the following, you will be able to diagnose in under 5 minutes if the DMR and server.log are consistent. Log into CLI for the server running in domain mode, and the go to runtime path of the coordintor, in the case below, that's server-one:
{code}
[domain@localhost:9990 /] pwd
/
[domain@localhost:9990 /] cd /host=master/server=server-one/subsystem=datagrid-infinispan/cache-container=clustered
[domain@localhost:9990 cache-container=clustered] :read-event-log(lines=1)
{
"outcome" => "success",
"result" => [{
"when" => "2018-01-10T09:43:13.314Z",
"level" => "INFO",
"category" => "CLUSTER",
"message" => "ISPN100003: Node master:server-one finished rebalance phase with topology id 4",
"context" => "___hotRodTopologyCache",
"scope" => "master:server-one"
}]
}
[domain@localhost:9990 cache-container=clustered]
{code}
Obviously, in your case, just increase the number of lines to some larger number, capture the output and then compare it either visually or through some diff tool with server log.
was (Author: vblagojevic):
[~rmacor] Let's do the following, you will be able to diagnose in under 5 minutes if the DMR and server.log are consistent. Log into CLI for the server running in domain mode, and the go to runtime path of the coordintor, in the case below, that's server-one:
{code}
[domain@localhost:9990 /] pwd
/
[domain@localhost:9990 /] cd /host=master/server=server-one/subsystem=datagrid-infinispan/cache-container=clustered
[domain@localhost:9990 cache-container=clustered] :read-event-log(lines=1)
{
"outcome" => "success",
"result" => [{
"when" => "2018-01-10T09:43:13.314Z",
"level" => "INFO",
"category" => "CLUSTER",
"message" => "ISPN100003: Node master:server-one finished rebalance phase with topology id 4",
"context" => "___hotRodTopologyCache",
"scope" => "master:server-one"
}]
}
[domain@localhost:9990 cache-container=clustered]
{code}
> Administration console - some events are not displayed in the console
> ---------------------------------------------------------------------
>
> Key: ISPN-8558
> URL: https://issues.jboss.org/browse/ISPN-8558
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.2.0.Beta1
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
>
> Some events are not displayed in the console.
> e.g.
> I see events in the server log, but not in the status event tab in the console:
> 10 INFO [org.infinispan.CLUSTER] (transport-thread--p4-t24) [Context=___query_known_classes][Context=master:server-one]ISPN100003: Node master:server-one finished rebalance phase with topology id 12
> [Server:server-one] 11:06:08,011 INFO [org.infinispan.CLUSTER] (remote-thread--p2-t24) [Context=___query_known_classes][Context=master:server-two]ISPN100003: Node master:server-two finished rebalance phase with topology id 12
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-8558) Administration console - some events are not displayed in the console
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-8558?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-8558:
-------------------------------------------
[~rmacor] Let's do the following, you will be able to diagnose in under 5 minutes if the DMR and server.log are consistent. Log into CLI for the server running in domain mode, and the go to runtime path of the coordintor, in the case below, that's server-one:
{code}
[domain@localhost:9990 /] pwd
/
[domain@localhost:9990 /] cd /host=master/server=server-one/subsystem=datagrid-infinispan/cache-container=clustered
[domain@localhost:9990 cache-container=clustered] :read-event-log(lines=1)
{
"outcome" => "success",
"result" => [{
"when" => "2018-01-10T09:43:13.314Z",
"level" => "INFO",
"category" => "CLUSTER",
"message" => "ISPN100003: Node master:server-one finished rebalance phase with topology id 4",
"context" => "___hotRodTopologyCache",
"scope" => "master:server-one"
}]
}
[domain@localhost:9990 cache-container=clustered]
{code}
> Administration console - some events are not displayed in the console
> ---------------------------------------------------------------------
>
> Key: ISPN-8558
> URL: https://issues.jboss.org/browse/ISPN-8558
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.2.0.Beta1
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
>
> Some events are not displayed in the console.
> e.g.
> I see events in the server log, but not in the status event tab in the console:
> 10 INFO [org.infinispan.CLUSTER] (transport-thread--p4-t24) [Context=___query_known_classes][Context=master:server-one]ISPN100003: Node master:server-one finished rebalance phase with topology id 12
> [Server:server-one] 11:06:08,011 INFO [org.infinispan.CLUSTER] (remote-thread--p2-t24) [Context=___query_known_classes][Context=master:server-two]ISPN100003: Node master:server-two finished rebalance phase with topology id 12
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-8668) Template configuration should be replicated across the cluster in standalone mode
by Diego Lovison (JIRA)
Diego Lovison created ISPN-8668:
-----------------------------------
Summary: Template configuration should be replicated across the cluster in standalone mode
Key: ISPN-8668
URL: https://issues.jboss.org/browse/ISPN-8668
Project: Infinispan
Issue Type: Feature Request
Reporter: Diego Lovison
Priority: Minor
Create a cluster with 3 servers in standalone mode.
You can create a cluster executing the following command:
./standalone.sh -Djboss.socket.binding.port-offset=100 -Djboss.node.name=nodeA -c clustered.xml
./standalone.sh -Djboss.socket.binding.port-offset=200 -Djboss.node.name=nodeB -c clustered.xml
./standalone.sh -Djboss.socket.binding.port-offset=300 -Djboss.node.name=nodeC -c clustered.xml
Open the Web Console on the nodeA and create a template configuration.
The template configuration will not be replicated to nodeB and nodeC.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-8667) EncoderCache.withWrapping(Class) is not implemented
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-8667?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes reassigned ISPN-8667:
---------------------------------------
Assignee: Gustavo Fernandes
> EncoderCache.withWrapping(Class) is not implemented
> ---------------------------------------------------
>
> Key: ISPN-8667
> URL: https://issues.jboss.org/browse/ISPN-8667
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.2.0.Beta2, 9.1.4.Final
> Reporter: William Burns
> Assignee: Gustavo Fernandes
>
> The EncoderCache.withWrapping(Class) method falls back to the AbstractDelegatingAdvancedCache which causes it to always supply the previous encoding and wrapping, completely ignoring the wrapping supplied. The EncoderCache.withWrapping(Class, Class) is properly implemented and works as it should.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-8667) EncoderCache.withWrapping(Class) is not implemented
by William Burns (JIRA)
William Burns created ISPN-8667:
-----------------------------------
Summary: EncoderCache.withWrapping(Class) is not implemented
Key: ISPN-8667
URL: https://issues.jboss.org/browse/ISPN-8667
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 9.1.4.Final, 9.2.0.Beta2
Reporter: William Burns
The EncoderCache.withWrapping(Class) method falls back to the AbstractDelegatingAdvancedCache which causes it to always supply the previous encoding and wrapping, completely ignoring the wrapping supplied. The EncoderCache.withWrapping(Class, Class) is properly implemented and works as it should.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-8666) Off Heap Data Container compute doesn't present expired entries
by William Burns (JIRA)
William Burns created ISPN-8666:
-----------------------------------
Summary: Off Heap Data Container compute doesn't present expired entries
Key: ISPN-8666
URL: https://issues.jboss.org/browse/ISPN-8666
Project: Infinispan
Issue Type: Bug
Components: Off Heap
Affects Versions: 9.1.4.Final, 9.2.0.Beta2
Reporter: William Burns
With ISPN-8500 we no longer return expired entries from the data container. This change also affected compute method on the Data Container. The DataContainer method should always present expired entries as stated in its documentation. This is causing issues with notifications and others when an entry expires as it seems it was never there to begin with.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-8665) MergePolicyPreferredAlwaysTest.testPartitionMergePolicy[DIST_SYNC, 3N] Fails
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-8665?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-8665:
-------------------------------
Fix Version/s: 9.2.0.CR1
> MergePolicyPreferredAlwaysTest.testPartitionMergePolicy[DIST_SYNC, 3N] Fails
> ----------------------------------------------------------------------------
>
> Key: ISPN-8665
> URL: https://issues.jboss.org/browse/ISPN-8665
> Project: Infinispan
> Issue Type: Task
> Components: Test Suite - Core
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Fix For: 9.2.0.CR1
>
>
> {code}
> java.lang.AssertionError: Key=MagicKey{8F0/AE75082F/115@MergePolicyPreferredAlwaysTest[DIST_SYNC, 3N]-NodeA-52162}. VersionMap: {MergePolicyPreferredAlwaysTest[DIST_SYNC, 3N]-NodeC-13208=ImmortalCacheValue {value=DURING SPLIT}, MergePolicyPreferredAlwaysTest[DIST_SYNC, 3N]-NodeA-52162=ImmortalCacheValue {value=DURING SPLIT}} expected:<BEFORE SPLIT> but was:<DURING SPLIT>
> at org.infinispan.conflict.impl.BaseMergePolicyTest.afterConflictResolutionAndMerge(BaseMergePolicyTest.java:109)
> at org.infinispan.conflict.impl.BaseMergePolicyTest.testPartitionMergePolicy(BaseMergePolicyTest.java:132)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ... Removed 19 stack frames
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months