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

[BUG] Building on Raspberry 4 fails #336

Closed
Talkabout opened this issue Aug 9, 2021 · 4 comments · Fixed by #343
Closed

[BUG] Building on Raspberry 4 fails #336

Talkabout opened this issue Aug 9, 2021 · 4 comments · Fixed by #343

Comments

@Talkabout
Copy link

Talkabout commented Aug 9, 2021

Describe the bug

Build on Raspberry Pi 4 fails with following error:

    CC adlist.o
    CC quicklist.o
    CC ae.o
    CC anet.o
    CC dict.o
    CC server.o
In file included from server.cpp:31:
server.h:857:35: error: static assertion failed: object size is critical, don't increase
 static_assert(sizeof(redisObject) == 16, "object size is critical, don't increase");
               ~~~~~~~~~~~~~~~~~~~~^~~~~
make[1]: *** [Makefile:392: server.o] Fehler 1
make[1]: Verzeichnis „/home/xxx/keydb/src“ wird verlassen
make: *** [Makefile:6: all] Fehler 2

To reproduce

Try to build on a Raspberry Pi 4 :)

Expected behavior

Build should run without error

Additional information

@Talkabout Talkabout changed the title [BUG] [BUG] Building on Raspberry 4 fails Aug 9, 2021
@Talkabout
Copy link
Author

Hi,

seems to be related to this:

#240

putting "<=" instead of "==" makes building possible again.

Bye

@Talkabout
Copy link
Author

Hi,

after building and starting I was facing major memory/cpu issues. I have 2 nodes with active-replica configured and a database of 250+ MBs. Both nodes were consuming 100% cpu (2 processes), no other applications were able to set keys because of error (redis is loading data file into memory). At some point the kernel killed keydb because of memory overflow. Not sure what exactly has been done but for my environment it is not working at all. Rollback to 6.0.16 and everyhing is working smoothly again. If any further information is required to track this down, please ask.

Bye

@BobEQAlpha
Copy link

BobEQAlpha commented Aug 12, 2021

Hello Talkabout!

Thank you for contacting EQAlpha. We appreciate you reaching out to us. To help us address your specific issue better.

Do you have the memory overflow during or after the redis is loading data file into memory?

If it's during, I recommend you still enable active-replica, try to have the first node only replicate from the second. Then when full synchronization is complete, then have the second node replicate from the first. This way, we can see if the issue is for one of the nodes or both of the nodes only.

If it's after, what is the maximum number of concurrent clients you have for the 2 nodes?

@christianEQ
Copy link
Contributor

Hey, to keep things organized here I'm going to have this issue close when #343 merges as it fixes the inciting build failure. If you're still seeing the other problems after the fix, feel free to open a new issue about them, and please address Bob's above questions in that post. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants