mirror of
https://github.com/apache/zeppelin
synced 2026-05-24 09:38:26 +00:00
address comments
This commit is contained in:
parent
575b7b9649
commit
a4c9b9cde1
3 changed files with 5 additions and 5 deletions
|
|
@ -16,7 +16,7 @@
|
|||
# See the License for the specific language governing permissions and
|
||||
# limitations under the License.
|
||||
#
|
||||
# Run Zeppelin
|
||||
# Stop Zeppelin Interpreter Processes
|
||||
#
|
||||
|
||||
bin=$(dirname "${BASH_SOURCE-$0}")
|
||||
|
|
|
|||
|
|
@ -147,8 +147,8 @@ In this scenario, user need to put `ConfInterpreter` as the first paragraph as t
|
|||
|
||||
## Interpreter Process Recovery
|
||||
|
||||
Before 0.8.0, shutting down Zeppelin also mean to shutdown all the running interpreter processes. Usually admin will shutdown zeppelin server for maintenance or upgrade, but don't want to shut down the running interpreter process.
|
||||
Before 0.8.0, shutting down Zeppelin also mean to shutdown all the running interpreter processes. Usually admin will shutdown Zeppelin server for maintenance or upgrade, but don't want to shut down the running interpreter processes.
|
||||
In such cases, interpreter process recovery is necessary. Starting from 0.8.0, user can enable interpreter process recovering via setting `zeppelin.recovery.storage.class` as
|
||||
`org.apache.zeppelin.interpreter.recovery.FileSystemRecoveryStorage` or other implementations if available in future, by default it is `org.apache.zeppelin.interpreter.recovery.NullRecoveryStorage`
|
||||
which means recovery is not enabled. Enable recover means shutting down zeppelin would not terminating interpreter process,
|
||||
and when zeppelin is restarted, it would try to reconnect to the existing running interpreter process. If you want to kill all the interpreter process after terminating zeppelin even when recovery is enabled, you can run `bin/stop-interpreter.sh`
|
||||
which means recovery is not enabled. Enable recover means shutting down Zeppelin would not terminating interpreter process,
|
||||
and when Zeppelin is restarted, it would try to reconnect to the existing running interpreter processes. If you want to kill all the interpreter processes after terminating Zeppelin even when recovery is enabled, you can run `bin/stop-interpreter.sh`
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@ public class RemoteInterpreterRunningProcess extends RemoteInterpreterProcess {
|
|||
}
|
||||
});
|
||||
} catch (Exception e) {
|
||||
logger.warn("ignore the exception when shutting down");
|
||||
logger.warn("ignore the exception when shutting down interpreter process.", e);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in a new issue