-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: add transaction on mongo #10491
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can use the tag run-e2e-tests
on the PR to trigger the e2e to ensure that everything is good
d8227c0
to
fd19471
Compare
Before doing it, I needed to wait until the first build was successful. Edit: I knew I should have wait... |
fd19471
to
17c945d
Compare
17c945d
to
db2b91c
Compare
db2b91c
to
be2041c
Compare
2a6ec5e
to
18886a7
Compare
70f3e0d
to
18f8e64
Compare
APIM UI Tests Run #3628
Run Properties:
|
Project |
APIM UI Tests
|
Branch Review |
add-init-mongodb-script
|
Run status |
Passed #3628
|
Run duration | 07m 08s |
Commit |
585cf1cdd4: feat: enable mongodb transaction manager
|
Committer | Guillaume Lamirand |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
0
|
Pending |
8
|
Skipped |
0
|
Passing |
82
|
View all changes introduced in this branch ↗︎ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to also add the retry annotation to https://github.com/gravitee-io/gravitee-api-management/blob/master/gravitee-apim-rest-api/gravitee-apim-rest-api-service/src/main/java/io/gravitee/apim/core/UseCase.java#L52
and for the future I'm wondering it we need to add a CI pipeline to test the E2E in non transactional mode: have 2 run for MongoDB like we have multiple run for JDBC cc @phiz71
I am wondering, if it is a good idea to have to different kind of annotation for Transaction, especialy because usecase uses service which are transactionnal and already in retry mode... Don't know about the two kind of tests because the non transactional shouldn't be advice to anyone |
943ab86
to
bd6300d
Compare
...dalone/gravitee-apim-rest-api-standalone-distribution/src/main/resources/config/gravitee.yml
Show resolved
Hide resolved
bd6300d
to
585cf1c
Compare
585cf1c
to
4eb22c6
Compare
- add option repository.mongodb.transactional to disable transaction (enable by default) - add repliSet option on all docker-compose - add retryable framework to retry TransientDataAccessException and some NonTransientDataAccessException including WriteConflict error coming from mongodb transaction
4eb22c6
to
d139585
Compare
Description
A init script to init replicatset.
Additional context
📚 View the storybook of this branch here