1:45 a.m.
Execution timeout should not be linked to replication timeout
-------------------------------------------------------------
Key: ISPN-1313
URL: https://issues.jboss.org/browse/ISPN-1313
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Cache
Affects Versions: 5.0.0.CR8
Reporter: Thomas Peuss
Assignee: Manik Surtani
Currently the timeout of a distributed execution is linked to the settings for the
replication timeout (we have set the timeout to <sync
replTimeout="120000"/> as a workaround). For long running tasks this is
really annoying because you get an error back from the framework but the distributed tasks
runs till the end without a problem.
There should be an extra timeout for the execution of distributed tasks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:45 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-1313) Distributed execution timeout should not be linked to replication timeout
[
https://issues.jboss.org/browse/ISPN-1313?page=com.atlassian.jira.plugin....
]
Thomas Peuss updated ISPN-1313:
-------------------------------
Summary: Distributed execution timeout should not be linked to replication timeout
(was: Execution timeout should not be linked to replication timeout)
Distributed execution timeout should not be linked to replication
timeout
-------------------------------------------------------------------------
Key: ISPN-1313
URL: https://issues.jboss.org/browse/ISPN-1313
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Cache
Affects Versions: 5.0.0.CR8
Reporter: Thomas Peuss
Assignee: Manik Surtani
Currently the timeout of a distributed execution is linked to the settings for the
replication timeout (we have set the timeout to <sync
replTimeout="120000"/> as a workaround). For long running tasks this is
really annoying because you get an error back from the framework but the distributed tasks
runs till the end without a problem.
There should be an extra timeout for the execution of distributed tasks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:38 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-1313) Distributed execution timeout should not be linked to replication timeout
[
https://issues.jboss.org/browse/ISPN-1313?page=com.atlassian.jira.plugin....
]
Manik Surtani updated ISPN-1313:
--------------------------------
Assignee: Vladimir Blagojevic (was: Manik Surtani)
Fix Version/s: 5.1.0.BETA1
5.1.0.FINAL
Distributed execution timeout should not be linked to replication
timeout
-------------------------------------------------------------------------
Key: ISPN-1313
URL: https://issues.jboss.org/browse/ISPN-1313
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Cache
Affects Versions: 5.0.0.CR8
Reporter: Thomas Peuss
Assignee: Vladimir Blagojevic
Fix For: 5.1.0.BETA1, 5.1.0.FINAL
Currently the timeout of a distributed execution is linked to the settings for the
replication timeout (we have set the timeout to <sync
replTimeout="120000"/> as a workaround). For long running tasks this is
really annoying because you get an error back from the framework but the distributed tasks
runs till the end without a problem.
There should be an extra timeout for the execution of distributed tasks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:23 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-1313) Distributed execution timeout should not be linked to replication timeout
[
https://issues.jboss.org/browse/ISPN-1313?page=com.atlassian.jira.plugin....
]
Manik Surtani updated ISPN-1313:
--------------------------------
Fix Version/s: 5.2.0.FINAL
(was: 5.1.0.BETA1)
(was: 5.1.0.FINAL)
Distributed execution timeout should not be linked to replication
timeout
-------------------------------------------------------------------------
Key: ISPN-1313
URL: https://issues.jboss.org/browse/ISPN-1313
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Cache
Affects Versions: 5.0.0.CR8
Reporter: Thomas Peuss
Assignee: Vladimir Blagojevic
Fix For: 5.2.0.FINAL
Currently the timeout of a distributed execution is linked to the settings for the
replication timeout (we have set the timeout to <sync
replTimeout="120000"/> as a workaround). For long running tasks this is
really annoying because you get an error back from the framework but the distributed tasks
runs till the end without a problem.
There should be an extra timeout for the execution of distributed tasks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:46 a.m.
New subject: [JBoss JIRA] (ISPN-1313) Distributed execution timeout should not be linked to replication timeout
[
https://issues.jboss.org/browse/ISPN-1313?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic commented on ISPN-1313:
-------------------------------------------
Agreed. Right now, there is little I can to do solve this issue appropriately. Most likely
we will add a new configuration element for distributed executors where one of the
configuration settings will be a task timeout.
Distributed execution timeout should not be linked to replication
timeout
-------------------------------------------------------------------------
Key: ISPN-1313
URL: https://issues.jboss.org/browse/ISPN-1313
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Cache
Affects Versions: 5.0.0.CR8
Reporter: Thomas Peuss
Assignee: Vladimir Blagojevic
Fix For: 5.2.0.FINAL
Currently the timeout of a distributed execution is linked to the settings for the
replication timeout (we have set the timeout to <sync
replTimeout="120000"/> as a workaround). For long running tasks this is
really annoying because you get an error back from the framework but the distributed tasks
runs till the end without a problem.
There should be an extra timeout for the execution of distributed tasks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:42 a.m.
New subject: [JBoss JIRA] (ISPN-1313) Distributed execution timeout should not be linked to replication timeout
[
https://issues.jboss.org/browse/ISPN-1313?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic updated ISPN-1313:
--------------------------------------
Component/s: Distributed Execution and Map/Reduce
(was: Distributed Cache)
Distributed execution timeout should not be linked to replication
timeout
-------------------------------------------------------------------------
Key: ISPN-1313
URL: https://issues.jboss.org/browse/ISPN-1313
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Execution and Map/Reduce
Affects Versions: 5.0.0.CR8
Reporter: Thomas Peuss
Assignee: Vladimir Blagojevic
Fix For: 5.2.0.Final
Currently the timeout of a distributed execution is linked to the settings for the
replication timeout (we have set the timeout to <sync
replTimeout="120000"/> as a workaround). For long running tasks this is
really annoying because you get an error back from the framework but the distributed tasks
runs till the end without a problem.
There should be an extra timeout for the execution of distributed tasks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:27 a.m.
New subject: [JBoss JIRA] (ISPN-1313) Distributed execution timeout should not be linked to replication timeout
[
https://issues.jboss.org/browse/ISPN-1313?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic updated ISPN-1313:
--------------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/1312
Distributed execution timeout should not be linked to replication
timeout
-------------------------------------------------------------------------
Key: ISPN-1313
URL: https://issues.jboss.org/browse/ISPN-1313
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Execution and Map/Reduce
Affects Versions: 5.0.0.CR8
Reporter: Thomas Peuss
Assignee: Vladimir Blagojevic
Fix For: 5.2.0.Final
Currently the timeout of a distributed execution is linked to the settings for the
replication timeout (we have set the timeout to <sync
replTimeout="120000"/> as a workaround). For long running tasks this is
really annoying because you get an error back from the framework but the distributed tasks
runs till the end without a problem.
There should be an extra timeout for the execution of distributed tasks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:15 a.m.
New subject: [JBoss JIRA] (ISPN-1313) Distributed execution timeout should not be linked to replication timeout
[
https://issues.jboss.org/browse/ISPN-1313?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic resolved ISPN-1313.
---------------------------------------
Fix Version/s: 5.2.0.Beta1
(was: 5.2.0.Final)
Resolution: Done
Distributed execution timeout should not be linked to replication
timeout
-------------------------------------------------------------------------
Key: ISPN-1313
URL: https://issues.jboss.org/browse/ISPN-1313
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Execution and Map/Reduce
Affects Versions: 5.0.0.CR8
Reporter: Thomas Peuss
Assignee: Vladimir Blagojevic
Fix For: 5.2.0.Beta1
Currently the timeout of a distributed execution is linked to the settings for the
replication timeout (we have set the timeout to <sync
replTimeout="120000"/> as a workaround). For long running tasks this is
really annoying because you get an error back from the framework but the distributed tasks
runs till the end without a problem.
There should be an extra timeout for the execution of distributed tasks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:17 a.m.
New subject: [JBoss JIRA] (ISPN-1313) Distributed execution timeout should not be linked to replication timeout
[
https://issues.jboss.org/browse/ISPN-1313?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic updated ISPN-1313:
--------------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/1343 (was:
https://github.com/infinispan/infinispan/pull/1312)
Distributed execution timeout should not be linked to replication
timeout
-------------------------------------------------------------------------
Key: ISPN-1313
URL: https://issues.jboss.org/browse/ISPN-1313
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Execution and Map/Reduce
Affects Versions: 5.0.0.CR8
Reporter: Thomas Peuss
Assignee: Vladimir Blagojevic
Fix For: 5.2.0.Beta1
Currently the timeout of a distributed execution is linked to the settings for the
replication timeout (we have set the timeout to <sync
replTimeout="120000"/> as a workaround). For long running tasks this is
really annoying because you get an error back from the framework but the distributed tasks
runs till the end without a problem.
There should be an extra timeout for the execution of distributed tasks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4226
days inactive
4646
days old
infinispan-issues@lists.jboss.org
8 comments
4 participants
participants (4)
-
Manik Surtani (JIRA) -
Thomas Peuss (JIRA)
-
Vladimir Blagojevic (Commented) (JIRA)
-
Vladimir Blagojevic (JIRA)