-
Notifications
You must be signed in to change notification settings - Fork 134
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
New Jar Files With Same App Name Not Used #91
Comments
This is expected. Right now due to the way classloaders work, you cannot Enabling dynamic reload of the same jar in the same context is a pretty On Mon, Nov 24, 2014 at 10:18 AM, paulmagid [email protected]
The fruit of silence is prayer; |
From looking at the code this is what we expected might be the case: that jobserver behaves this way by design and the issue cannot be easily fixed due to other upstream problems. Would it be possible to treat this as a documentation bug because this cost us 5 days to track down what was causing the behavior then narrow in and read the code and really understand what is going on? We could not find documentation or reports of this issue/behavior anywhere. Maybe we were not looking in the right spots but probably the behavior and the work-around should be clearly documented somewhere in the official documentation. |
@paulmagid, sorry about the wasted time. Yes, let's definitely make it a On Tue, Nov 25, 2014 at 7:46 AM, paulmagid [email protected] wrote:
The fruit of silence is prayer; |
Speaking of which, would it be helpful to create a wiki instead of a giant On Tue, Nov 25, 2014 at 8:34 AM, Evan Chan [email protected] wrote:
The fruit of silence is prayer; |
I think so… At some point the amount of info gets too unwieldy for a README. Thanks, Paul Magid From: Evan Chan [mailto:[email protected]] Speaking of which, would it be helpful to create a wiki instead of a giant On Tue, Nov 25, 2014 at 8:34 AM, Evan Chan <[email protected]mailto:[email protected]> wrote:
The fruit of silence is prayer; — |
If you submit a new jar file to a named context only the first Jar file is executed. Subsequent uploads are ignored until a spark-jobserver restart. If you submit a jar to the default context this issue does not occur.
The text was updated successfully, but these errors were encountered: