Mich, thanks for the suggestion. I tried your settings, but they did not solve the problem.
I'm running in yarn-client mode, not local or standalone, so the resources in the Spark cluster (which is very large) should not be an issue. Right? The problem seems to be that Zeppelin is not submitting the 2nd job to the Spark cluster.