[JBoss JIRA] (ISPN-5972) Number of entries not working correctly in cache statistics in mgmt console
by Pedro Zapata (JIRA)
[ https://issues.jboss.org/browse/ISPN-5972?page=com.atlassian.jira.plugin.... ]
Pedro Zapata reassigned ISPN-5972:
----------------------------------
Assignee: Pedro Ruivo (was: Pedro Zapata)
> Number of entries not working correctly in cache statistics in mgmt console
> ---------------------------------------------------------------------------
>
> Key: ISPN-5972
> URL: https://issues.jboss.org/browse/ISPN-5972
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.1.0.Beta1
> Reporter: Jiří Holuša
> Assignee: Pedro Ruivo
>
> Page: Caches -> select cache container -> select cache.
> Configuration of the cache: replicated cache, 2 nodes in the domain
> In the "Cache content" tab, there is a field "# Entries" which should probably show number of entries in the cache. When I put 100 entries in the cache, this field shows 200. Given that it's replicated cache, I think what's happening is that it shows numberOfNodes*numberOfEntries, because when I try to put 100 entries with 3 nodes in the domain, the "# Entries" shows 300.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-5972) Number of entries not working correctly in cache statistics in mgmt console
by Pedro Zapata (JIRA)
[ https://issues.jboss.org/browse/ISPN-5972?page=com.atlassian.jira.plugin.... ]
Pedro Zapata commented on ISPN-5972:
------------------------------------
I believe the console is showing the right DMR attribute (clusterwide-number-of-entries). The problem seems that for replicated caches it's calculated as number_of_entries x number_of_nodes. It needs to be fixed at the DMR level.
> Number of entries not working correctly in cache statistics in mgmt console
> ---------------------------------------------------------------------------
>
> Key: ISPN-5972
> URL: https://issues.jboss.org/browse/ISPN-5972
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.1.0.Beta1
> Reporter: Jiří Holuša
> Assignee: Pedro Zapata
>
> Page: Caches -> select cache container -> select cache.
> Configuration of the cache: replicated cache, 2 nodes in the domain
> In the "Cache content" tab, there is a field "# Entries" which should probably show number of entries in the cache. When I put 100 entries in the cache, this field shows 200. Given that it's replicated cache, I think what's happening is that it shows numberOfNodes*numberOfEntries, because when I try to put 100 entries with 3 nodes in the domain, the "# Entries" shows 300.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-6587) Eviction type does not chage after reconfiguring in console
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-6587?page=com.atlassian.jira.plugin.... ]
Ryan Emerson moved JDG-300 to ISPN-6587:
----------------------------------------
Project: Infinispan (was: JBoss Data Grid)
Key: ISPN-6587 (was: JDG-300)
Workflow: GIT Pull Request with Triage workflow (was: CDW with loose statuses v1)
Component/s: Console
(was: Management and Monitoring)
Affects Version/s: 9.0.0.Alpha1
(was: JDG 7.0.0 ER2)
Fix Version/s: (was: JDG 7.0.0 ER5)
> Eviction type does not chage after reconfiguring in console
> -----------------------------------------------------------
>
> Key: ISPN-6587
> URL: https://issues.jboss.org/browse/ISPN-6587
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 9.0.0.Alpha1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
>
> container -> cache -> configuration -> eviction -> eviction type
> "Type" was empty before.
> After changing it to COUNT or MEMORY and afterwards open the configuration page again to check if it was changed the "Type" remained empty.
> The JMX value was also not changed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-6586) Run ReadOnlyKeyCommand and ReadOnlyManyCommand on owner
by Radim Vansa (JIRA)
Radim Vansa created ISPN-6586:
---------------------------------
Summary: Run ReadOnlyKeyCommand and ReadOnlyManyCommand on owner
Key: ISPN-6586
URL: https://issues.jboss.org/browse/ISPN-6586
Project: Infinispan
Issue Type: Sub-task
Reporter: Radim Vansa
Assignee: Galder Zamarreño
Currently the remote value is fetched to origin and the function runs locally. That's not aligned with the idea of replicating only the operations, and suboptimal if the entry is bigger || more complex to marshall than the function return value.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-5806) Add transaction support for Functional API
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-5806?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on ISPN-5806:
-----------------------------------
Please see ISPN-6573, I have started to work on this [1], but I've underestimated the amount of work required.
[1] https://github.com/rvansa/infinispan/tree/ISPN-6573
> Add transaction support for Functional API
> ------------------------------------------
>
> Key: ISPN-5806
> URL: https://issues.jboss.org/browse/ISPN-5806
> Project: Infinispan
> Issue Type: Sub-task
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
>
> A local cache with batching enabled produces this:
> {code:java}
> java.lang.IllegalArgumentException: Cannot create a transactional
> context without a valid Transaction instance.
> at org.infinispan.context.TransactionalInvocationContextFactory.createInvocationContext(TransactionalInvocationContextFactory.java:69)
> at org.infinispan.context.TransactionalInvocationContextFactory.createInvocationContext(TransactionalInvocationContextFactory.java:63)
> at org.infinispan.functional.impl.ReadWriteMapImpl.eval(ReadWriteMapImpl.java:56)
> at org.infinispan.lucene.impl.FileListOperations.addFileName(FileListOperations.java:60)
> (<-- experimental uncommitted code here)
> {code}
> For single operations that carry no transaction context, don't try to start a transaction and create a transactional context.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months