[JBoss JIRA] (ISPN-6229) Rename select box for choosing the Task to be run
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-6229?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-6229:
--------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Rename select box for choosing the Task to be run
> -------------------------------------------------
>
> Key: ISPN-6229
> URL: https://issues.jboss.org/browse/ISPN-6229
> Project: Infinispan
> Issue Type: Enhancement
> Components: Console
> Affects Versions: 8.2.0.Beta2
> Reporter: Martin Gencur
> Assignee: Tristan Tarrant
> Priority: Minor
> Fix For: 8.2.0.Final
>
>
> The select box for choosing the task on "Launch new task" screen is misleading. From a usability standpoint, it would be better to rename it to either "Task" or "Task name" (and also the tooltip). Right now it is named "Type".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6327) InboundTransferTask erroneously log CacheException for successful responses
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6327?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes commented on ISPN-6327:
-----------------------------------------
{code}
17:26:53,139 WARN (stateTransferExecutor-thread-ShardedIndexManagerMassIndexTest-NodeB-p896-t4) [InboundTransferTask] ISPN000210: Failed to request segments [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 242, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255] of cache LuceneIndexesMetadata from node ShardedIndexManagerMassIndexTest-NodeA-26448 (node will not be retried)
org.infinispan.commons.CacheException: SuccessfulResponse{responseValue=true}
at org.infinispan.statetransfer.InboundTransferTask.requestSegments(InboundTransferTask.java:150)
at org.infinispan.statetransfer.StateConsumerImpl$4.call(StateConsumerImpl.java:1048)
at org.infinispan.statetransfer.StateConsumerImpl$4.call(StateConsumerImpl.java:1045)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.runInternal(SemaphoreCompletionService.java:172)
at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.run(SemaphoreCompletionService.java:151)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)17:26:53,139 INFO (remote-thread-ShardedIndexManagerMassIndexTest-NodeA-p883-t6) [CLUSTER] ISPN000336: Finished cluster-wide rebalance for cache LuceneIndexesMetadata, topology id = 1
{code}
> InboundTransferTask erroneously log CacheException for successful responses
> ---------------------------------------------------------------------------
>
> Key: ISPN-6327
> URL: https://issues.jboss.org/browse/ISPN-6327
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Reporter: Gustavo Fernandes
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-5943) Access log and statistics of cache operations
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-5943?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-5943:
--------------------------------
Status: Open (was: New)
> Access log and statistics of cache operations
> ---------------------------------------------
>
> Key: ISPN-5943
> URL: https://issues.jboss.org/browse/ISPN-5943
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Reporter: Pedro Zapata
> Assignee: William Burns
> Labels: jdg7
>
> The HotRod and REST endpoint will have a dedicated log category, which will be disabled by default, to which we will log using a format which follows the typical HTTPD server access.log format, i.e. client_ip user_id timestamp op key response_size processing_time.
> Enabling the log will be possible either by configuring the XML or by using the CLI.
> Additional JMX and DMR metrics will be implemented which report the number of invocations for each operation, their cumulative execution time, and the average execution time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-5943) Access log and statistics of cache operations
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-5943?page=com.atlassian.jira.plugin.... ]
Work on ISPN-5943 started by William Burns.
-------------------------------------------
> Access log and statistics of cache operations
> ---------------------------------------------
>
> Key: ISPN-5943
> URL: https://issues.jboss.org/browse/ISPN-5943
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Reporter: Pedro Zapata
> Assignee: William Burns
> Labels: jdg7
>
> The HotRod and REST endpoint will have a dedicated log category, which will be disabled by default, to which we will log using a format which follows the typical HTTPD server access.log format, i.e. client_ip user_id timestamp op key response_size processing_time.
> Enabling the log will be possible either by configuring the XML or by using the CLI.
> Additional JMX and DMR metrics will be implemented which report the number of invocations for each operation, their cumulative execution time, and the average execution time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month