You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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!
The text was updated successfully, but these errors were encountered: