cdap-ui dies when master is killed
Description
Release Notes
None
is duplicated by
relates to
Activity
Show:
Edwin Elia
changed the StatusJuly 7, 2015 at 12:16 AMOpen
Resolved
Edwin Elia
updated the ResolutionJuly 7, 2015 at 12:16 AMNone
Fixed
Edwin Elia
updated the SprintJuly 7, 2015 at 12:10 AMNone
FE Sprint ending 07/06
Edwin Elia
updated the RankJuly 7, 2015 at 12:10 AMNone
Ranked higher
Edwin Elia
updated the LinkJuly 2, 2015 at 10:47 PMNone
This issue relates to CDAP-2740
Sreevatsan Raman
updated the LinkJuly 2, 2015 at 6:23 PMNone
This issue is duplicated by CDAP-2850
Edwin Elia
updated the Fix versionsJuly 1, 2015 at 7:38 PMNone
3.1.0
Edwin Elia
changed the AssigneeJuly 1, 2015 at 7:38 PM
NitinM
Edwin Elia
Andreas Neumann
created the IssueJune 22, 2015 at 2:15 AMFixed
Pinned fields
Click on the next to a field label to start pinning.
Created June 22, 2015 at 2:15 AM
Updated July 7, 2015 at 12:16 AM
Resolved July 7, 2015 at 12:16 AM
It should not crash in that situation. The router would start routing to the secondary master and the ui would function again. The ui should wait for that and then get back to normal. In the logs I see:
Error: socket hang up at createHangUpError (http.js:1477:15) at Socket.socketOnEnd [as onend] (http.js:1573:23) at Socket.g (events.js:180:16) at Socket.emit (events.js:117:20) at _stream_readable.js:944:16 at process._tickCallback (node.js:442:13) /var/log/cdap/ui-cdap-hanew1792-1000.dev.continuuity.net.log (END)