apache / apache/incubator-seata-samples
Seata to ensure consistency between Dubbo Microservices
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 2k
- PR merge metrics
- No merged PRs in 30d
Description
Hi team
I am working on seata sample file for testing and deploying microservices and ensure consistency between Seata and Dubbo Microservices by following this [reference](https://github.com/seata/seata-samples/tree/master/dubbo) .
I have tried to startup seata-server by `$ docker run --name seata-server -p 8091:8091 seataio/seata-server:1.4.2`
**Log startup seata-server:** [seata-server_startup.txt](https://github.com/seata/seata-samples/files/9100200/seata-server_startup.txt)
And also I tried it by downloded [seata](https://github.com/seata/seata/releases/download/v1.5.2/seata-server-1.5.2.tar.gz) [release](https://github.com/seata/seata/releases) version ,then ran
`||sh ./bin/seata-server.sh||`
**Output:**
```
apm-skywalking not enabled
./bin/seata-server.sh: 138: [[: not found
seata-server is starting, you can check the /home/ubuntu/ARM_FAAS_Project/abhay/seata-samples/seata/logs/start.out
```
After that, I tried to execute these services
“DubboStockServiceStarter”,”DubboAccountServiceStarter”,”DubboOrderServiceStarter”,”DubboBusinessTester”
Under the **seata-samples\dubbo\src\main\resources\sql** but couldn’t able to start above service .
Please share some pointer on it how to deploy these microservices in seata.
Thanks in advance.
Contributor guide
Research direction
Start with the dubbo sample referenced in the issue, especially the services named DubboStockServiceStarter, DubboAccountServiceStarter, DubboOrderServiceStarter, and DubboBusinessTester. Review the resources/sql directory and the attached seata-server_startup.txt, then reproduce the Docker and seata-server.sh startup attempts. Done means the services start and the sample can exercise consistency between Seata and Dubbo microservices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- backend, devops, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100