The driver does not do processing (for the most part), but it does do
scheduling and block management, so it can keep around a significant amount
of metadata about all the stored RDD and broadcast blocks, as well as
statistics about prior executions. Much of this is bounded in some way,
though, so
Hi Guys,
I would like understanding why the Driver's RAM goes down, Does the
processing occur only in the workers?
Thanks
# Start Tests
computer1(Worker/Source Stream)
23:57:18 up 12:03, 1 user, load average: 0.03, 0.31, 0.44
total used free sharedbuffers
