[
https://issues.apache.org/jira/browse/KAFKA-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629055#comment-14629055
]
Ewen Cheslack-Postava commented on KAFKA-2330:
----------------------------------------------
[~granders] Uggh, that's really annoying. It looks like the right setting
depends on the version of vagrant-aws you're using. Older versions had a custom
rsyncing solution inside the vagrant-aws plugin, newer versions (0.6.0+) use
the support provided by vagrant. It's very likely that I originally developed
this pre-0.6.0 when this setting would have worked.
Since the rsync_excludes version no longer works on the most recent versions of
the plugin, we should switch to the rsync__exclude form, but we'll probably
have to dig through Vagrant code to figure out why its not working.
For reference, which versions do vagrant version and vagrant plugin list show
for the machine you tested this on?
> Vagrantfile sets global configs instead of per-provider override configs
> ------------------------------------------------------------------------
>
> Key: KAFKA-2330
> URL: https://issues.apache.org/jira/browse/KAFKA-2330
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.2.1
> Reporter: Ewen Cheslack-Postava
> Assignee: Ewen Cheslack-Postava
> Priority: Minor
> Fix For: 0.8.3
>
> Attachments: KAFKA-2330.patch
>
>
> There's a couple of minor incorrect usages of the global configuration object
> in the Vagrantfile inside provider-specific override blocks where we should
> be using the override config object. Two end up being harmless since they
> have no affect on other providers (but should still be corrected). The third
> results in using rsync when using Virtualbox, which is unnecessary, slower,
> and requires copying the entire kafka directory to every VM.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
