[
https://issues.apache.org/jira/browse/STORM-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987814#comment-14987814
]
ASF GitHub Bot commented on STORM-876:
--------------------------------------
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/845#issuecomment-153448299
@ptgoetz I know you want to be careful about what gets merged in, and if
you insist we will go through the IP clearance process, but if we can avoid it
I really would prefer to do so. We have not had any issues in the past with
large commits, like when we contributed the security code to storm which
followed essentially the same process as this code. On my end it is probably
going to take longer than the 72 hour waiting period to track down the right
people to get signatures and they will all ask me why we have to do this when
my team has blanket approval to contribute to storm.
Like I said if you insist on getting IP clearance we will do it, but all it
is just going to do is add more pain for me which I really would like to avoid
if I can.
> Dist Cache: Basic Functionality
> -------------------------------
>
> Key: STORM-876
> URL: https://issues.apache.org/jira/browse/STORM-876
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-core
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Attachments: DISTCACHE.md, DistributedCacheDesignDocument.pdf
>
>
> Basic functionality for the Dist Cache feature.
> As part of this a new API should be added to support uploading and
> downloading dist cache items. storm-core.ser, storm-conf.ser and storm.jar
> should be written into the blob store instead of residing locally. We need a
> default implementation of the blob store that does essentially what nimbus
> currently does and does not need anything extra. But having an HDFS backend
> too would be great for scalability and HA.
> The supervisor should provide a way to download and manage these blobs and
> provide a working directory for the worker process with symlinks to the
> blobs. It should also allow the blobs to be updated and switch the symlink
> atomically to point to the new blob once it is downloaded.
> All of this is already done by code internal to Yahoo! we are in the process
> of getting it ready to push back to open source shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
