[JBoss JIRA] (ISPN-5811) View list of jobs status
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-5811?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5811:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 8.2.0.Beta2
8.2.0.Final
Resolution: Done
> View list of jobs status
> ------------------------
>
> Key: ISPN-5811
> URL: https://issues.jboss.org/browse/ISPN-5811
> Project: Infinispan
> Issue Type: Sub-task
> Components: Console
> Reporter: Pedro Zapata
> Assignee: Pedro Zapata
> Fix For: 8.2.0.Beta2, 8.2.0.Final
>
>
> As an administrator, I want to know the set of server script jobs which have completed. Info should include, start time and end time of the jobs, number of successful execution, number of failed executions.
> See details in mockup screen:
> https://rawgit.com/infinispan/infinispan-console-mockup/master/cache-cont...
> The task output (if any), will be render (=toString()) as plain text in a pre-formatted area. Output will be trimmed down to some max size to prevent storing something too big. The default max size for output will be 64KB.
> Jobs are never retried automatically.
> Map/Reduce jobs are not to be displayed in this screen.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-5810) View to start a job
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-5810?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5810:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 8.2.0.Beta2
8.2.0.Final
Resolution: Done
> View to start a job
> -------------------
>
> Key: ISPN-5810
> URL: https://issues.jboss.org/browse/ISPN-5810
> Project: Infinispan
> Issue Type: Sub-task
> Components: Console
> Reporter: Pedro Zapata
> Assignee: Pedro Zapata
> Fix For: 8.2.0.Beta2, 8.2.0.Final
>
>
> As an administrator, I want to start a Server script job on my cluster from my Management Console (instead of an application). I want to specify the input data-set (cache), output data-set (cache) and additional parameters.
> There will be a modal dialog to start a task, which can be launched from the Cache container task list and the cache details view.
> This menu has the following fields:
> * Select type of task
> * Select a cache (only if it’s called from outside the cache context, otherwise pre-select the value with the current’s cache value)
> * If the task requires named parameters, fill them in:
> * Checkbox, if the task will log its completion as a grid event.
> No output cache needs to be defined
> A message ‘Task has been started’ will be displayed.
> See details in mockup screen:
> https://rawgit.com/infinispan/infinispan-console-mockup/master/cache-cont...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-5811) View list of jobs status
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-5811?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5811:
----------------------------------
Status: Open (was: New)
> View list of jobs status
> ------------------------
>
> Key: ISPN-5811
> URL: https://issues.jboss.org/browse/ISPN-5811
> Project: Infinispan
> Issue Type: Sub-task
> Components: Console
> Reporter: Pedro Zapata
> Assignee: Pedro Zapata
> Fix For: 8.2.0.Beta2, 8.2.0.Final
>
>
> As an administrator, I want to know the set of server script jobs which have completed. Info should include, start time and end time of the jobs, number of successful execution, number of failed executions.
> See details in mockup screen:
> https://rawgit.com/infinispan/infinispan-console-mockup/master/cache-cont...
> The task output (if any), will be render (=toString()) as plain text in a pre-formatted area. Output will be trimmed down to some max size to prevent storing something too big. The default max size for output will be 64KB.
> Jobs are never retried automatically.
> Map/Reduce jobs are not to be displayed in this screen.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-5810) View to start a job
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-5810?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5810:
----------------------------------
Status: Open (was: New)
> View to start a job
> -------------------
>
> Key: ISPN-5810
> URL: https://issues.jboss.org/browse/ISPN-5810
> Project: Infinispan
> Issue Type: Sub-task
> Components: Console
> Reporter: Pedro Zapata
> Assignee: Pedro Zapata
>
> As an administrator, I want to start a Server script job on my cluster from my Management Console (instead of an application). I want to specify the input data-set (cache), output data-set (cache) and additional parameters.
> There will be a modal dialog to start a task, which can be launched from the Cache container task list and the cache details view.
> This menu has the following fields:
> * Select type of task
> * Select a cache (only if it’s called from outside the cache context, otherwise pre-select the value with the current’s cache value)
> * If the task requires named parameters, fill them in:
> * Checkbox, if the task will log its completion as a grid event.
> No output cache needs to be defined
> A message ‘Task has been started’ will be displayed.
> See details in mockup screen:
> https://rawgit.com/infinispan/infinispan-console-mockup/master/cache-cont...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-5810) View to start a job
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-5810?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-5810:
-------------------------------------
Assignee: Pedro Zapata (was: Vladimir Blagojevic)
> View to start a job
> -------------------
>
> Key: ISPN-5810
> URL: https://issues.jboss.org/browse/ISPN-5810
> Project: Infinispan
> Issue Type: Sub-task
> Components: Console
> Reporter: Pedro Zapata
> Assignee: Pedro Zapata
>
> As an administrator, I want to start a Server script job on my cluster from my Management Console (instead of an application). I want to specify the input data-set (cache), output data-set (cache) and additional parameters.
> There will be a modal dialog to start a task, which can be launched from the Cache container task list and the cache details view.
> This menu has the following fields:
> * Select type of task
> * Select a cache (only if it’s called from outside the cache context, otherwise pre-select the value with the current’s cache value)
> * If the task requires named parameters, fill them in:
> * Checkbox, if the task will log its completion as a grid event.
> No output cache needs to be defined
> A message ‘Task has been started’ will be displayed.
> See details in mockup screen:
> https://rawgit.com/infinispan/infinispan-console-mockup/master/cache-cont...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-825) Consider staggering remote get requests when using DIST
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-825?page=com.atlassian.jira.plugin.s... ]
Tristan Tarrant updated ISPN-825:
---------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 8.2.0.Beta2
8.2.0.Final
Assignee: Dan Berindei (was: William Burns)
Resolution: Done
> Consider staggering remote get requests when using DIST
> -------------------------------------------------------
>
> Key: ISPN-825
> URL: https://issues.jboss.org/browse/ISPN-825
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 4.1.0.Final
> Reporter: Manik Surtani
> Assignee: Dan Berindei
> Priority: Critical
> Labels: optimization, performance
> Fix For: 8.2.0.Beta2, 8.2.0.Final
>
>
> In DIST mode, when a request is made on a key that is not mapped locally, a remote get is sent to all data owners of that key and the first response is used. This can add unnecessary load on the network as all nodes still eventually respond, and if values are large this can cause a lot of unnecessary network traffic.
> The purpose of broadcasting to all data owners is so that (1) if one is down, another could still respond (2) if one is overloaded, others may respond faster.
> A solution around this could be based on either (or both) of:
> * Provide a configurable stagger timeout, e.g. 100ms. E.g., RPC to (random) Owner1. Wait for timeout t. If no response, RPC to Owner2. etc.
> * Always broadcast to a (configurable) subset of owners, e.g., always 2 even if numOwners is 5.
> Needs careful thought and design.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6195) CacheNotFoundResponse error when starting multiple Infinispan Server instances in parallel
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-6195?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-6195:
------------------------------
Status: Open (was: New)
> CacheNotFoundResponse error when starting multiple Infinispan Server instances in parallel
> ------------------------------------------------------------------------------------------
>
> Key: ISPN-6195
> URL: https://issues.jboss.org/browse/ISPN-6195
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.2.0.Beta1
> Reporter: Galder Zamarreño
> Assignee: Pedro Ruivo
> Fix For: 8.2.0.Beta2
>
>
> Starting two clustered Infinispan Server instances in parallel throws CacheNotFoundResponse exception in one of the nodes with the other not showing any other exceptions/errors:
> {code}
> 08:52:46,152 ERROR [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread--p4-t1)
> ISPN000196: Failed to recover cluster state after the current node became the coordinator:
> org.infinispan.commons.CacheException: Unsuccessful response received from node node2:
> CacheNotFoundResponse
> at org.infinispan.topology.ClusterTopologyManagerImpl.executeOnClusterSync(ClusterTopologyManagerImpl.java:529)
> at org.infinispan.topology.ClusterTopologyManagerImpl.recoverClusterStatus(ClusterTopologyManagerImpl.java:387)
> at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:321)
> at org.infinispan.topology.ClusterTopologyManagerImpl.lambda$start$133(ClusterTopologyManagerImpl.java:131)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.runInternal(SemaphoreCompletionService.java:173)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6195) CacheNotFoundResponse error when starting multiple Infinispan Server instances in parallel
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-6195?page=com.atlassian.jira.plugin.... ]
Work on ISPN-6195 started by Pedro Ruivo.
-----------------------------------------
> CacheNotFoundResponse error when starting multiple Infinispan Server instances in parallel
> ------------------------------------------------------------------------------------------
>
> Key: ISPN-6195
> URL: https://issues.jboss.org/browse/ISPN-6195
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.2.0.Beta1
> Reporter: Galder Zamarreño
> Assignee: Pedro Ruivo
> Fix For: 8.2.0.Beta2
>
>
> Starting two clustered Infinispan Server instances in parallel throws CacheNotFoundResponse exception in one of the nodes with the other not showing any other exceptions/errors:
> {code}
> 08:52:46,152 ERROR [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread--p4-t1)
> ISPN000196: Failed to recover cluster state after the current node became the coordinator:
> org.infinispan.commons.CacheException: Unsuccessful response received from node node2:
> CacheNotFoundResponse
> at org.infinispan.topology.ClusterTopologyManagerImpl.executeOnClusterSync(ClusterTopologyManagerImpl.java:529)
> at org.infinispan.topology.ClusterTopologyManagerImpl.recoverClusterStatus(ClusterTopologyManagerImpl.java:387)
> at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:321)
> at org.infinispan.topology.ClusterTopologyManagerImpl.lambda$start$133(ClusterTopologyManagerImpl.java:131)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.runInternal(SemaphoreCompletionService.java:173)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month