Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Sep 2, 2016

What is this PR for?

PR is for logging configuration details of Zeppelin server.

What type of PR is it?

Improvement

Todos

  • - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-1182

How should this be tested?

Please check the log if information on Server host, server path, context path, zeppelin version, class path is available in that file.

Screenshots (if appropriate)

Questions:

  • Does the licenses files need update? No
  • Is there breaking changes for older versions? No
  • Does this needs documentation? No

Note:
For configuration details such as zeppelin version, server host, port & context path , these are available as part of zeppelin configuration.

Logging information

 INFO [2016-09-02 14:35:25,218] ({main} ZeppelinConfiguration.java[create]:107) - Server Host: 0.0.0.0
 INFO [2016-09-02 14:35:25,218] ({main} ZeppelinConfiguration.java[create]:108) - Server Port: 8080
 INFO [2016-09-02 14:35:25,218] ({main} ZeppelinConfiguration.java[create]:109) - Context Path: /
 INFO [2016-09-02 14:35:25,224] ({main} ZeppelinConfiguration.java[create]:110) - Zeppelin Version: 0.7.0-SNAPSHOT

For Zeppelin class path and restart information, I am logging it from Shell script to log file as in below paragraph, So the format of logging is different . I know this is not per standards, Please let me know if you have any suggestions

Zeppelin is restarted

ZEPPELIN_CLASSPATH: /home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-server/target/lib/*:/home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-zengine/target/lib/*:/home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-interpreter/target/lib/*:/home/rajarajang/Workspace/stsWorksapce/zeppelin/*::/home/rajarajang/Workspace/stsWorksapce/zeppelin/conf:/home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-interpreter/target/classes:/home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-zengine/target/classes:/home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-server/target/classes

@jongyoul
Copy link
Member

jongyoul commented Sep 6, 2016

Done or WIP?

@ghost
Copy link
Author

ghost commented Sep 7, 2016

I am logging the configuration details of Zeppelin . I am not sure if we have any more configuration details to be logged. Please check PR and let me know if any more configuration needs to be added.

@ghost
Copy link
Author

ghost commented Sep 14, 2016

@ALL: Please do review and let me know your opnion

@ghost
Copy link
Author

ghost commented Sep 19, 2016

Ping

Copy link
Member

@Leemoonsoo Leemoonsoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @rajarajan-g for the contribution.

I think the message can be printed in ${ZEPPELIN_OUTFILE} instead of ${ZEPPELIN_LOGFILE}. Then there will be no concern for log message format. And i think it's better print log message before Zeppelin process starts and the process holds both ${ZEPPELIN_OUTFILE} and ${ZEPPELIN_LOGFILE} files open.

wait_zeppelin_is_up_for_ci
sleep 2
check_if_process_is_alive
echo "ZEPPELIN_CLASSPATH: ${ZEPPELIN_CLASSPATH}" >> "${ZEPPELIN_LOGFILE}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think printing entire classpath i.e $ZEPPELIN_CLASSPATH_OVERRIDES:$CLASSPATH is more make sense. what do you think?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure.

But one quick question, Do we really set or use ZEPPELIN_CLASSPATH_OVERRIDES ? I don't see any assignment operation on that property. Please let me know if i am missing something.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ghost
Copy link
Author

ghost commented Sep 20, 2016

It makes more sense to have message logged in ${ZEPPELIN_OUTFILE} rather of ${ZEPPELIN_LOGFILE}.

@Leemoonsoo
Copy link
Member

CI failure is irrelevant.
LGTM and merge if there're no further discussions.

@asfgit asfgit closed this in eb01bdd Sep 21, 2016
pedrozatta pushed a commit to pedrozatta/zeppelin that referenced this pull request Oct 27, 2016
### What is this PR for?
PR is for logging configuration details of Zeppelin server.

### What type of PR is it?
Improvement

### Todos
* [ ] - Task

### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1182

### How should this be tested?
Please check the log if information on Server host, server path, context path, zeppelin version, class path is available in that file.

### Screenshots (if appropriate)

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No

Note:
    For configuration details such as  zeppelin version, server host, port & context path , these are available as part of zeppelin configuration.

Logging information

```
 INFO [2016-09-02 14:35:25,218] ({main} ZeppelinConfiguration.java[create]:107) - Server Host: 0.0.0.0
 INFO [2016-09-02 14:35:25,218] ({main} ZeppelinConfiguration.java[create]:108) - Server Port: 8080
 INFO [2016-09-02 14:35:25,218] ({main} ZeppelinConfiguration.java[create]:109) - Context Path: /
 INFO [2016-09-02 14:35:25,224] ({main} ZeppelinConfiguration.java[create]:110) - Zeppelin Version: 0.7.0-SNAPSHOT
```

For Zeppelin class path and restart information,  I am logging it from Shell script to log file as in below paragraph, So the format of logging is different . I know this is not per standards, Please let me know if you have any suggestions
```
Zeppelin is restarted

ZEPPELIN_CLASSPATH: /home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-server/target/lib/*:/home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-zengine/target/lib/*:/home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-interpreter/target/lib/*:/home/rajarajang/Workspace/stsWorksapce/zeppelin/*::/home/rajarajang/Workspace/stsWorksapce/zeppelin/conf:/home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-interpreter/target/classes:/home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-zengine/target/classes:/home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-server/target/classes
```

Author: rajarajan-g <[email protected]>

Closes apache#1399 from rajarajan-g/ZEPPELIN-1182 and squashes the following commits:

f4f7f44 [rajarajan-g] updated as per review comments
da69b16 [rajarajan-g] Added log statements for configuration
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

Successfully merging this pull request may close these issues.

3 participants