acelyc111 commented on code in PR #51:
URL:
https://github.com/apache/incubator-pegasus-website/pull/51#discussion_r1437999304
##########
_overview/en/onebox.md:
##########
@@ -2,4 +2,61 @@
permalink: /overview/onebox/
---
-TRANSLATING
+# Understanding the Onebox Cluster
+Actions speak louder than words.
+
+When you first delve into Pegasus, you're probably most eager to understand
how its cluster functions in action. But as it's a distributed system, you may
not have an abundance of machines at your disposal. Hence, we provide the
onebox cluster, enabling you to experience the cluster-style service of Pegasus
on a single machine.
+
+Here's what the onebox cluster does when it starts up:
+
+- Initiates Zookeeper: Automatically downloads the Zookeeper installation
package from a remote source, installs it in the local hidden
folder```.zk_install```, and then launches the local Zookeeper service on port
22181.
+- Launches 3 MetaServers and 3 ReplicaServers: The ports for the MetaServers
are 34601, 34602, and 34603; for the ReplicaServers, they are 34801, 34802, and
34803.
+- After the cluster starts, it automatically creates a temporary table.
+
+With the onebox cluster, you can explore how Pegasus operates. You can use the
shell tool for reading and writing data, run tests with the bench tool (though
don't expect stellar performance from onebox), delve into implementation
details through logs, or conduct various experiments on the cluster.
+
+# How to Experience It
+Before launching the onebox cluster, you need to compile Pegasus. Please refer
to [Compile and Build](/docs/build/compile-from-source/).
+
+To start the onebox cluster:
+```bash
+./run.sh start_onebox
+```
+
+To view the onebox cluster:
+```bash
+./run.sh list_onebox
+```
+
+If you see 3 MetaServer and 3 ReplicaServer processes, congratulations, you've
successfully launched it. Otherwise, check the logs and core files in
the```./onebox```folder and report any errors to us via a pull request. For
example, if the replica1 process is missing, find the core file
in```onebox/replica1```(assuming ulimit allows core file generation) and the
log files in```onebox/replica1/data/log```.
Review Comment:
```suggestion
If you see 3 MetaServer and 3 ReplicaServer processes, congratulations,
you've successfully launched it. Otherwise, check the logs and core files in
the `./onebox`
folder and report any errors to us via a pull request. For example, if the
replica1 process is missing, find the core file in `onebox/replica1` (assuming
ulimit allows core file generation), the log files in
`onebox/replica1/data/log` and the standard error output in
`onebox/replica1/result`.
```
##########
_overview/en/onebox.md:
##########
@@ -2,4 +2,61 @@
permalink: /overview/onebox/
---
-TRANSLATING
+# Understanding the Onebox Cluster
+Actions speak louder than words.
+
+When you first delve into Pegasus, you're probably most eager to understand
how its cluster functions in action. But as it's a distributed system, you may
not have an abundance of machines at your disposal. Hence, we provide the
onebox cluster, enabling you to experience the cluster-style service of Pegasus
on a single machine.
+
+Here's what the onebox cluster does when it starts up:
+
+- Initiates Zookeeper: Automatically downloads the Zookeeper installation
package from a remote source, installs it in the local hidden
folder```.zk_install```, and then launches the local Zookeeper service on port
22181.
+- Launches 3 MetaServers and 3 ReplicaServers: The ports for the MetaServers
are 34601, 34602, and 34603; for the ReplicaServers, they are 34801, 34802, and
34803.
+- After the cluster starts, it automatically creates a temporary table.
+
+With the onebox cluster, you can explore how Pegasus operates. You can use the
shell tool for reading and writing data, run tests with the bench tool (though
don't expect stellar performance from onebox), delve into implementation
details through logs, or conduct various experiments on the cluster.
+
+# How to Experience It
+Before launching the onebox cluster, you need to compile Pegasus. Please refer
to [Compile and Build](/docs/build/compile-from-source/).
+
+To start the onebox cluster:
+```bash
+./run.sh start_onebox
+```
+
+To view the onebox cluster:
+```bash
+./run.sh list_onebox
+```
+
+If you see 3 MetaServer and 3 ReplicaServer processes, congratulations, you've
successfully launched it. Otherwise, check the logs and core files in
the```./onebox```folder and report any errors to us via a pull request. For
example, if the replica1 process is missing, find the core file
in```onebox/replica1```(assuming ulimit allows core file generation) and the
log files in```onebox/replica1/data/log```.
+
+To stop the onebox cluster:
+```bash
+./run.sh stop_onebox
+```
+
+After stopping, you can restart the cluster using the start_onebox command.
+
+To clean the onebox cluster (including data):
Review Comment:
```suggestion
To clean the onebox cluster (**All the data will be clean up as well!**):
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
