phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Istvan Toth <st...@apache.org>
Subject Re: [jira] [Updated] (PHOENIX-5902) Document or fix new compat jar behavior.
Date Mon, 18 May 2020 09:14:03 GMT
Thanks for tracking this down and filing the ticket.

I've uploaded the patch, please test it!

On Mon, May 18, 2020 at 12:54 AM Lars Hofhansl (Jira) <jira@apache.org>
wrote:

>
>      [
> https://issues.apache.org/jira/browse/PHOENIX-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Lars Hofhansl updated PHOENIX-5902:
> -----------------------------------
>     Description:
> After PHOENIX-5808 (I think), the compat classes are no longer included in
> Phoenix' server jar.
>
> This causes the HBase regionservers to fail with:
> 2020-05-15 15:35:36,098 FATAL [RS_OPEN_PRIORITY_REGION-host:16201-1]
> regionserver.HRegionServer: ABORTING region server
> think,16201,1589581955446: The coprocessor
> org.apache.phoenix.coprocessor.UngroupedAggregateRegionObserver threw
> java.lang.NoClassDefFoundError:
> org/apache/phoenix/compat/hbase/CompatRpcControllerFactory
>
> It is now necessary to copy
> lib/phoenix-hbase-compat-1.5.0-4.16.0-SNAPSHOT.jar into HBase's lib
> directory as well.
>
> The jar in the Phoenix directory is called:
> phoenix-server-4.16.0-SNAPSHOT-hbase-1.5.jar, so I do not see why it could
> not include the compatibility classes.
>
> Alternatively we can rename that jar to just
> phoenix-server-4.16.0-SNAPSHOT.jar and place the compatbility jar in
> Phoenix' top level directory and document the change.
>
> (Of course a release would not have SNAPSHOT in the name...)
>
> Marking as blocker for 4.16.0, because as is, it will bring HBase down
> hard upon upgrade if this is not kept in mind.
>
>   was:
> After PHOENIX-5808 (I think), the compat classes are no longer included in
> Phoenix' server jar.
>
> This causes the HBase regionservers to fail with:
> 2020-05-15 15:35:36,098 FATAL [RS_OPEN_PRIORITY_REGION-host:16201-1]
> regionserver.HRegionServer: ABORTING region server
> think,16201,1589581955446: The coprocessor
> org.apache.phoenix.coprocessor.UngroupedAggregateRegionObserver threw
> java.lang.NoClassDefFoundError:
> org/apache/phoenix/compat/hbase/CompatRpcControllerFactory
>
> It is now necessary to copy
> lib/phoenix-hbase-compat-1.5.0-4.16.0-SNAPSHOT.jar into HBase's lib
> directory as well.
>
> The jar in the Phoenix directory is called:
> phoenix-server-4.16.0-SNAPSHOT-hbase-1.5.jar, so I do not see why it could
> not include the compatibility classes.
>
> Alternatively we can rename that jar to just
> phoenix-server-4.16.0-SNAPSHOT.jar and place the compatbility jar in
> Phoenix' top level directory and document the change.
>
> Marking as blocker for 4.16.0, because as is, it will bring HBase down
> hard upon upgrade if this is not kept in mind.
>
>
> > Document or fix new compat jar behavior.
> > ----------------------------------------
> >
> >                 Key: PHOENIX-5902
> >                 URL: https://issues.apache.org/jira/browse/PHOENIX-5902
> >             Project: Phoenix
> >          Issue Type: Bug
> >    Affects Versions: 5.1.0, 4.16.0
> >            Reporter: Lars Hofhansl
> >            Priority: Blocker
> >             Fix For: 5.1.0, 4.16.0
> >
> >
> > After PHOENIX-5808 (I think), the compat classes are no longer included
> in Phoenix' server jar.
> > This causes the HBase regionservers to fail with:
> > 2020-05-15 15:35:36,098 FATAL [RS_OPEN_PRIORITY_REGION-host:16201-1]
> regionserver.HRegionServer: ABORTING region server
> think,16201,1589581955446: The coprocessor
> org.apache.phoenix.coprocessor.UngroupedAggregateRegionObserver threw
> java.lang.NoClassDefFoundError:
> org/apache/phoenix/compat/hbase/CompatRpcControllerFactory
> > It is now necessary to copy
> lib/phoenix-hbase-compat-1.5.0-4.16.0-SNAPSHOT.jar into HBase's lib
> directory as well.
> > The jar in the Phoenix directory is called:
> phoenix-server-4.16.0-SNAPSHOT-hbase-1.5.jar, so I do not see why it could
> not include the compatibility classes.
> > Alternatively we can rename that jar to just
> phoenix-server-4.16.0-SNAPSHOT.jar and place the compatbility jar in
> Phoenix' top level directory and document the change.
> > (Of course a release would not have SNAPSHOT in the name...)
> > Marking as blocker for 4.16.0, because as is, it will bring HBase down
> hard upon upgrade if this is not kept in mind.
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message