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

ASF GitHub Bot commented on TRAFODION-3102:
-------------------------------------------

GitHub user mashengchen opened a pull request:

    https://github.com/apache/trafodion/pull/1600

    [TRAFODION-3102] unify hostname format as what monitor does

    it's hard to update statistic message each time row datas change. so 
current version does not support CARDINALITY.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mashengchen/trafodion dcs

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafodion/pull/1600.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1600
    
----
commit a2635d0cac985443f1800496fa8bf99010b18988
Author: aven <shengchen.ma@...>
Date:   2018-06-11T03:38:52Z

    [TRAFODION-3102] unify hostname format as what monitor does

----


> znode for mxosrvr may have capital and small letter and long short name 
> problem
> -------------------------------------------------------------------------------
>
>                 Key: TRAFODION-3102
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-3102
>             Project: Apache Trafodion
>          Issue Type: Improvement
>          Components: dcs
>            Reporter: mashengchen
>            Assignee: mashengchen
>            Priority: Major
>
> the znode name for mxosrvr currently is case sensitive and short long name 
> sensitive which means if the hostname is different from what it's configured 
> in servers, there may met problem.
> For example:
> hostname is MACHINE-01.LOCAL
> conf in servers is trafodion-01
> Then the znode will be MACHINE-01.LOCAL, and memory cached in dcs is
>  trafodion-01 which may have error when there has any comparion



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to