oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management
Date Fri, 14 Jul 2017 15:40:00 GMT

    [ https://issues.apache.org/jira/browse/OODT-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087492#comment-16087492
] 

ASF GitHub Bot commented on OODT-945:
-------------------------------------

Github user chrismattmann commented on the issue:

    https://github.com/apache/oodt/pull/44
  
    So I checked, and I do have those environment variables set, except for ```RESMGR_HOME```
e.g., 
    
    ```
    LMC-053601:oodt mattmann$ echo $FILEMGR_HOME
    /usr/local/bigtranslate/filemgr
    LMC-053601:oodt mattmann$ echo $FILEMGR_URL
    http://localhost:9000
    LMC-053601:oodt mattmann$ 
    LMC-053601:oodt mattmann$ echo $RESMGR_URL
    http://localhost:9002
    LMC-053601:oodt mattmann$ 
    ```
    
    I was thinking about your code - is it that if an environment variable from local config
isn't that set - you are publishing a null value to ZK or there is a getPropertyOrNull call
somewhere that is causing this? If so, we should probably have a sensibleDefaults() configuration
which are all the sensible defaults in case the environment is Null. Even better would be
to use PathUtils in o.a.cas.metadata.util to do EnvVarOrMetadata replacement on all paths
you read from config.
    



> Rework OODT configuration to make use of  Zookeeper for distributed configuration management
> --------------------------------------------------------------------------------------------
>
>                 Key: OODT-945
>                 URL: https://issues.apache.org/jira/browse/OODT-945
>             Project: OODT
>          Issue Type: Bug
>            Reporter: Tom Barber
>            Assignee: Tom Barber
>              Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their own set
of configuration files and locations. This is complex to manage and causes additional problems
when the platform requires distribution across servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an opional
Zookeeper module that would allow users to commission a zookeeper cluster and register the
various OODT components against it, which will allow the zookeeper cluster to maintain the
state of the various OODT components regardless of scale.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message