[jira] [Commented] (TRAFODION-2877) DCS server can't be restarted when switch to backup-master

[ASF GitHub Bot (JIRA)]

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

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

Github user mashengchen commented on a diff in the pull request:

https://github.com/apache/trafodion/pull/1369#discussion_r159811900
  
--- Diff: dcs/src/main/java/org/trafodion/dcs/master/ServerManager.java ---
@@ -240,15 +240,14 @@ public ScriptContext call() throws Exception {
 }
 }
 } else {
-if (LOG.isDebugEnabled())
-LOG.debug("No restart for "
-+ znodePath
-+ "\nbecause DcsServer start time ["
-+ DateFormat.getDateTimeInstance().format(
-new Date(serverStartTimestamp))
-+ "] was before DcsMaster start time ["
-+ DateFormat.getDateTimeInstance().format(
-new Date(startupTimestamp)) + "]");
+LOG.info("No restart for "
--- End diff --

You are right, I should change the log, thanks.


> DCS server can't be restarted when switch to backup-master
> --
>
> Key: TRAFODION-2877
> URL: https://issues.apache.org/jira/browse/TRAFODION-2877
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: dcs
>Affects Versions: 2.3
>Reporter: mashengchen
>Assignee: mashengchen
>Priority: Critical
> Fix For: 2.3
>
>
> DcsServer does not be restarted by DcsMaster on HDP.
> Steps To Reproduce
> 1. check Hadoop and instance status
> 2. kill active DcsMaster
> 3. repeat Step 1
> 4. kill DcsServer on the active DcsMaster node
> 5. repeat Step 1
> 6. DcsServer never been restarted



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

[jira] [Created] (TRAFODION-2883) Preliminary Trafodion Scalability Enhancements

[Gonzalo E Correa (JIRA)]

Gonzalo E Correa created TRAFODION-2883:
---

 Summary: Preliminary Trafodion Scalability Enhancements
 Key: TRAFODION-2883
 URL: https://issues.apache.org/jira/browse/TRAFODION-2883
 Project: Apache Trafodion
  Issue Type: Improvement
  Components: dtm, foundation, installer
Affects Versions: 2.3
Reporter: Gonzalo E Correa
Assignee: Gonzalo E Correa
 Fix For: 2.3


Initial changes required to increase the size of Trafodion instance from 256 
servers to 1024 servers.



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

[jira] [Created] (TRAFODION-2882) Foundation infrastructure changes needed to support operating in Cloudera Manager environment

[Gonzalo E Correa (JIRA)]

Gonzalo E Correa created TRAFODION-2882:
---

 Summary: Foundation infrastructure changes needed to support 
operating in Cloudera Manager environment
 Key: TRAFODION-2882
 URL: https://issues.apache.org/jira/browse/TRAFODION-2882
 Project: Apache Trafodion
  Issue Type: Improvement
  Components: foundation
Affects Versions: 2.3
Reporter: Gonzalo E Correa
Assignee: Gonzalo E Correa
 Fix For: 2.3


The method for starting a Trafodion instance is based on Open MPI. A different 
method is needed to remove this dependency and to allow for larger cluster 
configuration installations.

This calls for a different method of instantiating a Trafodion cluster instance 
which utilizes existing node reintegration, i.e., node up, capability and is 
not dependent on Open MPI.



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

[jira] [Created] (TRAFODION-2881) Multiple node failures occur during HA testing

[Gonzalo E Correa (JIRA)]

Gonzalo E Correa created TRAFODION-2881:
---

 Summary: Multiple node failures occur during HA testing
 Key: TRAFODION-2881
 URL: https://issues.apache.org/jira/browse/TRAFODION-2881
 Project: Apache Trafodion
  Issue Type: Bug
  Components: foundation
Affects Versions: 2.3
Reporter: Gonzalo E Correa
Assignee: Gonzalo E Correa
 Fix For: 2.3


Inflicting server failure in certain modes will cause multiple monitor process 
to also bring their nodes down along with the intended target of the test.

Server down modes:

init 6
reboot -f
shutdown -r now
shell node down command

In addition, after a server down, the shell 'node up' command will also fail 
intermittently. This requires a longevity HA test to down and up nodes over a 
long period of time like 24-48 hours.




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

[jira] [Commented] (TRAFODION-2863) Website does not work well with https.

[ASF GitHub Bot (JIRA)]

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

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

GitHub user svarnau opened a pull request:

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

[TRAFODION-2863] Web-page style sheets should be protocol relative

To be compatible with http or https

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

$ git pull https://github.com/svarnau/trafodion j2863

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

https://github.com/apache/trafodion/pull/1371.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 #1371


commit 98a07c3f1e5843b061d197a6427400f521d793dd
Author: Steve Varnau 
Date:   2018-01-04T23:02:01Z

[TRAFODION-2863] Web-page style sheets should be protocol relative

To be compatible with http or https




> Website does not work well with https.
> --
>
> Key: TRAFODION-2863
> URL: https://issues.apache.org/jira/browse/TRAFODION-2863
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: website
>Reporter: Pierre Smits
>Assignee: Steve Varnau
>
> When viewing the website through the https protocol the style (which we see 
> applied when viewing it through the http protocol) is not applied. It seems 
> the style sheet is not loaded.



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

[jira] [Commented] (TRAFODION-2865) Update Messages Guide for some messages in the range 1300-1399

[David Wayne Birdsall (JIRA)]

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

David Wayne Birdsall commented on TRAFODION-2865:
-

The fix above actually takes care of the range 1400-1499 as well. Note that 
messages 1433-1499 are currently unused.

> Update Messages Guide for some messages in the range 1300-1399
> --
>
> Key: TRAFODION-2865
> URL: https://issues.apache.org/jira/browse/TRAFODION-2865
> Project: Apache Trafodion
>  Issue Type: Sub-task
>  Components: documentation
>Affects Versions: 2.3
> Environment: All
>Reporter: David Wayne Birdsall
>Assignee: David Wayne Birdsall
> Fix For: 2.3
>
>




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

[jira] [Resolved] (TRAFODION-2875) Fix some inaccurate comparisons in analyzeMessageGuide.py

[David Wayne Birdsall (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TRAFODION-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Wayne Birdsall resolved TRAFODION-2875.
-
   Resolution: Fixed
Fix Version/s: 2.3

> Fix some inaccurate comparisons in analyzeMessageGuide.py
> -
>
> Key: TRAFODION-2875
> URL: https://issues.apache.org/jira/browse/TRAFODION-2875
> Project: Apache Trafodion
>  Issue Type: Sub-task
>  Components: dev-environment
> Environment: All
>Reporter: David Wayne Birdsall
>Assignee: David Wayne Birdsall
>Priority: Minor
> Fix For: 2.3
>
>
> The analyzeMessagesGuide.py script will declare a mismatch if there are 
> differing numbers of trailing spaces in the message text as opposed to the 
> documentation. The script should ignore such differences. The script also may 
> incorrectly conclude that the message text matches the documentation when the 
> message text ends with two substitution fields but the documentation only 
> ends with one. This should be fixed.



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

[jira] [Commented] (TRAFODION-2875) Fix some inaccurate comparisons in analyzeMessageGuide.py

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> Fix some inaccurate comparisons in analyzeMessageGuide.py
> -
>
> Key: TRAFODION-2875
> URL: https://issues.apache.org/jira/browse/TRAFODION-2875
> Project: Apache Trafodion
>  Issue Type: Sub-task
>  Components: dev-environment
> Environment: All
>Reporter: David Wayne Birdsall
>Assignee: David Wayne Birdsall
>Priority: Minor
>
> The analyzeMessagesGuide.py script will declare a mismatch if there are 
> differing numbers of trailing spaces in the message text as opposed to the 
> documentation. The script should ignore such differences. The script also may 
> incorrectly conclude that the message text matches the documentation when the 
> message text ends with two substitution fields but the documentation only 
> ends with one. This should be fixed.



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

[jira] [Created] (TRAFODION-2879) Core dump due to reference to deallocated memory for EstLogProp object

[Hans Zeller (JIRA)]

Hans Zeller created TRAFODION-2879:
--

 Summary: Core dump due to reference to deallocated memory for 
EstLogProp object
 Key: TRAFODION-2879
 URL: https://issues.apache.org/jira/browse/TRAFODION-2879
 Project: Apache Trafodion
  Issue Type: Bug
  Components: sql-cmp
Affects Versions: 2.0-incubating
 Environment: Any
Reporter: Hans Zeller
Assignee: Hans Zeller
 Fix For: 2.3


This looks like an old bug that was recently found by Eric Owhadi, with a stack 
trace that looks like this:

{noformat}
#5  0x7f23af4264fa in NAHeap::deallocateHeapMemory (this=0x7f237ddd66c0, 
addr=0x7f236f70fba8) at ../common/NAMemory.cpp:3230
#6  0x7f23af42207b in NAMemory::deallocateMemory (this=0x7f237ddd66c0, 
addr=0x7f236f70fba8) at ../common/NAMemory.cpp:1265
#7  0x7f23ada97cdd in NABasicObject::operator delete (p=0x7f236f70fba8)
at ../export/NABasicObject.cpp:139
#8  0x7f23ac37fa24 in EstLogProp::~EstLogProp (this=0x7f236f70fba8, 
__in_chrg=) at ../optimizer/EstLogProp.cpp:130
#9  0x7f23ac38117e in IntrusiveSharedRefCount::destroyObjects (
this=0x7f236f70fbb8) at ../common/SharedPtr.h:226
#10 0x7f23ac1ce7de in SharedRefCountBase::decrUseCount (
this=0x7f236f70fbb8) at ../common/SharedPtr.h:136
#11 0x7f23ac1cb845 in SharedPtr::~SharedPtr (
---Type  to continue, or q  to quit---
this=0x7f2382e8e2d0, __in_chrg=)
at ../common/SharedPtr.h:280
#12 0x7f23ac1c591e in IntrusiveSharedPtr::~IntrusiveSharedPtr (
this=0x7f2382e8e2d0, __in_chrg=)
at ../common/SharedPtr.h:376
#13 0x7f23ab92d85a in CmpContext::~CmpContext (this=0x7f2382e8e090, 
__in_chrg=) at ../arkcmp/CmpContext.cpp:382
{noformat}

I suspect that we are trying to delete the CmpContext::emptyInLogProp_ data 
member here.
 
I think this data member is initialized incorrectly:
 
- The CmpContext object lives longer than an individual statement
- Initially, CmpContext::emptyInLogProp_ is a NULL pointer
- For every statement (or at least for most statements), we set this data 
member to an object allocated from the statement heap, see 
CmpStatement::initQueryAnalysis() in file arkcmp/CmpStatement.cpp.
- We don’t deallocate this data member explicitly, as far as I can see. It gets 
automatically deleted when we call the destructor or when we assign a different 
value to the IntrusiveSharedPtr.
 
So, what happens is that when we destroy the statement and its heap, we leave a 
dangling reference to a deallocated object in the CmpContext. As we can see 
here, when we later destroy the context, we point to an object in deallocated 
memory.

We need to do two things to fix this: First, with these shared pointers, we 
cannot allocate an object from the statement heap without calling the 
destructor for the object. Second, we cannot point from the CmpContext to an 
object that is allocated from the short-lived statement heap - at least not 
beyond the lifetime of the statement.




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

[jira] [Commented] (TRAFODION-2861) Remove incubating reference(s) from code base

[ASF GitHub Bot (JIRA)]

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

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

GitHub user svarnau opened a pull request:

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

[TRAFODION-2861][TRAFODION-2869] Remove incubating from release packaging

Remove disclaimer file and incubating string from packaging file names.

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

$ git pull https://github.com/svarnau/trafodion pkg-tlp

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

https://github.com/apache/trafodion/pull/1370.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 #1370


commit 34bf83acb40350b646b1e906445423b2c041412f
Author: Steve Varnau 
Date:   2018-01-04T20:07:47Z

[TRAFODION-2861][TRAFODION-2869] Remove incubating from release packaging

Remove disclaimer file and incubating string from packaging file names.




> Remove incubating reference(s) from code base
> -
>
> Key: TRAFODION-2861
> URL: https://issues.apache.org/jira/browse/TRAFODION-2861
> Project: Apache Trafodion
>  Issue Type: Sub-task
>  Components: documentation, website
>Reporter: Pierre Smits
>




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

[jira] [Resolved] (TRAFODION-2865) Update Messages Guide for some messages in the range 1300-1399

[David Wayne Birdsall (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TRAFODION-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Wayne Birdsall resolved TRAFODION-2865.
-
   Resolution: Fixed
Fix Version/s: 2.3

> Update Messages Guide for some messages in the range 1300-1399
> --
>
> Key: TRAFODION-2865
> URL: https://issues.apache.org/jira/browse/TRAFODION-2865
> Project: Apache Trafodion
>  Issue Type: Sub-task
>  Components: documentation
>Affects Versions: 2.3
> Environment: All
>Reporter: David Wayne Birdsall
>Assignee: David Wayne Birdsall
> Fix For: 2.3
>
>




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

[jira] [Commented] (TRAFODION-2865) Update Messages Guide for some messages in the range 1300-1399

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> Update Messages Guide for some messages in the range 1300-1399
> --
>
> Key: TRAFODION-2865
> URL: https://issues.apache.org/jira/browse/TRAFODION-2865
> Project: Apache Trafodion
>  Issue Type: Sub-task
>  Components: documentation
>Affects Versions: 2.3
> Environment: All
>Reporter: David Wayne Birdsall
>Assignee: David Wayne Birdsall
>




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

[jira] [Commented] (TRAFODION-2866) Add HBase Configuration Changes for *Trafodion Provisioning Guide*

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> Add HBase Configuration Changes for *Trafodion Provisioning Guide*
> --
>
> Key: TRAFODION-2866
> URL: https://issues.apache.org/jira/browse/TRAFODION-2866
> Project: Apache Trafodion
>  Issue Type: Documentation
>Reporter: Liu Yu
>Assignee: Liu Yu
>




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

[jira] [Commented] (TRAFODION-2818) For Server 2008, function pow() in driver ODBC throws STATUS_ILLEGAL_INSTRUCTION

[ASF GitHub Bot (JIRA)]

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

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

Github user selvaganesang commented on a diff in the pull request:

https://github.com/apache/trafodion/pull/1311#discussion_r159498302
  
--- Diff: win-odbc64/odbcclient/drvr35/sqltocconv.cpp ---
@@ -2278,7 +2316,9 @@ unsigned long ODBC::ConvertSQLToC(SQLINTEGER  
ODBCAppVersion,
if (srcPrecision > 0)
{
// SQL returns fraction of a second 
which has to be converted to nano seconds
-   dTmp = 
(*(UDWORD*)SQLTimestamp->fraction *  10.0) / pow(10,srcPrecision);
+   dTmp = 
(*(UDWORD*)SQLTimestamp->fraction *  10.0) / 
pow(10,srcPrecision,);
+   if (retCode == IDS_22_003)
--- End diff --

Please consider checking the retCode before using it to divide in line 2319


> For Server 2008, function pow() in driver ODBC throws 
> STATUS_ILLEGAL_INSTRUCTION
> 
>
> Key: TRAFODION-2818
> URL: https://issues.apache.org/jira/browse/TRAFODION-2818
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: client-odbc-windows
>Affects Versions: any
> Environment: Server 2008 R2
>Reporter: XuWeixin
>Assignee: XuWeixin
> Fix For: any
>
>
> SQL_NUMERIC to SQL_C_CHAR
> ***ERROR: SQLGetData: Expected: SQL_SUCCESS Actual: SQL_ERROR
>State: HY000
>Native Error: 29
>Error: [TRAF][Trafodion ODBC Driver] General error.EXCEPTION: UNKNOWN - 
> Exception Code = c01d



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

[jira] [Commented] (TRAFODION-2873) LOB:Cleanup usage of LOBLoad which si deprecated and LobGlobals

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> LOB:Cleanup usage of LOBLoad which si deprecated and LobGlobals
> ---
>
> Key: TRAFODION-2873
> URL: https://issues.apache.org/jira/browse/TRAFODION-2873
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-exe
>Affects Versions: 2.3
>Reporter: Sandhya Sundaresan
>Assignee: Sandhya Sundaresan
>
> The LOBGlobals structure contains information relevant to LOBLoad which was 
> an operator initially designed to operate at the disk level. It is no longer 
> needed/relevant so cleaning up that code and simplifying the LOBGlobals 
> sturcture as well to keep only the relevant data members. 



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

[jira] [Resolved] (TRAFODION-2857) Remove incubating from trafodion web pages

[Steve Varnau (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TRAFODION-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Varnau resolved TRAFODION-2857.
-
   Resolution: Fixed
Fix Version/s: 2.3

master branch

> Remove incubating from trafodion web pages
> --
>
> Key: TRAFODION-2857
> URL: https://issues.apache.org/jira/browse/TRAFODION-2857
> Project: Apache Trafodion
>  Issue Type: Improvement
>Reporter: Steve Varnau
>Assignee: Steve Varnau
> Fix For: 2.3
>
>
> Preparing for announcment of graduation.



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

[jira] [Commented] (TRAFODION-2877) DCS server can't be restarted when switch to backup-master

[ASF GitHub Bot (JIRA)]

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

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

GitHub user mashengchen opened a pull request:

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

TRAFODION-2877 can't restart DCSServer when switch to backup-master

DcsServer does not be restarted by DcsMaster on HDP.
Steps To Reproduce
1. check Hadoop and instance status
2. kill active DcsMaster
3. repeat Step 1
4. kill DcsServer on the active DcsMaster node
5. repeat Step 1
6. DcsServer never been restarted

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

$ git pull https://github.com/mashengchen/incubator-trafodion 
dcsServerNotRestart

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

https://github.com/apache/trafodion/pull/1369.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 #1369


commit 2595998299e1a6bb281544e00faab1f7c7ceddda
Author: aven 
Date:   2018-01-04T10:15:54Z

TRAFODION-2877 restart DCSServer when switch to backup-master




> DCS server can't be restarted when switch to backup-master
> --
>
> Key: TRAFODION-2877
> URL: https://issues.apache.org/jira/browse/TRAFODION-2877
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: dcs
>Affects Versions: 2.3
>Reporter: mashengchen
>Assignee: mashengchen
>Priority: Critical
> Fix For: 2.3
>
>
> DcsServer does not be restarted by DcsMaster on HDP.
> Steps To Reproduce
> 1. check Hadoop and instance status
> 2. kill active DcsMaster
> 3. repeat Step 1
> 4. kill DcsServer on the active DcsMaster node
> 5. repeat Step 1
> 6. DcsServer never been restarted



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

[jira] [Created] (TRAFODION-2877) DCS server can't be restarted when switch to backup-master

[mashengchen (JIRA)]

mashengchen created TRAFODION-2877:
--

 Summary: DCS server can't be restarted when switch to backup-master
 Key: TRAFODION-2877
 URL: https://issues.apache.org/jira/browse/TRAFODION-2877
 Project: Apache Trafodion
  Issue Type: Bug
  Components: dcs
Affects Versions: 2.3
Reporter: mashengchen
Assignee: mashengchen
Priority: Critical
 Fix For: 2.3


DcsServer does not be restarted by DcsMaster on HDP.
Steps To Reproduce
1. check Hadoop and instance status
2. kill active DcsMaster
3. repeat Step 1
4. kill DcsServer on the active DcsMaster node
5. repeat Step 1
6. DcsServer never been restarted



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