Re: Slack access

[Apekshit Sharma]

Right now, anyone who's in room should be able to invite more people, not
just committers.
+1 for a process. Shooting a mail with predefined subject line is probably
better since most people track emails, but fewer actively track new jiras.

- Appy

On Wed, Aug 9, 2017 at 3:10 PM, Misty Stanley-Jones 
wrote:

> Can we just make a process for this (and document it), like asking the
> person to submit a JIRA tagged with slack, and giving all the committers
> access to invite people? Am I missing something?
>
> On Mon, Jul 24, 2017 at 12:03 AM, Samir Ahmic 
> wrote:
>
> > Hi Dima,
> >
> > Mind sending me invite to channel to?
> > Thanks chief.
> >
> > Best Regards
> > Samir
> >
> > On Mon, Jul 24, 2017 at 8:28 AM, Apekshit Sharma 
> > wrote:
> >
> > > There are 2 other ways:
> > > - whitelist domain names. For eg. @apache.com.
> > > - Signup link which anyone can use to join the group. Sadly, that
> remains
> > > alive only for a day or two.
> > >
> > >
> > > On Sun, Jul 23, 2017 at 9:47 AM, Sachin Jain 
> > > wrote:
> > >
> > > > As long as you are fine with sending invitations manually, the world
> > will
> > > > be happily joining.
> > > >
> > > > Thanks for invite BTW.
> > > >
> > > > On 23-Jul-2017 7:34 PM, "Dima Spivak"  wrote:
> > > >
> > > > > Unfortunately this looks to be the only way. Aw well, it's slow but
> > > > really
> > > > > effective against spam. 
> > > > >
> > > > > On Sat, Jul 22, 2017 at 8:32 PM Sachin Jain <
> sachinjain...@gmail.com
> > >
> > > > > wrote:
> > > > >
> > > > > > HI Dima,
> > > > > >
> > > > > > Given that so many users may come to know about slack user
> > community,
> > > > > most
> > > > > > of them would like to get on board. Is there any better way to
> get
> > > > > involved
> > > > > > or mailing to dev list is the only and best option available!
> > > > > >
> > > > > > Count me in too. sachinjain024 at gmail
> > > > > >
> > > > > > On Fri, Jul 21, 2017 at 11:49 PM, Ajay Jadhav <
> > > ajaybjadh...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Dima,
> > > > > > >
> > > > > > > Can you send me an invite too?
> > > > > > >
> > > > > > > Thanks.
> > > > > > >
> > > > > > > On Fri, Jul 21, 2017 at 11:15 AM Gustavo Anatoly <
> > > > > > gustavoanat...@gmail.com
> > > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Thank you. @Dima
> > > > > > > >
> > > > > > > > 2017-07-21 15:11 GMT-03:00 Dima Spivak <
> dimaspi...@apache.org
> > >:
> > > > > > > >
> > > > > > > > > Everyone gets an invite! Done.
> > > > > > > > >
> > > > > > > > > On Fri, Jul 21, 2017 at 11:01 AM Gustavo Anatoly <
> > > > > > > > gustavoanat...@gmail.com
> > > > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Could you please, send me an invite too?
> > > > > > > > > >
> > > > > > > > > > Cheers,
> > > > > > > > > >
> > > > > > > > > > 2017-07-21 11:23 GMT-03:00 Dima Spivak <
> > > dimaspi...@apache.org
> > > > >:
> > > > > > > > > >
> > > > > > > > > > > Invite sent. :)
> > > > > > > > > > >
> > > > > > > > > > > On Fri, Jul 21, 2017 at 12:58 AM Dawid Adach <
> > > > > > > > d.ad...@mdbootstrap.com>
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Hi Guys,
> > > > > > > > > > > >
> > > > > > > > > > > > could I get access to HBase slack? I would like to
> get
> > > > > involved
> > > > > > > > into
> > > > > > > > > > the
> > > > > > > > > > > > community.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Kind regards,
> > > > > > > > > > > > Dawid
> > > > > > > > > > > >
> > > > > > > > > > > > [image: mdb-logo]
> > > > > > > > > > > >
> > > > > > > > > > > > Dawid Adach
> > > > > > > > > > > >
> > > > > > > > > > > > +48 695 608 802 <+48%20695%20608%20802>
> > > > > > > > > > > > www.MDBootstrap.com  > > > > > > > > > > material-design-for-bootstrap/
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > [image: li-logo] <
> > > > > > > > https://pl.linkedin.com/pub/dawid-adach/34/355/974
> > > > > > > > > >
> > > > > > > > > > > > [image:
> > > > > > > > > > > > tw-logo]  [image:
> > > > gp-logo]
> > > > > > > > > > > > 
> > > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > -Dima
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > *»* *Gustavo Anatoly Fernandes Velásquez Solís*
> > > > > > > > > >
> > > > > > > > > --
> > > > > > > > > -Dima
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > *»* *Gustavo Anatoly Fernandes Velásquez Solís*
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > --
> > > > > -Dima
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > >
> > > -- Appy
> > >
> >
>



-- 

-- Appy

Re: Ycsb and Hbase - read+write simulation.

[Apekshit Sharma]

not clear on what's the ask here.
Going by just two sentences, am confused how it can be 97% in last 2 hours
but only 90% in 24 hours? Shouldn't second number be larger?
-- Appy

On Wed, Aug 9, 2017 at 1:01 AM, Meirav Malka  wrote:

> -- Forwarded message --
> From: "meirav.malka" 
> Date: Aug 9, 2017 10:56
> Subject: Ycsb and Hbase - read+write simulation.
> To: "Hbase User Group" 
> Cc:
>
> Hi everyone,
>
> Does anyone know of a ycdb option that will allow the following read
> request distribution:
>
>
> 1. 90% of the material read was inserted in the last 24 hours.
> 2. 97% in the last 2 hours.
>
> The only options i see for request distribution is "latest", "zipfian" and
> "uniform"
>
> Is there anyway to provide an this distribution?
>
> Thanks!
>
>
> Sent from my Samsung Galaxy smartphone.
>



-- 

-- Appy

[jira] [Created] (HBASE-18553) Expose scan cursor for asynchronous scanner

[Duo Zhang (JIRA)]

Duo Zhang created HBASE-18553:
-

 Summary: Expose scan cursor for asynchronous scanner
 Key: HBASE-18553
 URL: https://issues.apache.org/jira/browse/HBASE-18553
 Project: HBase
  Issue Type: Sub-task
Affects Versions: 2.0.0-alpha-1, 3.0.0
Reporter: Duo Zhang
 Fix For: 3.0.0, 2.0.0-alpha-2






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HBASE-18552) Backport the server side change in HBASE-18489 to branch-1

[Duo Zhang (JIRA)]

Duo Zhang created HBASE-18552:
-

 Summary: Backport the server side change in HBASE-18489 to branch-1
 Key: HBASE-18552
 URL: https://issues.apache.org/jira/browse/HBASE-18552
 Project: HBase
  Issue Type: Sub-task
Affects Versions: 1.4.0, 1.5.0
Reporter: Duo Zhang
 Fix For: 1.4.0, 1.5.0






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HBASE-18551) [AMv2] UnassignProcedure and crashed regionservers

[stack (JIRA)]

stack created HBASE-18551:
-

 Summary: [AMv2] UnassignProcedure and crashed regionservers
 Key: HBASE-18551
 URL: https://issues.apache.org/jira/browse/HBASE-18551
 Project: HBase
  Issue Type: Bug
  Components: amv2
Reporter: stack


This has been [~uagashe] and my obsession over the last few days, what should 
an UnassignProcedure do when it dispatches a CLOSE but the CLOSE fails because 
of ConnectException or SocketTimeout.

+ We used to let UnassignProcedure continue presuming the Region would be 
closed since the server is dead. BUT, if the unassign was part of a 
MoveProcedure, the unassign would proceed and the Move would then run WITHOUT 
first splitting logs. Bad.
+ So, we made it so UnassignProcedure failed; let the upper layers take care of 
the failure. See HBASE-18491 that enabled this behavior. BUT, we are since 
figuring that even if the UP completes as a failure, since it gives up the 
Region lock on completion, another procedure -- say an AssignProcedure -- could 
cut in before the ServerCrashProcedure had finished and again there could be 
dataloss.
+ Now we are thinking the UP should hold on to the Region lock until we are 
signalled by a ServerCrashProcedure; only then let go of the region. The UP has 
context that is hard to pass another. Waiting on a SCP has the UP living on for 
what could be a good amount of time. It might be ok if we can suspend the 
procedure.

There is a good sample scenario that came up doing the no-regions-on-master 
issue, HBASE-18511. When meta is not on master, TestSplitTransactionOnCluster 
is failing. It fails because though the test completes, the tests commonly kill 
a RegionServer. The teardown for the test runs before we've noticed the aborted 
RS. So, the disable of the table in the teardown prepartory to our deleting the 
test table as part of clean up, goes to unassign regions but the unassign fails 
against the aborted server.

Good stuff.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HBASE-18550) Move sanity checks for BucketCache configs inside BucketCache

[Zach York (JIRA)]

Zach York created HBASE-18550:
-

 Summary: Move sanity checks for BucketCache configs inside 
BucketCache
 Key: HBASE-18550
 URL: https://issues.apache.org/jira/browse/HBASE-18550
 Project: HBase
  Issue Type: Improvement
  Components: BucketCache
Reporter: Zach York
Assignee: Zach York


In https://reviews.apache.org/r/61485/, Ramkrishna asked if I would move the 
sanity checking of all configs into the BucketCache constructor. This is a 
follow-up JIRA to move the sanity checking into the constructor.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Slack access

[Misty Stanley-Jones]

Can we just make a process for this (and document it), like asking the
person to submit a JIRA tagged with slack, and giving all the committers
access to invite people? Am I missing something?

On Mon, Jul 24, 2017 at 12:03 AM, Samir Ahmic  wrote:

> Hi Dima,
>
> Mind sending me invite to channel to?
> Thanks chief.
>
> Best Regards
> Samir
>
> On Mon, Jul 24, 2017 at 8:28 AM, Apekshit Sharma 
> wrote:
>
> > There are 2 other ways:
> > - whitelist domain names. For eg. @apache.com.
> > - Signup link which anyone can use to join the group. Sadly, that remains
> > alive only for a day or two.
> >
> >
> > On Sun, Jul 23, 2017 at 9:47 AM, Sachin Jain 
> > wrote:
> >
> > > As long as you are fine with sending invitations manually, the world
> will
> > > be happily joining.
> > >
> > > Thanks for invite BTW.
> > >
> > > On 23-Jul-2017 7:34 PM, "Dima Spivak"  wrote:
> > >
> > > > Unfortunately this looks to be the only way. Aw well, it's slow but
> > > really
> > > > effective against spam. 
> > > >
> > > > On Sat, Jul 22, 2017 at 8:32 PM Sachin Jain  >
> > > > wrote:
> > > >
> > > > > HI Dima,
> > > > >
> > > > > Given that so many users may come to know about slack user
> community,
> > > > most
> > > > > of them would like to get on board. Is there any better way to get
> > > > involved
> > > > > or mailing to dev list is the only and best option available!
> > > > >
> > > > > Count me in too. sachinjain024 at gmail
> > > > >
> > > > > On Fri, Jul 21, 2017 at 11:49 PM, Ajay Jadhav <
> > ajaybjadh...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi Dima,
> > > > > >
> > > > > > Can you send me an invite too?
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > > On Fri, Jul 21, 2017 at 11:15 AM Gustavo Anatoly <
> > > > > gustavoanat...@gmail.com
> > > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Thank you. @Dima
> > > > > > >
> > > > > > > 2017-07-21 15:11 GMT-03:00 Dima Spivak  >:
> > > > > > >
> > > > > > > > Everyone gets an invite! Done.
> > > > > > > >
> > > > > > > > On Fri, Jul 21, 2017 at 11:01 AM Gustavo Anatoly <
> > > > > > > gustavoanat...@gmail.com
> > > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Could you please, send me an invite too?
> > > > > > > > >
> > > > > > > > > Cheers,
> > > > > > > > >
> > > > > > > > > 2017-07-21 11:23 GMT-03:00 Dima Spivak <
> > dimaspi...@apache.org
> > > >:
> > > > > > > > >
> > > > > > > > > > Invite sent. :)
> > > > > > > > > >
> > > > > > > > > > On Fri, Jul 21, 2017 at 12:58 AM Dawid Adach <
> > > > > > > d.ad...@mdbootstrap.com>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi Guys,
> > > > > > > > > > >
> > > > > > > > > > > could I get access to HBase slack? I would like to get
> > > > involved
> > > > > > > into
> > > > > > > > > the
> > > > > > > > > > > community.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Kind regards,
> > > > > > > > > > > Dawid
> > > > > > > > > > >
> > > > > > > > > > > [image: mdb-logo]
> > > > > > > > > > >
> > > > > > > > > > > Dawid Adach
> > > > > > > > > > >
> > > > > > > > > > > +48 695 608 802 <+48%20695%20608%20802>
> > > > > > > > > > > www.MDBootstrap.com  > > > > > > > > > material-design-for-bootstrap/
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > [image: li-logo] <
> > > > > > > https://pl.linkedin.com/pub/dawid-adach/34/355/974
> > > > > > > > >
> > > > > > > > > > > [image:
> > > > > > > > > > > tw-logo]  [image:
> > > gp-logo]
> > > > > > > > > > > 
> > > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > -Dima
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > *»* *Gustavo Anatoly Fernandes Velásquez Solís*
> > > > > > > > >
> > > > > > > > --
> > > > > > > > -Dima
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > *»* *Gustavo Anatoly Fernandes Velásquez Solís*
> > > > > > >
> > > > > >
> > > > >
> > > > --
> > > > -Dima
> > > >
> > >
> >
> >
> >
> > --
> >
> > -- Appy
> >
>

Re: Still Failing: HBase Generate Website

[Misty Stanley-Jones]

https://issues.apache.org/jira/browse/HBASE-18548 Patch attached and ready
for review. Thanks, y'all!

On Wed, Aug 9, 2017 at 1:22 PM, Misty Stanley-Jones 
wrote:

> I got this.
>
> On Wed, Aug 9, 2017 at 12:17 PM, Sean Busbey  wrote:
>
>> could someone file a JIRA to get the website update job into source
>> control? it should be pretty straight forward; even if just the shell
>> script goes into dev-support it would make this a lot easier to
>> maintain over time. I'm happy to do the implementation, I'm just
>> likely to forget about it when I end up with the time.
>>
>> On Wed, Aug 9, 2017 at 1:29 PM, Stack  wrote:
>> > I pushed a fix on HBASE-18545 that should take care of it.
>> >
>> > I repro'd the issue by running commands found in the jenkins config.
>> >
>> > HBASE-18545 is the issue. Building rsgroups, it couldn't find protos
>> files
>> > it depends on that are over in hbase-protocol.
>> >
>> > S
>> >
>> >
>> > On Wed, Aug 9, 2017 at 8:25 AM, Mike Drob  wrote:
>> >
>> >> I tried to look at this failure on Jenkins, but couldn't make sense of
>> it
>> >> -- there's barely any information there. Does anybody else have
>> experience
>> >> with this job?
>> >>
>> >> Mike
>> >>
>> >> On Wed, Aug 9, 2017 at 9:53 AM, Apache Jenkins Server <
>> >> jenk...@builds.apache.org> wrote:
>> >>
>> >> > Build status: Still Failing
>> >> >
>> >> > The HBase website has not been updated to incorporate HBase commit
>> >> > ${HBASE_GIT_SHA}.
>> >> >
>> >> > See https://builds.apache.org/job/hbase_generate_website/1075/co
>> nsole
>> >>
>>
>
>

[jira] [Created] (HBASE-18549) Unclaimed replication queues can go undetected

[Ashu Pachauri (JIRA)]

Ashu Pachauri created HBASE-18549:
-

 Summary: Unclaimed replication queues can go undetected
 Key: HBASE-18549
 URL: https://issues.apache.org/jira/browse/HBASE-18549
 Project: HBase
  Issue Type: Bug
  Components: Replication
Reporter: Ashu Pachauri
Priority: Critical
 Fix For: 1.3.2


We have come across this situation multiple times where a zookeeper issues can 
cause NodeFailoverWorker to fail picking up replication queue for a dead region 
server silently. One example is when the znode size for a particular queue 
exceed jute.maxBuffer value.

There can be other situations that may lead to this and just go undetected. We 
need to have a metric for number of unclaimed replication queues. This will 
help in mitigating the problem through alerting on the metric and identifying 
underlying issues.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HBASE-18548) Move sources of important Jenkins jobs into source control

[Misty Stanley-Jones (JIRA)]

Misty Stanley-Jones created HBASE-18548:
---

 Summary: Move sources of important Jenkins jobs into source control
 Key: HBASE-18548
 URL: https://issues.apache.org/jira/browse/HBASE-18548
 Project: HBase
  Issue Type: Bug
  Components: documentation, scripts
Affects Versions: 2.0.0-alpha-1
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
Priority: Critical
 Fix For: 2.0.0


Move sources of the following Jenkins jobs into source control:

https://builds.apache.org/job/hbase_generate_website/

https://builds.apache.org/view/All/job/HBase%20Website%20Link%20Checker/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Still Failing: HBase Generate Website

[Misty Stanley-Jones]

I got this.

On Wed, Aug 9, 2017 at 12:17 PM, Sean Busbey  wrote:

> could someone file a JIRA to get the website update job into source
> control? it should be pretty straight forward; even if just the shell
> script goes into dev-support it would make this a lot easier to
> maintain over time. I'm happy to do the implementation, I'm just
> likely to forget about it when I end up with the time.
>
> On Wed, Aug 9, 2017 at 1:29 PM, Stack  wrote:
> > I pushed a fix on HBASE-18545 that should take care of it.
> >
> > I repro'd the issue by running commands found in the jenkins config.
> >
> > HBASE-18545 is the issue. Building rsgroups, it couldn't find protos
> files
> > it depends on that are over in hbase-protocol.
> >
> > S
> >
> >
> > On Wed, Aug 9, 2017 at 8:25 AM, Mike Drob  wrote:
> >
> >> I tried to look at this failure on Jenkins, but couldn't make sense of
> it
> >> -- there's barely any information there. Does anybody else have
> experience
> >> with this job?
> >>
> >> Mike
> >>
> >> On Wed, Aug 9, 2017 at 9:53 AM, Apache Jenkins Server <
> >> jenk...@builds.apache.org> wrote:
> >>
> >> > Build status: Still Failing
> >> >
> >> > The HBase website has not been updated to incorporate HBase commit
> >> > ${HBASE_GIT_SHA}.
> >> >
> >> > See https://builds.apache.org/job/hbase_generate_website/1075/console
> >>
>

[jira] [Created] (HBASE-18547) Provide better cleanup of WAL related entries in backup table

[Ted Yu (JIRA)]

Ted Yu created HBASE-18547:
--

 Summary: Provide better cleanup of WAL related entries in backup 
table
 Key: HBASE-18547
 URL: https://issues.apache.org/jira/browse/HBASE-18547
 Project: HBase
  Issue Type: Bug
Reporter: Ted Yu


I was discussing the design around incremental backup with Vladimir.

Currently if WAL file is recorded in backup table, BackupLogCleaner would 
signal that the file can be cleaned up.
However, cleaner chore doesn't notify BackupLogCleaner whether the file is 
actually deleted.
This means that potentially large number of WAL files would stay in backup 
table.

This issue is to investigate better cleanup strategy for the WAL entries.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Still Failing: HBase Generate Website

[Sean Busbey]

could someone file a JIRA to get the website update job into source
control? it should be pretty straight forward; even if just the shell
script goes into dev-support it would make this a lot easier to
maintain over time. I'm happy to do the implementation, I'm just
likely to forget about it when I end up with the time.

On Wed, Aug 9, 2017 at 1:29 PM, Stack  wrote:
> I pushed a fix on HBASE-18545 that should take care of it.
>
> I repro'd the issue by running commands found in the jenkins config.
>
> HBASE-18545 is the issue. Building rsgroups, it couldn't find protos files
> it depends on that are over in hbase-protocol.
>
> S
>
>
> On Wed, Aug 9, 2017 at 8:25 AM, Mike Drob  wrote:
>
>> I tried to look at this failure on Jenkins, but couldn't make sense of it
>> -- there's barely any information there. Does anybody else have experience
>> with this job?
>>
>> Mike
>>
>> On Wed, Aug 9, 2017 at 9:53 AM, Apache Jenkins Server <
>> jenk...@builds.apache.org> wrote:
>>
>> > Build status: Still Failing
>> >
>> > The HBase website has not been updated to incorporate HBase commit
>> > ${HBASE_GIT_SHA}.
>> >
>> > See https://builds.apache.org/job/hbase_generate_website/1075/console
>>

[jira] [Created] (HBASE-18546) Append/Increment a cell with custom timestamp

[Chia-Ping Tsai (JIRA)]

Chia-Ping Tsai created HBASE-18546:
--

 Summary: Append/Increment a cell with custom timestamp
 Key: HBASE-18546
 URL: https://issues.apache.org/jira/browse/HBASE-18546
 Project: HBase
  Issue Type: Bug
Reporter: Chia-Ping Tsai
Assignee: Chia-Ping Tsai


We don't pass the custom timestamp for Increment, and the increment's timestamp 
always be rewrite. Hence, user can't increment a cell with custom timestamp.
{code:title=ProtobufUtil.java}
  if (values != null && values.size() > 0) {
for (Cell cell: values) {
  valueBuilder.clear();
  valueBuilder.setQualifier(UnsafeByteOperations.unsafeWrap(
  cell.getQualifierArray(), cell.getQualifierOffset(), 
cell.getQualifierLength()));
  valueBuilder.setValue(UnsafeByteOperations.unsafeWrap(
  cell.getValueArray(), cell.getValueOffset(), 
cell.getValueLength()));
  if (cell.getTagsLength() > 0) {

valueBuilder.setTags(UnsafeByteOperations.unsafeWrap(cell.getTagsArray(),
cell.getTagsOffset(), cell.getTagsLength()));
  }
  columnBuilder.addQualifierValue(valueBuilder.build());
}
  }
{code}
In contrast to Increment, user can append the cell with custom timestamp. It 
would be better that make their behavior consistent. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Still Failing: HBase Generate Website

[Stack]

I pushed a fix on HBASE-18545 that should take care of it.

I repro'd the issue by running commands found in the jenkins config.

HBASE-18545 is the issue. Building rsgroups, it couldn't find protos files
it depends on that are over in hbase-protocol.

S


On Wed, Aug 9, 2017 at 8:25 AM, Mike Drob  wrote:

> I tried to look at this failure on Jenkins, but couldn't make sense of it
> -- there's barely any information there. Does anybody else have experience
> with this job?
>
> Mike
>
> On Wed, Aug 9, 2017 at 9:53 AM, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
> > Build status: Still Failing
> >
> > The HBase website has not been updated to incorporate HBase commit
> > ${HBASE_GIT_SHA}.
> >
> > See https://builds.apache.org/job/hbase_generate_website/1075/console
>

[jira] [Resolved] (HBASE-18545) Fix broke site build that fails in rsgroups

[stack (JIRA)]

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

stack resolved HBASE-18545.
---
   Resolution: Fixed
Fix Version/s: 3.0.0

I pushed this. It seems to fix it:

{code}
commit 794a3b104bf62d028fc8ae27596c3b98ef87e507
Author: Michael Stack 
Date:   Wed Aug 9 11:24:51 2017 -0700

HBASE-18545 Fix broke site build that fails in rsgroups

diff --git a/hbase-rsgroup/pom.xml b/hbase-rsgroup/pom.xml
index 0bbabe93ff..a3e710cac2 100644
--- a/hbase-rsgroup/pom.xml
+++ b/hbase-rsgroup/pom.xml
@@ -60,6 +60,11 @@
 
   compile
 
+
+  
+
${basedir}/../hbase-protocol/src/main/protobuf
+  
+
   
 
   
{code}

Repro'd the issue by running commands found here:

https://builds.apache.org/view/H-L/view/HBase/job/hbase_generate_website/configure

> Fix broke site build that fails in rsgroups
> ---
>
> Key: HBASE-18545
> URL: https://issues.apache.org/jira/browse/HBASE-18545
> Project: HBase
>  Issue Type: Bug
>  Components: site
>Reporter: stack
>Assignee: stack
> Fix For: 3.0.0
>
>
> Site is broke because of a failure finding .proto files (was pointed out on 
> list and in closed proto issue...). Failure looks like this:
> {code}
> [INFO] --- protobuf-maven-plugin:0.5.0:compile (compile-protoc) @ 
> hbase-rsgroup ---
> [INFO] Compiling 2 proto file(s) to 
> /home/jenkins/jenkins-slave/workspace/hbase_generate_website/hbase/hbase-rsgroup/target/generated-sources/protobuf/java
> [ERROR] PROTOC FAILED: HBase.proto: File not found.
> RSGroup.proto: Import "HBase.proto" was not found or had errors.
> RSGroup.proto:31:12: "ServerName" is not defined.
> RSGroup.proto:32:12: "TableName" is not defined.
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/hbase_generate_website/hbase/hbase-rsgroup/src/main/protobuf/RSGroup.proto
>  [0:0]: HBase.proto: File not found.
> RSGroup.proto: Import "HBase.proto" was not found or had errors.
> RSGroup.proto:31:12: "ServerName" is not defined.
> RSGroup.proto:32:12: "TableName" is not defined.
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/hbase_generate_website/hbase/hbase-rsgroup/src/main/protobuf/RSGroupAdmin.proto
>  [0:0]: HBase.proto: File not found.
> RSGroup.proto: Import "HBase.proto" was not found or had errors.
> RSGroup.proto:31:12: "ServerName" is not defined.
> RSGroup.proto:32:12: "TableName" is not defined.
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HBASE-18545) Fix broke site build that fails in rsgroups

[stack (JIRA)]

stack created HBASE-18545:
-

 Summary: Fix broke site build that fails in rsgroups
 Key: HBASE-18545
 URL: https://issues.apache.org/jira/browse/HBASE-18545
 Project: HBase
  Issue Type: Bug
  Components: site
Reporter: stack
Assignee: stack


Site is broke because of a failure finding .proto files (was pointed out on 
list and in closed proto issue...). Failure looks like this:

{code}
[INFO] --- protobuf-maven-plugin:0.5.0:compile (compile-protoc) @ hbase-rsgroup 
---
[INFO] Compiling 2 proto file(s) to 
/home/jenkins/jenkins-slave/workspace/hbase_generate_website/hbase/hbase-rsgroup/target/generated-sources/protobuf/java
[ERROR] PROTOC FAILED: HBase.proto: File not found.
RSGroup.proto: Import "HBase.proto" was not found or had errors.
RSGroup.proto:31:12: "ServerName" is not defined.
RSGroup.proto:32:12: "TableName" is not defined.

[ERROR] 
/home/jenkins/jenkins-slave/workspace/hbase_generate_website/hbase/hbase-rsgroup/src/main/protobuf/RSGroup.proto
 [0:0]: HBase.proto: File not found.
RSGroup.proto: Import "HBase.proto" was not found or had errors.
RSGroup.proto:31:12: "ServerName" is not defined.
RSGroup.proto:32:12: "TableName" is not defined.

[ERROR] 
/home/jenkins/jenkins-slave/workspace/hbase_generate_website/hbase/hbase-rsgroup/src/main/protobuf/RSGroupAdmin.proto
 [0:0]: HBase.proto: File not found.
RSGroup.proto: Import "HBase.proto" was not found or had errors.
RSGroup.proto:31:12: "ServerName" is not defined.
RSGroup.proto:32:12: "TableName" is not defined.
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Still Failing: HBase Generate Website

[Ted Yu]

Have you looked at the following ?

https://builds.apache.org/job/hbase_generate_website/1072/artifact/hbase-install-log-82d554e3783372cc6b05489452c815b57c06f6cd.txt

Cheers

On Wed, Aug 9, 2017 at 8:25 AM, Mike Drob  wrote:

> I tried to look at this failure on Jenkins, but couldn't make sense of it
> -- there's barely any information there. Does anybody else have experience
> with this job?
>
> Mike
>
> On Wed, Aug 9, 2017 at 9:53 AM, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
> > Build status: Still Failing
> >
> > The HBase website has not been updated to incorporate HBase commit
> > ${HBASE_GIT_SHA}.
> >
> > See https://builds.apache.org/job/hbase_generate_website/1075/console
>

Re: Still Failing: HBase Generate Website

[Mike Drob]

I tried to look at this failure on Jenkins, but couldn't make sense of it
-- there's barely any information there. Does anybody else have experience
with this job?

Mike

On Wed, Aug 9, 2017 at 9:53 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Still Failing
>
> The HBase website has not been updated to incorporate HBase commit
> ${HBASE_GIT_SHA}.
>
> See https://builds.apache.org/job/hbase_generate_website/1075/console

Re: DISCUSS: How can we have less branches?

[Mike Drob]

One thing that we need to be super careful about after releasing 2.0 is
that we don't accidentally introduce any incompatible changes. It's much
harder to reason about forwards compatibility than backwards compatibility
in my experience. So even though a hypothetical 1.5 would be released after
2.0, users would still have the expectation that a 1.5->2.0 upgrade would
be smooth (unless we explicitly message that it isn't but that is a whole
new set of problems).

Also, to clarify some context here -- what is the difference between an LTS
branch and a Stable branch? Don't they convey the same thing to users? As a
relative newcomer, I feel like I missed an earlier conversation about this.

Mike

On Tue, Aug 8, 2017 at 10:45 PM, Phil Yang  wrote:

> Another option is no 1.5/branch-1 any more. What new features we are going
> to have in HBase 1.5 (if it will be released)? Backporting from branch-2 to
> branch-1 is not easy, so maybe we will not have any big feature in branch-1
> after releasing 1.4. And if we release 1.5 after releasing 2.0, it may
> confuse users. So IMO we can focus on branch-2 for new features.
>
> I think it will be good if we have fixed logic for EOL branches, for
> example(just an example, can discuss):
> 1:Release a final version and EOL 1.x after we think 1.x+1 is stable.
> 2:Cut off new 1.x+2 branch after 1.x+1 is stable, don't cut too early.
>
> Then we will not need discussing each time for each branch EOL and we will
> have a fixed number of maintaining branches.
>
> Thanks,
> Phil
>
>
> 2017-08-09 1:44 GMT+08:00 Andrew Purtell :
>
> > Well you are not wrong that branching was premature, it turns out. But
> I'll
> > roll with it...
> >
> >
> > On Tue, Aug 8, 2017 at 10:43 AM, Zach York  >
> > wrote:
> >
> > > > I made branch-1.4 a few weeks ago only.
> > >
> > > Whoops, sorry for that! For some reason I thought I had seen it months
> > ago.
> > >
> > > On Tue, Aug 8, 2017 at 10:40 AM, Andrew Purtell 
> > > wrote:
> > >
> > > > +1 from me on making 1.1 our LTS. Either 1.1 or 1.2 are candidates. I
> > > think
> > > > 1.1 has the edge because it lacks locking changes introduced into
> 1.2,
> > > just
> > > > like 1.2 lacks locking changes introduced in 1.3 - the latter of
> which
> > > has
> > > > had far reaching consequences, and the former not an insignificant
> > change
> > > > either.
> > > >
> > > >
> > > >
> > > > On Tue, Aug 8, 2017 at 10:31 AM, Nick Dimiduk 
> > > wrote:
> > > >
> > > > > On Tue, Aug 8, 2017 at 9:15 AM Mike Drob  wrote:
> > > > >
> > > > > > > The discussion also brought up the notion of an LTS release
> line.
> > > I'm
> > > > > not
> > > > > > > sure how this jives with the more fequent minors, but would
> > require
> > > > > some
> > > > > > > branch that's so stable that an RM can effectively spin
> releases
> > > > blind.
> > > > > >
> > > > > > Seems to me like this branch would necessarily need to be very
> > > > > > backport-light? Only the top of the highest priority issues would
> > be
> > > > > > backportable to it, no?
> > > > >
> > > > >
> > > > > The LTS is as 1.1 is today -- bug fixes only. The difference here
> is
> > > we'd
> > > > > "formally" recognize the LTS designation somehow, perhaps with a
> > > symlink
> > > > > marker as we do for the "stable" designation.
> > > > >
> > > > > On Tue, Aug 8, 2017 at 11:09 AM, Nick Dimiduk  >
> > > > wrote:
> > > > > >
> > > > > > > Last time we DISCUSSed EOL of 1.1 was back in November. At that
> > > > time, a
> > > > > > > litany of issues were raised re: 1.2. Have those concerns been
> > > > > addressed?
> > > > > > > It seems to me that making this one the last release is too
> > abrupt
> > > to
> > > > > > folks
> > > > > > > tracking Apache. Would be better to give some notice.
> > > > > > >
> > > > > > > Had a nice hallway conversation a couple months back (at
> > > PhoenixCon,
> > > > as
> > > > > > it
> > > > > > > happens; they feel the pain as well) about our branch
> situation.
> > > I'll
> > > > > let
> > > > > > > the others chime in with more details, but the gist as I recall
> > is
> > > > that
> > > > > > we
> > > > > > > should be doing more frequent minor releases with fewer patch
> > > > releases.
> > > > > > > This pushes stabilization efforts closer to master and also
> > imposes
> > > > > more
> > > > > > > strict stability requirements on big new features before they
> can
> > > be
> > > > > > merged
> > > > > > > off the feature branch.
> > > > > > >
> > > > > > > The discussion also brought up the notion of an LTS release
> line.
> > > I'm
> > > > > not
> > > > > > > sure how this jives with the more fequent minors, but would
> > require
> > > > > some
> > > > > > > branch that's so stable that an RM can effectively spin
> releases
> > > > blind.
> > > > > > >
> > > > > > > On Tue, Aug 8, 2017 at 12:14 AM Stack 

Still Failing: HBase Generate Website

[Apache Jenkins Server]

Build status: Still Failing

The HBase website has not been updated to incorporate HBase commit 
${HBASE_GIT_SHA}.

See https://builds.apache.org/job/hbase_generate_website/1075/console

Fwd: Ycsb and Hbase - read+write simulation.

[Meirav Malka]

-- Forwarded message --
From: "meirav.malka" 
Date: Aug 9, 2017 10:56
Subject: Ycsb and Hbase - read+write simulation.
To: "Hbase User Group" 
Cc:

Hi everyone,

Does anyone know of a ycdb option that will allow the following read
request distribution:


1. 90% of the material read was inserted in the last 24 hours.
2. 97% in the last 2 hours.

The only options i see for request distribution is "latest", "zipfian" and
"uniform"

Is there anyway to provide an this distribution?

Thanks!


Sent from my Samsung Galaxy smartphone.

[jira] [Created] (HBASE-18544) Move the HRegion#addRegionToMETA to TestDefaultMemStore

[Chia-Ping Tsai (JIRA)]

Chia-Ping Tsai created HBASE-18544:
--

 Summary: Move the HRegion#addRegionToMETA to TestDefaultMemStore
 Key: HBASE-18544
 URL: https://issues.apache.org/jira/browse/HBASE-18544
 Project: HBase
  Issue Type: Task
  Components: regionserver
Affects Versions: 2.0.0-alpha-1, 3.0.0
Reporter: Chia-Ping Tsai
Priority: Minor
 Fix For: 3.0.0, 2.0.0-alpha-2


The usages of addRegionToMETA  are almost removed by HBASE-17470. 
HRegion#addRegionToMETA is used only by TestDefaultMemStore now. Let us reduce 
the file size of HRegion.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)