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

data is not consistent in index if rebuild failed #2507

Closed
HarrisChu opened this issue Aug 12, 2021 · 1 comment
Closed

data is not consistent in index if rebuild failed #2507

HarrisChu opened this issue Aug 12, 2021 · 1 comment
Labels
need to discuss Solution: issue or PR without a clear conclusion on whether to handle it type/enhancement Type: make the code neat or more efficient

Comments

@HarrisChu
Copy link
Contributor

HarrisChu commented Aug 12, 2021

  1. has three storage, 192.168.15.8, 192.168.15.9, 192.168.15.10
  2. create tag index and rebuild.
  3. 192.168.15.8 rebuild failed as index schema is not synchronous.
  4. query match.

expect:
cannot query match as the index job is failed.

actual:
can query some data, and then data in index is not consistent, because storage index built failed.

image

image

image

@HarrisChu
Copy link
Contributor Author

could we rerun the failed job automatically?

@CPWstatic CPWstatic added type/enhancement Type: make the code neat or more efficient type/feature req Type: feature request labels Aug 27, 2021
@Sophie-Xie Sophie-Xie removed the type/feature req Type: feature request label Aug 30, 2021
@HarrisChu HarrisChu added the need to discuss Solution: issue or PR without a clear conclusion on whether to handle it label Sep 27, 2021
yixinglu pushed a commit to yixinglu/nebula that referenced this issue Sep 14, 2023
* disable edgelist join

* add test case

* address comment

* address comment

* address comment

* fix ctest error

* add test case

---------

Co-authored-by: jimingquan <[email protected]>
Co-authored-by: Sophie <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need to discuss Solution: issue or PR without a clear conclusion on whether to handle it type/enhancement Type: make the code neat or more efficient
Projects
None yet
Development

No branches or pull requests

3 participants