Skip to content
This repository has been archived by the owner on Feb 8, 2019. It is now read-only.

fix GEARPUMP-143 add doc worker.executor-share-same-jvm-as-worker #29

Closed
wants to merge 2 commits into from

Conversation

PipsqueakH
Copy link
Contributor

add deployment config doc

@@ -89,3 +89,4 @@ This is the default configuration for `gear.conf`.
| gearpump.shared-thread-pool-dispatcher | default Dispatcher with "fork-join-executor" | default shared thread pool dispatcher |
| gearpump.single-thread-dispatcher | PinnedDispatcher | default single thread dispatcher |
| gearpump.serialization-framework | "org.apache.gearpump.serializer.FastKryoSerializationFramework" | Gearpump has built-in serialization framework using Kryo. Users are allowed to use a different serialization framework, like Protobuf. See `org.apache.gearpump.serializer.FastKryoSerializationFramework` to find how a custom serialization framework can be defined |
| worker.executor-share-same-jvm-as-worker | false | whether the executor actor is started in a seperate jvm(process) from which running the worker actor |
Copy link
Contributor

Choose a reason for hiding this comment

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

small typo "seperate". IMHO, "whether ... is started in the same JVM(process)" is more intuitive since the configuration is "share-same-jvm".

@manuzhang
Copy link
Contributor

thanks for contribution. Some minor points.

@whjiang
Copy link
Contributor

whjiang commented May 31, 2016

+1

@asfgit asfgit closed this in 9e25198 May 31, 2016
@manuzhang
Copy link
Contributor

@PipsqueakH merged to master. Do you have a jira id such that I can assign it to you ?

manuzhang pushed a commit to manuzhang/incubator-gearpump that referenced this pull request Jan 24, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants