blob: f778edee2abba494e64a8adda7f1dd568f72d50a (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
|
# How to run a standalone Hazelcast server for testing distributed cache.
- First you need to run a standalone Hazelcast server with default
configuration. If you already have a separate Hazelcast cluster you can skip
this step.
java -cp third_party/hazelcast/hazelcast-3.6.4.jar \
com.hazelcast.core.server.StartServer
- Then you run Bazel pointing to the Hazelcast server.
bazel build --hazelcast_node=localhost:5701 --spawn_strategy=remote \
src/tools/generate_workspace:all
Above command will build generate_workspace with remote spawn strategy that uses
Hazelcast as the distributed caching backend.
# How to run a remote worker for testing remote execution.
- First run the remote worker. This will start a standalone Hazelcast server
with default configuration.
bazel-bin/src/tools/remote_worker/remote_worker \
--work_path=/tmp/remote --listen_port 8080
- Then run Bazel pointing to the Hazelcast server and remote worker.
bazel build --hazelcast_node=localhost:5701 \
--remote_worker=localhost:8080 \
--spawn_strategy=remote src/tools/generate_workspace:all
|
