[jira] [Updated] (MAPREDUCE-6552) Add job search button in JobHistoryServer WebUI
[ https://issues.apache.org/jira/browse/MAPREDUCE-6552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6552: - Resolution: Invalid Status: Resolved (was: Patch Available) > Add job search button in JobHistoryServer WebUI > --- > > Key: MAPREDUCE-6552 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6552 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: webapps >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun > Attachments: MAPREDUCE-6552.001.patch, MAPREDUCE-6552.002.patch, > Screen Shot 2015-11-19.png > > > In jobhistory webui, it's not convenient to direct search the specific > retired job when there are only few job records in page.And if you want to > show more jobs in page(so that you can find your target job), the main page > will be opened slowly.Because the renderd page will be large,and the browser > will be cost much time to download this page.So we can add a search job > button , and by inputing a specific jobid and clicking the button, we can > jump its job page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6552) Add job search button in JobHistoryServer WebUI
[ https://issues.apache.org/jira/browse/MAPREDUCE-6552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144270#comment-15144270 ] Lin Yiqun commented on MAPREDUCE-6552: -- Ok, I close this jira. > Add job search button in JobHistoryServer WebUI > --- > > Key: MAPREDUCE-6552 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6552 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: webapps >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun > Attachments: MAPREDUCE-6552.001.patch, MAPREDUCE-6552.002.patch, > Screen Shot 2015-11-19.png > > > In jobhistory webui, it's not convenient to direct search the specific > retired job when there are only few job records in page.And if you want to > show more jobs in page(so that you can find your target job), the main page > will be opened slowly.Because the renderd page will be large,and the browser > will be cost much time to download this page.So we can add a search job > button , and by inputing a specific jobid and clicking the button, we can > jump its job page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6626) Reuse ObjectMapper instance in MapReduce
[
https://issues.apache.org/jira/browse/MAPREDUCE-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140229#comment-15140229
]
Lin Yiqun commented on MAPREDUCE-6626:
--
Thanks [~ajisakaa] for commit and thanks [~brahmareddy] for review.
> Reuse ObjectMapper instance in MapReduce
>
>
> Key: MAPREDUCE-6626
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6626
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: performance
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
>Priority: Minor
> Fix For: 2.8.0
>
> Attachments: MAPREDUCE-6626.002.patch, MAPREDUCE-6626.003.patch,
> MAPREDUCE-6626.004.patch, MAPREDUCE.001.patch
>
>
> Now in MapReduce, there are some places creating a new ObjectMapper instance
> every time. In wiki of ObjectMapper, it suggested:
> {code}
> Further: it is beneficial to use just one instance (or small number of
> instances) for data binding; many optimizations for reuse (of symbol tables,
> some buffers) depend on ObjectMapper instances being reused.
> {code}
> http://webcache.googleusercontent.com/search?q=cache:kybMTIJC6F4J:wiki.fasterxml.com/JacksonFAQ+&cd=4&hl=ja&ct=clnk&gl=jp,
> it's similar to HDFS-9724.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6626) Reuse objectMapper instance in MapReduce
[
https://issues.apache.org/jira/browse/MAPREDUCE-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136711#comment-15136711
]
Lin Yiqun commented on MAPREDUCE-6626:
--
The test are all passed. The patch looks fine to the current code, can you
review patch again, [~brahmareddy].
> Reuse objectMapper instance in MapReduce
>
>
> Key: MAPREDUCE-6626
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6626
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: performance
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
> Attachments: MAPREDUCE-6626.002.patch, MAPREDUCE-6626.003.patch,
> MAPREDUCE-6626.004.patch, MAPREDUCE.001.patch
>
>
> Now in MapReduce, there are some places creating a new ObjectMapper instance
> every time. In wiki of ObjectMapper, it suggested:
> {code}
> Further: it is beneficial to use just one instance (or small number of
> instances) for data binding; many optimizations for reuse (of symbol tables,
> some buffers) depend on ObjectMapper instances being reused.
> {code}
> http://webcache.googleusercontent.com/search?q=cache:kybMTIJC6F4J:wiki.fasterxml.com/JacksonFAQ+&cd=4&hl=ja&ct=clnk&gl=jp,
> it's similar to HDFS-9724.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6626) Reuse objectMapper instance in MapReduce
[
https://issues.apache.org/jira/browse/MAPREDUCE-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated MAPREDUCE-6626:
-
Attachment: MAPREDUCE-6626.004.patch
Update the latest patch.
> Reuse objectMapper instance in MapReduce
>
>
> Key: MAPREDUCE-6626
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6626
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: performance
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
> Attachments: MAPREDUCE-6626.002.patch, MAPREDUCE-6626.003.patch,
> MAPREDUCE-6626.004.patch, MAPREDUCE.001.patch
>
>
> Now in MapReduce, there are some places creating a new ObjectMapper instance
> every time. In wiki of ObjectMapper, it suggested:
> {code}
> Further: it is beneficial to use just one instance (or small number of
> instances) for data binding; many optimizations for reuse (of symbol tables,
> some buffers) depend on ObjectMapper instances being reused.
> {code}
> http://webcache.googleusercontent.com/search?q=cache:kybMTIJC6F4J:wiki.fasterxml.com/JacksonFAQ+&cd=4&hl=ja&ct=clnk&gl=jp,
> it's similar to HDFS-9724.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6626) Reuse objectMapper instance in MapReduce
[
https://issues.apache.org/jira/browse/MAPREDUCE-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated MAPREDUCE-6626:
-
Attachment: (was: MAPREDUCE-6626.004.patch)
> Reuse objectMapper instance in MapReduce
>
>
> Key: MAPREDUCE-6626
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6626
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: performance
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
> Attachments: MAPREDUCE-6626.002.patch, MAPREDUCE-6626.003.patch,
> MAPREDUCE.001.patch
>
>
> Now in MapReduce, there are some places creating a new ObjectMapper instance
> every time. In wiki of ObjectMapper, it suggested:
> {code}
> Further: it is beneficial to use just one instance (or small number of
> instances) for data binding; many optimizations for reuse (of symbol tables,
> some buffers) depend on ObjectMapper instances being reused.
> {code}
> http://webcache.googleusercontent.com/search?q=cache:kybMTIJC6F4J:wiki.fasterxml.com/JacksonFAQ+&cd=4&hl=ja&ct=clnk&gl=jp,
> it's similar to HDFS-9724.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6626) Reuse objectMapper instance in MapReduce
[
https://issues.apache.org/jira/browse/MAPREDUCE-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated MAPREDUCE-6626:
-
Attachment: MAPREDUCE-6626.004.patch
Thanks [~ajisakaa] for comments. Update the patch.
> Reuse objectMapper instance in MapReduce
>
>
> Key: MAPREDUCE-6626
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6626
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: performance
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
> Attachments: MAPREDUCE-6626.002.patch, MAPREDUCE-6626.003.patch,
> MAPREDUCE-6626.004.patch, MAPREDUCE.001.patch
>
>
> Now in MapReduce, there are some places creating a new ObjectMapper instance
> every time. In wiki of ObjectMapper, it suggested:
> {code}
> Further: it is beneficial to use just one instance (or small number of
> instances) for data binding; many optimizations for reuse (of symbol tables,
> some buffers) depend on ObjectMapper instances being reused.
> {code}
> http://webcache.googleusercontent.com/search?q=cache:kybMTIJC6F4J:wiki.fasterxml.com/JacksonFAQ+&cd=4&hl=ja&ct=clnk&gl=jp,
> it's similar to HDFS-9724.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6626) Reuse objectMapper instance in MapReduce
[
https://issues.apache.org/jira/browse/MAPREDUCE-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131521#comment-15131521
]
Lin Yiqun commented on MAPREDUCE-6626:
--
There was no failed test. It looks fine to the current code.
> Reuse objectMapper instance in MapReduce
>
>
> Key: MAPREDUCE-6626
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6626
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: performance
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
> Attachments: MAPREDUCE-6626.002.patch, MAPREDUCE-6626.003.patch,
> MAPREDUCE.001.patch
>
>
> Now in MapReduce, there are some places creating a new ObjectMapper instance
> every time. In wiki of ObjectMapper, it suggested:
> {code}
> Further: it is beneficial to use just one instance (or small number of
> instances) for data binding; many optimizations for reuse (of symbol tables,
> some buffers) depend on ObjectMapper instances being reused.
> {code}
> http://webcache.googleusercontent.com/search?q=cache:kybMTIJC6F4J:wiki.fasterxml.com/JacksonFAQ+&cd=4&hl=ja&ct=clnk&gl=jp,
> it's similar to HDFS-9724.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6626) Reuse objectMapper instance in MapReduce
[
https://issues.apache.org/jira/browse/MAPREDUCE-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated MAPREDUCE-6626:
-
Attachment: MAPREDUCE-6626.003.patch
Fix checkstyle errors.
> Reuse objectMapper instance in MapReduce
>
>
> Key: MAPREDUCE-6626
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6626
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: performance
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
> Attachments: MAPREDUCE-6626.002.patch, MAPREDUCE-6626.003.patch,
> MAPREDUCE.001.patch
>
>
> Now in MapReduce, there are some places creating a new ObjectMapper instance
> every time. In wiki of ObjectMapper, it suggested:
> {code}
> Further: it is beneficial to use just one instance (or small number of
> instances) for data binding; many optimizations for reuse (of symbol tables,
> some buffers) depend on ObjectMapper instances being reused.
> {code}
> http://webcache.googleusercontent.com/search?q=cache:kybMTIJC6F4J:wiki.fasterxml.com/JacksonFAQ+&cd=4&hl=ja&ct=clnk&gl=jp,
> it's similar to HDFS-9724.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6626) Reuse objectMapper instance in MapReduce
[
https://issues.apache.org/jira/browse/MAPREDUCE-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated MAPREDUCE-6626:
-
Attachment: MAPREDUCE-6626.002.patch
> Reuse objectMapper instance in MapReduce
>
>
> Key: MAPREDUCE-6626
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6626
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: performance
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
> Attachments: MAPREDUCE-6626.002.patch, MAPREDUCE.001.patch
>
>
> Now in MapReduce, there are some places creating a new ObjectMapper instance
> every time. In wiki of ObjectMapper, it suggested:
> {code}
> Further: it is beneficial to use just one instance (or small number of
> instances) for data binding; many optimizations for reuse (of symbol tables,
> some buffers) depend on ObjectMapper instances being reused.
> {code}
> http://webcache.googleusercontent.com/search?q=cache:kybMTIJC6F4J:wiki.fasterxml.com/JacksonFAQ+&cd=4&hl=ja&ct=clnk&gl=jp,
> it's similar to HDFS-9724.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6626) Reuse objectMapper instance in MapReduce
[
https://issues.apache.org/jira/browse/MAPREDUCE-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15129931#comment-15129931
]
Lin Yiqun commented on MAPREDUCE-6626:
--
Thanks [~brahmareddy]. Update the latest patch.
> Reuse objectMapper instance in MapReduce
>
>
> Key: MAPREDUCE-6626
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6626
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: performance
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
> Attachments: MAPREDUCE.001.patch
>
>
> Now in MapReduce, there are some places creating a new ObjectMapper instance
> every time. In wiki of ObjectMapper, it suggested:
> {code}
> Further: it is beneficial to use just one instance (or small number of
> instances) for data binding; many optimizations for reuse (of symbol tables,
> some buffers) depend on ObjectMapper instances being reused.
> {code}
> http://webcache.googleusercontent.com/search?q=cache:kybMTIJC6F4J:wiki.fasterxml.com/JacksonFAQ+&cd=4&hl=ja&ct=clnk&gl=jp,
> it's similar to HDFS-9724.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6594) JobHistory WebUI add jobName-filtered searching function
[ https://issues.apache.org/jira/browse/MAPREDUCE-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6594: - Attachment: MAPREDUCE-6594.001.patch > JobHistory WebUI add jobName-filtered searching function > - > > Key: MAPREDUCE-6594 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6594 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: webapps >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun > Attachments: MAPREDUCE-6594.001.patch > > > In JobHistory main page, it can't search those jobs which are not displayed > in main page.So if you want to search earlier job, you should set the > job-cache size bigger. And this will let the main page opening slowly due to > the large of job records. We should provider a way to search these jobs not > depending on the displayed jobs on page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6594) JobHistory WebUI add jobName-filtered searching function
[ https://issues.apache.org/jira/browse/MAPREDUCE-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6594: - Status: Patch Available (was: Open) I attach a initial patch. Thanks reviewing! > JobHistory WebUI add jobName-filtered searching function > - > > Key: MAPREDUCE-6594 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6594 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: webapps >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun > > In JobHistory main page, it can't search those jobs which are not displayed > in main page.So if you want to search earlier job, you should set the > job-cache size bigger. And this will let the main page opening slowly due to > the large of job records. We should provider a way to search these jobs not > depending on the displayed jobs on page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MAPREDUCE-6594) JobHistory WebUI add jobName-filtered searching function
Lin Yiqun created MAPREDUCE-6594: Summary: JobHistory WebUI add jobName-filtered searching function Key: MAPREDUCE-6594 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6594 Project: Hadoop Map/Reduce Issue Type: Improvement Components: webapps Affects Versions: 2.7.1 Reporter: Lin Yiqun Assignee: Lin Yiqun In JobHistory main page, it can't search those jobs which are not displayed in main page.So if you want to search earlier job, you should set the job-cache size bigger. And this will let the main page opening slowly due to the large of job records. We should provider a way to search these jobs not depending on the displayed jobs on page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6587) Remove unused params in connection-related methods of Fetcher
[
https://issues.apache.org/jira/browse/MAPREDUCE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073734#comment-15073734
]
Lin Yiqun commented on MAPREDUCE-6587:
--
[~aw], could you have time review patch? This is a obvious problem.
> Remove unused params in connection-related methods of Fetcher
> -
>
> Key: MAPREDUCE-6587
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6587
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
>Priority: Trivial
> Attachments: MAPREDUCE-6587.001.patch
>
>
> There are some unused params in Fecther#openConnectionWithRetry.The code is
> following:
> {code}
> private void openConnectionWithRetry(MapHost host,
> Set remaining, URL url) throws IOException {
> long startTime = Time.monotonicNow();
> boolean shouldWait = true;
> while (shouldWait) {
> try {
> openConnection(url);
> shouldWait = false;
> } catch (IOException e) {
> if (!fetchRetryEnabled) {
>// throw exception directly if fetch's retry is not enabled
>throw e;
> }
> if ((Time.monotonicNow() - startTime) >= this.fetchRetryTimeout) {
> LOG.warn("Failed to connect to host: " + url + "after "
> + fetchRetryTimeout + " milliseconds.");
> throw e;
> }
> try {
> Thread.sleep(this.fetchRetryInterval);
> } catch (InterruptedException e1) {
> if (stopped) {
> return;
> }
> }
> }
> }
> }
> {code}
> we can see that the param remaing and host is not be used in this method. So
> we need to remove these param and update the method params which invoke this
> method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6587) Remove unused params in connection-related methods of Fetcher
[
https://issues.apache.org/jira/browse/MAPREDUCE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072028#comment-15072028
]
Lin Yiqun commented on MAPREDUCE-6587:
--
Have someone review my patch?
> Remove unused params in connection-related methods of Fetcher
> -
>
> Key: MAPREDUCE-6587
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6587
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
>Priority: Trivial
> Attachments: MAPREDUCE-6587.001.patch
>
>
> There are some unused params in Fecther#openConnectionWithRetry.The code is
> following:
> {code}
> private void openConnectionWithRetry(MapHost host,
> Set remaining, URL url) throws IOException {
> long startTime = Time.monotonicNow();
> boolean shouldWait = true;
> while (shouldWait) {
> try {
> openConnection(url);
> shouldWait = false;
> } catch (IOException e) {
> if (!fetchRetryEnabled) {
>// throw exception directly if fetch's retry is not enabled
>throw e;
> }
> if ((Time.monotonicNow() - startTime) >= this.fetchRetryTimeout) {
> LOG.warn("Failed to connect to host: " + url + "after "
> + fetchRetryTimeout + " milliseconds.");
> throw e;
> }
> try {
> Thread.sleep(this.fetchRetryInterval);
> } catch (InterruptedException e1) {
> if (stopped) {
> return;
> }
> }
> }
> }
> }
> {code}
> we can see that the param remaing and host is not be used in this method. So
> we need to remove these param and update the method params which invoke this
> method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6587) Remove unused params in connection-related methods of Fetcher
[
https://issues.apache.org/jira/browse/MAPREDUCE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069161#comment-15069161
]
Lin Yiqun commented on MAPREDUCE-6587:
--
The jenkins findbug-warnings and asflicense-warning likely not related.
> Remove unused params in connection-related methods of Fetcher
> -
>
> Key: MAPREDUCE-6587
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6587
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
>Priority: Trivial
> Attachments: MAPREDUCE-6587.001.patch
>
>
> There are some unused params in Fecther#openConnectionWithRetry.The code is
> following:
> {code}
> private void openConnectionWithRetry(MapHost host,
> Set remaining, URL url) throws IOException {
> long startTime = Time.monotonicNow();
> boolean shouldWait = true;
> while (shouldWait) {
> try {
> openConnection(url);
> shouldWait = false;
> } catch (IOException e) {
> if (!fetchRetryEnabled) {
>// throw exception directly if fetch's retry is not enabled
>throw e;
> }
> if ((Time.monotonicNow() - startTime) >= this.fetchRetryTimeout) {
> LOG.warn("Failed to connect to host: " + url + "after "
> + fetchRetryTimeout + " milliseconds.");
> throw e;
> }
> try {
> Thread.sleep(this.fetchRetryInterval);
> } catch (InterruptedException e1) {
> if (stopped) {
> return;
> }
> }
> }
> }
> }
> {code}
> we can see that the param remaing and host is not be used in this method. So
> we need to remove these param and update the method params which invoke this
> method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6587) Remove unused params in connection-related methods of Fetcher
[
https://issues.apache.org/jira/browse/MAPREDUCE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated MAPREDUCE-6587:
-
Status: Patch Available (was: Open)
I attach a initial patch. Thanks reviewing!
> Remove unused params in connection-related methods of Fetcher
> -
>
> Key: MAPREDUCE-6587
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6587
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
>Priority: Trivial
> Attachments: MAPREDUCE-6587.001.patch
>
>
> There are some unused params in Fecther#openConnectionWithRetry.The code is
> following:
> {code}
> private void openConnectionWithRetry(MapHost host,
> Set remaining, URL url) throws IOException {
> long startTime = Time.monotonicNow();
> boolean shouldWait = true;
> while (shouldWait) {
> try {
> openConnection(url);
> shouldWait = false;
> } catch (IOException e) {
> if (!fetchRetryEnabled) {
>// throw exception directly if fetch's retry is not enabled
>throw e;
> }
> if ((Time.monotonicNow() - startTime) >= this.fetchRetryTimeout) {
> LOG.warn("Failed to connect to host: " + url + "after "
> + fetchRetryTimeout + " milliseconds.");
> throw e;
> }
> try {
> Thread.sleep(this.fetchRetryInterval);
> } catch (InterruptedException e1) {
> if (stopped) {
> return;
> }
> }
> }
> }
> }
> {code}
> we can see that the param remaing and host is not be used in this method. So
> we need to remove these param and update the method params which invoke this
> method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6587) Remove unused params in connection-related methods of Fetcher
[
https://issues.apache.org/jira/browse/MAPREDUCE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated MAPREDUCE-6587:
-
Attachment: MAPREDUCE-6587.001.patch
> Remove unused params in connection-related methods of Fetcher
> -
>
> Key: MAPREDUCE-6587
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6587
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
>Priority: Trivial
> Attachments: MAPREDUCE-6587.001.patch
>
>
> There are some unused params in Fecther#openConnectionWithRetry.The code is
> following:
> {code}
> private void openConnectionWithRetry(MapHost host,
> Set remaining, URL url) throws IOException {
> long startTime = Time.monotonicNow();
> boolean shouldWait = true;
> while (shouldWait) {
> try {
> openConnection(url);
> shouldWait = false;
> } catch (IOException e) {
> if (!fetchRetryEnabled) {
>// throw exception directly if fetch's retry is not enabled
>throw e;
> }
> if ((Time.monotonicNow() - startTime) >= this.fetchRetryTimeout) {
> LOG.warn("Failed to connect to host: " + url + "after "
> + fetchRetryTimeout + " milliseconds.");
> throw e;
> }
> try {
> Thread.sleep(this.fetchRetryInterval);
> } catch (InterruptedException e1) {
> if (stopped) {
> return;
> }
> }
> }
> }
> }
> {code}
> we can see that the param remaing and host is not be used in this method. So
> we need to remove these param and update the method params which invoke this
> method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MAPREDUCE-6587) Remove unused params in connection-related methods of Fetcher
Lin Yiqun created MAPREDUCE-6587:
Summary: Remove unused params in connection-related methods of
Fetcher
Key: MAPREDUCE-6587
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6587
Project: Hadoop Map/Reduce
Issue Type: Improvement
Affects Versions: 2.7.1
Reporter: Lin Yiqun
Assignee: Lin Yiqun
Priority: Trivial
There are some unused params in Fecther#openConnectionWithRetry.The code is
following:
{code}
private void openConnectionWithRetry(MapHost host,
Set remaining, URL url) throws IOException {
long startTime = Time.monotonicNow();
boolean shouldWait = true;
while (shouldWait) {
try {
openConnection(url);
shouldWait = false;
} catch (IOException e) {
if (!fetchRetryEnabled) {
// throw exception directly if fetch's retry is not enabled
throw e;
}
if ((Time.monotonicNow() - startTime) >= this.fetchRetryTimeout) {
LOG.warn("Failed to connect to host: " + url + "after "
+ fetchRetryTimeout + " milliseconds.");
throw e;
}
try {
Thread.sleep(this.fetchRetryInterval);
} catch (InterruptedException e1) {
if (stopped) {
return;
}
}
}
}
}
{code}
we can see that the param remaing and host is not be used in this method. So we
need to remove these param and update the method params which invoke this
method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6586) TaskAttempt Page should reset the progress to 0 when its state is failed
[
https://issues.apache.org/jira/browse/MAPREDUCE-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated MAPREDUCE-6586:
-
Attachment: Screen shot 2015-12-22.png
> TaskAttempt Page should reset the progress to 0 when its state is failed
>
>
> Key: MAPREDUCE-6586
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6586
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: webapps
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
> Attachments: MAPREDUCE-6586.001.patch, Screen shot 2015-12-22.png
>
>
> The progress of taskAttempt is not correctly showing when the taskAttempt is
> failed. The value is 100.00, but actually the taskAttempt is failed. And I
> found the reason is following:
> {code:title=CompletedTaskAttempt.java|borderStyle=solid}
> @Override
> public Counters getCounters() {
> return attemptInfo.getCounters();
> }
> @Override
> public TaskAttemptId getID() {
> return attemptId;
> }
> @Override
> public float getProgress() {
> return 1.0f;
> }
> {code}
> When the taskAttempt is completed, the progress will always return 1.0
> whenever the result is failed or succeed. This will let users confused. May
> be it should be reset to 0 better. I attach a screen shot of this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6586) TaskAttempt Page should reset the progress to 0 when its state is failed
[
https://issues.apache.org/jira/browse/MAPREDUCE-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated MAPREDUCE-6586:
-
Attachment: MAPREDUCE-6586.001.patch
> TaskAttempt Page should reset the progress to 0 when its state is failed
>
>
> Key: MAPREDUCE-6586
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6586
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: webapps
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
> Attachments: MAPREDUCE-6586.001.patch
>
>
> The progress of taskAttempt is not correctly showing when the taskAttempt is
> failed. The value is 100.00, but actually the taskAttempt is failed. And I
> found the reason is following:
> {code:title=CompletedTaskAttempt.java|borderStyle=solid}
> @Override
> public Counters getCounters() {
> return attemptInfo.getCounters();
> }
> @Override
> public TaskAttemptId getID() {
> return attemptId;
> }
> @Override
> public float getProgress() {
> return 1.0f;
> }
> {code}
> When the taskAttempt is completed, the progress will always return 1.0
> whenever the result is failed or succeed. This will let users confused. May
> be it should be reset to 0 better. I attach a screen shot of this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6586) TaskAttempt Page should reset the progress to 0 when its state is failed
[
https://issues.apache.org/jira/browse/MAPREDUCE-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067780#comment-15067780
]
Lin Yiqun commented on MAPREDUCE-6586:
--
Thanks reviewing!
> TaskAttempt Page should reset the progress to 0 when its state is failed
>
>
> Key: MAPREDUCE-6586
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6586
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: webapps
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
> Attachments: MAPREDUCE-6586.001.patch
>
>
> The progress of taskAttempt is not correctly showing when the taskAttempt is
> failed. The value is 100.00, but actually the taskAttempt is failed. And I
> found the reason is following:
> {code:title=CompletedTaskAttempt.java|borderStyle=solid}
> @Override
> public Counters getCounters() {
> return attemptInfo.getCounters();
> }
> @Override
> public TaskAttemptId getID() {
> return attemptId;
> }
> @Override
> public float getProgress() {
> return 1.0f;
> }
> {code}
> When the taskAttempt is completed, the progress will always return 1.0
> whenever the result is failed or succeed. This will let users confused. May
> be it should be reset to 0 better. I attach a screen shot of this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6586) TaskAttempt Page should reset the progress to 0 when its state is failed
[
https://issues.apache.org/jira/browse/MAPREDUCE-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated MAPREDUCE-6586:
-
Status: Patch Available (was: Open)
I attach a initial patch. I reset the progress to 0 when the taskAttemptState
is killed or failed.
> TaskAttempt Page should reset the progress to 0 when its state is failed
>
>
> Key: MAPREDUCE-6586
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6586
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: webapps
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
> Attachments: MAPREDUCE-6586.001.patch
>
>
> The progress of taskAttempt is not correctly showing when the taskAttempt is
> failed. The value is 100.00, but actually the taskAttempt is failed. And I
> found the reason is following:
> {code:title=CompletedTaskAttempt.java|borderStyle=solid}
> @Override
> public Counters getCounters() {
> return attemptInfo.getCounters();
> }
> @Override
> public TaskAttemptId getID() {
> return attemptId;
> }
> @Override
> public float getProgress() {
> return 1.0f;
> }
> {code}
> When the taskAttempt is completed, the progress will always return 1.0
> whenever the result is failed or succeed. This will let users confused. May
> be it should be reset to 0 better. I attach a screen shot of this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6586) TaskAttempt Page should reset the progress to 0 when its state is failed
[
https://issues.apache.org/jira/browse/MAPREDUCE-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated MAPREDUCE-6586:
-
Description:
The progress of taskAttempt is not correctly showing when the taskAttempt is
failed. The value is 100.00, but actually the taskAttempt is failed. And I
found the reason is following:
{code:title=CompletedTaskAttempt.java|borderStyle=solid}
@Override
public Counters getCounters() {
return attemptInfo.getCounters();
}
@Override
public TaskAttemptId getID() {
return attemptId;
}
@Override
public float getProgress() {
return 1.0f;
}
{code}
When the taskAttempt is completed, the progress will always return 1.0 whenever
the result is failed or succeed. This will let users confused. May be it should
be reset to 0 better. I attach a screen shot of this case.
was:
The progress of taskAttempt is not correctly showing when the taskAttempt is
failed. The value is 100.00, but actually the taskAttempt is failed. And I
found the reason is following:
{code:title=.CompletedTaskAttempt.java|borderStyle=solid}
@Override
public Counters getCounters() {
return attemptInfo.getCounters();
}
@Override
public TaskAttemptId getID() {
return attemptId;
}
@Override
public float getProgress() {
return 1.0f;
}
{code}
When the taskAttempt is completed, the progress will always return 1.0 whenever
the result is failed or succeed. This will let users confused. May be it should
be reset to 0 better. I attach a screen shot of this case.
> TaskAttempt Page should reset the progress to 0 when its state is failed
>
>
> Key: MAPREDUCE-6586
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6586
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: webapps
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
>
> The progress of taskAttempt is not correctly showing when the taskAttempt is
> failed. The value is 100.00, but actually the taskAttempt is failed. And I
> found the reason is following:
> {code:title=CompletedTaskAttempt.java|borderStyle=solid}
> @Override
> public Counters getCounters() {
> return attemptInfo.getCounters();
> }
> @Override
> public TaskAttemptId getID() {
> return attemptId;
> }
> @Override
> public float getProgress() {
> return 1.0f;
> }
> {code}
> When the taskAttempt is completed, the progress will always return 1.0
> whenever the result is failed or succeed. This will let users confused. May
> be it should be reset to 0 better. I attach a screen shot of this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MAPREDUCE-6586) TaskAttempt Page should reset the progress to 0 when its state is failed
Lin Yiqun created MAPREDUCE-6586:
Summary: TaskAttempt Page should reset the progress to 0 when its
state is failed
Key: MAPREDUCE-6586
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6586
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: webapps
Affects Versions: 2.7.1
Reporter: Lin Yiqun
Assignee: Lin Yiqun
The progress of taskAttempt is not correctly showing when the taskAttempt is
failed. The value is 100.00, but actually the taskAttempt is failed. And I
found the reason is following:
{code:title=.CompletedTaskAttempt.java|borderStyle=solid}
@Override
public Counters getCounters() {
return attemptInfo.getCounters();
}
@Override
public TaskAttemptId getID() {
return attemptId;
}
@Override
public float getProgress() {
return 1.0f;
}
{code}
When the taskAttempt is completed, the progress will always return 1.0 whenever
the result is failed or succeed. This will let users confused. May be it should
be reset to 0 better. I attach a screen shot of this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6552) Add job search button in JobHistoryServer WebUI
[ https://issues.apache.org/jira/browse/MAPREDUCE-6552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054163#comment-15054163 ] Lin Yiqun commented on MAPREDUCE-6552: -- Hi [~ajisakaa], could you have time review my patch for this jira? The test is all passed and no failed test. > Add job search button in JobHistoryServer WebUI > --- > > Key: MAPREDUCE-6552 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6552 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: webapps >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun > Attachments: MAPREDUCE-6552.001.patch, MAPREDUCE-6552.002.patch, > Screen Shot 2015-11-19.png > > > In jobhistory webui, it's not convenient to direct search the specific > retired job when there are only few job records in page.And if you want to > show more jobs in page(so that you can find your target job), the main page > will be opened slowly.Because the renderd page will be large,and the browser > will be cost much time to download this page.So we can add a search job > button , and by inputing a specific jobid and clicking the button, we can > jump its job page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6552) Add job search button in JobHistoryServer WebUI
[ https://issues.apache.org/jira/browse/MAPREDUCE-6552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6552: - Attachment: MAPREDUCE-6552.002.patch Modify the checkstyle warning and update the patch. > Add job search button in JobHistoryServer WebUI > --- > > Key: MAPREDUCE-6552 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6552 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: webapps >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun > Attachments: MAPREDUCE-6552.001.patch, MAPREDUCE-6552.002.patch, > Screen Shot 2015-11-19.png > > > In jobhistory webui, it's not convenient to direct search the specific > retired job when there are only few job records in page.And if you want to > show more jobs in page(so that you can find your target job), the main page > will be opened slowly.Because the renderd page will be large,and the browser > will be cost much time to download this page.So we can add a search job > button , and by inputing a specific jobid and clicking the button, we can > jump its job page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6552) Add job search button in JobHistoryServer WebUI
[ https://issues.apache.org/jira/browse/MAPREDUCE-6552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6552: - Attachment: Screen Shot 2015-11-19.png > Add job search button in JobHistoryServer WebUI > --- > > Key: MAPREDUCE-6552 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6552 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: webapps >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun > Attachments: MAPREDUCE-6552.001.patch, Screen Shot 2015-11-19.png > > > In jobhistory webui, it's not convenient to direct search the specific > retired job when there are only few job records in page.And if you want to > show more jobs in page(so that you can find your target job), the main page > will be opened slowly.Because the renderd page will be large,and the browser > will be cost much time to download this page.So we can add a search job > button , and by inputing a specific jobid and clicking the button, we can > jump its job page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6552) Add job search button in JobHistoryServer WebUI
[ https://issues.apache.org/jira/browse/MAPREDUCE-6552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6552: - Attachment: MAPREDUCE-6552.001.patch > Add job search button in JobHistoryServer WebUI > --- > > Key: MAPREDUCE-6552 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6552 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: webapps >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun > Attachments: MAPREDUCE-6552.001.patch > > > In jobhistory webui, it's not convenient to direct search the specific > retired job when there are only few job records in page.And if you want to > show more jobs in page(so that you can find your target job), the main page > will be opened slowly.Because the renderd page will be large,and the browser > will be cost much time to download this page.So we can add a search job > button , and by inputing a specific jobid and clicking the button, we can > jump its job page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MAPREDUCE-6552) Add job search button in JobHistoryServer WebUI
Lin Yiqun created MAPREDUCE-6552: Summary: Add job search button in JobHistoryServer WebUI Key: MAPREDUCE-6552 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6552 Project: Hadoop Map/Reduce Issue Type: Improvement Components: webapps Affects Versions: 2.7.1 Reporter: Lin Yiqun Assignee: Lin Yiqun In jobhistory webui, it's not convenient to direct search the specific retired job when there are only few job records in page.And if you want to show more jobs in page(so that you can find your target job), the main page will be opened slowly.Because the renderd page will be large,and the browser will be cost much time to download this page.So we can add a search job button , and by inputing a specific jobid and clicking the button, we can jump its job page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6552) Add job search button in JobHistoryServer WebUI
[ https://issues.apache.org/jira/browse/MAPREDUCE-6552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6552: - Status: Patch Available (was: Open) I attach a init patch and a screen shot .In my patch,I add a button and some javascript code. > Add job search button in JobHistoryServer WebUI > --- > > Key: MAPREDUCE-6552 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6552 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: webapps >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun > > In jobhistory webui, it's not convenient to direct search the specific > retired job when there are only few job records in page.And if you want to > show more jobs in page(so that you can find your target job), the main page > will be opened slowly.Because the renderd page will be large,and the browser > will be cost much time to download this page.So we can add a search job > button , and by inputing a specific jobid and clicking the button, we can > jump its job page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6551) Dynamic adjust mapTaskAttempt memory size
[
https://issues.apache.org/jira/browse/MAPREDUCE-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated MAPREDUCE-6551:
-
Status: Patch Available (was: Open)
> Dynamic adjust mapTaskAttempt memory size
> -
>
> Key: MAPREDUCE-6551
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6551
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: task
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
> Attachments: MAPREDUCE-6551.001.patch
>
>
> I found a scenario that the map tasks cost so much resource of cluster.This
> scenario will be happened that if there are many small file blokcs (even some
> are not reach 1M),and this will lead to many map task to read.And in
> gengeral,a map task attempt will use the default config
> {{MRJobConfig#MAP_MEMORY_MB}} to set its resourceCapcity's memory to deal
> with their datas.And this will cause a problem that map tasks cost so much
> memory resource and target data is small.So I have a idea that wherther we
> can dynamic set mapTaskAttempt memory size by its inputDataLength.And this
> value can be provided by {{TaskSplitMetaInfo#getInputDataLength}}
> methods.Besides that,we should provided a standard unit dataLength for a
> standard memory size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6551) Dynamic adjust mapTaskAttempt memory size
[
https://issues.apache.org/jira/browse/MAPREDUCE-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated MAPREDUCE-6551:
-
Attachment: MAPREDUCE-6551.001.patch
> Dynamic adjust mapTaskAttempt memory size
> -
>
> Key: MAPREDUCE-6551
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6551
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: task
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
> Attachments: MAPREDUCE-6551.001.patch
>
>
> I found a scenario that the map tasks cost so much resource of cluster.This
> scenario will be happened that if there are many small file blokcs (even some
> are not reach 1M),and this will lead to many map task to read.And in
> gengeral,a map task attempt will use the default config
> {{MRJobConfig#MAP_MEMORY_MB}} to set its resourceCapcity's memory to deal
> with their datas.And this will cause a problem that map tasks cost so much
> memory resource and target data is small.So I have a idea that wherther we
> can dynamic set mapTaskAttempt memory size by its inputDataLength.And this
> value can be provided by {{TaskSplitMetaInfo#getInputDataLength}}
> methods.Besides that,we should provided a standard unit dataLength for a
> standard memory size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6551) Dynamic adjust mapTaskAttempt memory size
[
https://issues.apache.org/jira/browse/MAPREDUCE-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010955#comment-15010955
]
Lin Yiqun commented on MAPREDUCE-6551:
--
I add the 3 new config info
* MRJobConfig.MAP_MEMORY_MB_AUTOSET_ENABLED:wherther enable this function
* MRJobConfig.MAP_UNIT_INPUT_LENGTH:the standard unit deal data length.
And if auto-set function is enabled, in
{{MapTaskAttemptImpl#autoSetMemorySize}} method will adjust memory size by its
{{splitInfo}} dataLength.If dataLength is large than UNIT_INPUT_LENGTH,the size
will be larger, other will be smaller.
> Dynamic adjust mapTaskAttempt memory size
> -
>
> Key: MAPREDUCE-6551
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6551
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: task
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
>
> I found a scenario that the map tasks cost so much resource of cluster.This
> scenario will be happened that if there are many small file blokcs (even some
> are not reach 1M),and this will lead to many map task to read.And in
> gengeral,a map task attempt will use the default config
> {{MRJobConfig#MAP_MEMORY_MB}} to set its resourceCapcity's memory to deal
> with their datas.And this will cause a problem that map tasks cost so much
> memory resource and target data is small.So I have a idea that wherther we
> can dynamic set mapTaskAttempt memory size by its inputDataLength.And this
> value can be provided by {{TaskSplitMetaInfo#getInputDataLength}}
> methods.Besides that,we should provided a standard unit dataLength for a
> standard memory size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MAPREDUCE-6551) Dynamic adjust mapTaskAttempt memory size
Lin Yiqun created MAPREDUCE-6551:
Summary: Dynamic adjust mapTaskAttempt memory size
Key: MAPREDUCE-6551
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6551
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: task
Affects Versions: 2.7.1
Reporter: Lin Yiqun
Assignee: Lin Yiqun
I found a scenario that the map tasks cost so much resource of cluster.This
scenario will be happened that if there are many small file blokcs (even some
are not reach 1M),and this will lead to many map task to read.And in gengeral,a
map task attempt will use the default config {{MRJobConfig#MAP_MEMORY_MB}} to
set its resourceCapcity's memory to deal with their datas.And this will cause a
problem that map tasks cost so much memory resource and target data is small.So
I have a idea that wherther we can dynamic set mapTaskAttempt memory size by
its inputDataLength.And this value can be provided by
{{TaskSplitMetaInfo#getInputDataLength}} methods.Besides that,we should
provided a standard unit dataLength for a standard memory size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6548) Jobs executed can be configurated with specific users and time hours
[ https://issues.apache.org/jira/browse/MAPREDUCE-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6548: - Resolution: Invalid Status: Resolved (was: Patch Available) > Jobs executed can be configurated with specific users and time hours > > > Key: MAPREDUCE-6548 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6548 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: job submission >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun > Attachments: MAPREDUCE-6548.001.patch > > > In recent hadoop versions,the system has no limitation for users to execute > their jobs if you don't configurate ACL.And I find that the ACL is only > called in IPC, isn't operated in job submissions.And this condition can't > satisfied with this case that I have a very important job, and I am prepared > to execute this job in 0 to 9 o'clock.In order to let this job executed > quickly, I am not allowed other user's job to execute in these time. So I can > see the result in tomorrow morning.So may be we can let jobs executed with > specific users in specific time hours. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6548) Jobs executed can be configurated with specific users and time hours
[ https://issues.apache.org/jira/browse/MAPREDUCE-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008500#comment-15008500 ] Lin Yiqun commented on MAPREDUCE-6548: -- Thanks [~ste...@apache.org] for comments.I have ignored some other influence of hive or spark on yarn,. That's a good idea to create a special queue for critical jobs now.But I thinks maybe we can do some admission control for jobs in some other aspects in the future. > Jobs executed can be configurated with specific users and time hours > > > Key: MAPREDUCE-6548 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6548 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: job submission >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun > Attachments: MAPREDUCE-6548.001.patch > > > In recent hadoop versions,the system has no limitation for users to execute > their jobs if you don't configurate ACL.And I find that the ACL is only > called in IPC, isn't operated in job submissions.And this condition can't > satisfied with this case that I have a very important job, and I am prepared > to execute this job in 0 to 9 o'clock.In order to let this job executed > quickly, I am not allowed other user's job to execute in these time. So I can > see the result in tomorrow morning.So may be we can let jobs executed with > specific users in specific time hours. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6499) Add elapsed time for retired job in JobHistoryServer WebUI
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008464#comment-15008464 ] Lin Yiqun commented on MAPREDUCE-6499: -- Thanks [~ajisakaa] for commit ! > Add elapsed time for retired job in JobHistoryServer WebUI > -- > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: webapps >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun > Fix For: 2.8.0 > > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch, > HADOOP-MAPREDUCE-6499.5.patch, HADOOP-MAPREDUCE-6499.6.patch, > HADOOP-MAPREDUCE-6499.7.patch, HADOOP-MAPREDUCE-6499.8.patch, > HADOOP-MAPREDUCE-6499.9.patch, HADOOP-MAPREDUCE-6499.patch, Screen Shot > 2015-11-13 at 23.47.10.png > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6548) Jobs executed can be configurated with specific users and time hours
[ https://issues.apache.org/jira/browse/MAPREDUCE-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6548: - Affects Version/s: 2.7.1 > Jobs executed can be configurated with specific users and time hours > > > Key: MAPREDUCE-6548 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6548 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: job submission >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun > Attachments: MAPREDUCE-6548.001.patch > > > In recent hadoop versions,the system has no limitation for users to execute > their jobs if you don't configurate ACL.And I find that the ACL is only > called in IPC, isn't operated in job submissions.And this condition can't > satisfied with this case that I have a very important job, and I am prepared > to execute this job in 0 to 9 o'clock.In order to let this job executed > quickly, I am not allowed other user's job to execute in these time. So I can > see the result in tomorrow morning.So may be we can let jobs executed with > specific users in specific time hours. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6548) Jobs executed can be configurated with specific users and time hours
[ https://issues.apache.org/jira/browse/MAPREDUCE-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005817#comment-15005817 ] Lin Yiqun commented on MAPREDUCE-6548: -- Hi [~bikassaha],I look through the jira YARN-1051.I think it tends to let jobs executed with the RM at admission control time.And these jobs guaranteed enough resources.But the main of my idea is to limit users/jobs and limit time-hours with a simple check in job-client. And it's not only for guaranteed the important jobs have enough resources, that's a satisfied scenario of this function.So I will have a users/time admission control and don't allowed the unsatisfied jobs to be submited to cluster. And this function is easy to be achieved in job-client rather than in YRAN. > Jobs executed can be configurated with specific users and time hours > > > Key: MAPREDUCE-6548 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6548 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: job submission >Reporter: Lin Yiqun >Assignee: Lin Yiqun > Attachments: MAPREDUCE-6548.001.patch > > > In recent hadoop versions,the system has no limitation for users to execute > their jobs if you don't configurate ACL.And I find that the ACL is only > called in IPC, isn't operated in job submissions.And this condition can't > satisfied with this case that I have a very important job, and I am prepared > to execute this job in 0 to 9 o'clock.In order to let this job executed > quickly, I am not allowed other user's job to execute in these time. So I can > see the result in tomorrow morning.So may be we can let jobs executed with > specific users in specific time hours. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6548) Jobs executed can be configurated with specific users and time hours
[ https://issues.apache.org/jira/browse/MAPREDUCE-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6548: - Attachment: MAPREDUCE-6548.001.patch > Jobs executed can be configurated with specific users and time hours > > > Key: MAPREDUCE-6548 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6548 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: job submission >Reporter: Lin Yiqun >Assignee: Lin Yiqun > Attachments: MAPREDUCE-6548.001.patch > > > In recent hadoop versions,the system has no limitation for users to execute > their jobs if you don't configurate ACL.And I find that the ACL is only > called in IPC, isn't operated in job submissions.And this condition can't > satisfied with this case that I have a very important job, and I am prepared > to execute this job in 0 to 9 o'clock.In order to let this job executed > quickly, I am not allowed other user's job to execute in these time. So I can > see the result in tomorrow morning.So may be we can let jobs executed with > specific users in specific time hours. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6548) Jobs executed can be configurated with specific users and time hours
[
https://issues.apache.org/jira/browse/MAPREDUCE-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated MAPREDUCE-6548:
-
Status: Patch Available (was: Open)
I attach a initial patch.I do some user-check and time-check in job submission
methods {{Job#submit}} and {{Job#waitForCompletion}}. And I add the 3 new
config as below.
* MAPREDUCE_LIMIT_EXECUTED_ENABLED:whether enable the limit-executed function.
* MAPREDUCE_LIMIT_EXECUTED_USERS:the user that can be executed in cluster.
* MAPREDUCE_LIMIT_EXECUTED_HOURS:the job can be executed in these hours in this
config value.
> Jobs executed can be configurated with specific users and time hours
>
>
> Key: MAPREDUCE-6548
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6548
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: job submission
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
>
> In recent hadoop versions,the system has no limitation for users to execute
> their jobs if you don't configurate ACL.And I find that the ACL is only
> called in IPC, isn't operated in job submissions.And this condition can't
> satisfied with this case that I have a very important job, and I am prepared
> to execute this job in 0 to 9 o'clock.In order to let this job executed
> quickly, I am not allowed other user's job to execute in these time. So I can
> see the result in tomorrow morning.So may be we can let jobs executed with
> specific users in specific time hours.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6548) Jobs executed can be configurated with specific users and time hours
[ https://issues.apache.org/jira/browse/MAPREDUCE-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6548: - Description: In recent hadoop versions,the system has no limitation for users to execute their jobs if you don't configurate ACL.And I find that the ACL is only called in IPC, isn't operated in job submissions.And this condition can't satisfied with this case that I have a very important job, and I am prepared to execute this job in 0 to 9 o'clock.In order to let this job executed quickly, I am not allowed other user's job to execute in these time. So I can see the result in tomorrow morning.So may be we can let jobs executed with specific users in specific time hours. (was: In recent hadoop versions,the system has no limitation for users to execute their jobs if you don't configurate ACL.And I find that the ACL is only called in IPC, isn't operated in job submissions.And this condition can't satisfied with this case that I have a very important job, and I am prepared to execute this job in 0 to 9 o'clock.In order to let this job executed quickli, I am not allowed other users job to execute in these time. So I can see the result in tomorrow morning.So may be we can let jobs executed with specific users in specific time hours.) > Jobs executed can be configurated with specific users and time hours > > > Key: MAPREDUCE-6548 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6548 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: job submission >Reporter: Lin Yiqun >Assignee: Lin Yiqun > > In recent hadoop versions,the system has no limitation for users to execute > their jobs if you don't configurate ACL.And I find that the ACL is only > called in IPC, isn't operated in job submissions.And this condition can't > satisfied with this case that I have a very important job, and I am prepared > to execute this job in 0 to 9 o'clock.In order to let this job executed > quickly, I am not allowed other user's job to execute in these time. So I can > see the result in tomorrow morning.So may be we can let jobs executed with > specific users in specific time hours. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MAPREDUCE-6548) Jobs executed can be configurated with specific users and time hours
Lin Yiqun created MAPREDUCE-6548: Summary: Jobs executed can be configurated with specific users and time hours Key: MAPREDUCE-6548 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6548 Project: Hadoop Map/Reduce Issue Type: Improvement Components: job submission Reporter: Lin Yiqun Assignee: Lin Yiqun In recent hadoop versions,the system has no limitation for users to execute their jobs if you don't configurate ACL.And I find that the ACL is only called in IPC, isn't operated in job submissions.And this condition can't satisfied with this case that I have a very important job, and I am prepared to execute this job in 0 to 9 o'clock.In order to let this job executed quickli, I am not allowed other users job to execute in these time. So I can see the result in tomorrow morning.So may be we can let jobs executed with specific users in specific time hours. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6499) Add elapsed time for retired job in JobHistoryServer WebUI
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004133#comment-15004133 ] Lin Yiqun commented on MAPREDUCE-6499: -- Thanks [~ajisakaa] reviews. > Add elapsed time for retired job in JobHistoryServer WebUI > -- > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: webapps >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch, > HADOOP-MAPREDUCE-6499.5.patch, HADOOP-MAPREDUCE-6499.6.patch, > HADOOP-MAPREDUCE-6499.7.patch, HADOOP-MAPREDUCE-6499.8.patch, > HADOOP-MAPREDUCE-6499.9.patch, HADOOP-MAPREDUCE-6499.patch, Screen Shot > 2015-11-13 at 23.47.10.png > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000329#comment-15000329 ] Lin Yiqun commented on MAPREDUCE-6499: -- Thanks [~ajisakaa] comment.I updated the method annotaion and attach the patch. > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch, > HADOOP-MAPREDUCE-6499.5.patch, HADOOP-MAPREDUCE-6499.6.patch, > HADOOP-MAPREDUCE-6499.7.patch, HADOOP-MAPREDUCE-6499.8.patch, > HADOOP-MAPREDUCE-6499.9.patch, HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6499: - Attachment: HADOOP-MAPREDUCE-6499.9.patch > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch, > HADOOP-MAPREDUCE-6499.5.patch, HADOOP-MAPREDUCE-6499.6.patch, > HADOOP-MAPREDUCE-6499.7.patch, HADOOP-MAPREDUCE-6499.8.patch, > HADOOP-MAPREDUCE-6499.9.patch, HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997830#comment-14997830 ] Lin Yiqun commented on MAPREDUCE-6499: -- The faild test is likely not related. > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch, > HADOOP-MAPREDUCE-6499.5.patch, HADOOP-MAPREDUCE-6499.6.patch, > HADOOP-MAPREDUCE-6499.7.patch, HADOOP-MAPREDUCE-6499.8.patch, > HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[
https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996481#comment-14996481
]
Lin Yiqun commented on MAPREDUCE-6499:
--
That's a good point.Thanks [~ajisakaa].I update with a sortable time
format.It's similar to hrs,mins,seconds.The methond {{StringUtils.formatTime}}
will be sorted not correctlly because some the format has not a complete same
format,and the elapsed time is a string comparation,it will compare from left
to right.So it will appear "44sec is larger than 1mins",I update a new format
method {{StringUtils.formatTimeSortable}},The format is like
"00hrs,00mins,00sec", but this format will not satisfied with all times.When
the hours is more than 99hours,it will be show a max value
"99hrs,59mins,59sec".But I think this is enough for we to find the
long-time-running jobs.And this methods can be reuse in other cases When I
define it in hadoop-common-project.I attch the updated patch.
> Add More Informations Of Jobs In JobHistory Main Page
> -
>
> Key: MAPREDUCE-6499
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
>Priority: Trivial
> Attachments: HADOOP-MAPREDUCE-6499.2.patch,
> HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch,
> HADOOP-MAPREDUCE-6499.5.patch, HADOOP-MAPREDUCE-6499.6.patch,
> HADOOP-MAPREDUCE-6499.7.patch, HADOOP-MAPREDUCE-6499.8.patch,
> HADOOP-MAPREDUCE-6499.patch
>
>
> Now in JobHistory Main Page show too little information about finished
> jobs,even don't have the job's running total time,only
> startTime,finishedTime.So,in jobHistory main page,we can add more
> informations about jobs, that we can better analyze jobs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6499: - Attachment: HADOOP-MAPREDUCE-6499.8.patch > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch, > HADOOP-MAPREDUCE-6499.5.patch, HADOOP-MAPREDUCE-6499.6.patch, > HADOOP-MAPREDUCE-6499.7.patch, HADOOP-MAPREDUCE-6499.8.patch, > HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[
https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986380#comment-14986380
]
Lin Yiqun commented on MAPREDUCE-6499:
--
Thanks [~ajisakaa] advices.I accept your first comment.It's simple to use
{{StringUtils.formatTime}} method to show times, and can be consistent with
other pages that also has show elapsed time.The hh:mm:ss is also good format
,but when the elapsed time is more than 99:99:99, maybe it can'be show the real
value,and still be 99:99:99.And finally I update the patch.
> Add More Informations Of Jobs In JobHistory Main Page
> -
>
> Key: MAPREDUCE-6499
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
>Affects Versions: 2.7.1
>Reporter: Lin Yiqun
>Assignee: Lin Yiqun
>Priority: Trivial
> Attachments: HADOOP-MAPREDUCE-6499.2.patch,
> HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch,
> HADOOP-MAPREDUCE-6499.5.patch, HADOOP-MAPREDUCE-6499.6.patch,
> HADOOP-MAPREDUCE-6499.7.patch, HADOOP-MAPREDUCE-6499.patch
>
>
> Now in JobHistory Main Page show too little information about finished
> jobs,even don't have the job's running total time,only
> startTime,finishedTime.So,in jobHistory main page,we can add more
> informations about jobs, that we can better analyze jobs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6499: - Attachment: HADOOP-MAPREDUCE-6499.7.patch > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch, > HADOOP-MAPREDUCE-6499.5.patch, HADOOP-MAPREDUCE-6499.6.patch, > HADOOP-MAPREDUCE-6499.7.patch, HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6499: - Attachment: HADOOP-MAPREDUCE-6499.6.patch Simplified the patch, only leave the elapsed time and modfiy some wrong hint text in search input. > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch, > HADOOP-MAPREDUCE-6499.5.patch, HADOOP-MAPREDUCE-6499.6.patch, > HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978292#comment-14978292 ] Lin Yiqun commented on MAPREDUCE-6499: -- Thanks [~ajisakaa] advices. So should I update my patch and only leave the things as you said ? > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch, > HADOOP-MAPREDUCE-6499.5.patch, HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977445#comment-14977445 ] Lin Yiqun commented on MAPREDUCE-6499: -- Thanks [~ajisakaa] review. I update the patch.But there is a problem when the history job is larger enough, it will be load much more job infos and so slowly to open jobhistory pages. > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch, > HADOOP-MAPREDUCE-6499.5.patch, HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6499: - Attachment: HADOOP-MAPREDUCE-6499.5.patch add missed the elapsed time value. > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch, > HADOOP-MAPREDUCE-6499.5.patch, HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969228#comment-14969228 ] Lin Yiqun commented on MAPREDUCE-6499: -- [~ste...@apache.org] > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch, > HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969227#comment-14969227 ] Lin Yiqun commented on MAPREDUCE-6499: -- Steve Loughran,can you have time review my patch, test is all passed,thanks > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch, > HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14967290#comment-14967290 ] Lin Yiqun commented on MAPREDUCE-6499: -- please review my patch, thank you. > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch, > HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6499: - Attachment: HADOOP-MAPREDUCE-6499.4.patch modify remain checkstyle issues. > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch, > HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6499: - Attachment: (was: HADOOP-MAPREDUCE-6499.4.patch) > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6499: - Attachment: HADOOP-MAPREDUCE-6499.4.patch modify some checkstyle issues. > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.4.patch, > HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6499: - Attachment: HADOOP-MAPREDUCE-6499.3.patch modify some whitespace error other some warn. > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Fix For: 2.7.1 > > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.3.patch, HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6499: - Attachment: HADOOP-MAPREDUCE-6499.2.patch add the latest new patch. > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Fix For: 2.7.1 > > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6499: - Attachment: (was: HADOOP-MAPREDUCE-6499.2.patch) > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Fix For: 2.7.1 > > Attachments: HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6499: - Attachment: HADOOP-MAPREDUCE-6499.2.patch modify TestHsJobsBlock testcase and modify wrong name hint in search input on bottom of jobHistory app page table. > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Fix For: 2.7.1 > > Attachments: HADOOP-MAPREDUCE-6499.2.patch, > HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated MAPREDUCE-6499: - Attachment: HADOOP-MAPREDUCE-6499.patch > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Fix For: 2.7.1 > > Attachments: HADOOP-MAPREDUCE-6499.patch > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
[ https://issues.apache.org/jira/browse/MAPREDUCE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun resolved MAPREDUCE-6499. -- Resolution: Fixed Totally add the follow informations: 1.UberTask-where the job is uberTask type. 2.Avg MapTime 3.Avg MergeTime 4.Avg ShuffleTime 5.Avg ReduceTime 6.Failed MapAttempts 7.Failed ReduceAttempts 8.Successed MapAttempts 9.Successed ReduceAttempts and then change the jobPage showing's code.And we can sort Jobs in page with more different conditions. > Add More Informations Of Jobs In JobHistory Main Page > - > > Key: MAPREDUCE-6499 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Lin Yiqun >Assignee: Lin Yiqun >Priority: Trivial > Fix For: 2.7.1 > > > Now in JobHistory Main Page show too little information about finished > jobs,even don't have the job's running total time,only > startTime,finishedTime.So,in jobHistory main page,we can add more > informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MAPREDUCE-6499) Add More Informations Of Jobs In JobHistory Main Page
Lin Yiqun created MAPREDUCE-6499: Summary: Add More Informations Of Jobs In JobHistory Main Page Key: MAPREDUCE-6499 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6499 Project: Hadoop Map/Reduce Issue Type: Improvement Reporter: Lin Yiqun Assignee: Lin Yiqun Priority: Trivial Fix For: 2.7.1 Now in JobHistory Main Page show too little information about finished jobs,even don't have the job's running total time,only startTime,finishedTime.So,in jobHistory main page,we can add more informations about jobs, that we can better analyze jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
