-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[SMALLFIX] Put the lineage master and worker behind the flag #1814
Conversation
Test PASSed. |
@@ -170,7 +170,10 @@ protected TachyonMaster() { | |||
mBlockMaster = new BlockMaster(mBlockMasterJournal); | |||
mFileSystemMaster = new FileSystemMaster(mBlockMaster, mFileSystemMasterJournal); | |||
mRawTableMaster = new RawTableMaster(mFileSystemMaster, mRawTableMasterJournal); | |||
mLineageMaster = new LineageMaster(mFileSystemMaster, mLineageMasterJournal); | |||
boolean enableLineage = MasterContext.getConf().getBoolean(Constants.USER_LINEAGE_ENABLED); |
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.
lineageEnabled
? (Applies to the worker part as well)
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.
done
Test PASSed. |
LGTM |
[SMALLFIX] Put the lineage master and worker behind the flag
@yupeng9 Do you mind changing the variable to no longer be a |
@calvinjia, I set it to be a user variable because it's a feature flag up to the user to turn on/off. But I'm open to other suggestions. What kind of variable that you think is better? |
No description provided.