[JBoss JIRA] (ISPN-6596) get and remove don't understand the --codec switch
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-6596:
-------------------------------------
Summary: get and remove don't understand the --codec switch
Key: ISPN-6596
URL: https://issues.jboss.org/browse/ISPN-6596
Project: Infinispan
Issue Type: Bug
Components: CLI, Server
Affects Versions: 9.0.0.Alpha1, 8.2.1.Final
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 9.0.0.Alpha2, 9.0.0.Final
The get and remove CLI operations in the server should understand the --codec argument but instead print out "Unrecognized arguments: [--codec]"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ISPN-6104) Cache.Purge issues
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6104?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant commented on ISPN-6104:
---------------------------------------
Purge doesn't exist anymore: it has been renamed to "flush" and its purpose is to ensure that data is safely flushed to the cache store.
The only required change is to remove/disable the entry if the cache doesn't have a configured store.
> Cache.Purge issues
> ------------------
>
> Key: ISPN-6104
> URL: https://issues.jboss.org/browse/ISPN-6104
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.1.0.Final
> Reporter: Martin Gencur
> Assignee: Vladimir Blagojevic
> Priority: Optional
>
> Currently, there are the following issues with the "Purge cache data" button:
> 1) The Purge operation only copies entries to the cache store, it does not remove the from the cache itself. So the cache remains full. Checked with cache.withFlags(Flag.SKIP_CACHE_LOAD).get() after I performed the Purge operation and still got the entries. The JMX stats also display entries in the cache.
> 2) The button is available even though the cache is attached to the remote endpoint and hence available to clients. It should only be available after the cache is detached from the endpoint.
> 3) The confirmation dialog for the operation always says "Purging cache xyCache will passivate all its cache entries." even though there's no cache store defined for the cache. This might lead users to expectations that their data will be stored somewhere. But if there's no cache store, the data will be lost. In this case, it would be better to show a warning that their data will be lost after performing the operation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ISPN-6104) Cache.Purge issues
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6104?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-6104:
-------------------------------------
Assignee: Vladimir Blagojevic (was: Tristan Tarrant)
> Cache.Purge issues
> ------------------
>
> Key: ISPN-6104
> URL: https://issues.jboss.org/browse/ISPN-6104
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.1.0.Final
> Reporter: Martin Gencur
> Assignee: Vladimir Blagojevic
> Priority: Optional
>
> Currently, there are the following issues with the "Purge cache data" button:
> 1) The Purge operation only copies entries to the cache store, it does not remove the from the cache itself. So the cache remains full. Checked with cache.withFlags(Flag.SKIP_CACHE_LOAD).get() after I performed the Purge operation and still got the entries. The JMX stats also display entries in the cache.
> 2) The button is available even though the cache is attached to the remote endpoint and hence available to clients. It should only be available after the cache is detached from the endpoint.
> 3) The confirmation dialog for the operation always says "Purging cache xyCache will passivate all its cache entries." even though there's no cache store defined for the cache. This might lead users to expectations that their data will be stored somewhere. But if there's no cache store, the data will be lost. In this case, it would be better to show a warning that their data will be lost after performing the operation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ISPN-6316) Expiration data (lifespan, max-idle, interval) is empty in cachce configuration
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-6316?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-6316:
-------------------------------------------
[~mvrabel] Maybe defaults changed and are not present anymore by default. I created a new template from cache container configurations page, edited expiration values, and saved the template. Once templated is used these values are shown. To me, it seems like everything is ok. Would you please try it out with latest master. And let me know if and how it does not work for you!
> Expiration data (lifespan,max-idle,interval) is empty in cachce configuration
> -----------------------------------------------------------------------------
>
> Key: ISPN-6316
> URL: https://issues.jboss.org/browse/ISPN-6316
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Reporter: Martin Vrabel
> Assignee: Vladimir Blagojevic
>
> <cluster> -> <cache> -> "actions" -> "View configuration" -> "expiration" tab.
> lifespan max-idle interval is empty.
> It worked 1-2 weeks ago.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ISPN-6531) when editing security roles in cache configuration page I have to manually add [ ] brackets before updating
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-6531?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-6531:
-------------------------------------------
[~mvrabel] How would you prefer to add a list of items? What kind of text input control would be more suitable?
> when editing security roles in cache configuration page I have to manually add [ ] brackets before updating
> -----------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6531
> URL: https://issues.jboss.org/browse/ISPN-6531
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.2.0.Final
> Reporter: Martin Vrabel
> Assignee: Vladimir Blagojevic
>
> If there are for example 2 roles in the "roles" filed the cache configuration page shows it as "admin,reader" but if I want to add/remove a role I have to add all role in a [ ].
> e.g. adding [admin,reader,writer] removing [admin].
> Otherwise it throws:
> Error
> domain-failure-description
> WFLYCTL0097: Wrong type for roles. Expected [LIST] but was STRING
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ISPN-6580) Hotrod performance regressions after ISPN-5342 ISPN-6545
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-6580?page=com.atlassian.jira.plugin.... ]
William Burns commented on ISPN-6580:
-------------------------------------
Also found that skipping access logging if tracing is not enabled saves a small noticeable amount as well.
> Hotrod performance regressions after ISPN-5342 ISPN-6545
> --------------------------------------------------------
>
> Key: ISPN-6580
> URL: https://issues.jboss.org/browse/ISPN-6580
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols, Server
> Reporter: Jakub Markos
> Assignee: William Burns
> Attachments: jfr_recordings.zip, pom.xml, Reproducer.java
>
>
> There were 2 recent regressions in hotrod performance, one between commits dd5501c5e and 628819461 and the second one between 628819461 and db0890270. I didn't look for the exact commits, so the name of the issue might not be 100% exact...
> It is easily reproducable locally with a single server instance, reproducer attached.
> The numbers on my machine:
> ||Build commit||Puts time||Gets time||
> |dd5501c5e|21|74|
> |628819461|26|102|
> |db0890270|48|224|
> The JFR recordings (attached, captured is only the part of the test with gets) for db0890270 show a lot of time is spent in HotRodDecoder#resetNow(), and also the allocation rate goes from 100MB/s for dd5501c5e to over 1GB/s for db0890270. There are no glaring differences between dd5501c5e and 628819461.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ISPN-6124) List of caches is sometimes visually corrupt
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-6124?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-6124:
-------------------------------
Status: Open (was: New)
> List of caches is sometimes visually corrupt
> --------------------------------------------
>
> Key: ISPN-6124
> URL: https://issues.jboss.org/browse/ISPN-6124
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.1.0.Final
> Reporter: Jiří Holuša
> Assignee: Vladimir Blagojevic
> Fix For: 9.0.0.Alpha2
>
> Attachments: Snímek z 2016-01-29 11-37-21.png
>
>
> Page: Cache -> select some container -> list of caches
> Under certain circumstances, the cache cards are wrongly aligned, see the screenshot in attachments. I think it's because those two caches on the right don't have any icons below the cache type, making the box smaller.
> The solution would be to assign fixed height, since it can be predictable or add a "clearing" div after each row, I guess.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ISPN-6124) List of caches is sometimes visually corrupt
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-6124?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-6124.
--------------------------------
Fix Version/s: 9.0.0.Alpha2
Resolution: Done
> List of caches is sometimes visually corrupt
> --------------------------------------------
>
> Key: ISPN-6124
> URL: https://issues.jboss.org/browse/ISPN-6124
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.1.0.Final
> Reporter: Jiří Holuša
> Assignee: Vladimir Blagojevic
> Fix For: 9.0.0.Alpha2
>
> Attachments: Snímek z 2016-01-29 11-37-21.png
>
>
> Page: Cache -> select some container -> list of caches
> Under certain circumstances, the cache cards are wrongly aligned, see the screenshot in attachments. I think it's because those two caches on the right don't have any icons below the cache type, making the box smaller.
> The solution would be to assign fixed height, since it can be predictable or add a "clearing" div after each row, I guess.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months