[jira] [Commented] (HBASE-10500) Some tools OOM when BucketCache is enabled
[
https://issues.apache.org/jira/browse/HBASE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900047#comment-13900047
]
Hudson commented on HBASE-10500:
FAILURE: Integrated in HBase-0.98 #154 (See
[https://builds.apache.org/job/HBase-0.98/154/])
HBASE-10500 Some tools OOM when BucketCache is enabled (ndimiduk: rev 1567688)
*
/hbase/branches/0.98/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java
*
/hbase/branches/0.98/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
> Some tools OOM when BucketCache is enabled
> --
>
> Key: HBASE-10500
> URL: https://issues.apache.org/jira/browse/HBASE-10500
> Project: HBase
> Issue Type: Bug
> Components: HFile
>Affects Versions: 0.98.0, 0.96.0, 0.99.0
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
> Fix For: 0.96.2, 0.98.1, 0.99.0
>
> Attachments: HBASE-10500.00.patch, HBASE-10500.01.patch
>
>
> Running {{hbck --repair}} or {{LoadIncrementalHFiles}} when BucketCache is
> enabled in offheap mode can cause OOM. This is apparently because
> {{bin/hbase}} does not include $HBASE_REGIONSERVER_OPTS for these tools. This
> results in HRegion or HFileReaders initialized with a CacheConfig that
> doesn't have the necessary Direct Memory.
> Possible solutions include:
> - disable blockcache in the config used by hbck when running its repairs
> - include HBASE_REGIONSERVER_OPTS in the HBaseFSCK startup arguments
> I'm leaning toward the former because it's possible that hbck is run on a
> host with different hardware profile as the RS.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HBASE-10500) Some tools OOM when BucketCache is enabled
[
https://issues.apache.org/jira/browse/HBASE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899941#comment-13899941
]
Hudson commented on HBASE-10500:
FAILURE: Integrated in HBase-TRUNK-on-Hadoop-1.1 #88 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-1.1/88/])
HBASE-10500 Some tools OOM when BucketCache is enabled (ndimiduk: rev 1567687)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
> Some tools OOM when BucketCache is enabled
> --
>
> Key: HBASE-10500
> URL: https://issues.apache.org/jira/browse/HBASE-10500
> Project: HBase
> Issue Type: Bug
> Components: HFile
>Affects Versions: 0.98.0, 0.96.0, 0.99.0
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
> Fix For: 0.96.2, 0.98.1, 0.99.0
>
> Attachments: HBASE-10500.00.patch, HBASE-10500.01.patch
>
>
> Running {{hbck --repair}} or {{LoadIncrementalHFiles}} when BucketCache is
> enabled in offheap mode can cause OOM. This is apparently because
> {{bin/hbase}} does not include $HBASE_REGIONSERVER_OPTS for these tools. This
> results in HRegion or HFileReaders initialized with a CacheConfig that
> doesn't have the necessary Direct Memory.
> Possible solutions include:
> - disable blockcache in the config used by hbck when running its repairs
> - include HBASE_REGIONSERVER_OPTS in the HBaseFSCK startup arguments
> I'm leaning toward the former because it's possible that hbck is run on a
> host with different hardware profile as the RS.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HBASE-10500) Some tools OOM when BucketCache is enabled
[
https://issues.apache.org/jira/browse/HBASE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899895#comment-13899895
]
Hudson commented on HBASE-10500:
FAILURE: Integrated in hbase-0.96-hadoop2 #202 (See
[https://builds.apache.org/job/hbase-0.96-hadoop2/202/])
HBASE-10500 Some tools OOM when BucketCache is enabled (ndimiduk: rev 1567689)
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
> Some tools OOM when BucketCache is enabled
> --
>
> Key: HBASE-10500
> URL: https://issues.apache.org/jira/browse/HBASE-10500
> Project: HBase
> Issue Type: Bug
> Components: HFile
>Affects Versions: 0.98.0, 0.96.0, 0.99.0
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
> Fix For: 0.96.2, 0.98.1, 0.99.0
>
> Attachments: HBASE-10500.00.patch, HBASE-10500.01.patch
>
>
> Running {{hbck --repair}} or {{LoadIncrementalHFiles}} when BucketCache is
> enabled in offheap mode can cause OOM. This is apparently because
> {{bin/hbase}} does not include $HBASE_REGIONSERVER_OPTS for these tools. This
> results in HRegion or HFileReaders initialized with a CacheConfig that
> doesn't have the necessary Direct Memory.
> Possible solutions include:
> - disable blockcache in the config used by hbck when running its repairs
> - include HBASE_REGIONSERVER_OPTS in the HBaseFSCK startup arguments
> I'm leaning toward the former because it's possible that hbck is run on a
> host with different hardware profile as the RS.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HBASE-10500) Some tools OOM when BucketCache is enabled
[
https://issues.apache.org/jira/browse/HBASE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899540#comment-13899540
]
Hudson commented on HBASE-10500:
FAILURE: Integrated in HBase-TRUNK #4913 (See
[https://builds.apache.org/job/HBase-TRUNK/4913/])
HBASE-10500 Some tools OOM when BucketCache is enabled (ndimiduk: rev 1567687)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
> Some tools OOM when BucketCache is enabled
> --
>
> Key: HBASE-10500
> URL: https://issues.apache.org/jira/browse/HBASE-10500
> Project: HBase
> Issue Type: Bug
> Components: HFile
>Affects Versions: 0.98.0, 0.96.0, 0.99.0
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
> Fix For: 0.96.2, 0.98.1, 0.99.0
>
> Attachments: HBASE-10500.00.patch, HBASE-10500.01.patch
>
>
> Running {{hbck --repair}} or {{LoadIncrementalHFiles}} when BucketCache is
> enabled in offheap mode can cause OOM. This is apparently because
> {{bin/hbase}} does not include $HBASE_REGIONSERVER_OPTS for these tools. This
> results in HRegion or HFileReaders initialized with a CacheConfig that
> doesn't have the necessary Direct Memory.
> Possible solutions include:
> - disable blockcache in the config used by hbck when running its repairs
> - include HBASE_REGIONSERVER_OPTS in the HBaseFSCK startup arguments
> I'm leaning toward the former because it's possible that hbck is run on a
> host with different hardware profile as the RS.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HBASE-10500) Some tools OOM when BucketCache is enabled
[
https://issues.apache.org/jira/browse/HBASE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899488#comment-13899488
]
Hudson commented on HBASE-10500:
SUCCESS: Integrated in HBase-0.98-on-Hadoop-1.1 #140 (See
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/140/])
HBASE-10500 Some tools OOM when BucketCache is enabled (ndimiduk: rev 1567688)
*
/hbase/branches/0.98/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java
*
/hbase/branches/0.98/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
> Some tools OOM when BucketCache is enabled
> --
>
> Key: HBASE-10500
> URL: https://issues.apache.org/jira/browse/HBASE-10500
> Project: HBase
> Issue Type: Bug
> Components: HFile
>Affects Versions: 0.98.0, 0.96.0, 0.99.0
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
> Fix For: 0.96.2, 0.98.1, 0.99.0
>
> Attachments: HBASE-10500.00.patch, HBASE-10500.01.patch
>
>
> Running {{hbck --repair}} or {{LoadIncrementalHFiles}} when BucketCache is
> enabled in offheap mode can cause OOM. This is apparently because
> {{bin/hbase}} does not include $HBASE_REGIONSERVER_OPTS for these tools. This
> results in HRegion or HFileReaders initialized with a CacheConfig that
> doesn't have the necessary Direct Memory.
> Possible solutions include:
> - disable blockcache in the config used by hbck when running its repairs
> - include HBASE_REGIONSERVER_OPTS in the HBaseFSCK startup arguments
> I'm leaning toward the former because it's possible that hbck is run on a
> host with different hardware profile as the RS.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HBASE-10500) Some tools OOM when BucketCache is enabled
[
https://issues.apache.org/jira/browse/HBASE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899485#comment-13899485
]
Hudson commented on HBASE-10500:
FAILURE: Integrated in hbase-0.96 #292 (See
[https://builds.apache.org/job/hbase-0.96/292/])
HBASE-10500 Some tools OOM when BucketCache is enabled (ndimiduk: rev 1567689)
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
> Some tools OOM when BucketCache is enabled
> --
>
> Key: HBASE-10500
> URL: https://issues.apache.org/jira/browse/HBASE-10500
> Project: HBase
> Issue Type: Bug
> Components: HFile
>Affects Versions: 0.98.0, 0.96.0, 0.99.0
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
> Fix For: 0.96.2, 0.98.1, 0.99.0
>
> Attachments: HBASE-10500.00.patch, HBASE-10500.01.patch
>
>
> Running {{hbck --repair}} or {{LoadIncrementalHFiles}} when BucketCache is
> enabled in offheap mode can cause OOM. This is apparently because
> {{bin/hbase}} does not include $HBASE_REGIONSERVER_OPTS for these tools. This
> results in HRegion or HFileReaders initialized with a CacheConfig that
> doesn't have the necessary Direct Memory.
> Possible solutions include:
> - disable blockcache in the config used by hbck when running its repairs
> - include HBASE_REGIONSERVER_OPTS in the HBaseFSCK startup arguments
> I'm leaning toward the former because it's possible that hbck is run on a
> host with different hardware profile as the RS.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HBASE-10500) Some tools OOM when BucketCache is enabled
[
https://issues.apache.org/jira/browse/HBASE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898800#comment-13898800
]
Nick Dimiduk commented on HBASE-10500:
--
IntegrationTestBulkLoad and IntegrationTestImportTsv both pass here. Lacking
objection, will commit tomorrow.
> Some tools OOM when BucketCache is enabled
> --
>
> Key: HBASE-10500
> URL: https://issues.apache.org/jira/browse/HBASE-10500
> Project: HBase
> Issue Type: Bug
> Components: HFile
>Affects Versions: 0.98.0, 0.96.0, 0.99.0
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
> Attachments: HBASE-10500.00.patch, HBASE-10500.01.patch
>
>
> Running {{hbck --repair}} or {{LoadIncrementalHFiles}} when BucketCache is
> enabled in offheap mode can cause OOM. This is apparently because
> {{bin/hbase}} does not include $HBASE_REGIONSERVER_OPTS for these tools. This
> results in HRegion or HFileReaders initialized with a CacheConfig that
> doesn't have the necessary Direct Memory.
> Possible solutions include:
> - disable blockcache in the config used by hbck when running its repairs
> - include HBASE_REGIONSERVER_OPTS in the HBaseFSCK startup arguments
> I'm leaning toward the former because it's possible that hbck is run on a
> host with different hardware profile as the RS.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HBASE-10500) Some tools OOM when BucketCache is enabled
[
https://issues.apache.org/jira/browse/HBASE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898605#comment-13898605
]
Hadoop QA commented on HBASE-10500:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12628364/HBASE-10500.01.patch
against trunk revision .
ATTACHMENT ID: 12628364
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop1.1{color}. The patch compiles against the hadoop
1.1 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/8664//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/8664//console
This message is automatically generated.
> Some tools OOM when BucketCache is enabled
> --
>
> Key: HBASE-10500
> URL: https://issues.apache.org/jira/browse/HBASE-10500
> Project: HBase
> Issue Type: Bug
> Components: HFile
>Affects Versions: 0.98.0, 0.96.0, 0.99.0
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
> Attachments: HBASE-10500.00.patch, HBASE-10500.01.patch
>
>
> Running {{hbck --repair}} or {{LoadIncrementalHFiles}} when BucketCache is
> enabled in offheap mode can cause OOM. This is apparently because
> {{bin/hbase}} does not include $HBASE_REGIONSERVER_OPTS for these tools. This
> results in HRegion or HFileReaders initialized with a CacheConfig that
> doesn't have the necessary Direct Memory.
> Possible solutions include:
> - disable blockcache in the config used by hbck when running its repairs
> - include HBASE_REGIONSERVER_OPTS in the HBaseFSCK startup arguments
> I'm leaning toward the former because it's possible that hbck is run on a
> host with different hardware profile as the RS.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HBASE-10500) Some tools OOM when BucketCache is enabled
[
https://issues.apache.org/jira/browse/HBASE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898491#comment-13898491
]
stack commented on HBASE-10500:
---
Yeah, probably better. I can't think of case where tool would need to offheap.
If it does, lets deal then. Meantime, get these tools useable again when
offheap enabled.
> Some tools OOM when BucketCache is enabled
> --
>
> Key: HBASE-10500
> URL: https://issues.apache.org/jira/browse/HBASE-10500
> Project: HBase
> Issue Type: Bug
> Components: HFile
>Affects Versions: 0.98.0, 0.96.0, 0.99.0
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
> Attachments: HBASE-10500.00.patch, HBASE-10500.01.patch
>
>
> Running {{hbck --repair}} or {{LoadIncrementalHFiles}} when BucketCache is
> enabled in offheap mode can cause OOM. This is apparently because
> {{bin/hbase}} does not include $HBASE_REGIONSERVER_OPTS for these tools. This
> results in HRegion or HFileReaders initialized with a CacheConfig that
> doesn't have the necessary Direct Memory.
> Possible solutions include:
> - disable blockcache in the config used by hbck when running its repairs
> - include HBASE_REGIONSERVER_OPTS in the HBaseFSCK startup arguments
> I'm leaning toward the former because it's possible that hbck is run on a
> host with different hardware profile as the RS.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HBASE-10500) Some tools OOM when BucketCache is enabled
[
https://issues.apache.org/jira/browse/HBASE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898492#comment-13898492
]
Hadoop QA commented on HBASE-10500:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12628314/HBASE-10500.00.patch
against trunk revision .
ATTACHMENT ID: 12628314
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop1.1{color}. The patch compiles against the hadoop
1.1 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:red}-1 core tests{color}. The patch failed these unit tests:
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/8662//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8662//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8662//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8662//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8662//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8662//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8662//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8662//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8662//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8662//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/8662//console
This message is automatically generated.
> Some tools OOM when BucketCache is enabled
> --
>
> Key: HBASE-10500
> URL: https://issues.apache.org/jira/browse/HBASE-10500
> Project: HBase
> Issue Type: Bug
> Components: HFile
>Affects Versions: 0.98.0, 0.96.0, 0.99.0
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
> Attachments: HBASE-10500.00.patch, HBASE-10500.01.patch
>
>
> Running {{hbck --repair}} or {{LoadIncrementalHFiles}} when BucketCache is
> enabled in offheap mode can cause OOM. This is apparently because
> {{bin/hbase}} does not include $HBASE_REGIONSERVER_OPTS for these tools. This
> results in HRegion or HFileReaders initialized with a CacheConfig that
> doesn't have the necessary Direct Memory.
> Possible solutions include:
> - disable blockcache in the config used by hbck when running its repairs
> - include HBASE_REGIONSERVER_OPTS in the HBaseFSCK startup arguments
> I'm leaning toward the former because it's possible that hbck is run on a
> host with different hardware profile as the RS.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
