Bug 1128791
Summary: | Remove timeout from Map/Reduce jobs | |||
---|---|---|---|---|
Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Tristan Tarrant <ttarrant> | |
Component: | Infinispan | Assignee: | Tristan Tarrant <ttarrant> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Gencur <mgencur> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 6.3.0 | CC: | afield, gsheldon, jdg-bugs, mhusnain, vblagoje | |
Target Milestone: | ER1 | |||
Target Release: | 6.3.1 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Previously in Red Hat JBoss Data grid, users had to extend the timeout value of map/reduce jobs because the default timeout value was the RPC timeout value. In JBoss Data Grid 6.3.1, this is fixed so that the timeout value for map/reduce jobs has been removed and the job will wait for an infinite period before timing out. If required, users can lower the timeout. As a result, users do not need to set the timeout as often as before.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1128958 (view as bug list) | Environment: | ||
Last Closed: | 2015-01-26 14:05:40 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: |
Description
Tristan Tarrant
2014-08-11 14:40:35 UTC
Assuming this needs documentation based on needs_documentation+ flag. Cloned to docs component and assigned to Bobb as this looks like a minor issue. Verified that the default timeout for the MapReduceTask in JDG 6.3.1 ER1 is zero |