Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

expirationd doesn't process tasks with zero length box.cfg.replication #95

Closed
artemreyt opened this issue Nov 8, 2021 · 1 comment
Closed
Assignees
Labels
bug Something isn't working

Comments

@artemreyt
Copy link

artemreyt commented Nov 8, 2021

Documentation says "by default expirationd should process tasks only on the writeable instance, it means that expirationd will not start task processing on a replica. Here the word 'replica' means an instance with at least one configured upstream".

But if to create an instance like:

box.cfg{
    replication = {};
    read_only = false,
}

Expirationd doesn't process tasks. But it has no configured upstream in real.

If it's really a bug, it seems to be because of this line (box.cfg.replication actually not nil):

if (box.cfg.replication_source == nil and box.cfg.replication == nil) or task.force then

Of course option force of expirationd.start() can help at this case, but In my opinion the word force you should use only where it is really needed :)

@artemreyt artemreyt changed the title expirationd doesn't process tasks with zero length box.cfg.repliction expirationd doesn't process tasks with zero length box.cfg.replication Nov 8, 2021
@ArtDu
Copy link
Contributor

ArtDu commented Nov 9, 2021

also related to #92

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants