[
https://issues.apache.org/jira/browse/MYRIAD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Klaus Ma closed MYRIAD-231.
---
Resolution: Fixed
Configuration issue; updated document in
[
https://issues.apache.org/jira/browse/MYRIAD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357930#comment-15357930
]
DarinJ commented on MYRIAD-231:
---
[~klaus1982], merged your PR. Did that resolve the issue? If so I'll
Hi,
Yes - the imaginatively named slave2 was a zero-sized nm at that point -
I am looking at how small a pool of reserved resource I can get away
with, and use FGS for burst activity.
Here are all the logs related to that host:port combination around that
time:
2016-06-30 19:47:43,756 INFO
Steven, thanks. I thought I had fixed that but perhaps a regression was
made in another merge. I'll look into it, can you answer a few questions?
Was the node (slave2) a zero sided nodemanager (for fgs)? In the node
manager logs had it recently become unhealthy? I'm pretty concerned about
this
Hi,
Just playing with the 0.2.0 release (congratulations, by the way!)
I have seen this twice now, although it is by no means consistent - I
will have a dozen successful runs, and then one of these. This exits
the RM, which makes it rather noticable.
2016-06-30 19:47:43,952 INFO
John Yost created MYRIAD-232:
Summary: Display Flex Down/Up errors to UI
Key: MYRIAD-232
URL: https://issues.apache.org/jira/browse/MYRIAD-232
Project: Myriad
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/MYRIAD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357033#comment-15357033
]
Klaus Ma commented on MYRIAD-231:
-
thanks :).
> Failed to regist zero profile to ResourceManager (2.7.2)
[
https://issues.apache.org/jira/browse/MYRIAD-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356898#comment-15356898
]
DarinJ commented on MYRIAD-231:
---
Klaus, thanks I'll look at this later today.
> Failed to regist zero
