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

2.3.0-rc1: ERROR [AbstractRotationStrategy] Cannot perform rotation at this moment. #3997

Closed
frinnst opened this issue Jul 14, 2017 · 2 comments
Closed
Assignees
Labels
bug
Milestone

Comments

@frinnst
Copy link

@frinnst frinnst commented Jul 14, 2017

When using "Index Size" rotation strategy (5GB in my case) my graylog-server.log fills up with these messages:

2017-07-14T08:58:10.087Z ERROR [AbstractRotationStrategy] Cannot perform rotation at this moment.
2017-07-14T08:58:20.100Z ERROR [AbstractRotationStrategy] Cannot perform rotation at this moment.
2017-07-14T08:58:30.092Z ERROR [AbstractRotationStrategy] Cannot perform rotation at this moment.
2017-07-14T09:10:50.080Z ERROR [AbstractRotationStrategy] Cannot perform rotation at this moment.
2017-07-14T09:11:00.188Z ERROR [AbstractRotationStrategy] Cannot perform rotation at this moment.
2017-07-14T09:11:10.087Z ERROR [AbstractRotationStrategy] Cannot perform rotation at this moment.
2017-07-14T09:11:20.100Z ERROR [AbstractRotationStrategy] Cannot perform rotation at this moment.
2017-07-14T09:11:30.085Z ERROR [AbstractRotationStrategy] Cannot perform rotation at this moment.

If I switch to "Index Time" for example the log becomes quiet again.

Steps to Reproduce

  1. Switch Index rotation to "Index Size"
  2. tail -f /var/log/graylog-server/server.log
  • Graylog Version: 2.3.0-rc1
  • Elasticsearch Version: 5.5.0
  • MongoDB Version: 2.6.12
  • Operating System: ubuntu 16.04
  • Browser version: Various
@bernd bernd self-assigned this Jul 17, 2017
@bernd bernd added the bug label Jul 17, 2017
@bernd bernd added this to the 2.3.0 milestone Jul 17, 2017
@bernd
Copy link
Member

@bernd bernd commented Jul 17, 2017

Thank you for the report. I am able to reproduce that and currently work on a fix.

bernd added a commit that referenced this issue Jul 17, 2017
The size might be an integer instead of a long.

Fixes #3997
@ghost ghost added the in progress label Jul 17, 2017
@joschi joschi closed this in #4008 Jul 17, 2017
joschi added a commit that referenced this issue Jul 17, 2017
The size might be an integer instead of a long

Fixes #3997
@ghost ghost removed the in progress label Jul 17, 2017
bernd added a commit that referenced this issue Jul 17, 2017
The size might be an integer instead of a long

Fixes #3997
(cherry picked from commit b29b103)
@bernd
Copy link
Member

@bernd bernd commented Jul 17, 2017

@frinnst This will be fixed in the next 2.3 release candidate.

joschi added a commit that referenced this issue Jul 17, 2017
The size might be an integer instead of a long

Refs #4008
Fixes #3997
(cherry picked from commit b29b103)
mariussturm added a commit that referenced this issue Jul 18, 2017
The size might be an integer instead of a long

Fixes #3997
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.