[JBoss JIRA] (ISPN-11310) Cluster page (Data Management) - UX
by Katia Aresti (Jira)
[ https://issues.redhat.com/browse/ISPN-11310?page=com.atlassian.jira.plugi... ]
Katia Aresti resolved ISPN-11310.
---------------------------------
Fix Version/s: 10.1.3.Final
Resolution: Done
> Cluster page (Data Management) - UX
> -----------------------------------
>
> Key: ISPN-11310
> URL: https://issues.redhat.com/browse/ISPN-11310
> Project: Infinispan
> Issue Type: Enhancement
> Components: Console
> Affects Versions: 10.1.1.Final
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Major
> Labels: console-ng, console-ui
> Fix For: 10.1.3.Final
>
>
> Suggestion:
> 1. Breadcrumbs
> Add breadcrumbs
> 2. Move data management in Caches page
> It is better to move [create caches] and [display configuration] in the Caches tab since they are all related to Caches interaction.
> 3. The feature icons color are not very obvious
> The color of the Feature icons are not very friendly to disable users.
> The icon seems like it toggle action, but not clickable.
> The icon meaning is not very easy to understand, users need to hover the tooltip to understand the meaning.
> Solution will show on the following draft sketch.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11311) Cluster - Caches - UX improvment
by Katia Aresti (Jira)
[ https://issues.redhat.com/browse/ISPN-11311?page=com.atlassian.jira.plugi... ]
Katia Aresti resolved ISPN-11311.
---------------------------------
Fix Version/s: 10.1.3.Final
Resolution: Done
> Cluster - Caches - UX improvment
> --------------------------------
>
> Key: ISPN-11311
> URL: https://issues.redhat.com/browse/ISPN-11311
> Project: Infinispan
> Issue Type: Enhancement
> Components: Console
> Affects Versions: 10.1.1.Final
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Major
> Labels: console-ng, console-ui
> Fix For: 10.1.3.Final
>
>
> Suggestion:
> 1. Breadcrumb is missing
> 2. Feature label looks a bit like button
> We can use simple text to describe feature type
> 3. Content details layout
> It is better to list the number in front of the content text to help users better read. Please refer to [Global statistic] page
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11347) Change default TOS for UDP
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11347?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11347:
-----------------------------------
Fix Version/s: 10.1.3.Final
9.4.19.Final
> Change default TOS for UDP
> --------------------------
>
> Key: ISPN-11347
> URL: https://issues.redhat.com/browse/ISPN-11347
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration, Core
> Affects Versions: 9.4.18.Final, 10.1.2.Final, 11.0.0.Alpha1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.1.3.Final, 11.0.0.Alpha2, 9.4.19.Final
>
>
> The Linux kernel has some fairly sophisticated queueing disciplines like {{fq_codel}}, but the default one is {{pfifo_fast}}, and that's what our edg-perfXX machines use.
> {quote}
> pfifo_fast is like three tc-pfifo(8) queues side by side,
> where packets can be enqueued in any of the three bands based on
> their Type of Service bits or assigned priority.
> Not all three bands are dequeued simultaneously - as long as lower
> bands have traffic, higher bands are never dequeued. This can be used
> to prioritize interactive traffic or penalize 'lowest cost' traffic.
> ??[http://man7.org/linux/man-pages/man8/tc-pfifo_fast.8.html#ALGORITHM]??
> {quote}
> These are some examples of band mappings:
> {quote}
> {noformat}
> TOS Bits Means Linux Priority Band
> ------------------------------------------------------------
> 0x0 0 Normal Service 0 Best Effort 1
> 0x8 4 Maximize Throughput 2 Bulk 2
> 0x10 8 Minimize Delay 6 Interactive 0
> 0x18 12 mt+md 4 Int. Bulk 1
> {noformat}
> ??[http://man7.org/linux/man-pages/man8/tc-prio.8.html#QDISC_PARAMETERS]??
> {quote}
> By default {{UDP.tos="8"}}, which makes all UDP traffic go into band 2, lowest priority (bulk). HotRod clients and servers don't set a TOS on their sockets, so the client-server packets go into band 1, middle priority (best effort).
> {{FD_ALL}} and {{FD_ALL2}} heartbeats are also {{UDP}} traffic, and in some read-only client-server test there is enough client-server traffic in band 1 to delay the FD_ALL heartbeats for more than 10 seconds.
> We could either set the default TOS to {{0}} (best effort), or {{0x18}} (maximize throughput + minimize delay), the result is the same: band 1.
> We could also try to set the TOS to {{0x10}} to get them into band 0, but while it would work in Infinispan-only benchmarks, it would probably be unfair to other communications on the same machine.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11347) Change default TOS for UDP
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11347?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11347:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Change default TOS for UDP
> --------------------------
>
> Key: ISPN-11347
> URL: https://issues.redhat.com/browse/ISPN-11347
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration, Core
> Affects Versions: 9.4.18.Final, 10.1.2.Final, 11.0.0.Alpha1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Alpha2
>
>
> The Linux kernel has some fairly sophisticated queueing disciplines like {{fq_codel}}, but the default one is {{pfifo_fast}}, and that's what our edg-perfXX machines use.
> {quote}
> pfifo_fast is like three tc-pfifo(8) queues side by side,
> where packets can be enqueued in any of the three bands based on
> their Type of Service bits or assigned priority.
> Not all three bands are dequeued simultaneously - as long as lower
> bands have traffic, higher bands are never dequeued. This can be used
> to prioritize interactive traffic or penalize 'lowest cost' traffic.
> ??[http://man7.org/linux/man-pages/man8/tc-pfifo_fast.8.html#ALGORITHM]??
> {quote}
> These are some examples of band mappings:
> {quote}
> {noformat}
> TOS Bits Means Linux Priority Band
> ------------------------------------------------------------
> 0x0 0 Normal Service 0 Best Effort 1
> 0x8 4 Maximize Throughput 2 Bulk 2
> 0x10 8 Minimize Delay 6 Interactive 0
> 0x18 12 mt+md 4 Int. Bulk 1
> {noformat}
> ??[http://man7.org/linux/man-pages/man8/tc-prio.8.html#QDISC_PARAMETERS]??
> {quote}
> By default {{UDP.tos="8"}}, which makes all UDP traffic go into band 2, lowest priority (bulk). HotRod clients and servers don't set a TOS on their sockets, so the client-server packets go into band 1, middle priority (best effort).
> {{FD_ALL}} and {{FD_ALL2}} heartbeats are also {{UDP}} traffic, and in some read-only client-server test there is enough client-server traffic in band 1 to delay the FD_ALL heartbeats for more than 10 seconds.
> We could either set the default TOS to {{0}} (best effort), or {{0x18}} (maximize throughput + minimize delay), the result is the same: band 1.
> We could also try to set the TOS to {{0x10}} to get them into band 0, but while it would work in Infinispan-only benchmarks, it would probably be unfair to other communications on the same machine.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11353) JGroups subsystem does not persist relay properties
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-11353:
--------------------------------------
Summary: JGroups subsystem does not persist relay properties
Key: ISPN-11353
URL: https://issues.redhat.com/browse/ISPN-11353
Project: Infinispan
Issue Type: Bug
Components: WildFly Server
Affects Versions: 9.4.18.Final, 10.1.2.Final, 11.0.0.Alpha1
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 10.1.3.Final, 11.0.0.Alpha2, 9.4.19.Final
persist the proeprties in the relay element.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11352) JGroups subsystem does not persist relay properties
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-11352:
--------------------------------------
Summary: JGroups subsystem does not persist relay properties
Key: ISPN-11352
URL: https://issues.redhat.com/browse/ISPN-11352
Project: Infinispan
Issue Type: Bug
Components: WildFly Server
Affects Versions: 11.0.0.Alpha1, 10.1.2.Final, 9.4.18.Final
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 10.1.3.Final, 11.0.0.Alpha2, 9.4.19.Final
persist the proeprties in the relay element.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11004) SQL server exception purging data
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11004?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11004:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> SQL server exception purging data
> ---------------------------------
>
> Key: ISPN-11004
> URL: https://issues.redhat.com/browse/ISPN-11004
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 10.0.1.Final, 10.1.2.Final
> Reporter: Megan van de Valk
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.1.3.Final, 11.0.0.Alpha2, 9.4.19.Final
>
>
> When using string keyed jdbc store with dialect="SQL_SERVER" a SQL exception of 'FOR UPDATE clause allowed only for DECLARE CURSOR' is thrown.
> {code:java}
> 14:57:39,444 WARN [org.infinispan.PERSISTENCE] (expiration-thread--p7-t1) ISPN000026: Caught exception purging data container!: org.infinispan.persistence.spi.PersistenceException: Failed clearing string based JDBC store
> at org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore.purge(JdbcStringBasedStore.java:502)
> at org.infinispan.persistence.spi.SegmentedAdvancedLoadWriteStore.purge(SegmentedAdvancedLoadWriteStore.java:291)
> at org.infinispan.persistence.manager.PersistenceManagerImpl.lambda$purgeExpired$8(PersistenceManagerImpl.java:522)
> at java.util.ArrayList.forEach(ArrayList.java:1257)
> at org.infinispan.persistence.manager.PersistenceManagerImpl.purgeExpired(PersistenceManagerImpl.java:528)
> at org.infinispan.persistence.support.DelegatingPersistenceManager.purgeExpired(DelegatingPersistenceManager.java:90)
> at org.infinispan.expiration.impl.ExpirationManagerImpl.processExpiration(ExpirationManagerImpl.java:120)
> at org.infinispan.expiration.impl.ExpirationManagerImpl$ScheduledTask.run(ExpirationManagerImpl.java:282)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> 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)
> Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Line 1: FOR UPDATE clause allowed only for DECLARE CURSOR.
> at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
> at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515)
> at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:404)
> at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
> at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
> at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
> at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
> at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
> at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:285)
> at org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore.purge(JdbcStringBasedStore.java:467)
> ... 14 more
> {code}
> The method initSelectOnlyExpiredRowsSql in [AbstractTableManager|https://github.com/infinispan/infinispan/blob/master...] includes a FOR UPDATE:
> {code:java}
> return String.format("%1$s WHERE %2$s < ? AND %2$s > 0 FOR UPDATE", getLoadAllRowsSql(), config.timestampColumnName());
> {code}
> It should probably be overwritten in [SQLServerTableManger|https://github.com/infinispan/infinispan/blob/master...] with
> {code:java}
> return String.format("%1$s WITH(UPDLOCK) WHERE %2$s < ? AND %2$s > 0", getLoadAllRowsSql(), config.timestampColumnName());
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month