Skip to content
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

Open
paulmagid opened this issue Nov 24, 2014 · 5 comments
Open

New Jar Files With Same App Name Not Used #91

paulmagid opened this issue Nov 24, 2014 · 5 comments

Comments

@paulmagid
Copy link

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.

@velvia
Copy link
Contributor

velvia commented Nov 25, 2014

This is expected. Right now due to the way classloaders work, you cannot
update the same jar in the same context. However, you don't have to
restart the jobserver. You can simply -X DELETE the context and when you
create a new one the jar will reload.

Enabling dynamic reload of the same jar in the same context is a pretty
difficult problem and would require more changes in Spark itself.

On Mon, Nov 24, 2014 at 10:18 AM, paulmagid [email protected]
wrote:

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.


Reply to this email directly or view it on GitHub
#91.

The fruit of silence is prayer;
the fruit of prayer is faith;
the fruit of faith is love;
the fruit of love is service;
the fruit of service is peace. -- Mother Teresa

@paulmagid
Copy link
Author

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.

@velvia
Copy link
Contributor

velvia commented Nov 25, 2014

@paulmagid, sorry about the wasted time. Yes, let's definitely make it a
doc bug.

On Tue, Nov 25, 2014 at 7:46 AM, paulmagid [email protected] wrote:

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.


Reply to this email directly or view it on GitHub
#91 (comment)
.

The fruit of silence is prayer;
the fruit of prayer is faith;
the fruit of faith is love;
the fruit of love is service;
the fruit of service is peace. -- Mother Teresa

@velvia
Copy link
Contributor

velvia commented Nov 25, 2014

Speaking of which, would it be helpful to create a wiki instead of a giant
README?

On Tue, Nov 25, 2014 at 8:34 AM, Evan Chan [email protected] wrote:

@paulmagid, sorry about the wasted time. Yes, let's definitely make it a
doc bug.

On Tue, Nov 25, 2014 at 7:46 AM, paulmagid [email protected]
wrote:

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.


Reply to this email directly or view it on GitHub
#91 (comment)
.

The fruit of silence is prayer;
the fruit of prayer is faith;
the fruit of faith is love;
the fruit of love is service;
the fruit of service is peace. -- Mother Teresa

The fruit of silence is prayer;
the fruit of prayer is faith;
the fruit of faith is love;
the fruit of love is service;
the fruit of service is peace. -- Mother Teresa

@paulmagid
Copy link
Author

I think so… At some point the amount of info gets too unwieldy for a README.

Thanks,

Paul Magid
Toyota Motor Sales IS Enterprise Architecture (EA)
Architect I R&D
Ph: 310-468-9091 (X69091)
PCN 1C2970, Mail Drop PN12

From: Evan Chan [mailto:[email protected]]
Sent: Tuesday, November 25, 2014 8:35 AM
To: ooyala/spark-jobserver
Cc: Paul Magid
Subject: Re: [spark-jobserver] New Jar Files With Same App Name Not Used (#91)

Speaking of which, would it be helpful to create a wiki instead of a giant
README?

On Tue, Nov 25, 2014 at 8:34 AM, Evan Chan <[email protected]mailto:[email protected]> wrote:

@paulmagid, sorry about the wasted time. Yes, let's definitely make it a
doc bug.

On Tue, Nov 25, 2014 at 7:46 AM, paulmagid <[email protected]mailto:[email protected]>
wrote:

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.


Reply to this email directly or view it on GitHub
#91 (comment)
.

The fruit of silence is prayer;
the fruit of prayer is faith;
the fruit of faith is love;
the fruit of love is service;
the fruit of service is peace. -- Mother Teresa

The fruit of silence is prayer;
the fruit of prayer is faith;
the fruit of faith is love;
the fruit of love is service;
the fruit of service is peace. -- Mother Teresa


Reply to this email directly or view it on GitHubhttps://github.com//issues/91#issuecomment-64428677.

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

No branches or pull requests

2 participants