Skip to content
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

Fixed thrift generator #670

Merged
merged 2 commits into from
Jul 22, 2019
Merged

Fixed thrift generator #670

merged 2 commits into from
Jul 22, 2019

Conversation

dutor
Copy link
Contributor

@dutor dutor commented Jul 22, 2019

Since there are target files that will never be generated, the generator always gets invoked.

@dutor dutor added the ready-for-testing PR: ready for the CI test label Jul 22, 2019
Copy link
Contributor

@laura-ding laura-ding left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well done

Copy link
Contributor

@monadbobo monadbobo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@nebula-community-bot
Copy link
Member

Unit testing passed.

@nebula-community-bot
Copy link
Member

Unit testing passed.

@dutor dutor merged commit 73c4df0 into vesoft-inc:master Jul 22, 2019
@dutor dutor deleted the fix-thrift-generator branch July 22, 2019 07:42
tong-hao pushed a commit to tong-hao/nebula that referenced this pull request Jun 1, 2021
yixinglu pushed a commit to yixinglu/nebula that referenced this pull request Mar 21, 2022
## What type of PR is this?
- [ ] bug
- [ ] feature
- [X] enhancement

## What problem(s) does this PR solve?
#### Issue(s) number: 

#### Description:

This is some prepare work for later data balance test, mainly two changes:
1. Follow up of vesoft-inc#3717(In that pr we use snapshot when doing data scan, but the commit log id/term is not taken care). So in this PR, we create a rocksdb snapshot at first, read commit log id/term, and use the same snapshot to scan data.
2. We can't simply skip the special raft command, because if we skip the special log after rebooting, the state of raft peer will be wrong.
3. Add some metrics in raft, remove the `SlowOpTracker`.

## How do you solve it?

## Special notes for your reviewer, ex. impact of this fix, design document, etc:

## Checklist:
Tests:
- [X] Unit test(positive and negative cases)
- [ ] Function test
- [ ] Performance test
- [ ] N/A

Affects:
- [ ] Documentation affected (Please add the label if documentation needs to be modified.)
- [ ] Incompatibility (If it breaks the compatibility, please describe it and add the label.)
- [ ] If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
- [ ] Performance impacted: Consumes more CPU/Memory


## Release notes:
not related



Migrated from vesoft-inc#3846

Co-authored-by: Doodle <13706157+critical27@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-testing PR: ready for the CI test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants