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

About pre-apply in JournalSystem #18558

Open
QueenOfBees opened this issue Mar 22, 2024 · 2 comments
Open

About pre-apply in JournalSystem #18558

QueenOfBees opened this issue Mar 22, 2024 · 2 comments
Labels
type-bug This issue is about a bug

Comments

@QueenOfBees
Copy link

Alluxio Version:
release-310

Describe the bug

Let's say we have a x = 3 in memory

write request:
try (JournalContext c = journal.createJournalContext()) {
x = 3
c.append(exampleBlockJournalEntry);
}

read request:
return x

if the leader node lost leadership while flushing pending jounal (network reason/long time gc),
the read request will see x = 3 immediately, that means we read a uncommited change, is this correct?

I'd appreciate it if you could give me a hint.

To Reproduce

Expected behavior

Urgency

Are you planning to fix it

Additional context

@QueenOfBees QueenOfBees added the type-bug This issue is about a bug label Mar 22, 2024
@QueenOfBees QueenOfBees changed the title About pre-apply in JounalSystem About pre-apply in JournalSystem Mar 22, 2024
@QueenOfBees
Copy link
Author

my another conflusion is: what's the benefit of pre-apply exactly.
"avoid journaling operations which do not result in state modification" (comment of RaftJounalSystem),which is difficult to understand

@YichuanSun
Copy link
Contributor

Actually now we have no leading node in Alluxio 3.x, Alluxio 3.x is a decentralized architecture.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug This issue is about a bug
Projects
None yet
Development

No branches or pull requests

2 participants