[STORM-1733] Logs from bin/storm are lost because stdout and stderr are not flushed

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.9.3, 0.10.0, 0.9.4, 0.9.5, 0.9.6
• Fix Version/s: 2.0.0, 1.0.1, 0.10.2
• Assignee: Karthick Duraisamy Soundararaj
• Reporter: Karthick Duraisamy Soundararaj
• Created: 26/Apr/16 19:16
• Updated: 29/Apr/16 15:56
• Resolved: 29/Apr/16 15:56

Description

bin/storm.py emits the following crucial information that is lost because we don't flush the stdout before exec.

2016-04-25T08:23:43.17141 Running: java -server -Dstorm.options= -Dstorm.home= -Xmx1024m -Dlogfile.name=nimbus.log -Dlogback.configurationFile=logback/cluster.xml  backtype.storm.ui.core.nimbus

Observed Environment:

OS: CentOS release 6.5 
Kernel: 2.6.32-431.el6.x86_64
Python version: Python 2.7.2

For example, I using runit to start storm components like nimbus, ui, etc and the problem is applicable to all the components and in all the cases, I am not seeing logs that are emitted by bin/storm before os.execvp is called to actually launch the component.

Please note that in cases where stdout and stderr is terminal, the stdout and stderr are always flushed and the bug is not applicable.