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

feat(fuzz): enhance condition check of region migration finish #4283

Merged
merged 1 commit into from
Jul 4, 2024

Conversation

WenyXu
Copy link
Member

@WenyXu WenyXu commented Jul 4, 2024

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

What's changed and what's your intention?

check the migration result instead of check procedure state

Checklist

  • I have written the necessary rustdoc comments.
  • I have added the necessary unit tests and integration tests.
  • This PR requires documentation updates.

Summary by CodeRabbit

  • New Features

    • Introduced new asynchronous fetch functionality for partition data.
    • Added new procedures for handling migration states and conditions.
  • Improvements

    • Enhanced migration logic and control flow for better performance.
    • Updated methods to accept more efficient data types.

Copy link
Contributor

coderabbitai bot commented Jul 4, 2024

Walkthrough

The updates in this change set involve additions and modifications to the migration logic, including functions for handling partitions and procedures asynchronously. New functions fetch_partition and procedure_state, adjustments to existing functions to accept references, and the introduction of the Migration struct enhance the code's robustness and manageability. These refinements aim to streamline the process and ensure seamless execution during migrations.

Changes

File Summary
tests-fuzz/src/utils/partition.rs Added new fetch_partition function; modified fetch_partitions and region_distribution functions.
tests-fuzz/src/utils/procedure.rs Changed procedure_state to accept reference to string slice; altered wait_for_procedure_finish.
tests-fuzz/targets/migration/… Significant migration logic changes: restructuring, updating dependencies, and new functions for procedures.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant MigrationLogic as Migration Logic
    participant DB as Database
    participant Utils as Utils

    Client->>MigrationLogic: InitiateMigration()
    MigrationLogic->>DB: query(region_id)
    DB-->>MigrationLogic: return region details
    MigrationLogic->>Utils: fetch_partition(region_id)
    Utils->>DB: SQL query to fetch partition
    DB-->>Utils: return Partition
    Utils-->>MigrationLogic: Partition result
    MigrationLogic->>DB: execute migration steps
    MigrationLogic->>Utils: wait_for_procedure_finish(procedure_id)
    Utils->>DB: query procedure_state(procedure_id)
    DB-->>Utils: return procedure state
    Utils-->>MigrationLogic: procedure state
    MigrationLogic-->>Client: Migration completed
Loading

Poem

By the bytes and lines so bright,
We fetch partitions through the night.
Procedures state with strings in hand,
Migration flows across the land.
Code refactored, strong and lean,
In each commit, a clearer scene.
✨🔧🥕


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added the docs-not-required This change does not impact docs. label Jul 4, 2024
@WenyXu WenyXu marked this pull request as ready for review July 4, 2024 11:39
@WenyXu WenyXu requested a review from a team as a code owner July 4, 2024 11:39
@WenyXu WenyXu force-pushed the fix/enhance-condition-check branch from f7c75b1 to cda9f86 Compare July 4, 2024 11:40
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Outside diff range and nitpick comments (2)
tests-fuzz/src/utils/procedure.rs (2)

Line range hint 25-32:
Improve error handling.

Avoid using unwrap for error handling as it can cause the program to panic. Consider using ? to propagate errors or handling them appropriately.

-    let result = sqlx::query(&sql)
-        .fetch_one(e)
-        .await
-        .context(error::ExecuteQuerySnafu { sql })
-        .unwrap();
-    result.try_get(0).unwrap()
+    let result = sqlx::query(&sql)
+        .fetch_one(e)
+        .await
+        .context(error::ExecuteQuerySnafu { sql })?;
+    result.try_get(0).context(error::ExecuteQuerySnafu { sql })

Line range hint 35-53:
Improve error handling and avoid unnecessary cloning.

Avoid using unwrap for error handling as it can cause the program to panic. Consider using ? to propagate errors or handling them appropriately. Additionally, avoid unnecessary cloning of procedure_id.

-    wait_condition_fn(
-        timeout,
-        || {
-            let greptime = greptime.clone();
-            let procedure_id = procedure_id.clone();
-            Box::pin(async move { procedure_state(&greptime, &procedure_id).await })
-        },
-        |output| {
-            info!("Procedure({procedure_id}) state: {:?}", output);
-            output.to_lowercase().contains("done")
-        },
-        Duration::from_secs(5),
-    )
-    .await
+    wait_condition_fn(
+        timeout,
+        || {
+            let greptime = greptime.clone();
+            Box::pin(async move { procedure_state(&greptime, procedure_id).await })
+        },
+        |output| {
+            info!("Procedure({procedure_id}) state: {:?}", output);
+            output.to_lowercase().contains("done")
+        },
+        Duration::from_secs(5),
+    )
+    .await
    .context(error::ExecuteQuerySnafu { sql })
Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4ec247f and cda9f86.

Files selected for processing (3)
  • tests-fuzz/src/utils/partition.rs (1 hunks)
  • tests-fuzz/src/utils/procedure.rs (2 hunks)
  • tests-fuzz/targets/migration/fuzz_migrate_mito_regions.rs (3 hunks)
Additional comments not posted (1)
tests-fuzz/src/utils/partition.rs (1)

58-75: Improve error handling.

Avoid using unwrap for error handling as it can cause the program to panic. Consider using ? to propagate errors or handling them appropriately.

-    sqlx::query_as::<_, Partition>(sql)
-        .bind(region_id)
-        .fetch_one(e)
-        .await
-        .context(error::ExecuteQuerySnafu { sql })
-        .unwrap()
+    sqlx::query_as::<_, Partition>(sql)
+        .bind(region_id)
+        .fetch_one(e)
+        .await
+        .context(error::ExecuteQuerySnafu { sql })

Likely invalid or redundant comment.

Copy link

codecov bot commented Jul 4, 2024

Codecov Report

Attention: Patch coverage is 0% with 19 lines in your changes missing coverage. Please review.

Project coverage is 84.69%. Comparing base (22f4d43) to head (cda9f86).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4283      +/-   ##
==========================================
- Coverage   84.96%   84.69%   -0.27%     
==========================================
  Files        1058     1058              
  Lines      188059   188126      +67     
==========================================
- Hits       159789   159338     -451     
- Misses      28270    28788     +518     

@WenyXu WenyXu enabled auto-merge July 4, 2024 12:13
@WenyXu WenyXu added this pull request to the merge queue Jul 4, 2024
Merged via the queue into GreptimeTeam:main with commit 70f7baf Jul 4, 2024
55 checks passed
@WenyXu WenyXu deleted the fix/enhance-condition-check branch July 4, 2024 12:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-not-required This change does not impact docs.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants