[jira] [Work stopped] (HBASE-13195) IntegrationTestImportTsv doesn't support Chaos Monkey options
[ https://issues.apache.org/jira/browse/HBASE-13195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-13195 stopped by Dima Spivak. --- > IntegrationTestImportTsv doesn't support Chaos Monkey options > - > > Key: HBASE-13195 > URL: https://issues.apache.org/jira/browse/HBASE-13195 > Project: HBase > Issue Type: Bug > Components: integration tests >Reporter: Dima Spivak >Assignee: Dima Spivak >Priority: Major > > IntegrationTestImportTsv comes from a pre-monkey era and needs some simple > changes to support primative behaviors. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (HBASE-15964) Create Jenkins automation to run ITBLL on upstream infrastructure
[
https://issues.apache.org/jira/browse/HBASE-15964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak reassigned HBASE-15964:
---
Assignee: (was: Dima Spivak)
> Create Jenkins automation to run ITBLL on upstream infrastructure
> -
>
> Key: HBASE-15964
> URL: https://issues.apache.org/jira/browse/HBASE-15964
> Project: HBase
> Issue Type: Sub-task
> Components: integration tests
>Reporter: Dima Spivak
>Priority: Major
>
> Being able to run {{IntegrationTestBigLinkedList}} on demand on, for example,
> a five-node Apache HBase cluster, would be cool. Also having different chaos
> monkeys running would be even cooler.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (HBASE-13195) IntegrationTestImportTsv doesn't support Chaos Monkey options
[ https://issues.apache.org/jira/browse/HBASE-13195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-13195: --- Assignee: Dima Spivak > IntegrationTestImportTsv doesn't support Chaos Monkey options > - > > Key: HBASE-13195 > URL: https://issues.apache.org/jira/browse/HBASE-13195 > Project: HBase > Issue Type: Bug > Components: integration tests >Reporter: Dima Spivak >Assignee: Dima Spivak >Priority: Major > > IntegrationTestImportTsv comes from a pre-monkey era and needs some simple > changes to support primative behaviors. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (HBASE-13195) IntegrationTestImportTsv doesn't support Chaos Monkey options
[ https://issues.apache.org/jira/browse/HBASE-13195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-13195: --- Assignee: (was: Dima Spivak) > IntegrationTestImportTsv doesn't support Chaos Monkey options > - > > Key: HBASE-13195 > URL: https://issues.apache.org/jira/browse/HBASE-13195 > Project: HBase > Issue Type: Bug > Components: integration tests >Reporter: Dima Spivak >Priority: Major > > IntegrationTestImportTsv comes from a pre-monkey era and needs some simple > changes to support primative behaviors. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Work stopped] (HBASE-15964) Create Jenkins automation to run ITBLL on upstream infrastructure
[
https://issues.apache.org/jira/browse/HBASE-15964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HBASE-15964 stopped by Dima Spivak.
---
> Create Jenkins automation to run ITBLL on upstream infrastructure
> -
>
> Key: HBASE-15964
> URL: https://issues.apache.org/jira/browse/HBASE-15964
> Project: HBase
> Issue Type: Sub-task
> Components: integration tests
>Reporter: Dima Spivak
>Assignee: Dima Spivak
>Priority: Major
>
> Being able to run {{IntegrationTestBigLinkedList}} on demand on, for example,
> a five-node Apache HBase cluster, would be cool. Also having different chaos
> monkeys running would be even cooler.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (HBASE-15964) Create Jenkins automation to run ITBLL on upstream infrastructure
[
https://issues.apache.org/jira/browse/HBASE-15964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak reassigned HBASE-15964:
---
Assignee: Dima Spivak
> Create Jenkins automation to run ITBLL on upstream infrastructure
> -
>
> Key: HBASE-15964
> URL: https://issues.apache.org/jira/browse/HBASE-15964
> Project: HBase
> Issue Type: Sub-task
> Components: integration tests
>Reporter: Dima Spivak
>Assignee: Dima Spivak
>Priority: Major
>
> Being able to run {{IntegrationTestBigLinkedList}} on demand on, for example,
> a five-node Apache HBase cluster, would be cool. Also having different chaos
> monkeys running would be even cooler.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (HBASE-13195) IntegrationTestImportTsv doesn't support Chaos Monkey options
[ https://issues.apache.org/jira/browse/HBASE-13195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-13195: --- Assignee: (was: Dima Spivak) > IntegrationTestImportTsv doesn't support Chaos Monkey options > - > > Key: HBASE-13195 > URL: https://issues.apache.org/jira/browse/HBASE-13195 > Project: HBase > Issue Type: Bug > Components: integration tests >Reporter: Dima Spivak >Priority: Major > > IntegrationTestImportTsv comes from a pre-monkey era and needs some simple > changes to support primative behaviors. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (HBASE-15964) Create Jenkins automation to run ITBLL on upstream infrastructure
[
https://issues.apache.org/jira/browse/HBASE-15964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak reassigned HBASE-15964:
---
Assignee: (was: Dima Spivak)
> Create Jenkins automation to run ITBLL on upstream infrastructure
> -
>
> Key: HBASE-15964
> URL: https://issues.apache.org/jira/browse/HBASE-15964
> Project: HBase
> Issue Type: Sub-task
> Components: integration tests
>Reporter: Dima Spivak
>Priority: Major
>
> Being able to run {{IntegrationTestBigLinkedList}} on demand on, for example,
> a five-node Apache HBase cluster, would be cool. Also having different chaos
> monkeys running would be even cooler.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (HBASE-22206) dist.apache.org must not be used for public downloads
[ https://issues.apache.org/jira/browse/HBASE-22206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16819249#comment-16819249 ] Dima Spivak commented on HBASE-22206: - Fine by me, I'll keep an eye on HBASE-2 until then. Thanks for the heads up, [~busbey]. > dist.apache.org must not be used for public downloads > - > > Key: HBASE-22206 > URL: https://issues.apache.org/jira/browse/HBASE-22206 > Project: HBase > Issue Type: Bug > Components: website >Reporter: Sebb >Assignee: Dima Spivak >Priority: Major > Attachments: HBASE-22206.master.001.patch, > HBASE-22206.master.001.patch > > > The dist.apache.org server is only intended for use by developers in staging > releases. > It must not be used on public download pages. > Please use www.apache.org/dist (for KEYS, hashes and sigs) and the mirror > system instead. > The current download page has lots of references to dist.a.o; please replace > thes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22206) dist.apache.org must not be used for public downloads
[ https://issues.apache.org/jira/browse/HBASE-22206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak updated HBASE-22206: Status: Patch Available (was: Open) > dist.apache.org must not be used for public downloads > - > > Key: HBASE-22206 > URL: https://issues.apache.org/jira/browse/HBASE-22206 > Project: HBase > Issue Type: Bug > Components: website >Reporter: Sebb >Assignee: Dima Spivak >Priority: Major > Attachments: HBASE-22206.master.001.patch > > > The dist.apache.org server is only intended for use by developers in staging > releases. > It must not be used on public download pages. > Please use www.apache.org/dist (for KEYS, hashes and sigs) and the mirror > system instead. > The current download page has lots of references to dist.a.o; please replace > thes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22206) dist.apache.org must not be used for public downloads
[ https://issues.apache.org/jira/browse/HBASE-22206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak updated HBASE-22206: Attachment: HBASE-22206.master.001.patch > dist.apache.org must not be used for public downloads > - > > Key: HBASE-22206 > URL: https://issues.apache.org/jira/browse/HBASE-22206 > Project: HBase > Issue Type: Bug > Components: website >Reporter: Sebb >Assignee: Dima Spivak >Priority: Major > Attachments: HBASE-22206.master.001.patch > > > The dist.apache.org server is only intended for use by developers in staging > releases. > It must not be used on public download pages. > Please use www.apache.org/dist (for KEYS, hashes and sigs) and the mirror > system instead. > The current download page has lots of references to dist.a.o; please replace > thes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-22206) dist.apache.org must not be used for public downloads
[ https://issues.apache.org/jira/browse/HBASE-22206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-22206: --- Assignee: Dima Spivak Let's see if I still remember how to do this... > dist.apache.org must not be used for public downloads > - > > Key: HBASE-22206 > URL: https://issues.apache.org/jira/browse/HBASE-22206 > Project: HBase > Issue Type: Bug > Components: website >Reporter: Sebb >Assignee: Dima Spivak >Priority: Major > > The dist.apache.org server is only intended for use by developers in staging > releases. > It must not be used on public download pages. > Please use www.apache.org/dist (for KEYS, hashes and sigs) and the mirror > system instead. > The current download page has lots of references to dist.a.o; please replace > thes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (HBASE-22206) dist.apache.org must not be used for public downloads
[
https://issues.apache.org/jira/browse/HBASE-22206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814901#comment-16814901
]
Dima Spivak edited comment on HBASE-22206 at 4/10/19 10:02 PM:
---
The 2.0.5 listing in {{downloads.xml}} links to d.a.o. The rest of the releases
are good.
was (Author: dimaspivak):
The 2.0.5 listing is {{downloads.xml}} links to d.a.o. The rest of the releases
are good.
> dist.apache.org must not be used for public downloads
> -
>
> Key: HBASE-22206
> URL: https://issues.apache.org/jira/browse/HBASE-22206
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sebb
>Priority: Major
>
> The dist.apache.org server is only intended for use by developers in staging
> releases.
> It must not be used on public download pages.
> Please use www.apache.org/dist (for KEYS, hashes and sigs) and the mirror
> system instead.
> The current download page has lots of references to dist.a.o; please replace
> thes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-22206) dist.apache.org must not be used for public downloads
[
https://issues.apache.org/jira/browse/HBASE-22206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814901#comment-16814901
]
Dima Spivak commented on HBASE-22206:
-
The 2.0.5 listing is {{downloads.xml}} links to d.a.o. The rest of the releases
are good.
> dist.apache.org must not be used for public downloads
> -
>
> Key: HBASE-22206
> URL: https://issues.apache.org/jira/browse/HBASE-22206
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sebb
>Priority: Major
>
> The dist.apache.org server is only intended for use by developers in staging
> releases.
> It must not be used on public download pages.
> Please use www.apache.org/dist (for KEYS, hashes and sigs) and the mirror
> system instead.
> The current download page has lots of references to dist.a.o; please replace
> thes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (HBASE-15961) Create documentation on how to use of clusterdock
[ https://issues.apache.org/jira/browse/HBASE-15961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-15961: --- Assignee: (was: Dima Spivak) > Create documentation on how to use of clusterdock > - > > Key: HBASE-15961 > URL: https://issues.apache.org/jira/browse/HBASE-15961 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: Dima Spivak >Priority: Major > > Ref guide should include information on starting Docker container-based > distributed HBase clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-12221) Port TestFromClientSide to hbase-it
[ https://issues.apache.org/jira/browse/HBASE-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-12221: --- Assignee: (was: Dima Spivak) > Port TestFromClientSide to hbase-it > --- > > Key: HBASE-12221 > URL: https://issues.apache.org/jira/browse/HBASE-12221 > Project: HBase > Issue Type: New Feature >Affects Versions: 1.0.0, 0.98.7, 2.0.0 >Reporter: Dima Spivak >Priority: Major > > org.apache.hadoop.hbase.client.TestFromClientSide touches a lot of the HBase > Java API and would be a nice integration test to have for anyone looking to > verify end-to-end functionality. I'd like to turn it into an integration test > and have it live in hbase-it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-5580) Publish Thrift-generated files for other languages
[ https://issues.apache.org/jira/browse/HBASE-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-5580: -- Assignee: (was: Dima Spivak) > Publish Thrift-generated files for other languages > -- > > Key: HBASE-5580 > URL: https://issues.apache.org/jira/browse/HBASE-5580 > Project: HBase > Issue Type: New Feature > Components: Thrift >Affects Versions: 0.90.4 >Reporter: Patrick Angeles >Priority: Major > Labels: thrift, thrift2 > > HBase ships with Thrift-generated Java files for use with the ThriftServer. > For convenience (and to save users the frustration of having to compile and > install the Thrift compiler), HBase can ship with the thrift-generated files > for other languages as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-11945) Client writes may be reordered under contention
[ https://issues.apache.org/jira/browse/HBASE-11945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-11945: --- Assignee: (was: Dima Spivak) > Client writes may be reordered under contention > --- > > Key: HBASE-11945 > URL: https://issues.apache.org/jira/browse/HBASE-11945 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 0.98.6 >Reporter: Todd Lipcon >Priority: Major > > I haven't seen this bug in practice, but I was thinking about this a bit and > think there may be a correctness issue with the way that we handle client > batches which contain multiple operations which touch the same row. The > client expects that these operations will be performed in the same order they > were submitted, but under contention I believe they can get arbitrarily > reordered, leading to incorrect results. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-16483) Build and run tests against more HBase branches
[
https://issues.apache.org/jira/browse/HBASE-16483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak reassigned HBASE-16483:
---
Assignee: (was: Dima Spivak)
> Build and run tests against more HBase branches
> ---
>
> Key: HBASE-16483
> URL: https://issues.apache.org/jira/browse/HBASE-16483
> Project: HBase
> Issue Type: Sub-task
> Components: integration tests
>Reporter: Dima Spivak
>Priority: Major
>
> Started out with {{master}}, but getting tests going against {{branch-1.2}}
> and {{branch-1.3}} would be a good start.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (HBASE-15700) Add accessing web UI to Chaos Monkey actions
[ https://issues.apache.org/jira/browse/HBASE-15700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-15700: --- Assignee: (was: Dima Spivak) > Add accessing web UI to Chaos Monkey actions > > > Key: HBASE-15700 > URL: https://issues.apache.org/jira/browse/HBASE-15700 > Project: HBase > Issue Type: New Feature > Components: integration tests >Reporter: Dima Spivak >Priority: Minor > > We observed a strange bug where we saw the HBase Master go down when a > separate process started hitting the web UI. I'd like to add an Action that > does some fuzz-y behavior to that port to see if we can reproduce/fix this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-16482) Collect logs and other files when system tests fail
[
https://issues.apache.org/jira/browse/HBASE-16482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak reassigned HBASE-16482:
---
Assignee: (was: Dima Spivak)
> Collect logs and other files when system tests fail
> ---
>
> Key: HBASE-16482
> URL: https://issues.apache.org/jira/browse/HBASE-16482
> Project: HBase
> Issue Type: Sub-task
> Components: integration tests
>Reporter: Dima Spivak
>Priority: Major
>
> As requested by [~apurtell], when {{hbase-it}} jobs fail:
> {noformat}
> To completely retrace a rare botch we may need persisted post run:
> - The console log of the rum
> - All daemon logs
> - All WALs
> - All HFiles
> WALs and HFiles should be be organized by time from oldest to newest.
> All could reside in a S3 bucket.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (HBASE-16158) Automate runs of check_compatibility.sh on upstream infra
[
https://issues.apache.org/jira/browse/HBASE-16158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak reassigned HBASE-16158:
---
Assignee: (was: Dima Spivak)
> Automate runs of check_compatibility.sh on upstream infra
> -
>
> Key: HBASE-16158
> URL: https://issues.apache.org/jira/browse/HBASE-16158
> Project: HBase
> Issue Type: Task
> Components: test
>Reporter: Dima Spivak
>Priority: Major
>
> Now that we got {{check_compatiblity.sh}} working again, perhaps we should
> think about having it run regularly upstream? One possibility would be to tie
> it into Yetus runs so that the tool gets run on every commit between the
> branch in question and a designated Git reference (e.g. branch-1.2 could run
> against the earlier release of the 1.2 line) and simply grepping the output
> to make sure that the number of problems and warnings doesn't exceed a
> designated number. The other would be to run every branch in its own Jenkins
> job following the same workflow, but on a nightly basis. What do you guys and
> gals think would be best?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (HBASE-15963) Create Jenkins automation to build apache-hbase clusterdock images
[
https://issues.apache.org/jira/browse/HBASE-15963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak reassigned HBASE-15963:
---
Assignee: (was: Dima Spivak)
> Create Jenkins automation to build apache-hbase clusterdock images
> --
>
> Key: HBASE-15963
> URL: https://issues.apache.org/jira/browse/HBASE-15963
> Project: HBase
> Issue Type: Sub-task
> Components: build
>Reporter: Dima Spivak
>Priority: Major
>
> One of the main goals of {{clusterdock}} is to enable testing of distributed
> Apache HBase clusters built from source. There's no better way to facilitate
> this than to regularly (or continuously) build images of the branches we care
> about for use by other people and automation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (HBASE-12852) Tests from hbase-it that use ChaosMonkey don't fail if SSH commands fail
[
https://issues.apache.org/jira/browse/HBASE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak reassigned HBASE-12852:
---
Assignee: (was: Dima Spivak)
> Tests from hbase-it that use ChaosMonkey don't fail if SSH commands fail
>
>
> Key: HBASE-12852
> URL: https://issues.apache.org/jira/browse/HBASE-12852
> Project: HBase
> Issue Type: Bug
> Components: integration tests
>Affects Versions: 0.98.6
>Reporter: Dima Spivak
>Priority: Major
>
> I've just started rolling my sleeves up and playing about with hbase-it (at
> the moment, only on 0.98.6), but wanted to begin filing JIRAs for issues I
> encounter so that I don't forget to get to them. First up is the fact that it
> seems that tests run with ChaosMonkey don't fail when the ChaosMonkey fails
> to work. As an example, while running IntegrationTestIngest with a
> slowDeterministic CM, I forgot to set up SSH properly and saw the following:
> {code}
> 15/01/14 07:36:53 WARN hbase.ClusterManager: Remote command: ps aux | grep
> proc_regionserver | grep -v grep | tr -s ' ' | cut -d ' ' -f2 | xargs kill -s
> SIGKILL , hostname:node-5.internal failed at attempt 4. Retrying until
> maxAttempts: 5. Exception: stderr: Permission denied, please try again.
> Permission denied, please try again.
> Permission denied (publickey,password).
> , stdout:
> 15/01/14 07:36:53 INFO util.RetryCounter: Sleeping 16000ms before retry #4...
> 15/01/14 07:36:53 INFO zookeeper.ZooKeeper: Session: 0x14ae74d7bac006b closed
> 15/01/14 07:36:53 INFO policies.Policy: Sleeping for: 59541
> 15/01/14 07:36:53 INFO zookeeper.ClientCnxn: EventThread shut down
> Failed to write keys: 0
> Key range: [15..15]
> Batch updates: false
> Percent of keys to update: 60
> Updater threads: 10
> Ignore nonce conflicts: true
> Regions per server: 5
> 15/01/14 07:36:56 INFO util.LoadTestTool: Starting to mutate data...
> Starting to mutate data...
> 15/01/14 07:36:57 INFO policies.Policy: Sleeping for: 88816
> 15/01/14 07:37:01 INFO util.MultiThreadedAction: [U:10] Keys=471, cols=5.7 K,
> time=00:00:05 Overall: [keys/s= 94, latency=102 ms] Current: [keys/s=94,
> latency=102 ms], wroteUpTo=14
> 15/01/14 07:37:06 INFO util.MultiThreadedAction: [U:10] Keys=908, cols=11.0
> K, time=00:00:10 Overall: [keys/s= 90, latency=90 ms] Current: [keys/s=87,
> latency=77 ms], wroteUpTo=14
> 15/01/14 07:37:09 INFO hbase.ClusterManager: Executing remote command: ps aux
> | grep proc_regionserver | grep -v grep | tr -s ' ' | cut -d ' ' -f2 | xargs
> kill -s SIGKILL , hostname:node-5.internal
> 15/01/14 07:37:09 INFO util.Shell: Executing full command [/usr/bin/ssh
> node-5.internal "ps aux | grep proc_regionserver | grep -v grep | tr -s ' ' |
> cut -d ' ' -f2 | xargs kill -s SIGKILL"]
> 15/01/14 07:37:09 WARN policies.Policy: Exception occured during performing
> action: ExitCodeException exitCode=255: stderr: Permission denied, please try
> again.
> Permission denied, please try again.
> Permission denied (publickey,password).
> , stdout:
> at
> org.apache.hadoop.hbase.HBaseClusterManager.exec(HBaseClusterManager.java:208)
> at
> org.apache.hadoop.hbase.HBaseClusterManager.execWithRetries(HBaseClusterManager.java:223)
> at
> org.apache.hadoop.hbase.HBaseClusterManager.signal(HBaseClusterManager.java:268)
> at org.apache.hadoop.hbase.ClusterManager.kill(ClusterManager.java:97)
> at
> org.apache.hadoop.hbase.DistributedHBaseCluster.killRegionServer(DistributedHBaseCluster.java:110)
> at org.apache.hadoop.hbase.chaos.actions.Action.killRs(Action.java:84)
> at
> org.apache.hadoop.hbase.chaos.actions.RestartActionBaseAction.restartRs(RestartActionBaseAction.java:50)
> at
> org.apache.hadoop.hbase.chaos.actions.RestartRsHoldingMetaAction.perform(RestartRsHoldingMetaAction.java:38)
> at
> org.apache.hadoop.hbase.chaos.policies.DoActionsOncePolicy.runOneIteration(DoActionsOncePolicy.java:50)
> at
> org.apache.hadoop.hbase.chaos.policies.PeriodicPolicy.run(PeriodicPolicy.java:41)
> at
> org.apache.hadoop.hbase.chaos.policies.CompositeSequentialPolicy.run(CompositeSequentialPolicy.java:42)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Seems to me that tests should fail in these instances rather than just toss a
> warning. Was this just an oversight, [~enis] and [~ndimiduk], or is this by
> design?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (HBASE-16442) Create Jenkins automation for clusterdock
[ https://issues.apache.org/jira/browse/HBASE-16442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-16442: --- Assignee: (was: Dima Spivak) > Create Jenkins automation for clusterdock > - > > Key: HBASE-16442 > URL: https://issues.apache.org/jira/browse/HBASE-16442 > Project: HBase > Issue Type: New Feature >Reporter: Dima Spivak >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-12868) Update test section of ref guide
[ https://issues.apache.org/jira/browse/HBASE-12868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-12868: --- Assignee: (was: Dima Spivak) > Update test section of ref guide > > > Key: HBASE-12868 > URL: https://issues.apache.org/jira/browse/HBASE-12868 > Project: HBase > Issue Type: Bug > Components: documentation >Reporter: Dima Spivak >Priority: Minor > > [The test section|http://hbase.apache.org/book.html#hbase.tests] of the ref > guide can use a little love to bring it in line with how things currently > stand. As I get more familiar with hbase-it, in particular, I'll update our > docs to reflect reality. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-16131) Add optional docker image build and publish steps to release documentation and build_rc.sh
[ https://issues.apache.org/jira/browse/HBASE-16131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-16131: --- Assignee: (was: Dima Spivak) > Add optional docker image build and publish steps to release documentation > and build_rc.sh > -- > > Key: HBASE-16131 > URL: https://issues.apache.org/jira/browse/HBASE-16131 > Project: HBase > Issue Type: Sub-task > Components: build, community, documentation, test >Reporter: Andrew Purtell >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-15869) Create IntegrationTestCopyTable
[ https://issues.apache.org/jira/browse/HBASE-15869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-15869: --- Assignee: (was: Dima Spivak) > Create IntegrationTestCopyTable > --- > > Key: HBASE-15869 > URL: https://issues.apache.org/jira/browse/HBASE-15869 > Project: HBase > Issue Type: New Feature > Components: integration tests >Reporter: Dima Spivak >Priority: Minor > > Taking a cue from [~jmhsieh], I'd like to create a version of TestCopyTable > that can run against distributed clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-12857) Make hbase-it test running more consistent
[ https://issues.apache.org/jira/browse/HBASE-12857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-12857: --- Assignee: (was: Dima Spivak) > Make hbase-it test running more consistent > -- > > Key: HBASE-12857 > URL: https://issues.apache.org/jira/browse/HBASE-12857 > Project: HBase > Issue Type: Improvement > Components: integration tests >Reporter: Dima Spivak >Priority: Major > > Running tests from hbase-it can be painful because some of them have a main > method and can be run by invoking them with bin/hbase, while others have to > be called via something like IntegrationTestsDriver. Let's decide how we want > things to work and then I'll implement it. I imagine the easiest way to go is > to just to add a main method to any class that doesn't have one. Any opinion > one way or the other [~enis], [~ndimiduk], [~eclark], or [~stack]? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-16268) Add IntegrationTestRESTApi
[ https://issues.apache.org/jira/browse/HBASE-16268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-16268: --- Assignee: (was: Dima Spivak) > Add IntegrationTestRESTApi > -- > > Key: HBASE-16268 > URL: https://issues.apache.org/jira/browse/HBASE-16268 > Project: HBase > Issue Type: New Feature > Components: integration tests, REST >Reporter: Dima Spivak >Priority: Minor > > The REST API is documented, so people might use it, but it looks like there's > not an end-to-end test that can be run on a real cluster. Let's add one. > Since there are only a handful of commands, having this test pass (and new > cases added for new commands) might be a good way to quality gate new > additions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-16481) Improvements to clusterdock-based hbase-it jobs
[
https://issues.apache.org/jira/browse/HBASE-16481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak reassigned HBASE-16481:
---
Assignee: (was: Dima Spivak)
> Improvements to clusterdock-based hbase-it jobs
> ---
>
> Key: HBASE-16481
> URL: https://issues.apache.org/jira/browse/HBASE-16481
> Project: HBase
> Issue Type: Task
> Components: integration tests
>Reporter: Dima Spivak
>Priority: Major
>
> Parent JIRA to track things to improve in the nascent jobs on
> builds.apache.org that run tests from {{hbase-it}} on clusterdock-based
> Apache HBase clusters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (HBASE-12860) Integration tests that do bulkload should be better documented
[ https://issues.apache.org/jira/browse/HBASE-12860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-12860: --- Assignee: (was: Dima Spivak) > Integration tests that do bulkload should be better documented > -- > > Key: HBASE-12860 > URL: https://issues.apache.org/jira/browse/HBASE-12860 > Project: HBase > Issue Type: Improvement > Components: integration tests >Affects Versions: 0.98.10 >Reporter: Dima Spivak >Priority: Minor > > Running hbase-it tests that create and bulkload HFiles has a learning curve > at the moment. For example, these tests (e.g. IntegrationTestBulkLoad) need > to be run by the hbase user so that the files that are created have the > necessary permissions to be imported into HBase. Moreover, a /user/hbase > directory must already exist (or the hbase user must belong to a group > allowed to write in /user), or the test will fail because of permissions > problems. > We should document these things in the ref guide and log warnings in the > tests to help people catch these problems. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-13798) TestFromClientSide* don't close the Table
[ https://issues.apache.org/jira/browse/HBASE-13798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-13798: --- Assignee: (was: Dima Spivak) > TestFromClientSide* don't close the Table > - > > Key: HBASE-13798 > URL: https://issues.apache.org/jira/browse/HBASE-13798 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 1.1.0, 2.0.0 >Reporter: Matteo Bertozzi >Priority: Trivial > > TestFromClientSide, TestFromClientSide3 have lots of tests with the Table > object not closed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-12395) Some internal classes are logging to DEBUG what should be logged to TRACE
[ https://issues.apache.org/jira/browse/HBASE-12395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-12395: --- Assignee: (was: Dima Spivak) > Some internal classes are logging to DEBUG what should be logged to TRACE > - > > Key: HBASE-12395 > URL: https://issues.apache.org/jira/browse/HBASE-12395 > Project: HBase > Issue Type: Improvement >Reporter: Dima Spivak >Priority: Major > > e.g. RpcExecutor is doing this a lot. This leads to 1) huge log files that > waste disk space and IO and 2) difficulty debugging tests themselves since > you need to wade through thousands of lines to get to what your test is doing > (see TestDistributedLogSplitting-output for 25 MB of thread information). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20392) Automated Installation of HBase (and Hadoop) on a distributed cluster environment
[ https://issues.apache.org/jira/browse/HBASE-20392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436232#comment-16436232 ] Dima Spivak commented on HBASE-20392: - I think the point is that a few open source projects (e.g. Bigtop, Ambari) and some other proprietary licensed-ones (e.g. Cloudera Manager) are specifically designed to do this. I'd say it's best deferring to those than putting something into HBase to handle this task. > Automated Installation of HBase (and Hadoop) on a distributed cluster > environment > - > > Key: HBASE-20392 > URL: https://issues.apache.org/jira/browse/HBASE-20392 > Project: HBase > Issue Type: Task > Components: hbase >Reporter: Sakthi >Assignee: Sakthi >Priority: Minor > > The process of HBase (and Hadoop) installation on a distributed cluster could > be automated to enable the deployment with lesser manual labor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-16459) Remove unused hbase shell --format option
[
https://issues.apache.org/jira/browse/HBASE-16459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246749#comment-16246749
]
Dima Spivak commented on HBASE-16459:
-
+1. Haven't had much time to HBase for a long while now, so feel free to push
it, [~appy].
> Remove unused hbase shell --format option
> -
>
> Key: HBASE-16459
> URL: https://issues.apache.org/jira/browse/HBASE-16459
> Project: HBase
> Issue Type: Task
> Components: shell
>Reporter: Dima Spivak
>Assignee: Dima Spivak
>Priority: Trivial
> Labels: beginner
> Attachments: HBASE-16459.master.001.patch, HBASE-16459.patch,
> HBASE-16459_v2.patch
>
>
> The usage information when running {{hbase shell}} refers to a formatter
> option that has yet to implemented in over 8 years and which will ostensibly
> never be implemented. As such, let's cleanup the [help
> message|https://github.com/apache/hbase/blob/master/bin/hirb.rb#L57-L59] and
> remove some extraneous lines of code from
> {{[hirb.rb|https://github.com/apache/hbase/blob/master/bin/hirb.rb#L74-L83]}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18418) Remove apache_hbase_topology from dev-support
[
https://issues.apache.org/jira/browse/HBASE-18418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak updated HBASE-18418:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove apache_hbase_topology from dev-support
> -
>
> Key: HBASE-18418
> URL: https://issues.apache.org/jira/browse/HBASE-18418
> Project: HBase
> Issue Type: Task
>Reporter: Dima Spivak
>Assignee: Dima Spivak
>Priority: Minor
> Attachments: HBASE-18418_v1.patch
>
>
> As [~misty] noted on dev@, we still keep a folder containing the Apache HBase
> topology for [clusterdock|https://github.com/clusterdock/framework] in
> dev-support. Since the {{clusterdock}} org on GitHub will likely always have
> a more up-to-date iteration of this code (and since I plan on showing it some
> love there in the next few weeks), we'd probably be better off removing it
> from HBase. Any objections?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (HBASE-16559) Create script to automate RC testing
[
https://issues.apache.org/jira/browse/HBASE-16559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak reassigned HBASE-16559:
---
Assignee: (was: Dima Spivak)
> Create script to automate RC testing
>
>
> Key: HBASE-16559
> URL: https://issues.apache.org/jira/browse/HBASE-16559
> Project: HBase
> Issue Type: Task
> Components: scripts
>Reporter: Dima Spivak
>
> Testing RCs would be easier and more repeatable if we had a script under
> {{dev-support}} that declared certain typical operations (checking hashes,
> running unit tests, spinning up clusters with {{clusterdock}} and running
> tests from {{hbase-it}}), and allowed a user to run them on demand. Letting
> them specify a JSON file with actions to take (and which arguments to pass to
> various tests, for example) would be cool, too.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18834) fix shellcheck warning on hbase personality
[
https://issues.apache.org/jira/browse/HBASE-18834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16170032#comment-16170032
]
Dima Spivak commented on HBASE-18834:
-
+1
> fix shellcheck warning on hbase personality
> ---
>
> Key: HBASE-18834
> URL: https://issues.apache.org/jira/browse/HBASE-18834
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Minor
> Attachments: HBASE-18834.0.patch
>
>
> current shellcheck gives us two warnings:
> {code}
> $ shellcheck dev-support/hbase-personality.sh
> In dev-support/hbase-personality.sh line 123:
> if [[ $? -eq 0 ]]; then
> ^-- SC2181: Check exit code directly with e.g. 'if mycmd;', not
> indirectly with $?.
> In dev-support/hbase-personality.sh line 136:
> if [[ $? -eq 0 ]]; then
> ^-- SC2181: Check exit code directly with e.g. 'if mycmd;', not
> indirectly with $?.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18591) Upgrade thrift from 0.9.3 to 0.10.0
[ https://issues.apache.org/jira/browse/HBASE-18591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16125962#comment-16125962 ] Dima Spivak commented on HBASE-18591: - If this needs to be done for Jetty, I think it's worth doing. HappyBase is already only kind of maintained and lacks a lot of features (e.g. anything security related), so I feel like if the community has a strong interest in proper Python bindings to Thrift, it can create them anew with 0.10.0 support. > Upgrade thrift from 0.9.3 to 0.10.0 > --- > > Key: HBASE-18591 > URL: https://issues.apache.org/jira/browse/HBASE-18591 > Project: HBase > Issue Type: Bug > Components: Thrift >Reporter: stack >Assignee: stack > Fix For: 2.0.0 > > Attachments: 18591.txt > > > Maybe we don't want to do this for 2.0.0. Maybe we want to let it up to the > implementor. Going to 0.10.0 will probably break any 0.9.3 clients. I could > try it I suppose but if past experience is anything to go by...it'll break > (There is this note that it is broke up on happybase > https://github.com/wbolster/happybase/issues/154). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18020) Update API Compliance Checker to Incorporate Improvements Done in Hadoop
[ https://issues.apache.org/jira/browse/HBASE-18020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113667#comment-16113667 ] Dima Spivak commented on HBASE-18020: - Done. Sorry for the delay, the flu sucks. > Update API Compliance Checker to Incorporate Improvements Done in Hadoop > > > Key: HBASE-18020 > URL: https://issues.apache.org/jira/browse/HBASE-18020 > Project: HBase > Issue Type: Improvement > Components: API, community >Reporter: Alex Leblang >Assignee: Alex Leblang > Fix For: 2.0.0 > > Attachments: HBASE-18020.0.patch, HBASE-18020.branch-1.2.001.patch, > HBASE-18020.branch-1.2.002.patch, HBASE-18020.branch-1.2.003.patch, > HBASE-18020.branch-1.2.004.patch > > > Recently the Hadoop community has made a number of improvements in their api > compliance checker based on feedback from the hbase and kudu community. We > should adopt these changes ourselves. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18020) Update API Compliance Checker to Incorporate Improvements Done in Hadoop
[ https://issues.apache.org/jira/browse/HBASE-18020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16097064#comment-16097064 ] Dima Spivak commented on HBASE-18020: - Sorry for disappearing, [~awleblang]; been swamped at work. If it's okay, I'll take a look at this first thing next week. > Update API Compliance Checker to Incorporate Improvements Done in Hadoop > > > Key: HBASE-18020 > URL: https://issues.apache.org/jira/browse/HBASE-18020 > Project: HBase > Issue Type: Improvement > Components: API, community >Reporter: Alex Leblang >Assignee: Alex Leblang > Fix For: 2.0.0 > > Attachments: HBASE-18020.0.patch, HBASE-18020.branch-1.2.001.patch, > HBASE-18020.branch-1.2.002.patch, HBASE-18020.branch-1.2.003.patch, > HBASE-18020.branch-1.2.004.patch > > > Recently the Hadoop community has made a number of improvements in their api > compliance checker based on feedback from the hbase and kudu community. We > should adopt these changes ourselves. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18418) Remove apache_hbase_topology from dev-support
[
https://issues.apache.org/jira/browse/HBASE-18418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095058#comment-16095058
]
Dima Spivak commented on HBASE-18418:
-
Not as far as I know. The topology itself always ran out of a Docker image and
my work to add regular Jenkins automation to actually use it stopped when I
switched jobs.
> Remove apache_hbase_topology from dev-support
> -
>
> Key: HBASE-18418
> URL: https://issues.apache.org/jira/browse/HBASE-18418
> Project: HBase
> Issue Type: Task
>Reporter: Dima Spivak
>Assignee: Dima Spivak
>Priority: Minor
> Attachments: HBASE-18418_v1.patch
>
>
> As [~misty] noted on dev@, we still keep a folder containing the Apache HBase
> topology for [clusterdock|https://github.com/clusterdock/framework] in
> dev-support. Since the {{clusterdock}} org on GitHub will likely always have
> a more up-to-date iteration of this code (and since I plan on showing it some
> love there in the next few weeks), we'd probably be better off removing it
> from HBase. Any objections?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18418) Remove apache_hbase_topology from dev-support
[
https://issues.apache.org/jira/browse/HBASE-18418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak updated HBASE-18418:
Attachment: HBASE-18418_v1.patch
Posted v1 of patch.
> Remove apache_hbase_topology from dev-support
> -
>
> Key: HBASE-18418
> URL: https://issues.apache.org/jira/browse/HBASE-18418
> Project: HBase
> Issue Type: Task
>Reporter: Dima Spivak
>Assignee: Dima Spivak
>Priority: Minor
> Attachments: HBASE-18418_v1.patch
>
>
> As [~misty] noted on dev@, we still keep a folder containing the Apache HBase
> topology for [clusterdock|https://github.com/clusterdock/framework] in
> dev-support. Since the {{clusterdock}} org on GitHub will likely always have
> a more up-to-date iteration of this code (and since I plan on showing it some
> love there in the next few weeks), we'd probably be better off removing it
> from HBase. Any objections?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18418) Remove apache_hbase_topology from dev-support
[
https://issues.apache.org/jira/browse/HBASE-18418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak updated HBASE-18418:
Status: Patch Available (was: Open)
> Remove apache_hbase_topology from dev-support
> -
>
> Key: HBASE-18418
> URL: https://issues.apache.org/jira/browse/HBASE-18418
> Project: HBase
> Issue Type: Task
>Reporter: Dima Spivak
>Assignee: Dima Spivak
>Priority: Minor
> Attachments: HBASE-18418_v1.patch
>
>
> As [~misty] noted on dev@, we still keep a folder containing the Apache HBase
> topology for [clusterdock|https://github.com/clusterdock/framework] in
> dev-support. Since the {{clusterdock}} org on GitHub will likely always have
> a more up-to-date iteration of this code (and since I plan on showing it some
> love there in the next few weeks), we'd probably be better off removing it
> from HBase. Any objections?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-18418) Remove apache_hbase_topology from dev-support
Dima Spivak created HBASE-18418:
---
Summary: Remove apache_hbase_topology from dev-support
Key: HBASE-18418
URL: https://issues.apache.org/jira/browse/HBASE-18418
Project: HBase
Issue Type: Task
Reporter: Dima Spivak
Assignee: Dima Spivak
Priority: Minor
As [~misty] noted on dev@, we still keep a folder containing the Apache HBase
topology for [clusterdock|https://github.com/clusterdock/framework] in
dev-support. Since the {{clusterdock}} org on GitHub will likely always have a
more up-to-date iteration of this code (and since I plan on showing it some
love there in the next few weeks), we'd probably be better off removing it from
HBase. Any objections?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (HBASE-18413) SHORT DESCRIPTION
[ https://issues.apache.org/jira/browse/HBASE-18413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak resolved HBASE-18413. - Resolution: Invalid Hm? > SHORT DESCRIPTION > - > > Key: HBASE-18413 > URL: https://issues.apache.org/jira/browse/HBASE-18413 > Project: HBase > Issue Type: Bug > Components: documentation >Reporter: Silvano Tamburini >Priority: Blocker > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18404) Small typo on ACID documentation page
[
https://issues.apache.org/jira/browse/HBASE-18404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091945#comment-16091945
]
Dima Spivak commented on HBASE-18404:
-
Wanna take it on, [~mcrutcher]? The file to change is
{{src/main/site/asciidoc/acid-semantics.adoc}} and it would be wholly
appreciated. :-p
> Small typo on ACID documentation page
> -
>
> Key: HBASE-18404
> URL: https://issues.apache.org/jira/browse/HBASE-18404
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Affects Versions: 1.3.1
>Reporter: Michael Crutcher
>Priority: Trivial
>
> I noticed a couple of occurrences of the "word" wholely on the ACID semantics
> doc page (https://hbase.apache.org/acid-semantics.html)
> This should be "wholly".
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18020) Update API Compliance Checker to Incorporate Improvements Done in Hadoop
[ https://issues.apache.org/jira/browse/HBASE-18020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16067059#comment-16067059 ] Dima Spivak commented on HBASE-18020: - Woot. I'll give this a thorough review on RB later today, [~awleblang]. > Update API Compliance Checker to Incorporate Improvements Done in Hadoop > > > Key: HBASE-18020 > URL: https://issues.apache.org/jira/browse/HBASE-18020 > Project: HBase > Issue Type: Improvement > Components: API, community >Reporter: Alex Leblang >Assignee: Alex Leblang > Fix For: 2.0.0 > > Attachments: HBASE-18020.0.patch, HBASE-18020.branch-1.2.001.patch, > HBASE-18020.branch-1.2.002.patch > > > Recently the Hadoop community has made a number of improvements in their api > compliance checker based on feedback from the hbase and kudu community. We > should adopt these changes ourselves. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18273) hbase_rotate_log in hbase-daemon.sh script not working for some JDK
[ https://issues.apache.org/jira/browse/HBASE-18273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065860#comment-16065860 ] Dima Spivak commented on HBASE-18273: - Why not just check for the file with the suffixed name alone? No need to have it be a compound statement. > hbase_rotate_log in hbase-daemon.sh script not working for some JDK > --- > > Key: HBASE-18273 > URL: https://issues.apache.org/jira/browse/HBASE-18273 > Project: HBase > Issue Type: Bug > Components: hbase >Affects Versions: 1.2.6, 1.1.11, 2.0.0-alpha-1 >Reporter: Fangyuan Deng > Fix For: 2.0.0-beta-2 > > Attachments: HBASE-18273.0.patch, HBASE-18273.1.patch > > > When restarting a hbase process, hbase_rotate_log $HBASE_LOGGC will rotate > GC logs. > the code looks like this, > if [ -f "$log" ]; then # rotate logs > while [ $num -gt 1 ]; do > prev=`expr $num - 1` > [ -f "$log.$prev" ] && mv -f "$log.$prev" "$log.$num" > num=$prev > done > But, some version JDK will add a suffix (.0) to the gc file, like > hbase-xxx.gc.0, rather than hbase-xxx.gc. > So I add a check before rotate, > if [ ! -f "$log" ]; then #for some jdk, gc log has a postfix 0 > if [ -f "$log.0" ]; then > mv -f "$log.0" "$log"; > fi > fi -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18273) hbase_rotate_log in hbase-daemon.sh script not working for some JDK
[ https://issues.apache.org/jira/browse/HBASE-18273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064902#comment-16064902 ] Dima Spivak commented on HBASE-18273: - Can you do away with the outer conditional and just keep the one for the suffixed file? > hbase_rotate_log in hbase-daemon.sh script not working for some JDK > --- > > Key: HBASE-18273 > URL: https://issues.apache.org/jira/browse/HBASE-18273 > Project: HBase > Issue Type: Bug > Components: hbase >Affects Versions: 1.2.6, 1.1.11, 2.0.0-alpha-1 >Reporter: Fangyuan Deng > Fix For: 2.0.0-beta-2 > > Attachments: HBASE-18273.0.patch > > > When restarting a hbase process, hbase_rotate_log $HBASE_LOGGC will rotate > GC logs. > the code looks like this, > if [ -f "$log" ]; then # rotate logs > while [ $num -gt 1 ]; do > prev=`expr $num - 1` > [ -f "$log.$prev" ] && mv -f "$log.$prev" "$log.$num" > num=$prev > done > But, some version JDK will add a postfix .0 to the gc file, like > hbase-xxx.gc.0, rather than hbase-xxx.gc. > So I add a check before rotate, > if [ ! -f "$log" ]; then #for some jdk, gc log has a postfix 0 > if [ -f "$log.0" ]; then > mv -f "$log.0" "$log"; > fi > fi -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18041) Add pylintrc file to HBase
[ https://issues.apache.org/jira/browse/HBASE-18041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021976#comment-16021976 ] Dima Spivak commented on HBASE-18041: - And to answer the question of what's needed to move forward, I'd say let's just get a run of the code base with this and see what it gives us. If it looks reasonable, I'll +1 it and we can handle cleanup later. > Add pylintrc file to HBase > -- > > Key: HBASE-18041 > URL: https://issues.apache.org/jira/browse/HBASE-18041 > Project: HBase > Issue Type: Improvement > Components: community >Reporter: Alex Leblang >Assignee: Alex Leblang > Attachments: HBASE-18041.branch-1.2.001.patch > > > Yetus runs all commits with python files through a linter. I think that the > HBase community should add a pylintrc file to actively choose the project's > python style instead of just relying on yetus defaults. > As an argument for this, the yetus project itself doesn't even use the > default python linter for its own commits. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-18041) Add pylintrc file to HBase
[
https://issues.apache.org/jira/browse/HBASE-18041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021975#comment-16021975
]
Dima Spivak commented on HBASE-18041:
-
Eh, it's probably fine. It's kinda hard to review a big 300 line config file
that's full of commented out stuff since I can't tell what's different from the
'default' and what isn't. Personally, I'd have started from a clean
{{pylintrc}} and then added stuff based on which errors we think are spurious,
but I dunno if it's worth taking the time to go through this exercise if
there's not much value to be gained.
> Add pylintrc file to HBase
> --
>
> Key: HBASE-18041
> URL: https://issues.apache.org/jira/browse/HBASE-18041
> Project: HBase
> Issue Type: Improvement
> Components: community
>Reporter: Alex Leblang
>Assignee: Alex Leblang
> Attachments: HBASE-18041.branch-1.2.001.patch
>
>
> Yetus runs all commits with python files through a linter. I think that the
> HBase community should add a pylintrc file to actively choose the project's
> python style instead of just relying on yetus defaults.
> As an argument for this, the yetus project itself doesn't even use the
> default python linter for its own commits.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (HBASE-15930) Make IntegrationTestReplication's waitForReplication() smarter
[
https://issues.apache.org/jira/browse/HBASE-15930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak reassigned HBASE-15930:
---
Assignee: Mike Drob (was: Dima Spivak)
Please go ahead. Sorry, I've fallen off the face of the HBase planet. :)
> Make IntegrationTestReplication's waitForReplication() smarter
> --
>
> Key: HBASE-15930
> URL: https://issues.apache.org/jira/browse/HBASE-15930
> Project: HBase
> Issue Type: Improvement
> Components: integration tests
>Reporter: Dima Spivak
>Assignee: Mike Drob
> Fix For: 2.0.0
>
>
> {{IntegrationTestReplication}} is a great test, but can improved by changing
> how we handle waiting between generation of the linked list on the source
> cluster and verifying the linked list on the destination cluster. [Even the
> code suggests this should be
> done|https://github.com/apache/hbase/blob/master/hbase-it/src/test/java/org/apache/hadoop/hbase/test/IntegrationTestReplication.java#L251-252],
> so I'd like to take it on. [~mbertozzi] and [~busbey] have both suggested a
> simple solution wherein we write a row into each region on the source cluster
> after the linked list generation and then assume replication has gone through
> once these rows are detected on the destination cluster.
> Since you lads at Facebook are some of the heaviest users, [~eclark], would
> you prefer I maintain the API and add a new command line option (say {{\-c |
> \-\-check-replication}}) that would run before any {{--generateVerifyGap}}
> sleep is carried out as it is now?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-18041) Add pylintrc file to HBase
[ https://issues.apache.org/jira/browse/HBASE-18041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008860#comment-16008860 ] Dima Spivak commented on HBASE-18041: - Are we disabling a bunch of Pylint checks because the current code sucks? That seems like a bad idea. We should let it raise all kinds of errors and then open separate JIRAs to address them, I'd think. > Add pylintrc file to HBase > -- > > Key: HBASE-18041 > URL: https://issues.apache.org/jira/browse/HBASE-18041 > Project: HBase > Issue Type: Improvement > Components: community >Reporter: Alex Leblang >Assignee: Alex Leblang > Attachments: HBASE-18041.branch-1.2.001.patch > > > Yetus runs all commits with python files through a linter. I think that the > HBase community should add a pylintrc file to actively choose the project's > python style instead of just relying on yetus defaults. > As an argument for this, the yetus project itself doesn't even use the > default python linter for its own commits. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-18041) Add pylintrc file to HBase
[ https://issues.apache.org/jira/browse/HBASE-18041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008644#comment-16008644 ] Dima Spivak commented on HBASE-18041: - Yep, no problem. > Add pylintrc file to HBase > -- > > Key: HBASE-18041 > URL: https://issues.apache.org/jira/browse/HBASE-18041 > Project: HBase > Issue Type: Improvement > Components: community >Reporter: Alex Leblang > > Yetus runs all commits with python files through a linter. I think that the > HBase community should add a pylintrc file to actively choose the project's > python style instead of just relying on yetus defaults. > As an argument for this, the yetus project itself doesn't even use the > default python linter for its own commits. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (HBASE-18041) Add pylintrc file to HBase
[ https://issues.apache.org/jira/browse/HBASE-18041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-18041: --- Assignee: Alex Leblang > Add pylintrc file to HBase > -- > > Key: HBASE-18041 > URL: https://issues.apache.org/jira/browse/HBASE-18041 > Project: HBase > Issue Type: Improvement > Components: community >Reporter: Alex Leblang >Assignee: Alex Leblang > > Yetus runs all commits with python files through a linter. I think that the > HBase community should add a pylintrc file to actively choose the project's > python style instead of just relying on yetus defaults. > As an argument for this, the yetus project itself doesn't even use the > default python linter for its own commits. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-18041) Add pylintrc file to HBase
[ https://issues.apache.org/jira/browse/HBASE-18041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008616#comment-16008616 ] Dima Spivak commented on HBASE-18041: - Default is 4 spaces (that's a PEP 8 thing). > Add pylintrc file to HBase > -- > > Key: HBASE-18041 > URL: https://issues.apache.org/jira/browse/HBASE-18041 > Project: HBase > Issue Type: Improvement > Components: community >Reporter: Alex Leblang > > Yetus runs all commits with python files through a linter. I think that the > HBase community should add a pylintrc file to actively choose the project's > python style instead of just relying on yetus defaults. > As an argument for this, the yetus project itself doesn't even use the > default python linter for its own commits. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-18020) Update API Compliance Checker to Incorporate Improvements Done in Hadoop
[
https://issues.apache.org/jira/browse/HBASE-18020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007307#comment-16007307
]
Dima Spivak commented on HBASE-18020:
-
I guess what I'm saying is that the effort to convert this patch from Python 2
to Python 3 will be minimal, but by doing so, you'll be able to make certain
assumptions that will aid significantly in readability. For example,
{{argparse}} is part of the Python 3 standard library, so there'd be no need to
worry about not being able to import it. Furthermore, using {{os.path}} is
gross and awful and exactly why Python 3 has {{pathlib}}. Just my two cents.
> Update API Compliance Checker to Incorporate Improvements Done in Hadoop
>
>
> Key: HBASE-18020
> URL: https://issues.apache.org/jira/browse/HBASE-18020
> Project: HBase
> Issue Type: Improvement
> Components: API, community
>Reporter: Alex Leblang
>Assignee: Alex Leblang
> Fix For: 2.0.0
>
> Attachments: HBASE-18020.0.patch
>
>
> Recently the Hadoop community has made a number of improvements in their api
> compliance checker based on feedback from the hbase and kudu community. We
> should adopt these changes ourselves.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-18020) Update API Compliance Checker to Incorporate Improvements Done in Hadoop
[ https://issues.apache.org/jira/browse/HBASE-18020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007288#comment-16007288 ] Dima Spivak commented on HBASE-18020: - I'd generally go with 4 spaces because it is (IMHO) much more readable for a language that requires indentation. I'd be happy to mentor on any Python 3 refactor. I can say from my recent work that the effort required is minimal and the benefits have been substantial because of the greatly-expanded standard library. > Update API Compliance Checker to Incorporate Improvements Done in Hadoop > > > Key: HBASE-18020 > URL: https://issues.apache.org/jira/browse/HBASE-18020 > Project: HBase > Issue Type: Improvement > Components: API, community >Reporter: Alex Leblang >Assignee: Alex Leblang > Fix For: 2.0.0 > > Attachments: HBASE-18020.0.patch > > > Recently the Hadoop community has made a number of improvements in their api > compliance checker based on feedback from the hbase and kudu community. We > should adopt these changes ourselves. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-18020) Update API Compliance Checker to Incorporate Improvements Done in Hadoop
[ https://issues.apache.org/jira/browse/HBASE-18020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003926#comment-16003926 ] Dima Spivak commented on HBASE-18020: - Some thoughts from a brief glance: 1. Can you put this up on Apache's Review Board? 2. Yay for using code from other projects, but are we sure we don't want to use Python 3 for this? Lots of lines of code in this patch could be removed/the whole thing made significantly more readable with some of the constructs introduced in Python 3 and, seeing as how we control our test environment with Docker and the like, there's no compelling reason not to use it. (Also, Python 3 has been out for ten years. It's time to use it.) > Update API Compliance Checker to Incorporate Improvements Done in Hadoop > > > Key: HBASE-18020 > URL: https://issues.apache.org/jira/browse/HBASE-18020 > Project: HBase > Issue Type: Improvement > Components: API, community >Reporter: Alex Leblang >Assignee: Alex Leblang > Fix For: 2.0.0 > > Attachments: HBASE-18020.0.patch > > > Recently the Hadoop community has made a number of improvements in their api > compliance checker based on feedback from the hbase and kudu community. We > should adopt these changes ourselves. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-15936) Sort out how to push to apache/ repositories on Docker Hub
[ https://issues.apache.org/jira/browse/HBASE-15936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965031#comment-15965031 ] Dima Spivak commented on HBASE-15936: - [~clehene] We decided against pushing HBase images to Docker Hub since our goal was to handle testing of in-progress releases as opposed to for distribution. > Sort out how to push to apache/ repositories on Docker Hub > -- > > Key: HBASE-15936 > URL: https://issues.apache.org/jira/browse/HBASE-15936 > Project: HBase > Issue Type: Sub-task > Components: build >Reporter: Dima Spivak >Assignee: Dima Spivak > Labels: docker > > It looks like there's already a [Docker Hub username for Apache > stuff|https://hub.docker.com/r/apache/]. We should figure out how to use it > to push the Docker images we use/build for testing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (HBASE-16441) Document use of Apache HBase clusterdock topology
[ https://issues.apache.org/jira/browse/HBASE-16441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak reassigned HBASE-16441: --- Assignee: (was: Dima Spivak) > Document use of Apache HBase clusterdock topology > - > > Key: HBASE-16441 > URL: https://issues.apache.org/jira/browse/HBASE-16441 > Project: HBase > Issue Type: New Feature > Components: documentation >Reporter: Dima Spivak > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-16441) Document use of Apache HBase clusterdock topology
[ https://issues.apache.org/jira/browse/HBASE-16441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940810#comment-15940810 ] Dima Spivak commented on HBASE-16441: - Correct. Would you like to take it on, [~awleblang]? > Document use of Apache HBase clusterdock topology > - > > Key: HBASE-16441 > URL: https://issues.apache.org/jira/browse/HBASE-16441 > Project: HBase > Issue Type: New Feature > Components: documentation >Reporter: Dima Spivak >Assignee: Dima Spivak > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (HBASE-17659) How to connect to hbase hdfs filesystem
[ https://issues.apache.org/jira/browse/HBASE-17659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak resolved HBASE-17659. - Resolution: Not A Problem Please use the user mailing list for questions about getting HBase up and running. > How to connect to hbase hdfs filesystem > --- > > Key: HBASE-17659 > URL: https://issues.apache.org/jira/browse/HBASE-17659 > Project: HBase > Issue Type: Task > Components: API >Affects Versions: 0.94.7 >Reporter: Jenson Luke >Priority: Blocker > > I am not able to connect to HBASE hdfs file system. When I run my Java > program through server, it is picking up the local file system instead of > hdfs file system. > while Running through Server, I am passing only > conf = HBaseConfiguration.create(); > fs = FileSystem.get(this.conf); > Path tabledir = new Path(fs.makeQualified(new > Path(conf.get(HConstants.HBASE_DIR))), tableName); > It is giving the value of tabledir as > "/tmp/hbase-hbase/hbase/tsdb-uid_jentab_bkp1_scen06" > My actual hdfs path is "hdfs://ibdash-.xx.xx..net:8020/hbase". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-12852) Tests from hbase-it that use ChaosMonkey don't fail if SSH commands fail
[
https://issues.apache.org/jira/browse/HBASE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816839#comment-15816839
]
Dima Spivak commented on HBASE-12852:
-
Wanna take this one over [~awleblang]? I recently switched jobs and don't think
I'll get time for this anytime soon.
> Tests from hbase-it that use ChaosMonkey don't fail if SSH commands fail
>
>
> Key: HBASE-12852
> URL: https://issues.apache.org/jira/browse/HBASE-12852
> Project: HBase
> Issue Type: Bug
> Components: integration tests
>Affects Versions: 0.98.6
>Reporter: Dima Spivak
>Assignee: Dima Spivak
>
> I've just started rolling my sleeves up and playing about with hbase-it (at
> the moment, only on 0.98.6), but wanted to begin filing JIRAs for issues I
> encounter so that I don't forget to get to them. First up is the fact that it
> seems that tests run with ChaosMonkey don't fail when the ChaosMonkey fails
> to work. As an example, while running IntegrationTestIngest with a
> slowDeterministic CM, I forgot to set up SSH properly and saw the following:
> {code}
> 15/01/14 07:36:53 WARN hbase.ClusterManager: Remote command: ps aux | grep
> proc_regionserver | grep -v grep | tr -s ' ' | cut -d ' ' -f2 | xargs kill -s
> SIGKILL , hostname:node-5.internal failed at attempt 4. Retrying until
> maxAttempts: 5. Exception: stderr: Permission denied, please try again.
> Permission denied, please try again.
> Permission denied (publickey,password).
> , stdout:
> 15/01/14 07:36:53 INFO util.RetryCounter: Sleeping 16000ms before retry #4...
> 15/01/14 07:36:53 INFO zookeeper.ZooKeeper: Session: 0x14ae74d7bac006b closed
> 15/01/14 07:36:53 INFO policies.Policy: Sleeping for: 59541
> 15/01/14 07:36:53 INFO zookeeper.ClientCnxn: EventThread shut down
> Failed to write keys: 0
> Key range: [15..15]
> Batch updates: false
> Percent of keys to update: 60
> Updater threads: 10
> Ignore nonce conflicts: true
> Regions per server: 5
> 15/01/14 07:36:56 INFO util.LoadTestTool: Starting to mutate data...
> Starting to mutate data...
> 15/01/14 07:36:57 INFO policies.Policy: Sleeping for: 88816
> 15/01/14 07:37:01 INFO util.MultiThreadedAction: [U:10] Keys=471, cols=5.7 K,
> time=00:00:05 Overall: [keys/s= 94, latency=102 ms] Current: [keys/s=94,
> latency=102 ms], wroteUpTo=14
> 15/01/14 07:37:06 INFO util.MultiThreadedAction: [U:10] Keys=908, cols=11.0
> K, time=00:00:10 Overall: [keys/s= 90, latency=90 ms] Current: [keys/s=87,
> latency=77 ms], wroteUpTo=14
> 15/01/14 07:37:09 INFO hbase.ClusterManager: Executing remote command: ps aux
> | grep proc_regionserver | grep -v grep | tr -s ' ' | cut -d ' ' -f2 | xargs
> kill -s SIGKILL , hostname:node-5.internal
> 15/01/14 07:37:09 INFO util.Shell: Executing full command [/usr/bin/ssh
> node-5.internal "ps aux | grep proc_regionserver | grep -v grep | tr -s ' ' |
> cut -d ' ' -f2 | xargs kill -s SIGKILL"]
> 15/01/14 07:37:09 WARN policies.Policy: Exception occured during performing
> action: ExitCodeException exitCode=255: stderr: Permission denied, please try
> again.
> Permission denied, please try again.
> Permission denied (publickey,password).
> , stdout:
> at
> org.apache.hadoop.hbase.HBaseClusterManager.exec(HBaseClusterManager.java:208)
> at
> org.apache.hadoop.hbase.HBaseClusterManager.execWithRetries(HBaseClusterManager.java:223)
> at
> org.apache.hadoop.hbase.HBaseClusterManager.signal(HBaseClusterManager.java:268)
> at org.apache.hadoop.hbase.ClusterManager.kill(ClusterManager.java:97)
> at
> org.apache.hadoop.hbase.DistributedHBaseCluster.killRegionServer(DistributedHBaseCluster.java:110)
> at org.apache.hadoop.hbase.chaos.actions.Action.killRs(Action.java:84)
> at
> org.apache.hadoop.hbase.chaos.actions.RestartActionBaseAction.restartRs(RestartActionBaseAction.java:50)
> at
> org.apache.hadoop.hbase.chaos.actions.RestartRsHoldingMetaAction.perform(RestartRsHoldingMetaAction.java:38)
> at
> org.apache.hadoop.hbase.chaos.policies.DoActionsOncePolicy.runOneIteration(DoActionsOncePolicy.java:50)
> at
> org.apache.hadoop.hbase.chaos.policies.PeriodicPolicy.run(PeriodicPolicy.java:41)
> at
> org.apache.hadoop.hbase.chaos.policies.CompositeSequentialPolicy.run(CompositeSequentialPolicy.java:42)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Seems to me that tests should fail in these instances rather than just toss a
> warning. Was this just an oversight, [~enis] and [~ndimiduk], or is this by
> design?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-16936) TestRateLimiter#testOverconsumptionFixedIntervalRefillStrategy is flaky
Dima Spivak created HBASE-16936:
---
Summary:
TestRateLimiter#testOverconsumptionFixedIntervalRefillStrategy is flaky
Key: HBASE-16936
URL: https://issues.apache.org/jira/browse/HBASE-16936
Project: HBase
Issue Type: Bug
Components: test
Reporter: Dima Spivak
Seeing this once every month or two in-house. Looks like it's a timing-based
test, which makes it prone to flakiness, but I've noticed that whenever it
fails, it fails with the same {{AssertionError}} (including values), so it'd be
worth digging into. In our case:
{noformat}
expected:<1000> but was:<999>
Stack Trace:
java.lang.AssertionError: expected:<1000> but was:<999>
at
org.apache.hadoop.hbase.quotas.TestRateLimiter.testOverconsumptionFixedIntervalRefillStrategy(TestRateLimiter.java:119)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-16875) Cleanup docs' use of try-with-resources
Dima Spivak created HBASE-16875: --- Summary: Cleanup docs' use of try-with-resources Key: HBASE-16875 URL: https://issues.apache.org/jira/browse/HBASE-16875 Project: HBase Issue Type: Bug Components: documentation Reporter: Dima Spivak Priority: Trivial In a [number|https://github.com/apache/hbase/blame/bb3d9ccd489fb64e3cb2020583935a393382a678/src/main/asciidoc/_chapters/security.adoc#L205-L206] [of|https://github.com/apache/hbase/blame/bb3d9ccd489fb64e3cb2020583935a393382a678/src/main/asciidoc/_chapters/security.adoc#L1019-L1020] [places|https://github.com/apache/hbase/blame/bb3d9ccd489fb64e3cb2020583935a393382a678/src/main/asciidoc/_chapters/architecture.adoc#L222-L223], we show examples that lend themselves to using Java 7's try-with-resources statement, but we use the statement in a less-than-ideal nested way. Let's change our docs throughout to do it [the recommended way|https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-16842) Chaos policies can terminate all masters for extended periods of time
[
https://issues.apache.org/jira/browse/HBASE-16842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576447#comment-15576447
]
Dima Spivak commented on HBASE-16842:
-
We started seeing this behavior in-house at Cloudera starting with CDH 5.7,
when we rebased onto HBase 1.2, though I should note we sometimes saw it with
the {{calm}} monkey, as well. This would suggest stability problems with the
HBase master, though I haven't opened a separate JIRA as we didn't get any
useful logging to go along with the isolated failures we saw.
> Chaos policies can terminate all masters for extended periods of time
> -
>
> Key: HBASE-16842
> URL: https://issues.apache.org/jira/browse/HBASE-16842
> Project: HBase
> Issue Type: Bug
> Components: integration tests
>Reporter: Andrew Purtell
>
> Running ITBLL with the slowDeterministic monkey I observe our primary and
> backup masters in the test cluster can be both shut down by signals followed
> by no attempt to start replacements for an extended period of time. Meanwhile
> other actions continue to run that churn the regionserver fleet. Other
> monkeys may enter a similar state, but I haven't observed it. The outcome of
> the convergence of these behaviors is the eventual time out and termination
> of the running integration test, which is obvious and expected and unhelpful,
> so I believe unintentional.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-16750) hbase compilation failed on power system
[
https://issues.apache.org/jira/browse/HBASE-16750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562685#comment-15562685
]
Dima Spivak commented on HBASE-16750:
-
The link is at the bottom of the daily email to {{dev@}}. For posterity, the
failed build on {{ubuntu-5}} from earlier today is
[here|https://builds.apache.org/job/hbase_generate_website/372/]. After
[reverting your
commit|https://github.com/apache/hbase/commit/3c35a722d9c1c77826d7c86ee204274bfdaae65f],
[a build on {{H1}}
succeeded|https://builds.apache.org/job/hbase_generate_website/373/], despite
another build on the same machine [failing a few days back
|https://builds.apache.org/job/hbase_generate_website/370/] with the same
{{org.jruby.exceptions.RaiseException: (NotImplementedError) fstat
unimplemented unsupported or native support failed to load}} error when the
commit was present.
> hbase compilation failed on power system
>
>
> Key: HBASE-16750
> URL: https://issues.apache.org/jira/browse/HBASE-16750
> Project: HBase
> Issue Type: Bug
> Components: build, documentation
>Affects Versions: 1.1.2
>Reporter: Saravanan Krishnamoorthy
>Assignee: Saravanan Krishnamoorthy
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-16750.branch-1.patch, HBASE-16750.master.patch,
> apache_hbase_reference_guide.pdf, apache_hbase_reference_guide.pdfmarks,
> book.pdf, book.pdfmarks
>
>
> Hi,
> hbase compilation failed on IBM power system ppc64le architecture with below
> error:
> {code}
> Hbase Failure:
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:33 min
> [INFO] Finished at: 2016-09-30T08:58:47-04:00
> [INFO] Final Memory: 215M/843M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> o
[jira] [Reopened] (HBASE-16750) hbase compilation failed on power system
[
https://issues.apache.org/jira/browse/HBASE-16750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak reopened HBASE-16750:
-
Build #372 on {{ubuntu-5}} was also red, so I've reverted the last commit done
for this JIRA to try to get our website builds back to green. A deeper analysis
of the dependency tree changes introduced by this fix needs to be done. If
there's no interest in doing that, let's just close this as won't fix.
> hbase compilation failed on power system
>
>
> Key: HBASE-16750
> URL: https://issues.apache.org/jira/browse/HBASE-16750
> Project: HBase
> Issue Type: Bug
> Components: build, documentation
>Affects Versions: 1.1.2
>Reporter: Saravanan Krishnamoorthy
>Assignee: Saravanan Krishnamoorthy
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-16750.branch-1.patch, HBASE-16750.master.patch,
> apache_hbase_reference_guide.pdf, apache_hbase_reference_guide.pdfmarks,
> book.pdf, book.pdfmarks
>
>
> Hi,
> hbase compilation failed on IBM power system ppc64le architecture with below
> error:
> {code}
> Hbase Failure:
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:33 min
> [INFO] Finished at: 2016-09-30T08:58:47-04:00
> [INFO] Final Memory: 215M/843M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: org.jruby.exceptions.RaiseException: (NotImplementedError) fstat
> unimplemented unsupported or native support failed to load
> at org.jruby.RubyFile.size(org/jruby/RubyFile.java:1108)
> at
> RUBY.render_body(/grid/0/j
[jira] [Closed] (HBASE-16753) There is a mismatch between suggested Java version in hbase-env.sh
[
https://issues.apache.org/jira/browse/HBASE-16753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak closed HBASE-16753.
---
> There is a mismatch between suggested Java version in hbase-env.sh
> --
>
> Key: HBASE-16753
> URL: https://issues.apache.org/jira/browse/HBASE-16753
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 1.2.3
>Reporter: Umesh Agashe
>Assignee: Umesh Agashe
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16753.v1.patch, HBASE-16753.v2.patch,
> HBASE-16753.v3.patch, HBASE-16753.v4.patch
>
>
> There is a mismatch between suggested JAVA version and default in comments in
> hbase-env.sh:
> {code}
> # The java implementation to use. Java 1.7+ required.
> # export JAVA_HOME=/usr/java/jdk1.6.0/
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-16753) There is a mismatch between suggested Java version in hbase-env.sh
[
https://issues.apache.org/jira/browse/HBASE-16753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak updated HBASE-16753:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the patch, [~uagashe] and thanks [~anoop.hbase] for the review!
> There is a mismatch between suggested Java version in hbase-env.sh
> --
>
> Key: HBASE-16753
> URL: https://issues.apache.org/jira/browse/HBASE-16753
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 1.2.3
>Reporter: Umesh Agashe
>Assignee: Umesh Agashe
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16753.v1.patch, HBASE-16753.v2.patch,
> HBASE-16753.v3.patch, HBASE-16753.v4.patch
>
>
> There is a mismatch between suggested JAVA version and default in comments in
> hbase-env.sh:
> {code}
> # The java implementation to use. Java 1.7+ required.
> # export JAVA_HOME=/usr/java/jdk1.6.0/
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-16753) There is a mismatch between suggested Java version in hbase-env.sh
[
https://issues.apache.org/jira/browse/HBASE-16753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak updated HBASE-16753:
Fix Version/s: 2.0.0
> There is a mismatch between suggested Java version in hbase-env.sh
> --
>
> Key: HBASE-16753
> URL: https://issues.apache.org/jira/browse/HBASE-16753
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 1.2.3
>Reporter: Umesh Agashe
>Assignee: Umesh Agashe
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16753.v1.patch, HBASE-16753.v2.patch,
> HBASE-16753.v3.patch, HBASE-16753.v4.patch
>
>
> There is a mismatch between suggested JAVA version and default in comments in
> hbase-env.sh:
> {code}
> # The java implementation to use. Java 1.7+ required.
> # export JAVA_HOME=/usr/java/jdk1.6.0/
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-16753) There is a mismatch between suggested Java version in hbase-env.sh
[
https://issues.apache.org/jira/browse/HBASE-16753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak updated HBASE-16753:
Release Note: Updates the comments and default values in a few scripts and
docs to reflect our Java 1.8+ requirement. (was: Updates the comments and
default values in)
> There is a mismatch between suggested Java version in hbase-env.sh
> --
>
> Key: HBASE-16753
> URL: https://issues.apache.org/jira/browse/HBASE-16753
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 1.2.3
>Reporter: Umesh Agashe
>Assignee: Umesh Agashe
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16753.v1.patch, HBASE-16753.v2.patch,
> HBASE-16753.v3.patch, HBASE-16753.v4.patch
>
>
> There is a mismatch between suggested JAVA version and default in comments in
> hbase-env.sh:
> {code}
> # The java implementation to use. Java 1.7+ required.
> # export JAVA_HOME=/usr/java/jdk1.6.0/
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-16753) There is a mismatch between suggested Java version in hbase-env.sh
[
https://issues.apache.org/jira/browse/HBASE-16753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak updated HBASE-16753:
Release Note: Updates the comments and default values in (was: The java
implementation to use. Java 1.7+ required.)
> There is a mismatch between suggested Java version in hbase-env.sh
> --
>
> Key: HBASE-16753
> URL: https://issues.apache.org/jira/browse/HBASE-16753
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 1.2.3
>Reporter: Umesh Agashe
>Assignee: Umesh Agashe
>Priority: Minor
> Attachments: HBASE-16753.v1.patch, HBASE-16753.v2.patch,
> HBASE-16753.v3.patch, HBASE-16753.v4.patch
>
>
> There is a mismatch between suggested JAVA version and default in comments in
> hbase-env.sh:
> {code}
> # The java implementation to use. Java 1.7+ required.
> # export JAVA_HOME=/usr/java/jdk1.6.0/
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-16753) There is a mismatch between suggested Java version in hbase-env.sh
[
https://issues.apache.org/jira/browse/HBASE-16753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15546253#comment-15546253
]
Dima Spivak commented on HBASE-16753:
-
+1 from me. I'll push to master later today if no one objects.
> There is a mismatch between suggested Java version in hbase-env.sh
> --
>
> Key: HBASE-16753
> URL: https://issues.apache.org/jira/browse/HBASE-16753
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 1.2.3
>Reporter: Umesh Agashe
>Assignee: Umesh Agashe
>Priority: Minor
> Attachments: HBASE-16753.v1.patch, HBASE-16753.v2.patch,
> HBASE-16753.v3.patch
>
>
> There is a mismatch between suggested JAVA version and default in comments in
> hbase-env.sh:
> {code}
> # The java implementation to use. Java 1.7+ required.
> # export JAVA_HOME=/usr/java/jdk1.6.0/
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-16753) There is a mismatch between suggested Java version in hbase-env.sh
[
https://issues.apache.org/jira/browse/HBASE-16753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543490#comment-15543490
]
Dima Spivak commented on HBASE-16753:
-
I think we'll want to move this up to Java 1.8+ on {{master}}, right?
> There is a mismatch between suggested Java version in hbase-env.sh
> --
>
> Key: HBASE-16753
> URL: https://issues.apache.org/jira/browse/HBASE-16753
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 1.2.3
>Reporter: Umesh Agashe
>Assignee: Umesh Agashe
>Priority: Minor
> Attachments: HBASE-16753.v1.patch
>
>
> There is a mismatch between suggested JAVA version and default in comments in
> hbase-env.sh:
> {code}
> # The java implementation to use. Java 1.7+ required.
> # export JAVA_HOME=/usr/java/jdk1.6.0/
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-16750) hbase compilation failed
[
https://issues.apache.org/jira/browse/HBASE-16750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak updated HBASE-16750:
Assignee: Saravanan Krishnamoorthy
> hbase compilation failed
>
>
> Key: HBASE-16750
> URL: https://issues.apache.org/jira/browse/HBASE-16750
> Project: HBase
> Issue Type: Bug
> Components: build, documentation
>Affects Versions: 1.1.2
>Reporter: Saravanan Krishnamoorthy
>Assignee: Saravanan Krishnamoorthy
> Fix For: 1.1.2
>
> Attachments: HBASE-16750.patch
>
>
> Hi,
> hbase compilation failed on IBM power system ppc64le architecture with below
> error:
> {code}
> Hbase Failure:
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:33 min
> [INFO] Finished at: 2016-09-30T08:58:47-04:00
> [INFO] Final Memory: 215M/843M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: org.jruby.exceptions.RaiseException: (NotImplementedError) fstat
> unimplemented unsupported or native support failed to load
> at org.jruby.RubyFile.size(org/jruby/RubyFile.java:1108)
> at
> RUBY.render_body(/grid/0/jenkins/.m2/repository/org/asciidoctor/asciidoctorj-pdf/1.5.0-alpha.6/asciidoctorj-pdf-1.5.0-alpha.6.jar!/gems/pdf-core-0.2.5/lib/pdf/core/document_state.rb:69)
> at
> RUBY.each(/grid/0/jenkins/.m2/repository/org/asciidoctor/asciidoctorj-pdf/1.5.0-alpha.6/asciidoctorj-pdf-1.5.0-alpha.6.jar!/gems/pdf-core-0.2.5/lib/pdf/core/object_store.rb:70)
> at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1613)
> at
> RUBY.each(/grid/0/
[jira] [Updated] (HBASE-16750) hbase compilation failed
[
https://issues.apache.org/jira/browse/HBASE-16750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak updated HBASE-16750:
Status: Patch Available (was: Open)
> hbase compilation failed
>
>
> Key: HBASE-16750
> URL: https://issues.apache.org/jira/browse/HBASE-16750
> Project: HBase
> Issue Type: Bug
> Components: build, documentation
>Affects Versions: 1.1.2
>Reporter: Saravanan Krishnamoorthy
> Fix For: 1.1.2
>
> Attachments: HBASE-16750.patch
>
>
> Hi,
> hbase compilation failed on IBM power system ppc64le architecture with below
> error:
> {code}
> Hbase Failure:
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:33 min
> [INFO] Finished at: 2016-09-30T08:58:47-04:00
> [INFO] Final Memory: 215M/843M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: org.jruby.exceptions.RaiseException: (NotImplementedError) fstat
> unimplemented unsupported or native support failed to load
> at org.jruby.RubyFile.size(org/jruby/RubyFile.java:1108)
> at
> RUBY.render_body(/grid/0/jenkins/.m2/repository/org/asciidoctor/asciidoctorj-pdf/1.5.0-alpha.6/asciidoctorj-pdf-1.5.0-alpha.6.jar!/gems/pdf-core-0.2.5/lib/pdf/core/document_state.rb:69)
> at
> RUBY.each(/grid/0/jenkins/.m2/repository/org/asciidoctor/asciidoctorj-pdf/1.5.0-alpha.6/asciidoctorj-pdf-1.5.0-alpha.6.jar!/gems/pdf-core-0.2.5/lib/pdf/core/object_store.rb:70)
> at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1613)
> at
> RUBY.each(/grid/0/jenkins/.m2/repository/org/asciidoctor/asciido
[jira] [Commented] (HBASE-16750) hbase compilation failed
[
https://issues.apache.org/jira/browse/HBASE-16750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543076#comment-15543076
]
Dima Spivak commented on HBASE-16750:
-
Any concerns with this, [~misty]?
> hbase compilation failed
>
>
> Key: HBASE-16750
> URL: https://issues.apache.org/jira/browse/HBASE-16750
> Project: HBase
> Issue Type: Bug
> Components: build, documentation
>Affects Versions: 1.1.2
>Reporter: Saravanan Krishnamoorthy
> Fix For: 1.1.2
>
> Attachments: HBASE-16750.patch
>
>
> Hi,
> hbase compilation failed on IBM power system ppc64le architecture with below
> error:
> {code}
> Hbase Failure:
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:33 min
> [INFO] Finished at: 2016-09-30T08:58:47-04:00
> [INFO] Final Memory: 215M/843M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: org.jruby.exceptions.RaiseException: (NotImplementedError) fstat
> unimplemented unsupported or native support failed to load
> at org.jruby.RubyFile.size(org/jruby/RubyFile.java:1108)
> at
> RUBY.render_body(/grid/0/jenkins/.m2/repository/org/asciidoctor/asciidoctorj-pdf/1.5.0-alpha.6/asciidoctorj-pdf-1.5.0-alpha.6.jar!/gems/pdf-core-0.2.5/lib/pdf/core/document_state.rb:69)
> at
> RUBY.each(/grid/0/jenkins/.m2/repository/org/asciidoctor/asciidoctorj-pdf/1.5.0-alpha.6/asciidoctorj-pdf-1.5.0-alpha.6.jar!/gems/pdf-core-0.2.5/lib/pdf/core/object_store.rb:70)
> at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1613)
> at
> RUBY.each(/gr
[jira] [Updated] (HBASE-16750) hbase compilation failed
[
https://issues.apache.org/jira/browse/HBASE-16750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak updated HBASE-16750:
Component/s: (was: hbase)
documentation
build
> hbase compilation failed
>
>
> Key: HBASE-16750
> URL: https://issues.apache.org/jira/browse/HBASE-16750
> Project: HBase
> Issue Type: Bug
> Components: build, documentation
>Affects Versions: 1.1.2
>Reporter: Saravanan Krishnamoorthy
> Fix For: 1.1.2
>
> Attachments: HBASE-16750.patch
>
>
> Hi,
> hbase compilation failed on IBM power system ppc64le architecture with below
> error:
> {code}
> Hbase Failure:
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:33 min
> [INFO] Finished at: 2016-09-30T08:58:47-04:00
> [INFO] Final Memory: 215M/843M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: org.jruby.exceptions.RaiseException: (NotImplementedError) fstat
> unimplemented unsupported or native support failed to load
> at org.jruby.RubyFile.size(org/jruby/RubyFile.java:1108)
> at
> RUBY.render_body(/grid/0/jenkins/.m2/repository/org/asciidoctor/asciidoctorj-pdf/1.5.0-alpha.6/asciidoctorj-pdf-1.5.0-alpha.6.jar!/gems/pdf-core-0.2.5/lib/pdf/core/document_state.rb:69)
> at
> RUBY.each(/grid/0/jenkins/.m2/repository/org/asciidoctor/asciidoctorj-pdf/1.5.0-alpha.6/asciidoctorj-pdf-1.5.0-alpha.6.jar!/gems/pdf-core-0.2.5/lib/pdf/core/object_store.rb:70)
> at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1613)
> at
> RUBY.each(/grid/0
[jira] [Updated] (HBASE-16750) hbase compilation failed
[
https://issues.apache.org/jira/browse/HBASE-16750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak updated HBASE-16750:
Labels: (was: patch)
> hbase compilation failed
>
>
> Key: HBASE-16750
> URL: https://issues.apache.org/jira/browse/HBASE-16750
> Project: HBase
> Issue Type: Bug
> Components: hbase
>Affects Versions: 1.1.2
>Reporter: Saravanan Krishnamoorthy
> Fix For: 1.1.2
>
> Attachments: HBASE-16750.patch
>
>
> Hi,
> hbase compilation failed on IBM power system ppc64le architecture with below
> error:
> {code}
> Hbase Failure:
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:33 min
> [INFO] Finished at: 2016-09-30T08:58:47-04:00
> [INFO] Final Memory: 215M/843M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: org.jruby.exceptions.RaiseException: (NotImplementedError) fstat
> unimplemented unsupported or native support failed to load
> at org.jruby.RubyFile.size(org/jruby/RubyFile.java:1108)
> at
> RUBY.render_body(/grid/0/jenkins/.m2/repository/org/asciidoctor/asciidoctorj-pdf/1.5.0-alpha.6/asciidoctorj-pdf-1.5.0-alpha.6.jar!/gems/pdf-core-0.2.5/lib/pdf/core/document_state.rb:69)
> at
> RUBY.each(/grid/0/jenkins/.m2/repository/org/asciidoctor/asciidoctorj-pdf/1.5.0-alpha.6/asciidoctorj-pdf-1.5.0-alpha.6.jar!/gems/pdf-core-0.2.5/lib/pdf/core/object_store.rb:70)
> at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1613)
> at
> RUBY.each(/grid/0/jenkins/.m2/repository/org/asciidoctor/asciidoctorj-pdf/1.5.0-alpha.6/ascii
[jira] [Commented] (HBASE-16720) Sort build ids in flaky dashboard
[ https://issues.apache.org/jira/browse/HBASE-16720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527408#comment-15527408 ] Dima Spivak commented on HBASE-16720: - +1. > Sort build ids in flaky dashboard > - > > Key: HBASE-16720 > URL: https://issues.apache.org/jira/browse/HBASE-16720 > Project: HBase > Issue Type: Improvement >Reporter: Appy >Assignee: Appy >Priority: Minor > Attachments: HBASE-16720.master.001.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-16676) All RPC requests serviced by PriorityRpcServer in some deploys after HBASE-13375
[ https://issues.apache.org/jira/browse/HBASE-16676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15514596#comment-15514596 ] Dima Spivak commented on HBASE-16676: - Wow, awesome find, [~apurtell]! As [~stack] mentioned, I saw reproducible failures in the generator phase of ITBLL while testing 1.2.3, but just assumed something was wrong with my machine. Time for me to start trusting tests more :). > All RPC requests serviced by PriorityRpcServer in some deploys after > HBASE-13375 > > > Key: HBASE-16676 > URL: https://issues.apache.org/jira/browse/HBASE-16676 > Project: HBase > Issue Type: Bug >Affects Versions: 1.2.0, 1.2.1, 1.2.2, 1.2.3 >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 1.2.4 > > Attachments: HBASE-16676-branch-1.2.patch > > > I have been trying to track down why 1.2.x won't sometimes pass a 1 billion > row ITBLL run while 0.98.22 and 1.1.6 will always, and a defeat of RPC > prioritization could explain it. We get stuck during the loading phase and > the loader job eventually fails. > All testing is done in an insecure environment under the same UNIX user > (clusterdock) so effectively all ops are issued by the superuser. > Doing unrelated work - or so I thought! - I was looking at object allocations > by YCSB workload by thread and when looking at the RegionServer RPC threads > noticed that for 0.98.22 and 1.1.6, as expected, the vast majority of > allocations are from threads named "B.defaultRpcServer.handler*". In 1.2.0 > and up, instead the vast majority are from threads named > "PriorityRpcServer.handler*" with very little from threads named > "B.defaultRpcServer.handler*". A git bisect to find the change that causes > this leads to HBASE-13375, and so of course this makes sense out of what I am > seeing, but is this really what we want? What about production environments > (insecure and degenerate secure) where all ops are effectively issued by the > superuser? We run one of these at Salesforce. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15523) enhance hbase-daemon.sh to enable autorestart.
[ https://issues.apache.org/jira/browse/HBASE-15523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496793#comment-15496793 ] Dima Spivak commented on HBASE-15523: - Moving this to a variable (that would ostensibly need to be set on every machine in a cluster) moves the onus from the script to the user and also means you couldn't grep your cluster's restart behavior via looking at the process tree. For those reasons, I'm not a fan of this proposal (and I'm still not clear on why it was reopened after being closed for six months). > enhance hbase-daemon.sh to enable autorestart. > -- > > Key: HBASE-15523 > URL: https://issues.apache.org/jira/browse/HBASE-15523 > Project: HBase > Issue Type: Improvement >Reporter: Yi Liang >Assignee: Yi Liang >Priority: Minor > Attachments: HBASE-15523.patch > > > enhance hbase-daemon.sh to enable autorestart. > component(like master, region server) will auto-start when terminated/killed > abnormally if >(a) Add a new env variable $HBASE_AUTORESTART to hbase-env.sh i.e. > export HBASE_AUTORESTART=true > (b) Then add the following 3 simple lines(59-61) to > /bin/hbase-daemon.sh > > 51 # get arguments > 52 startStop=$1 > 53 shift > 54 > 55 command=$1 > 56 shift > 57 > 58 #make sure the auto-restart are default settings > 59 if [ "$HBASE_AUTORESTART" == "true" ] && [ "$startStop" == "start" ]; > then > 60 startStop="autorestart" > 61 fi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15523) enhance hbase-daemon.sh to enable autorestart.
[ https://issues.apache.org/jira/browse/HBASE-15523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496591#comment-15496591 ] Dima Spivak commented on HBASE-15523: - Not sure why this was reopened. Autorestart works and it shouldn't be up to HBase to fix a problem in Ambari. > enhance hbase-daemon.sh to enable autorestart. > -- > > Key: HBASE-15523 > URL: https://issues.apache.org/jira/browse/HBASE-15523 > Project: HBase > Issue Type: Improvement >Reporter: Yi Liang >Assignee: Yi Liang >Priority: Minor > Attachments: HBASE-15523.patch > > > enhance hbase-daemon.sh to enable autorestart. > component(like master, region server) will auto-start when terminated/killed > abnormally if >(a) Add a new env variable $HBASE_AUTORESTART to hbase-env.sh i.e. > export HBASE_AUTORESTART=true > (b) Then add the following 3 simple lines(59-61) to > /bin/hbase-daemon.sh > > 51 # get arguments > 52 startStop=$1 > 53 shift > 54 > 55 command=$1 > 56 shift > 57 > 58 #make sure the auto-restart are default settings > 59 if [ "$HBASE_AUTORESTART" == "true" ] && [ "$startStop" == "start" ]; > then > 60 startStop="autorestart" > 61 fi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HBASE-16628) Apache HBase ™ Reference Guide: 143.1.1. Code Formatting: miss the location of preference item
[
https://issues.apache.org/jira/browse/HBASE-16628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak resolved HBASE-16628.
-
Resolution: Duplicate
> Apache HBase ™ Reference Guide: 143.1.1. Code Formatting: miss the location
> of preference item
> --
>
> Key: HBASE-16628
> URL: https://issues.apache.org/jira/browse/HBASE-16628
> Project: HBase
> Issue Type: Bug
>Reporter: alexxiyang
>
> In 143.1.1. Code Formatting
> it just said
> {code}
> Still in Preferences, click . Be sure the following options are
> selected:Apache HBase ™ Reference Guide
> {code}
> But nothing after click. It should be Java->Editor->Save Actions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (HBASE-16628) Apache HBase ™ Reference Guide: 143.1.1. Code Formatting: miss the location of preference item
[
https://issues.apache.org/jira/browse/HBASE-16628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak closed HBASE-16628.
---
> Apache HBase ™ Reference Guide: 143.1.1. Code Formatting: miss the location
> of preference item
> --
>
> Key: HBASE-16628
> URL: https://issues.apache.org/jira/browse/HBASE-16628
> Project: HBase
> Issue Type: Bug
>Reporter: alexxiyang
>
> In 143.1.1. Code Formatting
> it just said
> {code}
> Still in Preferences, click . Be sure the following options are
> selected:Apache HBase ™ Reference Guide
> {code}
> But nothing after click. It should be Java->Editor->Save Actions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-16622) Fix some issues with the HBase reference guide
[
https://issues.apache.org/jira/browse/HBASE-16622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak updated HBASE-16622:
Component/s: documentation
> Fix some issues with the HBase reference guide
> --
>
> Key: HBASE-16622
> URL: https://issues.apache.org/jira/browse/HBASE-16622
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: alexxiyang
>Assignee: alexxiyang
> Attachments: HBASE-16622-v0.diff, HBASE-16622-v1.diff
>
>
> 1.
> {code}
> if (admin.tableExists(tableName)) {
> System.out.println("Table does not exist.");
> System.exit(-1);
> }
> {code}
> This should be
> {code}
> if (!admin.tableExists(tableName)) {
> {code}
> 2.
> SNAPPY is not suitable for begginer. They may get exceptions like
> {code}
> Caused by:
> org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.DoNotRetryIOException):
> org.apache.hadoop.hbase.DoNotRetryIOException: Compression algorithm
> 'snappy' previously failed test. Set hbase.table.sanity.checks to false at
> conf or table descriptor if you want to bypass sanity checks
> at
> org.apache.hadoop.hbase.master.HMaster.warnOrThrowExceptionForFailure(HMaster.java:1701)
> at
> org.apache.hadoop.hbase.master.HMaster.sanityCheckTableDescriptor(HMaster.java:1569)
> at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1491)
> at
> org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:462)
> at
> org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:55682)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2178)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:112)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> So the code below
> {code}
> table.addFamily(new
> HColumnDescriptor(CF_DEFAULT).setCompressionType(Algorithm.SNAPPY));
> {code}
> it better to change into
> {code}
> table.addFamily(new
> HColumnDescriptor(CF_DEFAULT).setCompressionType(Algorithm.NONE));
> {code}
> 3.
> Before modify column family , get the table from connection
> Change
> {code}
> HTableDescriptor table = new HTableDescriptor(tableName);
> {code}
> into
> {code}
> Table table = connection.getTable(TableName.valueOf(tablename));
> {code}
> 4.
> In 143.1.1. Code Formatting
> it just said
> {code}
> Still in Preferences, click . Be sure the following options are
> selected:Apache HBase ™ Reference Guide
> {code}
> But nothing after click. It should be Java->Editor->Save Actions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-16622) Fix some issues with the HBase reference guide
[
https://issues.apache.org/jira/browse/HBASE-16622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak updated HBASE-16622:
Assignee: alexxiyang
> Fix some issues with the HBase reference guide
> --
>
> Key: HBASE-16622
> URL: https://issues.apache.org/jira/browse/HBASE-16622
> Project: HBase
> Issue Type: Bug
>Reporter: alexxiyang
>Assignee: alexxiyang
> Attachments: HBASE-16622-v0.diff
>
>
> 1.
> {code}
> if (admin.tableExists(tableName)) {
> System.out.println("Table does not exist.");
> System.exit(-1);
> }
> {code}
> This should be
> {code}
> if (!admin.tableExists(tableName)) {
> {code}
> 2.
> SNAPPY is not suitable for begginer. They may get exceptions like
> {code}
> Caused by:
> org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.DoNotRetryIOException):
> org.apache.hadoop.hbase.DoNotRetryIOException: Compression algorithm
> 'snappy' previously failed test. Set hbase.table.sanity.checks to false at
> conf or table descriptor if you want to bypass sanity checks
> at
> org.apache.hadoop.hbase.master.HMaster.warnOrThrowExceptionForFailure(HMaster.java:1701)
> at
> org.apache.hadoop.hbase.master.HMaster.sanityCheckTableDescriptor(HMaster.java:1569)
> at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1491)
> at
> org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:462)
> at
> org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:55682)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2178)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:112)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> So the code below
> {code}
> table.addFamily(new
> HColumnDescriptor(CF_DEFAULT).setCompressionType(Algorithm.SNAPPY));
> {code}
> it better to change into
> {code}
> table.addFamily(new
> HColumnDescriptor(CF_DEFAULT).setCompressionType(Algorithm.NONE));
> {code}
> 3.
> Before modify column family , get the table from connection
> Change
> {code}
> HTableDescriptor table = new HTableDescriptor(tableName);
> {code}
> into
> {code}
> Table table = connection.getTable(TableName.valueOf(tablename));
> {code}
> 4.
> In 143.1.1. Code Formatting
> it just said
> {code}
> Still in Preferences, click . Be sure the following options are
> selected:Apache HBase ™ Reference Guide
> {code}
> But nothing after click. It should be Java->Editor->Save Actions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-16622) Fix some issues with the HBase reference guide
[
https://issues.apache.org/jira/browse/HBASE-16622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak updated HBASE-16622:
Status: Patch Available (was: Open)
> Fix some issues with the HBase reference guide
> --
>
> Key: HBASE-16622
> URL: https://issues.apache.org/jira/browse/HBASE-16622
> Project: HBase
> Issue Type: Bug
>Reporter: alexxiyang
> Attachments: HBASE-16622-v0.diff
>
>
> 1.
> {code}
> if (admin.tableExists(tableName)) {
> System.out.println("Table does not exist.");
> System.exit(-1);
> }
> {code}
> This should be
> {code}
> if (!admin.tableExists(tableName)) {
> {code}
> 2.
> SNAPPY is not suitable for begginer. They may get exceptions like
> {code}
> Caused by:
> org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.DoNotRetryIOException):
> org.apache.hadoop.hbase.DoNotRetryIOException: Compression algorithm
> 'snappy' previously failed test. Set hbase.table.sanity.checks to false at
> conf or table descriptor if you want to bypass sanity checks
> at
> org.apache.hadoop.hbase.master.HMaster.warnOrThrowExceptionForFailure(HMaster.java:1701)
> at
> org.apache.hadoop.hbase.master.HMaster.sanityCheckTableDescriptor(HMaster.java:1569)
> at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1491)
> at
> org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:462)
> at
> org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:55682)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2178)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:112)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> So the code below
> {code}
> table.addFamily(new
> HColumnDescriptor(CF_DEFAULT).setCompressionType(Algorithm.SNAPPY));
> {code}
> it better to change into
> {code}
> table.addFamily(new
> HColumnDescriptor(CF_DEFAULT).setCompressionType(Algorithm.NONE));
> {code}
> 3.
> Before modify column family , get the table from connection
> Change
> {code}
> HTableDescriptor table = new HTableDescriptor(tableName);
> {code}
> into
> {code}
> Table table = connection.getTable(TableName.valueOf(tablename));
> {code}
> 4.
> In 143.1.1. Code Formatting
> it just said
> {code}
> Still in Preferences, click . Be sure the following options are
> selected:Apache HBase ™ Reference Guide
> {code}
> But nothing after click. It should be Java->Editor->Save Actions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-16628) Apache HBase ™ Reference Guide: 143.1.1. Code Formatting: miss the location of preference item
[
https://issues.apache.org/jira/browse/HBASE-16628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487864#comment-15487864
]
Dima Spivak commented on HBASE-16628:
-
Hey [~alexxiyang], I'm loving that you're helping us find issues with our ref
guide. What if instead of opening separate JIRAs, we close this one and rename
HBASE-16622 to something like "Fix some issues with the HBase reference guide,"
where you can continue to post problems you've encountered? If we continue the
conversation over there, we'd be happy to help you put together a patch for
these, as well, to fix them.
> Apache HBase ™ Reference Guide: 143.1.1. Code Formatting: miss the location
> of preference item
> --
>
> Key: HBASE-16628
> URL: https://issues.apache.org/jira/browse/HBASE-16628
> Project: HBase
> Issue Type: Bug
>Reporter: alexxiyang
>
> In 143.1.1. Code Formatting
> it just said
> {code}
> Still in Preferences, click . Be sure the following options are
> selected:Apache HBase ™ Reference Guide
> {code}
> But nothing after click. It should be Java->Editor->Save Actions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-16622) Apache HBase ™ Reference Guide: HBase Java API example has several errors
[
https://issues.apache.org/jira/browse/HBASE-16622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15485901#comment-15485901
]
Dima Spivak commented on HBASE-16622:
-
Seems reasonable. Wanna put together and upload a patch, [~alexxiyang]?
> Apache HBase ™ Reference Guide: HBase Java API example has several errors
> -
>
> Key: HBASE-16622
> URL: https://issues.apache.org/jira/browse/HBASE-16622
> Project: HBase
> Issue Type: Bug
>Reporter: alexxiyang
>
> 1.
> {code}
> if (admin.tableExists(tableName)) {
> System.out.println("Table does not exist.");
> System.exit(-1);
> }
> {code}
> This should be
> {code}
> if (!admin.tableExists(tableName)) {
> {code}
> 2.
> SNAPPY is not suitable for begginer. They may get exceptions like
> {code}
> Caused by:
> org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.DoNotRetryIOException):
> org.apache.hadoop.hbase.DoNotRetryIOException: Compression algorithm
> 'snappy' previously failed test. Set hbase.table.sanity.checks to false at
> conf or table descriptor if you want to bypass sanity checks
> at
> org.apache.hadoop.hbase.master.HMaster.warnOrThrowExceptionForFailure(HMaster.java:1701)
> at
> org.apache.hadoop.hbase.master.HMaster.sanityCheckTableDescriptor(HMaster.java:1569)
> at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1491)
> at
> org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:462)
> at
> org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:55682)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2178)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:112)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> So the code below
> {code}
> table.addFamily(new
> HColumnDescriptor(CF_DEFAULT).setCompressionType(Algorithm.SNAPPY));
> {code}
> it better to change into
> {code}
> table.addFamily(new
> HColumnDescriptor(CF_DEFAULT).setCompressionType(Algorithm.NONE));
> {code}
> 3.
> Before modify column family , get the table from connection
> Change
> {code}
> HTableDescriptor table = new HTableDescriptor(tableName);
> {code}
> into
> {code}
> Table table = connection.getTable(TableName.valueOf(tablename));
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-16601) Expand Dynamic Configuration
[ https://issues.apache.org/jira/browse/HBASE-16601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15478113#comment-15478113 ] Dima Spivak commented on HBASE-16601: - Is this potentially a dupe of HBASE-13936? > Expand Dynamic Configuration > > > Key: HBASE-16601 > URL: https://issues.apache.org/jira/browse/HBASE-16601 > Project: HBase > Issue Type: Improvement >Reporter: Jerry He >Assignee: Jerry He > > HBase currently supports limited dynamic configuration (modify properties > without restarting the servers). Only some compaction, split properties are > supported. > We should expand to support more and possibly improve and make it more > flexible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-16568) Remove Cygwin-oriented instructions (for installing HBase in Windows OS) from official reference materials
[ https://issues.apache.org/jira/browse/HBASE-16568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469118#comment-15469118 ] Dima Spivak commented on HBASE-16568: - Sounds good to me, [~daniel_vimont]. Get a patch up here and I'll be happy to commit it for you. > Remove Cygwin-oriented instructions (for installing HBase in Windows OS) from > official reference materials > -- > > Key: HBASE-16568 > URL: https://issues.apache.org/jira/browse/HBASE-16568 > Project: HBase > Issue Type: Improvement > Components: documentation >Affects Versions: 2.0.0 >Reporter: Daniel Vimont >Assignee: Daniel Vimont >Priority: Minor > > Cygwin-oriented instructions in the official reference materials (for > installing HBase in a Windows environment) seem to be out of date and > incorrect; a number of unresolved/unresolvable requests for help have been > posted to d...@hbase.org and u...@hbase.org mailing lists. > Discussions on d...@apache.org and HBase Slack channel resulted in (1) no > volunteers to update/maintain the Cygwin-oriented instructions, and (2) > several "+" votes and no "-" votes on the suggestion of removing > Cygwin-oriented instructions from the official reference materials. > FUTURE POSSIBLE FOLLOW-UP: For the sake of setting up a > development/testing/sandbox environment in Windows, it might be helpful to > recommend the installation of a virtual machine environment (e.g. VirtualBox) > in a Windows OS, followed by the installation of an appropriate flavor of > Linux (e.g., Ubuntu) in the VM. After this, all the standard HBase > installation/config/usage instructions can be followed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16558) IntegrationTestBulkLoad failing during linked list check
[
https://issues.apache.org/jira/browse/HBASE-16558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dima Spivak updated HBASE-16558:
Affects Version/s: 1.2.3
> IntegrationTestBulkLoad failing during linked list check
>
>
> Key: HBASE-16558
> URL: https://issues.apache.org/jira/browse/HBASE-16558
> Project: HBase
> Issue Type: Bug
> Components: integration tests
>Affects Versions: 2.0.0, 1.1.5, 1.1.6, 1.2.3
>Reporter: Dima Spivak
>
> Noticed this while testing 1.1.6 RC2, but then also reproduced it against
> 1.1.5 and master (more testing to come, but I wanna get a JIRA open to
> reference in the RC vote). When running {{IntegrationTestBulkLoad}} on a
> 5-node {{cluserdock}}-based deployment (seen with no monkey as well as with
> the {{unbalance}} monkey, which is the only one I've tried), the test fails
> during the checking phase with a set of messages like the following:
> {noformat}
> 2016-09-04 05:27:52,313 INFO [main] mapreduce.Job: Task Id :
> attempt_1472966120303_0006_m_07_0, Status : FAILED
> Error: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> at java.util.ArrayList.rangeCheck(ArrayList.java:653)
> at java.util.ArrayList.get(ArrayList.java:429)
> at
> org.apache.hadoop.hbase.mapreduce.IntegrationTestBulkLoad$LinkedListCheckingMapper.map(IntegrationTestBulkLoad.java:600)
> at
> org.apache.hadoop.hbase.mapreduce.IntegrationTestBulkLoad$LinkedListCheckingMapper.map(IntegrationTestBulkLoad.java:591)
> at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:146)
> at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:787)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
> {noformat}
> [Here's the line of code that causes
> problems|https://github.com/apache/hbase/blob/branch-1.1/hbase-it/src/test/java/org/apache/hadoop/hbase/mapreduce/IntegrationTestBulkLoad.java#L603],
> but I'll need to dig further to understand what's going on.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-16559) Create script to automate RC testing
Dima Spivak created HBASE-16559:
---
Summary: Create script to automate RC testing
Key: HBASE-16559
URL: https://issues.apache.org/jira/browse/HBASE-16559
Project: HBase
Issue Type: Task
Components: scripts
Reporter: Dima Spivak
Assignee: Dima Spivak
Testing RCs would be easier and more repeatable if we had a script under
{{dev-support}} that declared certain typical operations (checking hashes,
running unit tests, spinning up clusters with {{clusterdock}} and running tests
from {{hbase-it}}), and allowed a user to run them on demand. Letting them
specify a JSON file with actions to take (and which arguments to pass to
various tests, for example) would be cool, too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-16558) IntegrationTestBulkLoad failing during linked list check
Dima Spivak created HBASE-16558:
---
Summary: IntegrationTestBulkLoad failing during linked list check
Key: HBASE-16558
URL: https://issues.apache.org/jira/browse/HBASE-16558
Project: HBase
Issue Type: Bug
Components: integration tests
Affects Versions: 1.1.5, 2.0.0, 1.1.6
Reporter: Dima Spivak
Noticed this while testing 1.1.6 RC2, but then also reproduced it against 1.1.5
and master (more testing to come, but I wanna get a JIRA open to reference in
the RC vote). When running {{IntegrationTestBulkLoad}} on a 5-node
{{cluserdock}}-based deployment (seen with no monkey as well as with the
{{unbalance}} monkey, which is the only one I've tried), the test fails during
the checking phase with a set of messages like the following:
{noformat}
2016-09-04 05:27:52,313 INFO [main] mapreduce.Job: Task Id :
attempt_1472966120303_0006_m_07_0, Status : FAILED
Error: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:653)
at java.util.ArrayList.get(ArrayList.java:429)
at
org.apache.hadoop.hbase.mapreduce.IntegrationTestBulkLoad$LinkedListCheckingMapper.map(IntegrationTestBulkLoad.java:600)
at
org.apache.hadoop.hbase.mapreduce.IntegrationTestBulkLoad$LinkedListCheckingMapper.map(IntegrationTestBulkLoad.java:591)
at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:146)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:787)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
{noformat}
[Here's the line of code that causes
problems|https://github.com/apache/hbase/blob/branch-1.1/hbase-it/src/test/java/org/apache/hadoop/hbase/mapreduce/IntegrationTestBulkLoad.java#L603],
but I'll need to dig further to understand what's going on.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-16547) hbase-archetype-builder shell scripts assume bash is installed in /bin
[
https://issues.apache.org/jira/browse/HBASE-16547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15457002#comment-15457002
]
Dima Spivak commented on HBASE-16547:
-
Perhaps {{/usr/bin/env bash}} should be the shebang we enforce in future shell
scripts? Looking at {{installArchetypes.sh}}, I can't help but think that maybe
it's doing things that the {{pom.xml}} in that module should be handling, but
that's a different story.
> hbase-archetype-builder shell scripts assume bash is installed in /bin
> --
>
> Key: HBASE-16547
> URL: https://issues.apache.org/jira/browse/HBASE-16547
> Project: HBase
> Issue Type: Bug
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Trivial
> Fix For: 2.0.0, 1.3.0, 1.4.0
>
> Attachments: HBASE-16547.patch
>
>
> There's no guarantee UNIX systems will have bash installed in /bin. HBase
> builds fail for me on FreeBSD. The hbase-archetype-builder scripts do not use
> any bash features so let's specify '/bin/sh' as interpreter instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
