starred/log.io-NarrativeScience-old

Fork 0

mirror of https://github.com/NarrativeScience-old/log.io.git synced 2026-04-26 09:35:53 +03:00

[GH-ISSUE #70] stream/node flickering in ui after harvester restart #55

New issue

Closed

opened 2026-02-26 05:31:11 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 05:31:11 +03:00

Owner

Originally created by @archieco on GitHub (May 18, 2013).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/70

Hi there,

Log.io is a fantastic tool - I wish I could send you the look on some engineers' faces after they saw it configured on our system - amazement, relief, joy :). But, I need some help with a problem we've run into.

We have a logio setup of about a dozen servers running 3.3 on ubuntu. It appears that if the following sequence of events occurs, nodes/streams begin to flicker in the ui and make it unusable. This is the most minimal way I was able to reproduce the issue.

start log.io-server
start log.io-harvester

At this point everything is good

stop log.io-harvester

Now the streams/nodes for the harvester disappear as expected

start log.io-harvester

Now the streams/nodes for the restarted harvester only appear in the UI when log events go to the log server.

Stopping and starting log.io-server resolves the issue in the UI but it would be great if the server was resilient to harvesters stopping and starting.

Originally created by @archieco on GitHub (May 18, 2013). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/70 Hi there, Log.io is a fantastic tool - I wish I could send you the look on some engineers' faces after they saw it configured on our system - amazement, relief, joy :). But, I need some help with a problem we've run into. We have a logio setup of about a dozen servers running 3.3 on ubuntu. It appears that if the following sequence of events occurs, nodes/streams begin to flicker in the ui and make it unusable. This is the most minimal way I was able to reproduce the issue. start log.io-server start log.io-harvester At this point everything is good stop log.io-harvester Now the streams/nodes for the harvester disappear as expected start log.io-harvester Now the streams/nodes for the restarted harvester only appear in the UI when log events go to the log server. Stopping and starting log.io-server resolves the issue in the UI but it would be great if the server was resilient to harvesters stopping and starting.

kerem closed this issue

2026-02-26 05:31:11 +03:00

kerem commented

2026-02-26 05:31:12 +03:00

Author

Owner

@archieco commented on GitHub (May 18, 2013):

After a little more debugging...

If I make a change to log.io.js...

  _on('add_node', this._addNode);
  _on('add_stream', this._addStream);
  //_on('remove_node', this._removeNode);
  //_on('remove_stream', this._removeStream);
  _on('add_pair', this._addPair);
  _on('new_log', this._newLog);
  _on('ping', this._ping);
  _on('disconnect', this._disconnect);

... causing the browser to ignore those events...

stopping the harvester process has no impact on the ui unless the browser is refreshed. When the browser is refreshed the node and its streams will be missing. After starting the harvester again, the browser sees the new node and all its streams and there is no flickering. Hope that narrows it down.

@archieco commented on GitHub (May 18, 2013): After a little more debugging... If I make a change to log.io.js... ``` _on('add_node', this._addNode); _on('add_stream', this._addStream); //_on('remove_node', this._removeNode); //_on('remove_stream', this._removeStream); _on('add_pair', this._addPair); _on('new_log', this._newLog); _on('ping', this._ping); _on('disconnect', this._disconnect); ``` ... causing the browser to ignore those events... stopping the harvester process has no impact on the ui unless the browser is refreshed. When the browser is refreshed the node and its streams will be missing. After starting the harvester again, the browser sees the new node and all its streams and there is no flickering. Hope that narrows it down.

kerem commented

2026-02-26 05:31:12 +03:00

Author

Owner

@jacobfra commented on GitHub (Nov 27, 2013):

Was this ever resolved. I just started looking into logio and I am liking what I see so far.

@jacobfra commented on GitHub (Nov 27, 2013): Was this ever resolved. I just started looking into logio and I am liking what I see so far.

kerem commented

2026-02-26 05:31:12 +03:00

Author

Owner

@jacobfra commented on GitHub (Nov 27, 2013):

I did archieco's solution above and it does seem to resolve the flickering.

@jacobfra commented on GitHub (Nov 27, 2013): I did archieco's solution above and it does seem to resolve the flickering.

kerem commented

2026-02-26 05:31:12 +03:00

Author

Owner

@msmathers commented on GitHub (Aug 1, 2014):

This has been addressed in v0.3.4. Both the server and harvester will gracefully recover from connection thrashing.

@msmathers commented on GitHub (Aug 1, 2014): This has been addressed in v0.3.4. Both the server and harvester will gracefully recover from connection thrashing.

kerem referenced this issue

2026-02-26 05:31:42 +03:00

[PR #55] [CLOSED] Using nssocket for sending logs #237