Skip to content

[SPARK-18959] the new leader will lost the statistics of the driver's resource on the worker When the leader master has changed. - #16525

Closed
hustfxj wants to merge 1 commit into
apache:masterfrom
hustfxj:2017
Closed

[SPARK-18959] the new leader will lost the statistics of the driver's resource on the worker When the leader master has changed.#16525
hustfxj wants to merge 1 commit into
apache:masterfrom
hustfxj:2017

Conversation

@hustfxj

Copy link
Copy Markdown
Contributor

I deploy the standalone cluster with two masters. and utilize zooKeeper to provide leader election. Firstly, I submit the application with cluster mode. Then I kill the leader master, and the standby master will be the leader. But the new leader will lost the statistics of the driver's resource. Then I stop the application, we will see the negative used resource at the worker from masterPage. Like that:

Workers
Worker Id	Address	State	Cores	Memory
worker-20161220162751-10.125.6.222-59295	10.125.6.222:59295	ALIVE	4 (-1 Used)	6.8 GB (-1073741824.0 B Used)
worker-20161220164233-10.218.135.80-10944	10.218.135.80:10944	ALIVE	4 (0 Used)	6.8 GB (0.0 B Used)

Because the new leader forget calculate the driver‘ resource when the master receive the "WorkerLatestState" message. At the same time we can set RUNNING state for the app after the master receive the message, otherwise the app' state will still be WAITTING.

…the worker When the leader master has changed.
@hustfxjhustfxj changed the title the new leader will lost the statistics of the driver's resource on the worker When the leader master has changed.[SPARK-18959] the new leader will lost the statistics of the driver's resource on the worker When the leader master has changed.Jan 10, 2017
@AmplabJenkins

Copy link
Copy Markdown

Can one of the admins verify this patch?

@hustfxj

Copy link
Copy Markdown
ContributorAuthor

@srowen can you help review it ? I think it is a bug. Thank you very much.

@hustfxj

Copy link
Copy Markdown
ContributorAuthor

@srowen@andrewor14 can you review it again? Thank you

@jiangxb1987

Copy link
Copy Markdown
Contributor

@hustfxj Unluckily we don't support multi-master nodes in standalone mode, so could you please close this PR? Thank you!

@jiangxb1987jiangxb1987 mentioned this pull request Jun 25, 2017
zifeif2 pushed a commit to zifeif2/spark that referenced this pull request Nov 22, 2025
## What changes were proposed in this pull request?
This PR proposes to close stale PRs, mostly the same instances with apache#18017
I believe the author in apache#14807 removed his account.
Closesapache#7075Closesapache#8927Closesapache#9202Closesapache#9366Closesapache#10861Closesapache#11420Closesapache#12356Closesapache#13028Closesapache#13506Closesapache#14191Closesapache#14198Closesapache#14330Closesapache#14807Closesapache#15839Closesapache#16225Closesapache#16685Closesapache#16692Closesapache#16995Closesapache#17181Closesapache#17211Closesapache#17235Closesapache#17237Closesapache#17248Closesapache#17341Closesapache#17708Closesapache#17716Closesapache#17721Closesapache#17937
Added:
Closesapache#14739Closesapache#17139Closesapache#17445Closesapache#18042Closesapache#18359
Added:
Closesapache#16450Closesapache#16525Closesapache#17738
Added:
Closesapache#16458Closesapache#16508Closesapache#17714
Added:
Closesapache#17830Closesapache#14742
## How was this patch tested?
N/A
Author: hyukjinkwon <gurwls223@gmail.com>
Closesapache#18417 from HyukjinKwon/close-stale-pr.
Sign up for freeto 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.

3 participants

@hustfxj@AmplabJenkins@jiangxb1987