[JBoss JIRA] (ISPN-7806) QueryInterceptor should not load entries from DC but context
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-7806?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on ISPN-7806:
-----------------------------------
I've created reproducers: https://github.com/rvansa/infinispan/tree/ISPN-7806
> QueryInterceptor should not load entries from DC but context
> ------------------------------------------------------------
>
> Key: ISPN-7806
> URL: https://issues.jboss.org/browse/ISPN-7806
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 9.0.0.Final
> Reporter: Radim Vansa
> Assignee: Gustavo Fernandes
>
> Currently in {{visitPrepareCommand}} the query interceptor is loading data directly from data container. That's wrong - if the entry is passivated/evicted, the previous value is incorrect.
> As the data is not loaded (from DC/persistence) at current QI position, we should move QueryInterceptor after EntryWrappingInterceptor, CacheLoaderInterceptor -and xDistributionInterceptor (which may load the data from remote node),- and load the previous entry from context instead. The same approach should be taken for non-tx command, rather than relying on their return value.
> **EDIT**: we should not move it below xDistributionInterceptor because on backup owner (which may be write-owner but not a read-owner) we would retrieve the updated value (affected by the current command), not the previous one.
> There will still be issues if the command has SKIP_CACHE_LOAD flag: I suggest warning message if it doesn't have SKIP_INDEXING flag as well.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (ISPN-7971) Display a warning that changes in standalone mode are not persisted
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7971?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-7971:
-------------------------------------------
Right, I agree [~ryanemerson]. In that case, I would say we postpone this issue until we have Openshift detection API.
> Display a warning that changes in standalone mode are not persisted
> -------------------------------------------------------------------
>
> Key: ISPN-7971
> URL: https://issues.jboss.org/browse/ISPN-7971
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Reporter: Sebastian Łaskawiec
> Assignee: Vladimir Blagojevic
> Attachments: Screen Shot 2017-07-26 at 9.45.27 AM.png
>
>
> The Infinispan Management Console can also operate in Standalone mode. We would like to make it accessible in OpenShift. However we should probably display a warning that the console should be used only for monitoring and none of the changes are persisted.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (ISPN-7971) Display a warning that changes in standalone mode are not persisted
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7971?page=com.atlassian.jira.plugin.... ]
Ryan Emerson commented on ISPN-7971:
------------------------------------
[~vblagojevic] The problem is that it is valid for a cache container's configuration to be updated in local standalone mode in non-openshift environments. So we don't want to tell users they can't perform a valid operation when they can, especially considering that our users at the moment will most likely be using infinispan on premise.
> Display a warning that changes in standalone mode are not persisted
> -------------------------------------------------------------------
>
> Key: ISPN-7971
> URL: https://issues.jboss.org/browse/ISPN-7971
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Reporter: Sebastian Łaskawiec
> Assignee: Vladimir Blagojevic
> Attachments: Screen Shot 2017-07-26 at 9.45.27 AM.png
>
>
> The Infinispan Management Console can also operate in Standalone mode. We would like to make it accessible in OpenShift. However we should probably display a warning that the console should be used only for monitoring and none of the changes are persisted.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (ISPN-7649) Administration console - transaction tab allows to set invalid options
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7649?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-7649.
--------------------------------
Fix Version/s: 9.1.1.Final
Resolution: Done
> Administration console - transaction tab allows to set invalid options
> ----------------------------------------------------------------------
>
> Key: ISPN-7649
> URL: https://issues.jboss.org/browse/ISPN-7649
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 9.0.0.CR3
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Fix For: 9.1.1.Final
>
>
> If a cache is set to distributed async mode, setting transactions to FULL_XA mode results in error after the cluster restart. The console shouldn't allow this combination.
> Suggested solution - dropdown should display only valid options for transaction mode for the given cache.
> (I'm not sure if this is the only invalid combination)
> Server error:
> ...
> org.infinispan.commons.CacheConfigurationException: ISPN000441: Unsupported async cache mode 'DIST_ASYNC' for transactional caches
> ...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (ISPN-7971) Display a warning that changes in standalone mode are not persisted
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7971?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-7971:
-------------------------------------------
I agree [~ryanemerson] but for the time being, it could be used in both standalone and openshift, no? Once we have Openshift detection mechanism in it is easy to adapt these dialogs. Either way, I am fine with either approach. Thoughts [~pzapataf]?
> Display a warning that changes in standalone mode are not persisted
> -------------------------------------------------------------------
>
> Key: ISPN-7971
> URL: https://issues.jboss.org/browse/ISPN-7971
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Reporter: Sebastian Łaskawiec
> Assignee: Vladimir Blagojevic
> Attachments: Screen Shot 2017-07-26 at 9.45.27 AM.png
>
>
> The Infinispan Management Console can also operate in Standalone mode. We would like to make it accessible in OpenShift. However we should probably display a warning that the console should be used only for monitoring and none of the changes are persisted.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (ISPN-7642) Administration console - remote sites are not displayed correctly on cache container page
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7642?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-7642.
--------------------------------
Fix Version/s: 9.1.1.Final
Resolution: Done
> Administration console - remote sites are not displayed correctly on cache container page
> -----------------------------------------------------------------------------------------
>
> Key: ISPN-7642
> URL: https://issues.jboss.org/browse/ISPN-7642
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 9.0.0.CR2
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Fix For: 9.1.1.Final
>
> Attachments: Screenshot-cacheContainer.png, Screenshot-detail-cache.png, clustered.xml
>
>
> Have 2 caches each configured with a different remote site.
> When you click on cache container, both remote sites are displayed on both cache cards. Clicking on a cache to see cache detail page shows correct remote site. Please see the attached screenshots.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months