[pulsar] branch master updated: [docs] Add thread/process modes in Configure Functions runtime (#4828)

[hj...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git


The following commit(s) were added to refs/heads/master by this push:
     new 8c163eb  [docs] Add thread/process modes in Configure Functions runtime (#4828)
8c163eb is described below

commit 8c163eb2321fb2fba62d7c85dd5d03bc75c1af7a
Author: Jennifer Huang <47...@users.noreply.github.com>
AuthorDate: Thu Aug 1 13:40:50 2019 +0800

    [docs] Add thread/process modes in Configure Functions runtime (#4828)
    
    * add thread/process modes
    
    * update the differences between thread and process modes
    
    * update
    
    * update
---
 site2/docs/functions-overview.md | 2 +-
 site2/docs/functions-runtime.md  | 4 ++++
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/site2/docs/functions-overview.md b/site2/docs/functions-overview.md
index 0f3769e..bc051a4 100644
--- a/site2/docs/functions-overview.md
+++ b/site2/docs/functions-overview.md
@@ -509,4 +509,4 @@ $ bin/pulsar-admin functions create \
 Pulsar Functions that use [Pulsar Functions SDK](#the-pulsar-functions-sdk) can publish metrics to Pulsar. For more information, see [Metrics for Pulsar Functions](functions-metrics.md).
 
 ## State storage
-Pulsar Functions use [Apache BookKeeper](https://bookkeeper.apache.org) as a state storage interface. Pulsar installation, including the local standalone installation, includes deployment of BookKeeper bookies.
\ No newline at end of file
+Pulsar Functions use [Apache BookKeeper](https://bookkeeper.apache.org) as a state storage interface. Pulsar installation, including the local standalone installation, includes deployment of BookKeeper bookies.
diff --git a/site2/docs/functions-runtime.md b/site2/docs/functions-runtime.md
index a603c60..f60555a 100644
--- a/site2/docs/functions-runtime.md
+++ b/site2/docs/functions-runtime.md
@@ -11,6 +11,10 @@ Pulsar Functions support the following methods to run functions.
 - *Process*: Invoke functions in processes forked by Functions Worker.
 - *Kubernetes*: Submit functions as Kubernetes StatefulSets by Functions Worker.
 
+The differences of the thread and process modes are:   
+- Thread mode: when a function runs in thread mode, it runs on the same Java virtual machine (JVM) with Functions worker.   
+- Process mode: when a function runs in process mode, it runs on the same machine that Functions worker runs.
+
 ## Configure thread runtime
 It is easy to configure *Thread* runtime. In most cases, you do not need to configure anything. You can customize the thread group name with the following settings: