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

Is it possible to run open-datastudio Zeppelin on your own K8S cluster? #2

Open
rogargon opened this issue Aug 8, 2020 · 1 comment

Comments

@rogargon
Copy link

rogargon commented Aug 8, 2020

From the documentation, I see that Zeppelin can be run on minikube. Is it also possible to run it on your own cluster?

@Leemoonsoo
Copy link
Member

Yes. Although each cluster environment is a little different and may require small changes sometimes, there's no reason why it can not run on any other Kubernetes cluster the same way it runs on minikube.

Leemoonsoo pushed a commit that referenced this issue Aug 13, 2020
…Interpreter database connection pool

### What is this PR for?
- Added support for personalized configuration of the JDBCInterpreter database connection pool.
- This feature can be used to solve the runtime error caused by HiveServer2 Session timeout.
- This connection pool configuration Compatible with [the official configuration of dbcp2 ](http://commons.apache.org/proper/commons-dbcp/configuration.html)

### What type of PR is it?
[Feature]

### Todos
* [ ] - Task

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

### How should this be tested?
* manually tested
* Supported configuration items
    - validationQuery
    - testOnBorrow
    - testOnCreate
    - testOnReturn
    - testWhileIdle
    - timeBetweenEvictionRunsMillis
    - maxWaitMillis
    - maxIdle
    - minIdle
    - maxTotal

### Screenshots (if appropriate)

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

Author: xiejiajun <xiejiajun02@163.com>
Author: JakeXie <xiejiajun02@163.com>
Author: xie-jia-jun <xiejiajun02@163.com>

Closes apache#3844 from xiejiajun/jdbc-pool-config and squashes the following commits:

3bb622b [xiejiajun] use html table display datasource pool configuration in the jdbc.md document
88b1ce0 [xiejiajun] jdbc interpreter datasource connection pool  document
1f2eb55 [xiejiajun] Compatible with the official configuration of dbcp2 connection pool
5c7f666 [xiejiajun] JDBCInterprete supports personalized database connection pool configuration to cope with scenarios such as HiveSession timeout
3d57719 [xiejiajun] Merge branch 'branch-0.9' of https://github.com/apache/zeppelin into apache-0.9
0e5f65a [xiejiajun] Merge branch 'branch-0.9' of https://github.com/apache/zeppelin into apache-0.9
076668a [JakeXie] Merge pull request #7 from apache/branch-0.9
00e14dd [JakeXie] Merge pull request #5 from apache/branch-0.9
9bb7341 [xiejiajun] Merge remote-tracking branch 'origin/branch-0.9' into branch-0.9
9bc5605 [xiejiajun] bug fix:  when we removing a paragraph , an interpreter process refused to connect due to it abnormal stop , which eventually caused the remove paragraph operation to fail to complete.
97d2714 [xie-jia-jun] Merge pull request #2 from apache/branch-0.9
9b3c744 [xiejiajun] added timeout for getting Thrift client to avoid situations where the interpreter may not be restarted when the interpreter process exits unexpectedly
Leemoonsoo pushed a commit that referenced this issue Aug 13, 2020
…Spark Interpreter Scala REPL

### What is this PR for?
- Support for manually specifying the Java version of Spark Interpreter Scala REPL.
- This feature can be used to resolve runtime errors caused by reference to third-party libraries that use high-version Java in Spark Interpreter.
 
### What type of PR is it?
[Feature]

### Todos
* [ ] - Task

### What is the Jira issue?
*  https://issues.apache.org/jira/projects/ZEPPELIN/issues/ZEPPELIN-4950

### How should this be tested?
* manually tested
    *  Specify spark.repl.target through %spark.conf or when configuring Spark Interpreter
    *  Reference and call a Java method in a third-party library developed using Java 8 and using Java 8 features such as interface static methods through the Spark interpreter. If the call is successful, it means the test passed

### Screenshots (if appropriate)
- A runtime error will be triggered when  we reference a third-party library that uses the new features of Java8  if we using the default value `jvm-1.6`  of `settings.target.value` :
![image](https://user-images.githubusercontent.com/26395958/87297066-6581c580-c53a-11ea-989a-ad11001501f4.png)

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

Author: xiejiajun <xiejiajun02@163.com>
Author: JakeXie <xiejiajun02@163.com>
Author: xie-jia-jun <xiejiajun02@163.com>

Closes apache#3852 from xiejiajun/spark_repl_target and squashes the following commits:

d131f19 [xiejiajun] spark.md docs fix
6872054 [xiejiajun] add spark.repl.target to spark.md docs
6a05b4f [xiejiajun] Support for manually specifying the Java version of Spark Interpreter Scala REPL  
6a2cf04 [xiejiajun] Merge branch 'branch-0.9' of https://github.com/apache/zeppelin into branch-0.9
076668a [JakeXie] Merge pull request #7 from apache/branch-0.9
00e14dd [JakeXie] Merge pull request #5 from apache/branch-0.9
9bb7341 [xiejiajun] Merge remote-tracking branch 'origin/branch-0.9' into branch-0.9
9bc5605 [xiejiajun] bug fix:  when we removing a paragraph , an interpreter process refused to connect due to it abnormal stop , which eventually caused the remove paragraph operation to fail to complete.
97d2714 [xie-jia-jun] Merge pull request #2 from apache/branch-0.9
9b3c744 [xiejiajun] added timeout for getting Thrift client to avoid situations where the interpreter may not be restarted when the interpreter process exits unexpectedly

(cherry picked from commit 054651f)
Signed-off-by: Jeff Zhang <zjffdu@apache.org>
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