-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix rebind #1194
Fix rebind #1194
Conversation
Brooklyn Central » brooklyn #1676 FAILURE |
For #1 - it should be configurable via properties, defaulting to a subdirectory of ~/.brooklyn. $PWD would just lead to directories scattered everywhere. |
Test failure:
Looking at the code now. |
if (isActive()) { | ||
LOG.warn("Problem generating memento for "+context, e); | ||
} else { | ||
Exceptions.propagateIfFatal(e); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
already done this 3 lines up!
code looks really good for addressing these, and tests - one trivial comment plus fix the test failure, then merge! |
+1 @sjcorbett location configurable based on brooklyn.properties defaulting to a stable place (now PWD) but worth some thought to think through how we will store and make files configurable -- note that we've got a BrooklynConfigKeys.BROOKLYN_DATA_DIR, which is used in BrooklynWebServer to decide where to place jetty files -- but we don't have a nice distinction between management server data dirs (currently under ~/.brooklyn/, perhaps ~/.brooklyn/mgmt/... as default for generated?) and target machine data/ops dirs (currently /tmp/brooklyn-xxx/ but i would move out of /tmp as default as we are better off asking people to clean up than risking their operational data gets blown away by a cron job!) see #1172 |
Having been bitten before (on a production server), definitely +1 to moving On 6 February 2014 14:42, ahgittin [email protected] wrote:
Martin Harris |
- so that other entity mementos will still be generated + persisted, even if one entity is faulty
- previously was bug where change-change-delete could cause the second file-change to be written after the delete, thus re-creating the deleted file.
Have incorporate review comments, and fixed failing test (forgot to include a file!) - waiting for buildhive to confirm and then will merge. |
Brooklyn Central » brooklyn #1680 SUCCESS |
@ahgittin and @nakomis - I've address almost all of the comments comments in #1185, except the biggies. Still to do are:
And unrelated unaddressed comments:
@ahgittin for the problems you hit with entities-only-on-the-catalog-classpath, ControlledDynamicWebAppCluster failed to serialize because of classpath issues. When persisting the EntityMemento it tried to look up the Class.forName to find which config keys were statically defined (because it wouldn't persist those). I've fixed that by injecting the
transient Class
into the Memento to avoid the lookup.