You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by John Vines <vi...@apache.org> on 2013/04/29 21:23:06 UTC
Classloader tiers
While trying to work out the issues with the reloading classloader, I
noticed that the 2nd tier classloader has a hard-coded path which utilizes
a series of hadoop directories, as well as zookeeper directories. This
causes my concern because, while I'm not sure what exactly this 2nd tier
NEEDS to load to get the VFS stuff going, there is always a possibility for
these jars to migrate between versions/packages and then there would be no
way to support without a code change.
Does anyone know what exactly this tier needs to load, and then can we see
about paring down this list and exposing it as something configurable?
Re: Classloader tiers
Posted by John Vines <vi...@apache.org>.
Ah, I see now. Those seem to be the defaults in lieu of the setting being
in the xml.
Thanks
On Mon, Apr 29, 2013 at 3:50 PM, Eric Newton <er...@gmail.com> wrote:
> Aren't the 2nd tier settings from the java classpath?
>
> -Eric
>
>
> On Mon, Apr 29, 2013 at 3:23 PM, John Vines <vi...@apache.org> wrote:
>
>> While trying to work out the issues with the reloading classloader, I
>> noticed that the 2nd tier classloader has a hard-coded path which utilizes
>> a series of hadoop directories, as well as zookeeper directories. This
>> causes my concern because, while I'm not sure what exactly this 2nd tier
>> NEEDS to load to get the VFS stuff going, there is always a possibility
>> for
>> these jars to migrate between versions/packages and then there would be no
>> way to support without a code change.
>>
>> Does anyone know what exactly this tier needs to load, and then can we see
>> about paring down this list and exposing it as something configurable?
>>
>
>
Re: Classloader tiers
Posted by Eric Newton <er...@gmail.com>.
Aren't the 2nd tier settings from the java classpath?
-Eric
On Mon, Apr 29, 2013 at 3:23 PM, John Vines <vi...@apache.org> wrote:
> While trying to work out the issues with the reloading classloader, I
> noticed that the 2nd tier classloader has a hard-coded path which utilizes
> a series of hadoop directories, as well as zookeeper directories. This
> causes my concern because, while I'm not sure what exactly this 2nd tier
> NEEDS to load to get the VFS stuff going, there is always a possibility for
> these jars to migrate between versions/packages and then there would be no
> way to support without a code change.
>
> Does anyone know what exactly this tier needs to load, and then can we see
> about paring down this list and exposing it as something configurable?
>