[jira] [Commented] (HBASE-10147) Canary additions
[ https://issues.apache.org/jira/browse/HBASE-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072299#comment-16072299 ] Gustavo Anatoly commented on HBASE-10147: - Hi, [~stack] Thanks for comment :) I'm going to rebase and prepare a new patch. > Canary additions > > > Key: HBASE-10147 > URL: https://issues.apache.org/jira/browse/HBASE-10147 > Project: HBase > Issue Type: Improvement >Reporter: stack >Assignee: Gustavo Anatoly > Attachments: HBASE-10147.patch, HBASE-10147.patch, HBASE-10147.patch, > HBASE-10147.patch, HBASE-10147-v2.patch, HBASE-10147-v3.patch, > HBASE-10147-v4.patch, HBASE-10147-v5.patch > > > I've been using the canary to quickly identify the dodgy machine in my > cluster. It is useful for this. What would make it better would be: > + Rather than saying how long it took to get a region after you have gotten > the region, it'd be sweet to log BEFORE you went to get the region the > regionname and the server it is on. I ask for this because as is, I have to > wait for the canary to timeout which can be a while. > + Second ask is that when I pass the -t, that when it fails, it says what it > failed against -- what region and hopefully what server location (might be > hard). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13229) Specify bash for local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly updated HBASE-13229:
Attachment: HBASE-13229-v2.patch
Specify bash for local-regionservers.sh and local-master-backup.sh
--
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-12339-v1.patch, HBASE-13229-v2.patch,
HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Specify bash for local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14364461#comment-14364461
]
Gustavo Anatoly commented on HBASE-13229:
-
Thanks for review the patch.
Specify bash for local-regionservers.sh and local-master-backup.sh
--
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-12339-v1.patch, HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13229) Specify bash for local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly updated HBASE-13229:
Attachment: HBASE-12339-v1.patch
Specify bash for local-regionservers.sh and local-master-backup.sh
--
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-12339-v1.patch, HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13229) Specify bash for local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly updated HBASE-13229:
Status: Patch Available (was: Open)
Specify bash for local-regionservers.sh and local-master-backup.sh
--
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 1.0.0, 0.98.0, 0.94.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-12339-v1.patch, HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360752#comment-14360752
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360777#comment-14360777
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360763#comment-14360763
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360779#comment-14360779
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360754#comment-14360754
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360762#comment-14360762
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360760#comment-14360760
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360764#comment-14360764
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360774#comment-14360774
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360771#comment-14360771
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360769#comment-14360769
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360775#comment-14360775
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360765#comment-14360765
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360767#comment-14360767
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360773#comment-14360773
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360768#comment-14360768
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360770#comment-14360770
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360756#comment-14360756
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360766#comment-14360766
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360758#comment-14360758
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Specify bash for local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360844#comment-14360844
]
Gustavo Anatoly commented on HBASE-13229:
-
Thanks, [~busbey]
Yes, I can to do it.
Specify bash for local-regionservers.sh and local-master-backup.sh
--
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360778#comment-14360778
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360772#comment-14360772
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360776#comment-14360776
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360759#comment-14360759
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360753#comment-14360753
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360757#comment-14360757
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360755#comment-14360755
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360761#comment-14360761
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~apurtell]
{quote} ... but it's not a bug technically {quote}
I agree, thinking a little better this issue could be an improvement based on
compatibility.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360748#comment-14360748
]
Gustavo Anatoly commented on HBASE-13229:
-
Hi, [~busbey]
I don't have specific need and I'm working with bash on Ubuntu.
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360790#comment-14360790
]
Gustavo Anatoly commented on HBASE-13229:
-
[~purtell]
Could you please remove duplicate commentaries?
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.94.0, 0.98.0, 1.0.0
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Labels: beginner
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
Gustavo Anatoly created HBASE-13229:
---
Summary: Bug compatibility validation to start
local-regionservers.sh and local-master-backup.sh
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2 3
4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13229) Bug compatibility validation to start local-regionservers.sh and local-master-backup.sh
[
https://issues.apache.org/jira/browse/HBASE-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly updated HBASE-13229:
Attachment: HBASE-13229.patch
Bug compatibility validation to start local-regionservers.sh and
local-master-backup.sh
---
Key: HBASE-13229
URL: https://issues.apache.org/jira/browse/HBASE-13229
Project: HBase
Issue Type: Bug
Components: scripts
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Attachments: HBASE-13229.patch
Running the following line, using /bin/sh:
$ bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/ start 1 2
3 4 5
Produces the output below:
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
bin/local-regionservers.sh: 55: bin/local-regionservers.sh: [[: not found
Invalid argument
Considering:
{code}
if [[ $i =~ ^[0-9]+$ ]]; then
run_master $cmd $i
else
echo Invalid argument
fi
{code}
The reasons is that the regex operator =~ doesn't have compatibility with
/bin/sh but works running /bin/bash
$ bash -x bin/local-regionservers.sh --config ~/hbase-dev/hbase-conf/conf/
start 1 2 3 4 5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12743) [ITBLL] Master fails rejoining cluster stuck splitting logs; Distributed log replay=true
[
https://issues.apache.org/jira/browse/HBASE-12743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14357969#comment-14357969
]
Gustavo Anatoly commented on HBASE-12743:
-
Hi, [~stack]
Sorry for long delay to reply and thanks for share how to reproduce the fail.
Well, I wasn't able to reproduce the exactly exception, but I'm hunting the
root causes, using ITBLL.
About my first idea, I was thinking to use mock to reproduce the error but I
going to follow with ITBLL.
[ITBLL] Master fails rejoining cluster stuck splitting logs; Distributed log
replay=true
Key: HBASE-12743
URL: https://issues.apache.org/jira/browse/HBASE-12743
Project: HBase
Issue Type: Bug
Reporter: stack
Fix For: 2.0.0, 1.0.1, 1.1.0
Attachments: 12743.hack.txt
Master is stuck for two days trying to rejoin cluster after monkey killed and
restarted it.
After retrying to get namespace 350 times, Master goes down:
{code}
2014-12-20 18:43:54,285 INFO [c2020:16020.activeMasterManager]
client.RpcRetryingCaller: Call exception, tries=349, retries=350,
started=6885331 ms ago, cancelled=false, msg=row 'default' on table
'hbase:namespace' at
region=hbase:namespace,,1417551886199.ecdcd0172cd3e32d291bc282771895da.,
hostname=c2023.halxg.cloudera.com,16020,1418988286696, seqNum=600190
2014-12-20 18:43:54,303 WARN [c2020:16020.activeMasterManager]
master.TableNamespaceManager: Caught exception in initializing namespace
table manager
org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after
attempts=350, exceptions:
Sat Dec 20 16:49:08 PST 2014,
RpcRetryingCaller{globalStartTime=1419122948954, pause=100, retries=350},
org.apache.hadoop.hbase.NotServingRegionException:
org.apache.hadoop.hbase.NotServingRegionException: Region
hbase:namespace,,1417551886199.ecdcd0172cd3e32d291bc282771895da. is not
online on c2023.halxg.cloudera.com,16020,1418988286696
at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2722)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.getRegion(RSRpcServices.java:851)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:1695)
at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30434)
{code}
Seems like 2014-12-20 16:49:03,665 INFO [RS_LOG_REPLAY_OPS-c2021:16020-0]
wal.WALSplitter: DistributedLogReplay = true
Seems easy enough to reproduce.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12743) [ITBLL] Master fails rejoining cluster stuck splitting logs; Distributed log replay=true
[
https://issues.apache.org/jira/browse/HBASE-12743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14280318#comment-14280318
]
Gustavo Anatoly commented on HBASE-12743:
-
I'm trying to reproduce it from
{{TableNamespaceManager.isTableAvailableAndInitialized()}}. Suggestions?
[ITBLL] Master fails rejoining cluster stuck splitting logs; Distributed log
replay=true
Key: HBASE-12743
URL: https://issues.apache.org/jira/browse/HBASE-12743
Project: HBase
Issue Type: Bug
Reporter: stack
Fix For: 1.0.0, 2.0.0, 1.1.0
Master is stuck for two days trying to rejoin cluster after monkey killed and
restarted it.
After retrying to get namespace 350 times, Master goes down:
{code}
2014-12-20 18:43:54,285 INFO [c2020:16020.activeMasterManager]
client.RpcRetryingCaller: Call exception, tries=349, retries=350,
started=6885331 ms ago, cancelled=false, msg=row 'default' on table
'hbase:namespace' at
region=hbase:namespace,,1417551886199.ecdcd0172cd3e32d291bc282771895da.,
hostname=c2023.halxg.cloudera.com,16020,1418988286696, seqNum=600190
2014-12-20 18:43:54,303 WARN [c2020:16020.activeMasterManager]
master.TableNamespaceManager: Caught exception in initializing namespace
table manager
org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after
attempts=350, exceptions:
Sat Dec 20 16:49:08 PST 2014,
RpcRetryingCaller{globalStartTime=1419122948954, pause=100, retries=350},
org.apache.hadoop.hbase.NotServingRegionException:
org.apache.hadoop.hbase.NotServingRegionException: Region
hbase:namespace,,1417551886199.ecdcd0172cd3e32d291bc282771895da. is not
online on c2023.halxg.cloudera.com,16020,1418988286696
at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2722)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.getRegion(RSRpcServices.java:851)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:1695)
at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30434)
{code}
Seems like 2014-12-20 16:49:03,665 INFO [RS_LOG_REPLAY_OPS-c2021:16020-0]
wal.WALSplitter: DistributedLogReplay = true
Seems easy enough to reproduce.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Work started] (HBASE-11743) Add unit test for the fix that sorts custom value of BUCKET_CACHE_BUCKETS_KEY
[ https://issues.apache.org/jira/browse/HBASE-11743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-11743 started by Gustavo Anatoly. Add unit test for the fix that sorts custom value of BUCKET_CACHE_BUCKETS_KEY - Key: HBASE-11743 URL: https://issues.apache.org/jira/browse/HBASE-11743 Project: HBase Issue Type: Test Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Minor HBASE-11550 sorts the custom value of BUCKET_CACHE_BUCKETS_KEY such that there is no wastage in bucket allocation. This JIRA is to add unit test for the fix so that there is no regression in the future. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Work stopped] (HBASE-11743) Add unit test for the fix that sorts custom value of BUCKET_CACHE_BUCKETS_KEY
[ https://issues.apache.org/jira/browse/HBASE-11743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-11743 stopped by Gustavo Anatoly. Add unit test for the fix that sorts custom value of BUCKET_CACHE_BUCKETS_KEY - Key: HBASE-11743 URL: https://issues.apache.org/jira/browse/HBASE-11743 Project: HBase Issue Type: Test Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Minor HBASE-11550 sorts the custom value of BUCKET_CACHE_BUCKETS_KEY such that there is no wastage in bucket allocation. This JIRA is to add unit test for the fix so that there is no regression in the future. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HBASE-11743) Add unit test for the fix that sorts custom value of BUCKET_CACHE_BUCKETS_KEY
[ https://issues.apache.org/jira/browse/HBASE-11743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly reassigned HBASE-11743: --- Assignee: Gustavo Anatoly Add unit test for the fix that sorts custom value of BUCKET_CACHE_BUCKETS_KEY - Key: HBASE-11743 URL: https://issues.apache.org/jira/browse/HBASE-11743 Project: HBase Issue Type: Test Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Minor HBASE-11550 sorts the custom value of BUCKET_CACHE_BUCKETS_KEY such that there is no wastage in bucket allocation. This JIRA is to add unit test for the fix so that there is no regression in the future. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-11550) Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated
[ https://issues.apache.org/jira/browse/HBASE-11550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-11550: Attachment: (was: HBASE-11550-v2.patch) Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated Key: HBASE-11550 URL: https://issues.apache.org/jira/browse/HBASE-11550 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Attachments: HBASE-11550-v1.patch, HBASE-11550.patch User can pass bucket sizes through hbase.bucketcache.bucket.sizes config entry. The sizes are supposed to be in increasing order. Validation should be added in CacheConfig#getL2(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-11550) Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated
[ https://issues.apache.org/jira/browse/HBASE-11550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-11550: Attachment: HBASE-11550-v2.patch Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated Key: HBASE-11550 URL: https://issues.apache.org/jira/browse/HBASE-11550 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Attachments: HBASE-11550-v1.patch, HBASE-11550-v2.patch, HBASE-11550.patch User can pass bucket sizes through hbase.bucketcache.bucket.sizes config entry. The sizes are supposed to be in increasing order. Validation should be added in CacheConfig#getL2(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-11550) Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated
[ https://issues.apache.org/jira/browse/HBASE-11550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-11550: Attachment: HBASE-11550-v3.patch Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated Key: HBASE-11550 URL: https://issues.apache.org/jira/browse/HBASE-11550 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Attachments: HBASE-11550-v1.patch, HBASE-11550-v2.patch, HBASE-11550-v3.patch, HBASE-11550.patch User can pass bucket sizes through hbase.bucketcache.bucket.sizes config entry. The sizes are supposed to be in increasing order. Validation should be added in CacheConfig#getL2(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HBASE-11550) Custom value for BUCKET_CACHE_BUCKETS_KEY should be sorted
[ https://issues.apache.org/jira/browse/HBASE-11550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14095750#comment-14095750 ] Gustavo Anatoly commented on HBASE-11550: - Hello Nick, I will convert again to int[]. Thanks. Custom value for BUCKET_CACHE_BUCKETS_KEY should be sorted -- Key: HBASE-11550 URL: https://issues.apache.org/jira/browse/HBASE-11550 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Fix For: 0.99.0, 2.0.0, 0.98.6 Attachments: HBASE-11550-v1.patch, HBASE-11550-v2.patch, HBASE-11550-v3.patch, HBASE-11550.patch User can pass bucket sizes through hbase.bucketcache.bucket.sizes config entry. The sizes are supposed to be in increasing order. Validation should be added in CacheConfig#getL2(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-11550) Custom value for BUCKET_CACHE_BUCKETS_KEY should be sorted
[ https://issues.apache.org/jira/browse/HBASE-11550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-11550: Attachment: HBASE-11550-v4.patch Gentlemen, New patch (v4) has been attached. Thanks. Custom value for BUCKET_CACHE_BUCKETS_KEY should be sorted -- Key: HBASE-11550 URL: https://issues.apache.org/jira/browse/HBASE-11550 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Fix For: 0.99.0, 2.0.0, 0.98.6 Attachments: HBASE-11550-v1.patch, HBASE-11550-v2.patch, HBASE-11550-v3.patch, HBASE-11550-v4.patch, HBASE-11550.patch User can pass bucket sizes through hbase.bucketcache.bucket.sizes config entry. The sizes are supposed to be in increasing order. Validation should be added in CacheConfig#getL2(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HBASE-11550) Custom value for BUCKET_CACHE_BUCKETS_KEY should be sorted
[ https://issues.apache.org/jira/browse/HBASE-11550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14096479#comment-14096479 ] Gustavo Anatoly commented on HBASE-11550: - I don't have objections [~ndimiduk]. Thanks everyone. I get happy to help a little bit. :) Custom value for BUCKET_CACHE_BUCKETS_KEY should be sorted -- Key: HBASE-11550 URL: https://issues.apache.org/jira/browse/HBASE-11550 Project: HBase Issue Type: Bug Affects Versions: 0.99.0, 0.98.4, 0.98.5 Reporter: Ted Yu Assignee: Gustavo Anatoly Fix For: 0.99.0, 2.0.0, 0.98.6 Attachments: HBASE-11550-v1.patch, HBASE-11550-v2.patch, HBASE-11550-v3.patch, HBASE-11550-v4.patch, HBASE-11550.patch User can pass bucket sizes through hbase.bucketcache.bucket.sizes config entry. The sizes are supposed to be in increasing order. Validation should be added in CacheConfig#getL2(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-11550) Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated
[ https://issues.apache.org/jira/browse/HBASE-11550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-11550: Attachment: HBASE-11550-v2.patch Gentlemen, The new patch was attached with sorted array instead reverse order to that finish this issue. So about the wastage tests I will need more time to complete it. Thanks for the patience. Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated Key: HBASE-11550 URL: https://issues.apache.org/jira/browse/HBASE-11550 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Attachments: HBASE-11550-v1.patch, HBASE-11550-v2.patch, HBASE-11550.patch User can pass bucket sizes through hbase.bucketcache.bucket.sizes config entry. The sizes are supposed to be in increasing order. Validation should be added in CacheConfig#getL2(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HBASE-11550) Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated
[ https://issues.apache.org/jira/browse/HBASE-11550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086753#comment-14086753 ] Gustavo Anatoly commented on HBASE-11550: - Hello, [~stack] Sorry for delay to delivery, I was a little bit busy lately. But I'm working the patch at this moment, so these days I'll finish the task. Thank you for your attention. Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated Key: HBASE-11550 URL: https://issues.apache.org/jira/browse/HBASE-11550 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Attachments: HBASE-11550-v1.patch, HBASE-11550.patch User can pass bucket sizes through hbase.bucketcache.bucket.sizes config entry. The sizes are supposed to be in increasing order. Validation should be added in CacheConfig#getL2(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HBASE-11550) Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated
[ https://issues.apache.org/jira/browse/HBASE-11550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075801#comment-14075801 ] Gustavo Anatoly commented on HBASE-11550: - Hello, [~stack]. I will do the confrontation for both ways to after and before of my patch. Thanks. Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated Key: HBASE-11550 URL: https://issues.apache.org/jira/browse/HBASE-11550 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Attachments: HBASE-11550-v1.patch, HBASE-11550.patch User can pass bucket sizes through hbase.bucketcache.bucket.sizes config entry. The sizes are supposed to be in increasing order. Validation should be added in CacheConfig#getL2(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HBASE-11550) Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated
[
https://issues.apache.org/jira/browse/HBASE-11550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075530#comment-14075530
]
Gustavo Anatoly commented on HBASE-11550:
-
Gentlemen, thanks for review.
Hello, [~ndimiduk] about your question:
bq. Why switch to List everywhere?
We have the follow code:
{code}
public BucketSizeInfo roundUpToBucketSizeInfo(int blockSize) {
for (int i = 0; i bucketSizes.size(); ++i)
if (blockSize = bucketSizes.get(i))
return bucketSizeInfos[i];
return null;
}
{code}
Thus, if we have a reversed bucketSizes it will search in the largest
bucketSizes( i ) on the top of array first. This sounds obvious, but the
intention is increase the probability to find the bucketSizeInfo in the largest
bucketSizes first. It's a pretty simple optimization.
But how you suggest and [~stack] I can add some tests to verify the sort
problem and other test to wastage.
Hello, [~tedyu] thanks for the comment, I will write some test to verify the
condition mentioned by you.
Thanks, guys.
Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated
Key: HBASE-11550
URL: https://issues.apache.org/jira/browse/HBASE-11550
Project: HBase
Issue Type: Task
Reporter: Ted Yu
Assignee: Gustavo Anatoly
Priority: Trivial
Attachments: HBASE-11550-v1.patch, HBASE-11550.patch
User can pass bucket sizes through hbase.bucketcache.bucket.sizes config
entry.
The sizes are supposed to be in increasing order. Validation should be added
in CacheConfig#getL2().
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-11550) Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated
[ https://issues.apache.org/jira/browse/HBASE-11550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-11550: Attachment: HBASE-11550-v1.patch Hi, [~ndimiduk]. Could you please review the new patch? Thanks Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated Key: HBASE-11550 URL: https://issues.apache.org/jira/browse/HBASE-11550 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Trivial Attachments: HBASE-11550-v1.patch, HBASE-11550.patch User can pass bucket sizes through hbase.bucketcache.bucket.sizes config entry. The sizes are supposed to be in increasing order. Validation should be added in CacheConfig#getL2(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-11550) Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated
[ https://issues.apache.org/jira/browse/HBASE-11550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-11550: Status: Patch Available (was: Open) Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated Key: HBASE-11550 URL: https://issues.apache.org/jira/browse/HBASE-11550 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Trivial Attachments: HBASE-11550-v1.patch, HBASE-11550.patch User can pass bucket sizes through hbase.bucketcache.bucket.sizes config entry. The sizes are supposed to be in increasing order. Validation should be added in CacheConfig#getL2(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-11550) Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated
[ https://issues.apache.org/jira/browse/HBASE-11550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-11550: Attachment: HBASE-11550.patch Gentlemen watchers, Who could please review the patch? Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated Key: HBASE-11550 URL: https://issues.apache.org/jira/browse/HBASE-11550 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Trivial Attachments: HBASE-11550.patch User can pass bucket sizes through hbase.bucketcache.bucket.sizes config entry. The sizes are supposed to be in increasing order. Validation should be added in CacheConfig#getL2(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HBASE-11550) Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated
[ https://issues.apache.org/jira/browse/HBASE-11550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14069710#comment-14069710 ] Gustavo Anatoly commented on HBASE-11550: - Thanks [~ndimiduk], for your attention. I will prepare a new draft patch, to resubmit. I agree, it makes no sense drop the variable, it's merely punctual. I didn't saw this possibility to refactor, transferring the responsability to BucketCache.retrieveFromFile :) Thanks again. Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated Key: HBASE-11550 URL: https://issues.apache.org/jira/browse/HBASE-11550 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Trivial Attachments: HBASE-11550.patch User can pass bucket sizes through hbase.bucketcache.bucket.sizes config entry. The sizes are supposed to be in increasing order. Validation should be added in CacheConfig#getL2(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HBASE-11163) Support providing a Scan instance in mapred.TableMapReduceUtil
[ https://issues.apache.org/jira/browse/HBASE-11163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly reassigned HBASE-11163: --- Assignee: Gustavo Anatoly Support providing a Scan instance in mapred.TableMapReduceUtil -- Key: HBASE-11163 URL: https://issues.apache.org/jira/browse/HBASE-11163 Project: HBase Issue Type: Improvement Components: mapreduce Reporter: Nick Dimiduk Assignee: Gustavo Anatoly Our mapred implementation is pretty meager compared to the code in mapreduce. Notably, it does not support a user-provided Scan instance for mapreduce jobs run over hbase tables. The only thing we offer is column family filtering. For applications to support predicate pushdown and enjoy efficient HBase access, either they transition their entire codebase over to mapreduce, or we offer this functionality. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HBASE-11550) Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated
[ https://issues.apache.org/jira/browse/HBASE-11550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly reassigned HBASE-11550: --- Assignee: Gustavo Anatoly Bucket sizes passed through BUCKET_CACHE_BUCKETS_KEY should be validated Key: HBASE-11550 URL: https://issues.apache.org/jira/browse/HBASE-11550 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Minor User can pass bucket sizes through hbase.bucketcache.bucket.sizes config entry. The sizes are supposed to be in increasing order. Validation should be added in CacheConfig#getL2(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-11507) Enhance test-patch.sh to check for direct calls to HBaseZeroCopyByteString.wrap()
[ https://issues.apache.org/jira/browse/HBASE-11507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-11507: Attachment: HBASE-11507-javadoc.patch Enhance test-patch.sh to check for direct calls to HBaseZeroCopyByteString.wrap() - Key: HBASE-11507 URL: https://issues.apache.org/jira/browse/HBASE-11507 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Trivial Attachments: HBASE-11507-javadoc.patch, HBASE-11507.patch HBaseZeroCopyByteString.wrap() should not be called directly. ByteStringer.wrap() should be called instead. This task adds check for direct calls to HBaseZeroCopyByteString.wrap() to test-patch.sh. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-11507) Enhance test-patch.sh to check for direct calls to HBaseZeroCopyByteString.wrap()
[ https://issues.apache.org/jira/browse/HBASE-11507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-11507: Status: Patch Available (was: Open) Enhance test-patch.sh to check for direct calls to HBaseZeroCopyByteString.wrap() - Key: HBASE-11507 URL: https://issues.apache.org/jira/browse/HBASE-11507 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Attachments: HBASE-11507.patch HBaseZeroCopyByteString.wrap() should not be called directly. ByteStringer.wrap() should be called instead. This task adds check for direct calls to HBaseZeroCopyByteString.wrap() to test-patch.sh. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-11507) Enhance test-patch.sh to check for direct calls to HBaseZeroCopyByteString.wrap()
[ https://issues.apache.org/jira/browse/HBASE-11507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-11507: Attachment: HBASE-11507.patch Enhance test-patch.sh to check for direct calls to HBaseZeroCopyByteString.wrap() - Key: HBASE-11507 URL: https://issues.apache.org/jira/browse/HBASE-11507 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Attachments: HBASE-11507.patch HBaseZeroCopyByteString.wrap() should not be called directly. ByteStringer.wrap() should be called instead. This task adds check for direct calls to HBaseZeroCopyByteString.wrap() to test-patch.sh. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-11507) Enhance test-patch.sh to check for direct calls to HBaseZeroCopyByteString.wrap()
[ https://issues.apache.org/jira/browse/HBASE-11507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-11507: Attachment: (was: HBASE-11507.patch) Enhance test-patch.sh to check for direct calls to HBaseZeroCopyByteString.wrap() - Key: HBASE-11507 URL: https://issues.apache.org/jira/browse/HBASE-11507 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly HBaseZeroCopyByteString.wrap() should not be called directly. ByteStringer.wrap() should be called instead. This task adds check for direct calls to HBaseZeroCopyByteString.wrap() to test-patch.sh. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-11507) Enhance test-patch.sh to check for direct calls to HBaseZeroCopyByteString.wrap()
[ https://issues.apache.org/jira/browse/HBASE-11507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-11507: Attachment: HBASE-11507.patch Enhance test-patch.sh to check for direct calls to HBaseZeroCopyByteString.wrap() - Key: HBASE-11507 URL: https://issues.apache.org/jira/browse/HBASE-11507 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Trivial Attachments: HBASE-11507.patch HBaseZeroCopyByteString.wrap() should not be called directly. ByteStringer.wrap() should be called instead. This task adds check for direct calls to HBaseZeroCopyByteString.wrap() to test-patch.sh. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HBASE-11507) Enhance test-patch.sh to check for direct calls to HBaseZeroCopyByteString.wrap()
[ https://issues.apache.org/jira/browse/HBASE-11507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14060216#comment-14060216 ] Gustavo Anatoly commented on HBASE-11507: - Hi, [~stack]. I would like to work with some substance and import. Do you have some task? Thanks. Enhance test-patch.sh to check for direct calls to HBaseZeroCopyByteString.wrap() - Key: HBASE-11507 URL: https://issues.apache.org/jira/browse/HBASE-11507 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Trivial Attachments: HBASE-11507.patch HBaseZeroCopyByteString.wrap() should not be called directly. ByteStringer.wrap() should be called instead. This task adds check for direct calls to HBaseZeroCopyByteString.wrap() to test-patch.sh. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HBASE-11507) Enhance test-patch.sh to check for direct calls to HBaseZeroCopyByteString.wrap()
[ https://issues.apache.org/jira/browse/HBASE-11507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly reassigned HBASE-11507: --- Assignee: Gustavo Anatoly Enhance test-patch.sh to check for direct calls to HBaseZeroCopyByteString.wrap() - Key: HBASE-11507 URL: https://issues.apache.org/jira/browse/HBASE-11507 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly HBaseZeroCopyByteString.wrap() should not be called directly. ByteStringer.wrap() should be called instead. This task adds check for direct calls to HBaseZeroCopyByteString.wrap() to test-patch.sh. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HBASE-11107) Provide utility method equivalent to 0.92's Result.getBytes().getSize()
[
https://issues.apache.org/jira/browse/HBASE-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14030543#comment-14030543
]
Gustavo Anatoly commented on HBASE-11107:
-
Thank you, Ted.
Thank you, Chunhui
Provide utility method equivalent to 0.92's Result.getBytes().getSize()
---
Key: HBASE-11107
URL: https://issues.apache.org/jira/browse/HBASE-11107
Project: HBase
Issue Type: Task
Reporter: Ted Yu
Assignee: Gustavo Anatoly
Priority: Trivial
Fix For: 0.99.0
Attachments: HBASE-11107.patch
Currently user has to write code similar to the following for replacement of
Result.getBytes().getSize() :
{code}
+Cell[] cellValues = resultRow.rawCells();
+
+long size = 0L;
+if (null != cellValues) {
+ for (Cell cellValue : cellValues) {
+size += KeyValueUtil.ensureKeyValue(cellValue).heapSize();
+ }
+}
{code}
In ClientScanner, we have:
{code}
for (Cell kv : rs.rawCells()) {
// TODO make method in Cell or CellUtil
remainingResultSize -=
KeyValueUtil.ensureKeyValue(kv).heapSize();
}
{code}
A utility method should be provided which computes summation of Cell sizes in
a Result.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-11107) Provide utility method equivalent to 0.92's Result.getBytes().getSize()
[
https://issues.apache.org/jira/browse/HBASE-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly updated HBASE-11107:
Attachment: HBASE-11107.patch
Provide utility method equivalent to 0.92's Result.getBytes().getSize()
---
Key: HBASE-11107
URL: https://issues.apache.org/jira/browse/HBASE-11107
Project: HBase
Issue Type: Task
Reporter: Ted Yu
Assignee: Gustavo Anatoly
Priority: Trivial
Attachments: HBASE-11107.patch
Currently user has to write code similar to the following for replacement of
Result.getBytes().getSize() :
{code}
+Cell[] cellValues = resultRow.rawCells();
+
+long size = 0L;
+if (null != cellValues) {
+ for (Cell cellValue : cellValues) {
+size += KeyValueUtil.ensureKeyValue(cellValue).heapSize();
+ }
+}
{code}
In ClientScanner, we have:
{code}
for (Cell kv : rs.rawCells()) {
// TODO make method in Cell or CellUtil
remainingResultSize -=
KeyValueUtil.ensureKeyValue(kv).heapSize();
}
{code}
A utility method should be provided which computes summation of Cell sizes in
a Result.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-11107) Provide utility method equivalent to 0.92's Result.getBytes().getSize()
[
https://issues.apache.org/jira/browse/HBASE-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly updated HBASE-11107:
Status: Patch Available (was: In Progress)
Provide utility method equivalent to 0.92's Result.getBytes().getSize()
---
Key: HBASE-11107
URL: https://issues.apache.org/jira/browse/HBASE-11107
Project: HBase
Issue Type: Task
Reporter: Ted Yu
Assignee: Gustavo Anatoly
Priority: Trivial
Attachments: HBASE-11107.patch
Currently user has to write code similar to the following for replacement of
Result.getBytes().getSize() :
{code}
+Cell[] cellValues = resultRow.rawCells();
+
+long size = 0L;
+if (null != cellValues) {
+ for (Cell cellValue : cellValues) {
+size += KeyValueUtil.ensureKeyValue(cellValue).heapSize();
+ }
+}
{code}
In ClientScanner, we have:
{code}
for (Cell kv : rs.rawCells()) {
// TODO make method in Cell or CellUtil
remainingResultSize -=
KeyValueUtil.ensureKeyValue(kv).heapSize();
}
{code}
A utility method should be provided which computes summation of Cell sizes in
a Result.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Work started] (HBASE-11107) Provide utility method equivalent to 0.92's Result.getBytes().getSize()
[
https://issues.apache.org/jira/browse/HBASE-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HBASE-11107 started by Gustavo Anatoly.
Provide utility method equivalent to 0.92's Result.getBytes().getSize()
---
Key: HBASE-11107
URL: https://issues.apache.org/jira/browse/HBASE-11107
Project: HBase
Issue Type: Task
Reporter: Ted Yu
Assignee: Gustavo Anatoly
Priority: Trivial
Currently user has to write code similar to the following for replacement of
Result.getBytes().getSize() :
{code}
+Cell[] cellValues = resultRow.rawCells();
+
+long size = 0L;
+if (null != cellValues) {
+ for (Cell cellValue : cellValues) {
+size += KeyValueUtil.ensureKeyValue(cellValue).heapSize();
+ }
+}
{code}
In ClientScanner, we have:
{code}
for (Cell kv : rs.rawCells()) {
// TODO make method in Cell or CellUtil
remainingResultSize -=
KeyValueUtil.ensureKeyValue(kv).heapSize();
}
{code}
A utility method should be provided which computes summation of Cell sizes in
a Result.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-10596) Remove deprecated Filter#getNextKeyHint(KeyValue) method
[ https://issues.apache.org/jira/browse/HBASE-10596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-10596: Status: In Progress (was: Patch Available) Remove deprecated Filter#getNextKeyHint(KeyValue) method Key: HBASE-10596 URL: https://issues.apache.org/jira/browse/HBASE-10596 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Trivial Attachments: HBASE-10596-v1.patch, HBASE-10596.patch Filter#getNextKeyHint(KeyValue) is deprecated. Filter#getNextCellHint(Cell) should be used instead. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Work stopped] (HBASE-10596) Remove deprecated Filter#getNextKeyHint(KeyValue) method
[ https://issues.apache.org/jira/browse/HBASE-10596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-10596 stopped by Gustavo Anatoly. Remove deprecated Filter#getNextKeyHint(KeyValue) method Key: HBASE-10596 URL: https://issues.apache.org/jira/browse/HBASE-10596 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Trivial Attachments: HBASE-10596-v1.patch, HBASE-10596.patch Filter#getNextKeyHint(KeyValue) is deprecated. Filter#getNextCellHint(Cell) should be used instead. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HBASE-11107) Provide utility method equivalent to 0.92's Result.getBytes().getSize()
[
https://issues.apache.org/jira/browse/HBASE-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020851#comment-14020851
]
Gustavo Anatoly commented on HBASE-11107:
-
Hi, [~rekhajoshm].
I will assign this task for me :)
Thanks.
Provide utility method equivalent to 0.92's Result.getBytes().getSize()
---
Key: HBASE-11107
URL: https://issues.apache.org/jira/browse/HBASE-11107
Project: HBase
Issue Type: Task
Reporter: Ted Yu
Assignee: Rekha Joshi
Priority: Trivial
Currently user has to write code similar to the following for replacement of
Result.getBytes().getSize() :
{code}
+Cell[] cellValues = resultRow.rawCells();
+
+long size = 0L;
+if (null != cellValues) {
+ for (Cell cellValue : cellValues) {
+size += KeyValueUtil.ensureKeyValue(cellValue).heapSize();
+ }
+}
{code}
In ClientScanner, we have:
{code}
for (Cell kv : rs.rawCells()) {
// TODO make method in Cell or CellUtil
remainingResultSize -=
KeyValueUtil.ensureKeyValue(kv).heapSize();
}
{code}
A utility method should be provided which computes summation of Cell sizes in
a Result.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (HBASE-11107) Provide utility method equivalent to 0.92's Result.getBytes().getSize()
[
https://issues.apache.org/jira/browse/HBASE-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly reassigned HBASE-11107:
---
Assignee: Gustavo Anatoly (was: Rekha Joshi)
Provide utility method equivalent to 0.92's Result.getBytes().getSize()
---
Key: HBASE-11107
URL: https://issues.apache.org/jira/browse/HBASE-11107
Project: HBase
Issue Type: Task
Reporter: Ted Yu
Assignee: Gustavo Anatoly
Priority: Trivial
Currently user has to write code similar to the following for replacement of
Result.getBytes().getSize() :
{code}
+Cell[] cellValues = resultRow.rawCells();
+
+long size = 0L;
+if (null != cellValues) {
+ for (Cell cellValue : cellValues) {
+size += KeyValueUtil.ensureKeyValue(cellValue).heapSize();
+ }
+}
{code}
In ClientScanner, we have:
{code}
for (Cell kv : rs.rawCells()) {
// TODO make method in Cell or CellUtil
remainingResultSize -=
KeyValueUtil.ensureKeyValue(kv).heapSize();
}
{code}
A utility method should be provided which computes summation of Cell sizes in
a Result.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HBASE-10596) Remove deprecated Filter#getNextKeyHint(KeyValue) method
[ https://issues.apache.org/jira/browse/HBASE-10596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012331#comment-14012331 ] Gustavo Anatoly commented on HBASE-10596: - Thanks again, Anoop. I'll fix this. Remove deprecated Filter#getNextKeyHint(KeyValue) method Key: HBASE-10596 URL: https://issues.apache.org/jira/browse/HBASE-10596 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Trivial Attachments: HBASE-10596-v1.patch, HBASE-10596.patch Filter#getNextKeyHint(KeyValue) is deprecated. Filter#getNextCellHint(Cell) should be used instead. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HBASE-10596) Remove deprecated Filter#getNextKeyHint(KeyValue) method
[ https://issues.apache.org/jira/browse/HBASE-10596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14009628#comment-14009628 ] Gustavo Anatoly commented on HBASE-10596: - Thanks for review the patch. I will fix it. Remove deprecated Filter#getNextKeyHint(KeyValue) method Key: HBASE-10596 URL: https://issues.apache.org/jira/browse/HBASE-10596 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Trivial Attachments: HBASE-10596.patch Filter#getNextKeyHint(KeyValue) is deprecated. Filter#getNextCellHint(Cell) should be used instead. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-10596) Remove deprecated Filter#getNextKeyHint(KeyValue) method
[ https://issues.apache.org/jira/browse/HBASE-10596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-10596: Attachment: HBASE-10596-v1.patch Remove deprecated Filter#getNextKeyHint(KeyValue) method Key: HBASE-10596 URL: https://issues.apache.org/jira/browse/HBASE-10596 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Trivial Attachments: HBASE-10596-v1.patch, HBASE-10596.patch Filter#getNextKeyHint(KeyValue) is deprecated. Filter#getNextCellHint(Cell) should be used instead. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-10596) Remove deprecated Filter#getNextKeyHint(KeyValue) method
[ https://issues.apache.org/jira/browse/HBASE-10596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-10596: Status: Patch Available (was: Open) Remove deprecated Filter#getNextKeyHint(KeyValue) method Key: HBASE-10596 URL: https://issues.apache.org/jira/browse/HBASE-10596 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Trivial Attachments: HBASE-10596.patch Filter#getNextKeyHint(KeyValue) is deprecated. Filter#getNextCellHint(Cell) should be used instead. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-10596) Remove deprecated Filter#getNextKeyHint(KeyValue) method
[ https://issues.apache.org/jira/browse/HBASE-10596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-10596: Attachment: HBASE-10596.patch Remove deprecated Filter#getNextKeyHint(KeyValue) method Key: HBASE-10596 URL: https://issues.apache.org/jira/browse/HBASE-10596 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Trivial Attachments: HBASE-10596.patch Filter#getNextKeyHint(KeyValue) is deprecated. Filter#getNextCellHint(Cell) should be used instead. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HBASE-10596) Remove deprecated Filter#getNextKeyHint(KeyValue) method
[ https://issues.apache.org/jira/browse/HBASE-10596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly reassigned HBASE-10596: --- Assignee: Gustavo Anatoly Remove deprecated Filter#getNextKeyHint(KeyValue) method Key: HBASE-10596 URL: https://issues.apache.org/jira/browse/HBASE-10596 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Priority: Minor Fix For: 0.99.0 Filter#getNextKeyHint(KeyValue) is deprecated. Filter#getNextCellHint(Cell) should be used instead. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-11225) Backport fix for HBASE-10417 'index is not incremented in PutSortReducer#reduce()'
[
https://issues.apache.org/jira/browse/HBASE-11225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly updated HBASE-11225:
Status: Patch Available (was: Open)
Backport fix for HBASE-10417 'index is not incremented in
PutSortReducer#reduce()'
--
Key: HBASE-11225
URL: https://issues.apache.org/jira/browse/HBASE-11225
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Gustavo Anatoly
Priority: Minor
Fix For: 0.94.20
Attachments: HBASE-11225.patch
The problem reported in HBASE-10417 exists in 0.94 code base.
{code}
for (KeyValue kv : map) {
context.write(row, kv);
if (index 0 index % 100 == 0)
context.setStatus(Wrote + index);
}
{code}
This JIRA backports the fix to 0.94.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-11225) Backport fix for HBASE-10417 'index is not incremented in PutSortReducer#reduce()'
[
https://issues.apache.org/jira/browse/HBASE-11225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly updated HBASE-11225:
Attachment: HBASE-11225.patch
Backport fix for HBASE-10417 'index is not incremented in
PutSortReducer#reduce()'
--
Key: HBASE-11225
URL: https://issues.apache.org/jira/browse/HBASE-11225
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Gustavo Anatoly
Priority: Minor
Fix For: 0.94.20
Attachments: HBASE-11225.patch
The problem reported in HBASE-10417 exists in 0.94 code base.
{code}
for (KeyValue kv : map) {
context.write(row, kv);
if (index 0 index % 100 == 0)
context.setStatus(Wrote + index);
}
{code}
This JIRA backports the fix to 0.94.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (HBASE-11235) Backport fix for HBASE-11212 - Fix increment index in KeyValueSortReducer
Gustavo Anatoly created HBASE-11235:
---
Summary: Backport fix for HBASE-11212 - Fix increment index in
KeyValueSortReducer
Key: HBASE-11235
URL: https://issues.apache.org/jira/browse/HBASE-11235
Project: HBase
Issue Type: Bug
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Fix For: 0.94.20
Fix increment index reported on to version 0.94:
[https://issues.apache.org/jira/browse/HBASE-11212]
{code}
int index = 0;
for (KeyValue kv: map) {
context.write(row, kv);
if (index 0 index % 100 == 0) context.setStatus(Wrote + index);
}
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-11235) Backport fix for HBASE-11212 - Fix increment index in KeyValueSortReducer
[
https://issues.apache.org/jira/browse/HBASE-11235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly updated HBASE-11235:
Description:
Fix increment index reported on :
[https://issues.apache.org/jira/browse/HBASE-11212]
{code}
int index = 0;
for (KeyValue kv: map) {
context.write(row, kv);
if (index 0 index % 100 == 0) context.setStatus(Wrote + index);
}
{code}
was:
Fix increment index reported on to version 0.94:
[https://issues.apache.org/jira/browse/HBASE-11212]
{code}
int index = 0;
for (KeyValue kv: map) {
context.write(row, kv);
if (index 0 index % 100 == 0) context.setStatus(Wrote + index);
}
{code}
Backport fix for HBASE-11212 - Fix increment index in KeyValueSortReducer
-
Key: HBASE-11235
URL: https://issues.apache.org/jira/browse/HBASE-11235
Project: HBase
Issue Type: Bug
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Fix For: 0.94.20
Fix increment index reported on :
[https://issues.apache.org/jira/browse/HBASE-11212]
{code}
int index = 0;
for (KeyValue kv: map) {
context.write(row, kv);
if (index 0 index % 100 == 0) context.setStatus(Wrote + index);
}
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-11235) Backport fix for HBASE-11212 - Fix increment index in KeyValueSortReducer
[
https://issues.apache.org/jira/browse/HBASE-11235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly updated HBASE-11235:
Attachment: HBASE-11235.patch
Backport fix for HBASE-11212 - Fix increment index in KeyValueSortReducer
-
Key: HBASE-11235
URL: https://issues.apache.org/jira/browse/HBASE-11235
Project: HBase
Issue Type: Bug
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Fix For: 0.94.20
Attachments: HBASE-11235.patch
Fix increment index reported on :
[https://issues.apache.org/jira/browse/HBASE-11212]
{code}
int index = 0;
for (KeyValue kv: map) {
context.write(row, kv);
if (index 0 index % 100 == 0) context.setStatus(Wrote + index);
}
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-11235) Backport fix for HBASE-11212 - Fix increment index in KeyValueSortReducer
[
https://issues.apache.org/jira/browse/HBASE-11235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly updated HBASE-11235:
Status: Patch Available (was: Open)
Backport fix for HBASE-11212 - Fix increment index in KeyValueSortReducer
-
Key: HBASE-11235
URL: https://issues.apache.org/jira/browse/HBASE-11235
Project: HBase
Issue Type: Bug
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Fix For: 0.94.20
Attachments: HBASE-11235.patch
Fix increment index reported on :
[https://issues.apache.org/jira/browse/HBASE-11212]
{code}
int index = 0;
for (KeyValue kv: map) {
context.write(row, kv);
if (index 0 index % 100 == 0) context.setStatus(Wrote + index);
}
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (HBASE-11225) Backport fix for HBASE-10417 'index is not incremented in PutSortReducer#reduce()'
[
https://issues.apache.org/jira/browse/HBASE-11225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly reassigned HBASE-11225:
---
Assignee: Gustavo Anatoly
Backport fix for HBASE-10417 'index is not incremented in
PutSortReducer#reduce()'
--
Key: HBASE-11225
URL: https://issues.apache.org/jira/browse/HBASE-11225
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Gustavo Anatoly
Priority: Minor
Fix For: 0.94.20
The problem reported in HBASE-10417 exists in 0.94 code base.
{code}
for (KeyValue kv : map) {
context.write(row, kv);
if (index 0 index % 100 == 0)
context.setStatus(Wrote + index);
}
{code}
This JIRA backports the fix to 0.94.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HBASE-11212) Fix increment index in KeyValueSortReducer
[
https://issues.apache.org/jira/browse/HBASE-11212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14005031#comment-14005031
]
Gustavo Anatoly commented on HBASE-11212:
-
Thanks.
Fix increment index in KeyValueSortReducer
--
Key: HBASE-11212
URL: https://issues.apache.org/jira/browse/HBASE-11212
Project: HBase
Issue Type: Bug
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Fix For: 0.99.0, 0.98.3
Attachments: HBASE-11212.patch
The index is never incremented inside the loop, therefore context.setStatus
also is never set.
{code}
int index = 0;
for (KeyValue kv: map) {
context.write(row, kv);
if (index 0 index % 100 == 0) context.setStatus(Wrote + index);
}
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-10417) index is not incremented in PutSortReducer#reduce()
[
https://issues.apache.org/jira/browse/HBASE-10417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly updated HBASE-10417:
Attachment: HBASE-10417.patch
index is not incremented in PutSortReducer#reduce()
---
Key: HBASE-10417
URL: https://issues.apache.org/jira/browse/HBASE-10417
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Gustavo Anatoly
Priority: Minor
Attachments: HBASE-10417.patch
Starting at line 76:
{code}
int index = 0;
for (KeyValue kv : map) {
context.write(row, kv);
if (index 0 index % 100 == 0)
context.setStatus(Wrote + index);
{code}
index is a variable inside while loop that is never incremented.
The condition index 0 cannot be true.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-10417) index is not incremented in PutSortReducer#reduce()
[
https://issues.apache.org/jira/browse/HBASE-10417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly updated HBASE-10417:
Status: Patch Available (was: Open)
index is not incremented in PutSortReducer#reduce()
---
Key: HBASE-10417
URL: https://issues.apache.org/jira/browse/HBASE-10417
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Gustavo Anatoly
Priority: Minor
Attachments: HBASE-10417.patch
Starting at line 76:
{code}
int index = 0;
for (KeyValue kv : map) {
context.write(row, kv);
if (index 0 index % 100 == 0)
context.setStatus(Wrote + index);
{code}
index is a variable inside while loop that is never incremented.
The condition index 0 cannot be true.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (HBASE-11212) Fix increment index in KeyValueSortReducer
Gustavo Anatoly created HBASE-11212:
---
Summary: Fix increment index in KeyValueSortReducer
Key: HBASE-11212
URL: https://issues.apache.org/jira/browse/HBASE-11212
Project: HBase
Issue Type: Bug
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Fix For: 0.99.0, 0.98.3
The index is never incremented inside the loop, therefore context.setStatus
also is never set.
{code}
int index = 0;
for (KeyValue kv: map) {
context.write(row, kv);
if (index 0 index % 100 == 0) context.setStatus(Wrote + index);
}
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HBASE-10417) index is not incremented in PutSortReducer#reduce()
[
https://issues.apache.org/jira/browse/HBASE-10417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14003909#comment-14003909
]
Gustavo Anatoly commented on HBASE-10417:
-
Thanks for review, Ted :)
index is not incremented in PutSortReducer#reduce()
---
Key: HBASE-10417
URL: https://issues.apache.org/jira/browse/HBASE-10417
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Gustavo Anatoly
Priority: Minor
Fix For: 0.99.0, 0.98.3
Attachments: HBASE-10417.patch
Starting at line 76:
{code}
int index = 0;
for (KeyValue kv : map) {
context.write(row, kv);
if (index 0 index % 100 == 0)
context.setStatus(Wrote + index);
{code}
index is a variable inside while loop that is never incremented.
The condition index 0 cannot be true.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-11212) Fix increment index in KeyValueSortReducer
[
https://issues.apache.org/jira/browse/HBASE-11212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly updated HBASE-11212:
Status: Patch Available (was: Open)
Fix increment index in KeyValueSortReducer
--
Key: HBASE-11212
URL: https://issues.apache.org/jira/browse/HBASE-11212
Project: HBase
Issue Type: Bug
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Fix For: 0.99.0, 0.98.3
Attachments: HBASE-11212.patch
The index is never incremented inside the loop, therefore context.setStatus
also is never set.
{code}
int index = 0;
for (KeyValue kv: map) {
context.write(row, kv);
if (index 0 index % 100 == 0) context.setStatus(Wrote + index);
}
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-11212) Fix increment index in KeyValueSortReducer
[
https://issues.apache.org/jira/browse/HBASE-11212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly updated HBASE-11212:
Attachment: HBASE-11212.patch
Fix increment index in KeyValueSortReducer
--
Key: HBASE-11212
URL: https://issues.apache.org/jira/browse/HBASE-11212
Project: HBase
Issue Type: Bug
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Fix For: 0.99.0, 0.98.3
Attachments: HBASE-11212.patch
The index is never incremented inside the loop, therefore context.setStatus
also is never set.
{code}
int index = 0;
for (KeyValue kv: map) {
context.write(row, kv);
if (index 0 index % 100 == 0) context.setStatus(Wrote + index);
}
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HBASE-11212) Fix increment index in KeyValueSortReducer
[
https://issues.apache.org/jira/browse/HBASE-11212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14003930#comment-14003930
]
Gustavo Anatoly commented on HBASE-11212:
-
Hi, [~yuzhih...@gmail.com]
I found the same problem, reported for you. Could you please review again :) ?
Thanks.
Fix increment index in KeyValueSortReducer
--
Key: HBASE-11212
URL: https://issues.apache.org/jira/browse/HBASE-11212
Project: HBase
Issue Type: Bug
Reporter: Gustavo Anatoly
Assignee: Gustavo Anatoly
Priority: Minor
Fix For: 0.99.0, 0.98.3
Attachments: HBASE-11212.patch
The index is never incremented inside the loop, therefore context.setStatus
also is never set.
{code}
int index = 0;
for (KeyValue kv: map) {
context.write(row, kv);
if (index 0 index % 100 == 0) context.setStatus(Wrote + index);
}
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (HBASE-11147) Avoid creating List of KeyValue in FilterBase#filterRowCells(ListCell)
[
https://issues.apache.org/jira/browse/HBASE-11147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo Anatoly reassigned HBASE-11147:
---
Assignee: Gustavo Anatoly
Avoid creating List of KeyValue in FilterBase#filterRowCells(ListCell)
Key: HBASE-11147
URL: https://issues.apache.org/jira/browse/HBASE-11147
Project: HBase
Issue Type: Task
Reporter: Ted Yu
Assignee: Gustavo Anatoly
Priority: Trivial
Currently a List of KeyValue's is always created:
{code}
ListKeyValue kvs = new ArrayListKeyValue(ignored.size());
{code}
When passed ignored List is of KeyValue (which is the only implementation of
Cell at the moment), the above step should be avoided.
This would reduce creation of short-lived objects.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HBASE-11076) Update refguide on getting 0.94.x to run on hadoop 2.2.0+
[ https://issues.apache.org/jira/browse/HBASE-11076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-11076: Attachment: HBASE-11076-v1.patch Thanks Ted. Update refguide on getting 0.94.x to run on hadoop 2.2.0+ - Key: HBASE-11076 URL: https://issues.apache.org/jira/browse/HBASE-11076 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Attachments: HBASE-11076-v1.patch, HBASE-11076.patch http://hbase.apache.org/book.html#d248e643 contains steps for rebuilding 0.94 code base to run on hadoop 2.2.0+ However, the files under src/main/java/org/apache/hadoop/hbase/protobuf/generated were produced by protoc 2.4.0 These files need to be regenerated. See http://search-hadoop.com/m/DHED4j7Um02/HBase+0.94+on+hadoop+2.2.0subj=Re+HBase+0+94+on+hadoop+2+2+0+2+4+0+ This issue is to update refguide with this regeneration step. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-11076) Update refguide on getting 0.94.x to run on hadoop 2.2.0+
[ https://issues.apache.org/jira/browse/HBASE-11076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-11076: Status: Patch Available (was: Open) Update refguide on getting 0.94.x to run on hadoop 2.2.0+ - Key: HBASE-11076 URL: https://issues.apache.org/jira/browse/HBASE-11076 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Attachments: HBASE-11076.patch http://hbase.apache.org/book.html#d248e643 contains steps for rebuilding 0.94 code base to run on hadoop 2.2.0+ However, the files under src/main/java/org/apache/hadoop/hbase/protobuf/generated were produced by protoc 2.4.0 These files need to be regenerated. See http://search-hadoop.com/m/DHED4j7Um02/HBase+0.94+on+hadoop+2.2.0subj=Re+HBase+0+94+on+hadoop+2+2+0+2+4+0+ This issue is to update refguide with this regeneration step. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HBASE-11076) Update refguide on getting 0.94.x to run on hadoop 2.2.0+
[ https://issues.apache.org/jira/browse/HBASE-11076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Anatoly updated HBASE-11076: Attachment: HBASE-11076.patch Update refguide on getting 0.94.x to run on hadoop 2.2.0+ - Key: HBASE-11076 URL: https://issues.apache.org/jira/browse/HBASE-11076 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Gustavo Anatoly Attachments: HBASE-11076.patch http://hbase.apache.org/book.html#d248e643 contains steps for rebuilding 0.94 code base to run on hadoop 2.2.0+ However, the files under src/main/java/org/apache/hadoop/hbase/protobuf/generated were produced by protoc 2.4.0 These files need to be regenerated. See http://search-hadoop.com/m/DHED4j7Um02/HBase+0.94+on+hadoop+2.2.0subj=Re+HBase+0+94+on+hadoop+2+2+0+2+4+0+ This issue is to update refguide with this regeneration step. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HBASE-11129) Expose Scan conversion methods in TableMapReduceUtil as public methods
[
https://issues.apache.org/jira/browse/HBASE-11129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994248#comment-13994248
]
Gustavo Anatoly commented on HBASE-11129:
-
We could enjoy this issue to refactor and plan some tests. This changes require
voting?
Expose Scan conversion methods in TableMapReduceUtil as public methods
--
Key: HBASE-11129
URL: https://issues.apache.org/jira/browse/HBASE-11129
Project: HBase
Issue Type: Task
Components: mapreduce
Reporter: Ted Yu
Assignee: Gustavo Anatoly
Priority: Minor
Attachments: HBASE-11129.patch
Scan#readFields() from 0.92 has been removed.
TableMapReduceUtil has the following package private methods:
{code}
static String convertScanToString(Scan scan) throws IOException {
{code}
{code}
static Scan convertStringToScan(String base64) throws IOException {
{code}
We should consider exposing them as public methods so that user can interpret
Scan objects easily in mapreduce jobs.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
