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

issue with logging sometimes not writing to the file #476

Open
z11373 opened this issue Feb 12, 2020 · 0 comments
Open

issue with logging sometimes not writing to the file #476

z11373 opened this issue Feb 12, 2020 · 0 comments

Comments

@z11373
Copy link

z11373 commented Feb 12, 2020

Hi, we are running streamparse v3.13.1 on production, and we have our spout code simply calls self.logger.info(), which I guess it inherits from pystorm component (maybe https://github.com/pystorm/pystorm/blob/master/pystorm/component.py#L247 ?)

I just learned that in the past few days no log lines being produced by that spout, but surprisingly today I see it writes the log again to the file. Checking the python process on the machine, I see the spout has been running since Jan 28th. This is very unfortunate, given when we really need the logs (from that spout), they are not available, and I don't know why :-( One thing for sure, the spout is still processing events, it's just what it's doing not being recorded to the log. I see other spouts/bolts in the topology seem fine.

Any idea what could be the cause of this mysterious missing logs? And how can I debug this? Of course, if I simply kill the spout process, then Storm will automatically restart it, and the logging will be fine again. I really appreciate any help here. 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

No branches or pull requests

1 participant