Sean Busbey (JIRA | 30 Jul 19:40 2015
Picon

[jira] [Resolved] (HBASE-14086) remove unused bundled dependencies


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

Sean Busbey resolved HBASE-14086.
---------------------------------
    Resolution: Fixed

Okay, we'll just need to make sure we update LICENSE files for HBASE-14087 on 0.94.

> remove unused bundled dependencies
> ----------------------------------
>
>                 Key: HBASE-14086
>                 URL: https://issues.apache.org/jira/browse/HBASE-14086
>             Project: HBase
>          Issue Type: Sub-task
>          Components: documentation
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Blocker
>             Fix For: 2.0.0, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>
>         Attachments: HBASE-14086.1.patch
>
>
> We have some files with compatible non-ASL licenses that don't appear to be used, so remove them.

--
This message was sent by Atlassian JIRA
(Continue reading)

beeshma r | 30 Jul 18:50 2015
Picon

A proposal for Provide key range support to bulkload to avoid too many reducers (HBASE-9556)

HI,

i'd like work with key range support to bulkload to avoid too many reducers
mentioned in with these issues (HBASE-9556,HBASE-4063)

Description and high level design for  proposed solution

Currently while we loading bulk data in to Hbase through Mapredue in form
of TableInputFormatBase the number of splits matches the number of regions
in a table
so Here i am going to change the process TableInputFormatBase deceides
range for key splits
 For example if input data going to load data in 50 regions(Actullay RS has
400 Regions)

   - List<InputSplit> getSplits(JobContext context) will find  50 exact
   list of splits (Currently it returns 400 )

Am i understand correctly? please let me know if Am I on the wrong track
.Any one is willing to mentor me because i am new to ASF

Thanks
Beeshma
Ted Yu (JIRA | 30 Jul 17:20 2015
Picon

[jira] [Created] (HBASE-14173) includeMVCCReadpoint parameter in DefaultCompactor#createTmpWriter() represents no-op

Ted Yu created HBASE-14173:
------------------------------

             Summary: includeMVCCReadpoint parameter in DefaultCompactor#createTmpWriter() represents no-op
                 Key: HBASE-14173
                 URL: https://issues.apache.org/jira/browse/HBASE-14173
             Project: HBase
          Issue Type: Bug
            Reporter: Ted Yu
            Assignee: Ted Yu
             Fix For: 2.0.0

Around line 160:
{code}
    return store.createWriterInTmp(fd.maxKeyCount, this.compactionCompression,
            true, fd.maxMVCCReadpoint >= 0, fd.maxTagsLength >0);
{code}
The condition, fd.maxMVCCReadpoint >= 0, represents no-op.

The correct condition should be fd.maxMVCCReadpoint > 0

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Srikanth Srungarapu (JIRA | 30 Jul 09:38 2015
Picon

[jira] [Created] (HBASE-14172) Upgrade existing thrift binding using thrift 0.9.2 compiler.

Srikanth Srungarapu created HBASE-14172:
-------------------------------------------

             Summary: Upgrade existing thrift binding using thrift 0.9.2 compiler.
                 Key: HBASE-14172
                 URL: https://issues.apache.org/jira/browse/HBASE-14172
             Project: HBase
          Issue Type: Improvement
            Reporter: Srikanth Srungarapu
            Assignee: Srikanth Srungarapu
            Priority: Minor

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Y. SREENIVASULU REDDY (JIRA | 30 Jul 09:01 2015
Picon

[jira] [Created] (HBASE-14171) [HBase Thrift] ThriftServer is not shutting down if "hbase.regionserver.thrift.port" Address already in use.

Y. SREENIVASULU REDDY created HBASE-14171:
---------------------------------------------

             Summary: [HBase Thrift] ThriftServer is not shutting down if "hbase.regionserver.thrift.port"
Address already in use.
                 Key: HBASE-14171
                 URL: https://issues.apache.org/jira/browse/HBASE-14171
             Project: HBase
          Issue Type: Bug
          Components: Thrift
            Reporter: Y. SREENIVASULU REDDY
             Fix For: 2.0.0, 1.0.2, 1.2.0

If "hbase.regionserver.thrift.port" Address already in use, ThriftServer should shutdown,

with out this "hbase.regionserver.thrift.port"  we cant perform any operations on ThriftServer . Then
there is no use of running ThriftServer process.
If port is already used then exception or message also not throwing like address already in use.
Only info port information is showing.
{code}
2015-07-30 12:20:56,186 INFO  [main] http.HttpServer: Jetty bound to port 9095
2015-07-30 12:20:56,186 INFO  [main] mortbay.log: jetty-6.1.26
2015-07-30 12:20:56,227 WARN  [main] mortbay.log: Can't reuse
/tmp/Jetty_0_0_0_0_9095_thrift____.vqpz9l, using /tmp/Jetty_0_0_0_0_9095_thrift____.vqpz9l_4913486964252131199
2015-07-30 12:20:56,553 INFO  [main] mortbay.log: Started
HttpServer$SelectChannelConnectorWithSafeStartup <at> 0.0.0.0:9095 {code}

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
(Continue reading)

Y. SREENIVASULU REDDY (JIRA | 30 Jul 08:32 2015
Picon

[jira] [Created] (HBASE-14170) [HBase Rest] RESTServer is not shutting down if "hbase.rest.port" Address already in use.

Y. SREENIVASULU REDDY created HBASE-14170:
---------------------------------------------

             Summary: [HBase Rest] RESTServer is not shutting down if "hbase.rest.port" Address already in use.
                 Key: HBASE-14170
                 URL: https://issues.apache.org/jira/browse/HBASE-14170
             Project: HBase
          Issue Type: Bug
          Components: REST
            Reporter: Y. SREENIVASULU REDDY
             Fix For: 2.0.0, 1.0.2, 1.2.0

[HBase Rest] RESTServer is not shutting down if "hbase.rest.port" Address already in use.

 If "hbase.rest.port" Address already in use, RESTServer should shutdown,

with out this "hbase.rest.port"  we cant perform any operations on RESTServer. Then there is no use of
running RESTServer process.

{code}
2015-07-30 11:49:48,273 WARN  [main] mortbay.log: failed SelectChannelConnector <at> 0.0.0.0:8080:
java.net.BindException: Address already in use
2015-07-30 11:49:48,274 WARN  [main] mortbay.log: failed Server <at> 563f38c4: java.net.BindException:
Address already in use
{code}

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

(Continue reading)

Francis Liu (JIRA | 30 Jul 07:31 2015
Picon

[jira] [Created] (HBASE-14169) API to refreshSuperUserGroupsConfiguration

Francis Liu created HBASE-14169:
-----------------------------------

             Summary: API to refreshSuperUserGroupsConfiguration
                 Key: HBASE-14169
                 URL: https://issues.apache.org/jira/browse/HBASE-14169
             Project: HBase
          Issue Type: New Feature
            Reporter: Francis Liu
            Assignee: Francis Liu

For deployments that use security. User impersonation (AKA doAs()) is needed for some services (ie
Stargate, thriftserver, Oozie, etc). Impersonation definitions are defined in a xml config file and
read and cached by the ProxyUsers class. Calling this api will refresh cached information, eliminating
the need to restart the master/regionserver whenever the configuration is changed. 

Implementation just adds another method to AccessControlService.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

zhouyingchao (JIRA | 30 Jul 05:17 2015
Picon

[jira] [Created] (HBASE-14168) Avoid useless retry as exception implies in TableRecordReaderImpl

zhouyingchao created HBASE-14168:
------------------------------------

             Summary: Avoid useless retry as exception implies in TableRecordReaderImpl
                 Key: HBASE-14168
                 URL: https://issues.apache.org/jira/browse/HBASE-14168
             Project: HBase
          Issue Type: Bug
          Components: mapreduce
            Reporter: zhouyingchao
            Priority: Minor

In TableRecordReaderImpl, even if the next() of scan throws DoNotRetryIOException, it would still be
retried. This does not make sense and should be avoided.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Andrew Purtell (JIRA | 30 Jul 03:22 2015
Picon

[jira] [Created] (HBASE-14167) hbase-spark integration tests do not respect -DskipITs

Andrew Purtell created HBASE-14167:
--------------------------------------

             Summary: hbase-spark integration tests do not respect -DskipITs
                 Key: HBASE-14167
                 URL: https://issues.apache.org/jira/browse/HBASE-14167
             Project: HBase
          Issue Type: Bug
    Affects Versions: 2.0.0
            Reporter: Andrew Purtell
            Priority: Minor

When running a build with {{mvn ... -DskipITs}}, the hbase-spark module's integration tests do not
respect the flag and run anyway. Fix. 

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Krishna | 30 Jul 01:23 2015
Picon

Compaction after bulk-load

Hi,

I am planning to bulk-load about 10 TB of data to a table pre-split with
30 regions with max region file size configured to 10 GB.

Is it recommended that I run a major compaction when bulk-loading finishes? How
many HFiles does the reducer create?
Andrew Purtell | 30 Jul 00:56 2015
Picon

Re: [DISCUSSION] Switching from RTC to CTR

Had this thought after getting back on the road. As an alternative to any sweeping change we could do one
incremental but very significant thing that acknowledges our status as trusted and busy peers: After
posting a patch to JIRA, after one week if there is no review or veto, a committer can commit their own work.

> On Jul 29, 2015, at 2:20 PM, Mikhail Antonov <olorinbant@...> wrote:
> 
> Just curious, I assume if this change is made, would it only apply to
> master branch?
> 
> -Mikhail
> 
> On Wed, Jul 29, 2015 at 2:09 PM, Andrew Purtell
> <andrew.purtell@...> wrote:
>>  <at> dev is now CCed
>> 
>> I didn't want to over structure the discussion with too much detail up front. I do think CTR without
supporting process or boundaries can be more problematic than helpful. That could take the form of
customarily waiting for reviews before commit even under a CTR regime. I think this discussion has been
great so far. I would also add that CTR moves 'R' from a gating requirement per commit (which can be hard to
overcome for niche areas or when volunteer resources are less available) more to RMs. will be back later
with more.
>> 
>> 
>>> On Jul 29, 2015, at 1:36 PM, Sean Busbey <sean.busbey@...> wrote:
>>> 
>>> I'd also favor having this discussion on dev <at> .
>>> 
>>>> On Wed, Jul 29, 2015 at 2:29 PM, Gary Helmling
<ghelmling@...> wrote:
>>>> 
(Continue reading)


Gmane