[jira] [Commented] (HBASE-22121) AsyncAdmin can not deal with non default meta replica
[
https://issues.apache.org/jira/browse/HBASE-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805969#comment-16805969
]
Hudson commented on HBASE-22121:
Results for branch master
[build #898 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/898/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/898//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/898//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/898//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> AsyncAdmin can not deal with non default meta replica
> -
>
> Key: HBASE-22121
> URL: https://issues.apache.org/jira/browse/HBASE-22121
> Project: HBase
> Issue Type: Bug
> Components: Admin, asyncclient, Client
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.3.0
>
> Attachments: HBASE-22121.patch, HBASE-22121.patch
>
>
> In AsyncAdmin we support passing both encodedRegionName and regionName as a
> parameter so we have a getRegionInfo method to get the RegionInfo first.
> In general we will scan the meta table to get the region info, but for meta
> region itself, the problem is that, we only check for the first replica, so
> for the non default replicas, we will still go to the meta region and then
> get an UnknownRegionException.
> We should find a way to deal with this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-22121) AsyncAdmin can not deal with non default meta replica
[
https://issues.apache.org/jira/browse/HBASE-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805959#comment-16805959
]
Hudson commented on HBASE-22121:
Results for branch branch-2.2
[build #144 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/144/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/144//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/144//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/144//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> AsyncAdmin can not deal with non default meta replica
> -
>
> Key: HBASE-22121
> URL: https://issues.apache.org/jira/browse/HBASE-22121
> Project: HBase
> Issue Type: Bug
> Components: Admin, asyncclient, Client
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.3.0
>
> Attachments: HBASE-22121.patch, HBASE-22121.patch
>
>
> In AsyncAdmin we support passing both encodedRegionName and regionName as a
> parameter so we have a getRegionInfo method to get the RegionInfo first.
> In general we will scan the meta table to get the region info, but for meta
> region itself, the problem is that, we only check for the first replica, so
> for the non default replicas, we will still go to the meta region and then
> get an UnknownRegionException.
> We should find a way to deal with this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-22121) AsyncAdmin can not deal with non default meta replica
[
https://issues.apache.org/jira/browse/HBASE-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805902#comment-16805902
]
Hudson commented on HBASE-22121:
Results for branch branch-2
[build #1787 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1787/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1787//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1787//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1787//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> AsyncAdmin can not deal with non default meta replica
> -
>
> Key: HBASE-22121
> URL: https://issues.apache.org/jira/browse/HBASE-22121
> Project: HBase
> Issue Type: Bug
> Components: Admin, asyncclient, Client
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.3.0
>
> Attachments: HBASE-22121.patch, HBASE-22121.patch
>
>
> In AsyncAdmin we support passing both encodedRegionName and regionName as a
> parameter so we have a getRegionInfo method to get the RegionInfo first.
> In general we will scan the meta table to get the region info, but for meta
> region itself, the problem is that, we only check for the first replica, so
> for the non default replicas, we will still go to the meta region and then
> get an UnknownRegionException.
> We should find a way to deal with this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-22121) AsyncAdmin can not deal with non default meta replica
[ https://issues.apache.org/jira/browse/HBASE-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805755#comment-16805755 ] Duo Zhang commented on HBASE-22121: --- Let me commit after fixing the checkstyle issues. > AsyncAdmin can not deal with non default meta replica > - > > Key: HBASE-22121 > URL: https://issues.apache.org/jira/browse/HBASE-22121 > Project: HBase > Issue Type: Bug > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.3.0, 2.1.5 > > Attachments: HBASE-22121.patch, HBASE-22121.patch > > > In AsyncAdmin we support passing both encodedRegionName and regionName as a > parameter so we have a getRegionInfo method to get the RegionInfo first. > In general we will scan the meta table to get the region info, but for meta > region itself, the problem is that, we only check for the first replica, so > for the non default replicas, we will still go to the meta region and then > get an UnknownRegionException. > We should find a way to deal with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22121) AsyncAdmin can not deal with non default meta replica
[ https://issues.apache.org/jira/browse/HBASE-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805734#comment-16805734 ] Guanghao Zhang commented on HBASE-22121: +1 > AsyncAdmin can not deal with non default meta replica > - > > Key: HBASE-22121 > URL: https://issues.apache.org/jira/browse/HBASE-22121 > Project: HBase > Issue Type: Bug > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.3.0, 2.1.5 > > Attachments: HBASE-22121.patch, HBASE-22121.patch > > > In AsyncAdmin we support passing both encodedRegionName and regionName as a > parameter so we have a getRegionInfo method to get the RegionInfo first. > In general we will scan the meta table to get the region info, but for meta > region itself, the problem is that, we only check for the first replica, so > for the non default replicas, we will still go to the meta region and then > get an UnknownRegionException. > We should find a way to deal with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22121) AsyncAdmin can not deal with non default meta replica
[ https://issues.apache.org/jira/browse/HBASE-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805678#comment-16805678 ] Duo Zhang commented on HBASE-22121: --- Because it is for locating meta region itself, not accessing meta? > AsyncAdmin can not deal with non default meta replica > - > > Key: HBASE-22121 > URL: https://issues.apache.org/jira/browse/HBASE-22121 > Project: HBase > Issue Type: Bug > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.3.0, 2.1.5 > > Attachments: HBASE-22121.patch, HBASE-22121.patch > > > In AsyncAdmin we support passing both encodedRegionName and regionName as a > parameter so we have a getRegionInfo method to get the RegionInfo first. > In general we will scan the meta table to get the region info, but for meta > region itself, the problem is that, we only check for the first replica, so > for the non default replicas, we will still go to the meta region and then > get an UnknownRegionException. > We should find a way to deal with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22121) AsyncAdmin can not deal with non default meta replica
[ https://issues.apache.org/jira/browse/HBASE-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805677#comment-16805677 ] Guanghao Zhang commented on HBASE-22121: Why don't move the new logic into AsyncMetaTableAccessor? > AsyncAdmin can not deal with non default meta replica > - > > Key: HBASE-22121 > URL: https://issues.apache.org/jira/browse/HBASE-22121 > Project: HBase > Issue Type: Bug > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.3.0, 2.1.5 > > Attachments: HBASE-22121.patch, HBASE-22121.patch > > > In AsyncAdmin we support passing both encodedRegionName and regionName as a > parameter so we have a getRegionInfo method to get the RegionInfo first. > In general we will scan the meta table to get the region info, but for meta > region itself, the problem is that, we only check for the first replica, so > for the non default replicas, we will still go to the meta region and then > get an UnknownRegionException. > We should find a way to deal with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22121) AsyncAdmin can not deal with non default meta replica
[
https://issues.apache.org/jira/browse/HBASE-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805278#comment-16805278
]
Hadoop QA commented on HBASE-22121:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 5m
16s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 4 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
34s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
42s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m
52s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
47s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
29s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
4s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
16s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
7s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m
40s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 4m
40s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
39s{color} | {color:green} hbase-client: The patch generated 0 new + 13
unchanged - 1 fixed = 13 total (was 14) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
22s{color} | {color:red} hbase-server: The patch generated 2 new + 10 unchanged
- 0 fixed = 12 total (was 10) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
32s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
11m 5s{color} | {color:green} Patch does not cause any errors with Hadoop
2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
1s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
47s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}251m 29s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
42s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}321m 11s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestAdmin1 |
| | hadoop.hbase.client.TestFromClientSideWithCoprocessor |
| | hadoop.hbase.client.TestFromClientSide |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:b002b0b |
| JIRA Issue | HBASE-22121 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12964184/HBASE-22121.patch |
| Optional Tests | dupname asflicense javac javadoc unit findbugs
shadedjars hadoopcheck hbaseanti checkstyle compile |
|
[jira] [Commented] (HBASE-22121) AsyncAdmin can not deal with non default meta replica
[ https://issues.apache.org/jira/browse/HBASE-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804919#comment-16804919 ] Duo Zhang commented on HBASE-22121: --- The error prone warning is still a bit unstable...Not sure why, maybe we should open an issue on the error prone project as we have already upgraded to the newest version... > AsyncAdmin can not deal with non default meta replica > - > > Key: HBASE-22121 > URL: https://issues.apache.org/jira/browse/HBASE-22121 > Project: HBase > Issue Type: Bug > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.3.0, 2.1.5 > > Attachments: HBASE-22121.patch, HBASE-22121.patch > > > In AsyncAdmin we support passing both encodedRegionName and regionName as a > parameter so we have a getRegionInfo method to get the RegionInfo first. > In general we will scan the meta table to get the region info, but for meta > region itself, the problem is that, we only check for the first replica, so > for the non default replicas, we will still go to the meta region and then > get an UnknownRegionException. > We should find a way to deal with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22121) AsyncAdmin can not deal with non default meta replica
[
https://issues.apache.org/jira/browse/HBASE-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804764#comment-16804764
]
Hadoop QA commented on HBASE-22121:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 4m
33s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 4 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
28s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
8s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m
29s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
19s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
21s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
52s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
15s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
56s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m
30s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 2m 39s{color}
| {color:red} hbase-server generated 1 new + 193 unchanged - 1 fixed = 194
total (was 194) {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
30s{color} | {color:green} hbase-client: The patch generated 0 new + 13
unchanged - 1 fixed = 13 total (was 14) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
5s{color} | {color:red} hbase-server: The patch generated 2 new + 10 unchanged
- 0 fixed = 12 total (was 10) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
16s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
8m 13s{color} | {color:green} Patch does not cause any errors with Hadoop 2.7.4
or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
51s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
22s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}265m 39s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
53s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}319m 38s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestFromClientSideWithCoprocessor |
| | hadoop.hbase.TestSplitMerge |
| | hadoop.hbase.client.TestSnapshotTemporaryDirectoryWithRegionReplicas |
| | hadoop.hbase.client.TestSnapshotDFSTemporaryDirectory |
| | hadoop.hbase.master.TestSplitWALManager |
| | hadoop.hbase.master.TestAssignmentManagerMetrics |
| | hadoop.hbase.client.TestAsyncTableBatch |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce
[jira] [Commented] (HBASE-22121) AsyncAdmin can not deal with non default meta replica
[ https://issues.apache.org/jira/browse/HBASE-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804569#comment-16804569 ] Duo Zhang commented on HBASE-22121: --- [~zghaobac] FYI. > AsyncAdmin can not deal with non default meta replica > - > > Key: HBASE-22121 > URL: https://issues.apache.org/jira/browse/HBASE-22121 > Project: HBase > Issue Type: Bug > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.3.0, 2.1.5 > > Attachments: HBASE-22121.patch > > > In AsyncAdmin we support passing both encodedRegionName and regionName as a > parameter so we have a getRegionInfo method to get the RegionInfo first. > In general we will scan the meta table to get the region info, but for meta > region itself, the problem is that, we only check for the first replica, so > for the non default replicas, we will still go to the meta region and then > get an UnknownRegionException. > We should find a way to deal with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
