Skip to content

Fixes for SNAP-3147 : #185

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 29, 2019
Merged

Fixes for SNAP-3147 : #185

merged 3 commits into from
Nov 29, 2019

Conversation

snappy-sachin
Copy link

What changes were proposed in this pull request?

Problem: When cluster restarted and if user do not refresh the page "Uptime:" field is not showing the correct Uptime of cluster.

Fixes:

  • Removed HTML Page specific start date-time value.
    Instead using ClusterStatistics object creation date-time as start time.
  • Code refactoring

How was this patch tested?

  • Tested manually

(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

Please review http://spark.apache.org/contributing.html before opening a pull request.

 - Removed HTML Page specific start date-time value.
   Instead using ClusterStatistics object creating date-time as start time.
 - Code refactoring
@snappy-sachin
Copy link
Author

Merging

@snappy-sachin snappy-sachin merged commit 01e14ec into snappy/branch-2.1 Nov 29, 2019
@snappy-sachin snappy-sachin deleted the SNAP-3147 branch November 29, 2019 19:51
sumwale pushed a commit to sumwale/spark that referenced this pull request Nov 5, 2020
- Removed start date-time value created and stored in HTML Page.
- Code refactoring
sumwale pushed a commit that referenced this pull request Jul 11, 2021
- Removed start date-time value created and stored in HTML Page.
- Code refactoring
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants