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

Memory useage keeps on high level and wouldn't be released by storage process #3422

Closed
Sophie-Xie opened this issue Dec 7, 2021 · 7 comments
Labels
need info Solution: need more information (ex. can't reproduce) priority/low-pri Priority: low type/bug Type: something is unexpected

Comments

@Sophie-Xie
Copy link
Contributor

Sophie-Xie commented Dec 7, 2021

Describe the bug (required)

After importing data, memory useage keeps on high level with bloom filter, which often results in OOM in some scenario -- huge and full data import everytime.

In out internal tests, prefix bloom filter couldn't reduce the memory usage obviously instead of whole key bloom filter with a 8 billion dataset.

Your Environments (required)

  • OS: uname -a
  • Compiler: g++ --version or clang++ --version
  • CPU: lscpu
  • Commit id (e.g. a3ffc7d8)

How To Reproduce(required)

Steps to reproduce the behavior:

  1. Step 1
  2. Step 2
  3. Step 3

Expected behavior

Additional context

@Sophie-Xie Sophie-Xie added the type/bug Type: something is unexpected label Dec 7, 2021
@Sophie-Xie Sophie-Xie added this to the v3.0.0 milestone Dec 7, 2021
@Sophie-Xie Sophie-Xie added need info Solution: need more information (ex. can't reproduce) priority/low-pri Priority: low labels Jan 4, 2022
@carrey-feng
Copy link
Contributor

Is there any new progress on this issue

@wey-gu
Copy link
Contributor

wey-gu commented Jan 15, 2022

Is there any new progress on this issue

It seems this issue was stuck lacking reproducing environment, are you facing similar issues? If so, could you please help provide some information on this?

@Sophie-Xie

@huzhi915
Copy link

Is there any new progress on this issue

It seems this issue was stuck lacking reproducing environment, are you facing similar issues? If so, could you please help provide some information on this?

@Sophie-Xie

this issure can be fixed by configuring the items "enable_rocksdb_prefix_filtering" and "enable_partitioned_index_filter" of nebula-storaged.conf file, close it plz.

@carrey-feng
Copy link
Contributor

this issure can be fixed by configuring the items "enable_rocksdb_prefix_filtering" and "enable_partitioned_index_filter" of nebula-storaged.conf file, close it plz.

Need rebuild index after modify enable_rocksdb_prefix_filtering ?

@wey-gu
Copy link
Contributor

wey-gu commented Jan 16, 2022

this issure can be fixed by configuring the items "enable_rocksdb_prefix_filtering" and "enable_partitioned_index_filter" of nebula-storaged.conf file, close it plz.

Need rebuild index after modify enable_rocksdb_prefix_filtering ?

Rebuild of the index is not needed, I think those two configurations are cache related.

@huzhi915 please correct me if wrong.

Thanks.

@huzhi915
Copy link

this issure can be fixed by configuring the items "enable_rocksdb_prefix_filtering" and "enable_partitioned_index_filter" of nebula-storaged.conf file, close it plz.

Need rebuild index after modify enable_rocksdb_prefix_filtering ?

Rebuild of the index is not needed, I think those two configurations are cache related.

@huzhi915 please correct me if wrong.

Thanks.

exactly.

@Sophie-Xie Sophie-Xie removed this from the v3.0.0 milestone Feb 9, 2022
@Sophie-Xie
Copy link
Contributor Author

Talked it offline, now it's work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need info Solution: need more information (ex. can't reproduce) priority/low-pri Priority: low type/bug Type: something is unexpected
Projects
None yet
Development

No branches or pull requests

6 participants