Option 1: (Locally)
- Find the JAR file located in the metadata_server directory and use it directly.
- Start the server by using the command: java -jar MetadataServer.jar --server.port=8080.
Option 2: (On AWS)
- Launch a AWS EC2 instance.
- Copy the JAR file to the EC2 instance.
- Install the JDK and Tmux on the EC2 instance. Use openjdk-17-jdk and openjdk-17-jre.
- Start Tmux.
- Start the metadata server using the command: sudo java -jar MetadataServer.jar.
- Press Control + B, then release and press D. This will ensure that the process is not killed when the SSH connection is closed.
Option 1: (Locally)
- Build the Project which exports a JAR file under PROJECT_ROOT/out/artifacts
- Run by using command: 'java -jar DistributedSystemsProject.jar --server.port=8083'. This will start a Leader server.
- Run multiple workers as desired by using command: java -jar DistributedSystemsProject.jar --server.port=8084/8085/8086...
Option 2: (On AWS)
- Launch AWS EC2 instances (1 for leader & minimum 3 for workers)
- Build the project and export the JAR file
- Copy JAR file to EC2 instances
- Install JDK and Tmux on the EC2 instances
- Start tmux
- Start leader server using 'sudo java -jar DistributedSystemsProject.jar'
- Start worker server using 'sudo java -jar DistributedSystemsProject.jar --nodeId 'http://<ip_of_machine' '
- Press Control + B, then release and press D
- This will ensure that the process is not killed when we kill the SSH connection.
The original package name 'com.scu.ds.dfs.dfs-coordinator' is invalid and the client server uses 'com.scu.ds.dfs.dfscoordinator' instead.