[jira] [Resolved] (PHOENIX-7115) Create separate handler thread pool for invalidating server metadata cache

[Rushabh Shah (Jira)]

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

Rushabh Shah resolved PHOENIX-7115.
---
Resolution: Fixed

> Create separate handler thread pool for invalidating server metadata cache
> --
>
> Key: PHOENIX-7115
> URL: https://issues.apache.org/jira/browse/PHOENIX-7115
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Rushabh Shah
>Assignee: Rushabh Shah
>Priority: Major
>
> MutableIndexFailureIT#testIndexWriteFailure is failing. See 
> [this|https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1726/9/#showFailuresLink]
>  build for reference.
> Currently all the invalidateServerMetadataCache invocations are handled by 
> default RPC handler threads. We have 5 default handler threads configured in 
> tests. 
> This test makes sure that write to index table fails and since 
> disableIndexOnWriteFailure is set to true, it will disable the index. We use 
> around 10 different threads on the client side to write to base table and  
> index table, so we use all the 5 handler threads to serve writes.
> Since writes to index fails, within the handler threads it will try to update 
> the index state to  DISABLE. 
> On receiving the updateIndexState rpc, MetadataEndpointImpl will try to 
> invalidate the server metadata cache on all the regionservers. The 
> regionserver hosting index table doesn't have any available handler threads 
> to serve invalidateServerMetadataCache requests. Hence the test fails.
> The root cause is all the read/write operations and invalidate server 
> metadata cache operations share the same RPC handler pool. We need to have 
> separate thread pool for 
> invalidate server metadata cache operations



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (PHOENIX-7159) ParallelPhoenixConnectionIT#testConnectionErrorCount is taking 10 minutes to complete.

[Rushabh Shah (Jira)]

Rushabh Shah created PHOENIX-7159:
-

 Summary: ParallelPhoenixConnectionIT#testConnectionErrorCount is 
taking 10 minutes to complete.
 Key: PHOENIX-7159
 URL: https://issues.apache.org/jira/browse/PHOENIX-7159
 Project: Phoenix
  Issue Type: Bug
  Components: core
Reporter: Rushabh Shah


ParallelPhoenixConnectionIT#testConnectionErrorCount is taking 10 minutes to 
complete.
See the build here: 
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1771/2/testReport/junit/org.apache.phoenix.jdbc/ParallelPhoenixConnectionIT/testConnectionErrorCount/

This is an insane amount of time. We should have some rule to limit the 
execution of test to some reasonable amount of time.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Meet our keynote speakers and register to Community Over Code EU!

[Ryan Skraba]

[Note: You're receiving this email because you are subscribed to one or
more project dev@ mailing lists at the Apache Software Foundation.]











*
Merge
with the ASF EUniverse!The registration for Community Over Code Europe is
finally open! Get your tickets now and save your spot!
We are happy to announce that we
have confirmed the first featured speakers
!  - Asim Hussain, Executive
Director at Green Software Foundation- Dirk-Willem Van Gulik, VP of Public
Policy at The Apache Software Foundation- Ruth Ikega, Community Lead at
CHAOSS Africa Visit our website
 to learn more about this
amazing lineup.CFP is openWe are looking forward to hearing all you have to
share with the Apache Community. Please submit your talk proposal
 before January 12, 2024.Interested in
boosting your brand?Take a look at our prospectus

and find out the opportunities we have for you. Be one step ahead and book
your room at the hotel venueWe have a special rate for you at the Radisson
Blu Carlton, the hotel that will hold Community Over Code EU. Learn more
about the location and venue 
and book your accommodation. Should you have any questions, please do not
hesitate to contact us. We wish you Happy Holidays in the company of your
loved ones! See you in Bratislava next year!Community Over Code EU
Organizer Committee*

[jira] [Updated] (PHOENIX-7130) Support skipping of shade sources jar creation

[Nihal Jain (Jira)]

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

Nihal Jain updated PHOENIX-7130:

Labels: build  (was: )

> Support skipping of shade sources jar creation
> --
>
> Key: PHOENIX-7130
> URL: https://issues.apache.org/jira/browse/PHOENIX-7130
> Project: Phoenix
>  Issue Type: Improvement
>  Components: phoenix
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Minor
>  Labels: build
>
> Shade sources jar creation takes a lot of time and we do not want to do this 
> for every dev build (in our internal phoenix jenkins). Hence with this Jira, 
> will add a profile to disable shade jar creation optionally by running with 
> '-PskipShadeSources'.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7130) Support skipping of shade sources jar creation

[Nihal Jain (Jira)]

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

Nihal Jain updated PHOENIX-7130:

Summary: Support skipping of shade sources jar creation  (was: Add maven 
profile to support skipping of shade sources jar creation)

> Support skipping of shade sources jar creation
> --
>
> Key: PHOENIX-7130
> URL: https://issues.apache.org/jira/browse/PHOENIX-7130
> Project: Phoenix
>  Issue Type: Improvement
>  Components: phoenix
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Minor
>
> Shade sources jar creation takes a lot of time and we do not want to do this 
> for every dev build (in our internal phoenix jenkins). Hence with this Jira, 
> will add a profile to disable shade jar creation optionally by running with 
> '-PskipShadeSources'.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (PHOENIX-7158) Update Connectors to phoenix-thirdparty 2.1.0

[Nihal Jain (Jira)]

Nihal Jain created PHOENIX-7158:
---

 Summary: Update Connectors to phoenix-thirdparty 2.1.0
 Key: PHOENIX-7158
 URL: https://issues.apache.org/jira/browse/PHOENIX-7158
 Project: Phoenix
  Issue Type: Improvement
  Components: core
Reporter: Nihal Jain
Assignee: Nihal Jain


Phoenix-thirdparty has been released, see 
[https://www.mail-archive.com/user@phoenix.apache.org/msg08204.html]
{quote}The recent release has upgraded Guava to version 32.1.3-jre from the 
previous 31.0.1-android version. Initially, the 4.x branch maintained 
compatibility with Java 7, necessitating the use of the Android variant of 
Guava. However, with the end-of-life (EOL) status of the 4.x branch, the move 
to the standard JRE version of Guava signifies a shift in compatibility 
standards
{quote}
It's time we bump up. Also, now PHOENIX-7116 is in place so we can pull this to 
branch 5.1.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7158) Update Connectors to phoenix-thirdparty 2.1.0

[Nihal Jain (Jira)]

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

Nihal Jain updated PHOENIX-7158:

Component/s: connectors
 (was: core)

> Update Connectors to phoenix-thirdparty 2.1.0
> -
>
> Key: PHOENIX-7158
> URL: https://issues.apache.org/jira/browse/PHOENIX-7158
> Project: Phoenix
>  Issue Type: Improvement
>  Components: connectors
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>
> Phoenix-thirdparty has been released, see 
> [https://www.mail-archive.com/user@phoenix.apache.org/msg08204.html]
> {quote}The recent release has upgraded Guava to version 32.1.3-jre from the 
> previous 31.0.1-android version. Initially, the 4.x branch maintained 
> compatibility with Java 7, necessitating the use of the Android variant of 
> Guava. However, with the end-of-life (EOL) status of the 4.x branch, the move 
> to the standard JRE version of Guava signifies a shift in compatibility 
> standards
> {quote}
> It's time we bump up. Also, now PHOENIX-7116 is in place so we can pull this 
> to branch 5.1.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (PHOENIX-7157) Upgrade to phoenix-thirdparty 2.1.0

[Nihal Jain (Jira)]

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

Nihal Jain updated PHOENIX-7157:

Description: 
Phoenix-thirdparty has been released, see 
[https://www.mail-archive.com/user@phoenix.apache.org/msg08204.html]
{quote}The recent release has upgraded Guava to version 32.1.3-jre from the 
previous 31.0.1-android version. Initially, the 4.x branch maintained 
compatibility with Java 7, necessitating the use of the Android variant of 
Guava. However, with the end-of-life (EOL) status of the 4.x branch, the move 
to the standard JRE version of Guava signifies a shift in compatibility 
standards
{quote}
It's time we bump up. Also, now PHOENIX-7116 is in place so we can pull this to 
branch 5.1.

> Upgrade to phoenix-thirdparty 2.1.0
> ---
>
> Key: PHOENIX-7157
> URL: https://issues.apache.org/jira/browse/PHOENIX-7157
> Project: Phoenix
>  Issue Type: Improvement
>  Components: core
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>
> Phoenix-thirdparty has been released, see 
> [https://www.mail-archive.com/user@phoenix.apache.org/msg08204.html]
> {quote}The recent release has upgraded Guava to version 32.1.3-jre from the 
> previous 31.0.1-android version. Initially, the 4.x branch maintained 
> compatibility with Java 7, necessitating the use of the Android variant of 
> Guava. However, with the end-of-life (EOL) status of the 4.x branch, the move 
> to the standard JRE version of Guava signifies a shift in compatibility 
> standards
> {quote}
> It's time we bump up. Also, now PHOENIX-7116 is in place so we can pull this 
> to branch 5.1.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (PHOENIX-7157) Upgrade to phoenix-thirdparty 2.1.0

[Nihal Jain (Jira)]

Nihal Jain created PHOENIX-7157:
---

 Summary: Upgrade to phoenix-thirdparty 2.1.0
 Key: PHOENIX-7157
 URL: https://issues.apache.org/jira/browse/PHOENIX-7157
 Project: Phoenix
  Issue Type: Improvement
  Components: core
Reporter: Nihal Jain
Assignee: Nihal Jain






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (OMID-254) Upgrade to phoenix-thirdparty 2.1.0

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/OMID-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799729#comment-17799729
 ] 

ASF GitHub Bot commented on OMID-254:
-

chrajeshbabu commented on PR #151:
URL: https://github.com/apache/phoenix-omid/pull/151#issuecomment-1867419622

   +lgtm




> Upgrade to phoenix-thirdparty 2.1.0
> ---
>
> Key: OMID-254
> URL: https://issues.apache.org/jira/browse/OMID-254
> Project: Phoenix Omid
>  Issue Type: Sub-task
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>
> Phoenix-thirdparty has been released, see 
> [https://www.mail-archive.com/user@phoenix.apache.org/msg08204.html]
> {quote}The recent release has upgraded Guava to version 32.1.3-jre from the 
> previous 31.0.1-android version. Initially, the 4.x branch maintained 
> compatibility with Java 7, necessitating the use of the Android variant of 
> Guava. However, with the end-of-life (EOL) status of the 4.x branch, the move 
> to the standard JRE version of Guava signifies a shift in compatibility 
> standards
> {quote}
> It's time we bump up.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (OMID-254) Upgrade to phoenix-thirdparty 2.1.0

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/OMID-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799726#comment-17799726
 ] 

ASF GitHub Bot commented on OMID-254:
-

NihalJain commented on PR #151:
URL: https://github.com/apache/phoenix-omid/pull/151#issuecomment-1867416988

   Built code locally and ran tests.:
   ```
   mvn clean install -Dhbase.version=2.5.6-hadoop3 -DskipTests
   mvn verify -Dsurefire.rerunFailingTestsCount=5 -Dhbase.version=2.5.6-hadoop3
   ```
   FYI @chrajeshbabu , @stoty , @gjacoby126 




> Upgrade to phoenix-thirdparty 2.1.0
> ---
>
> Key: OMID-254
> URL: https://issues.apache.org/jira/browse/OMID-254
> Project: Phoenix Omid
>  Issue Type: Sub-task
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>
> Phoenix-thirdparty has been released, see 
> [https://www.mail-archive.com/user@phoenix.apache.org/msg08204.html]
> {quote}The recent release has upgraded Guava to version 32.1.3-jre from the 
> previous 31.0.1-android version. Initially, the 4.x branch maintained 
> compatibility with Java 7, necessitating the use of the Android variant of 
> Guava. However, with the end-of-life (EOL) status of the 4.x branch, the move 
> to the standard JRE version of Guava signifies a shift in compatibility 
> standards
> {quote}
> It's time we bump up.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (OMID-254) Upgrade to phoenix-thirdparty 2.1.0

[Nihal Jain (Jira)]

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

Nihal Jain updated OMID-254:

Description: 
Phoenix-thirdparty has been released, see 
[https://www.mail-archive.com/user@phoenix.apache.org/msg08204.html]
{quote}The recent release has upgraded Guava to version 32.1.3-jre from the 
previous 31.0.1-android version. Initially, the 4.x branch maintained 
compatibility with Java 7, necessitating the use of the Android variant of 
Guava. However, with the end-of-life (EOL) status of the 4.x branch, the move 
to the standard JRE version of Guava signifies a shift in compatibility 
standards
{quote}
It's time we bump up.

  was:
Phoenix-thirdparty has been releases, see 
[https://www.mail-archive.com/user@phoenix.apache.org/msg08204.html]
{quote}The recent release has upgraded Guava to version 32.1.3-jre from the 
previous 31.0.1-android version. Initially, the 4.x branch maintained 
compatibility with Java 7, necessitating the use of the Android variant of 
Guava. However, with the end-of-life (EOL) status of the 4.x branch, the move 
to the standard JRE version of Guava signifies a shift in compatibility 
standards{quote}


> Upgrade to phoenix-thirdparty 2.1.0
> ---
>
> Key: OMID-254
> URL: https://issues.apache.org/jira/browse/OMID-254
> Project: Phoenix Omid
>  Issue Type: Sub-task
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>
> Phoenix-thirdparty has been released, see 
> [https://www.mail-archive.com/user@phoenix.apache.org/msg08204.html]
> {quote}The recent release has upgraded Guava to version 32.1.3-jre from the 
> previous 31.0.1-android version. Initially, the 4.x branch maintained 
> compatibility with Java 7, necessitating the use of the Android variant of 
> Guava. However, with the end-of-life (EOL) status of the 4.x branch, the move 
> to the standard JRE version of Guava signifies a shift in compatibility 
> standards
> {quote}
> It's time we bump up.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (OMID-254) Upgrade to phoenix-thirdparty 2.1.0

[Nihal Jain (Jira)]

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

Nihal Jain updated OMID-254:

Description: 
Phoenix-thirdparty has been releases, see 
[https://www.mail-archive.com/user@phoenix.apache.org/msg08204.html]
{quote}The recent release has upgraded Guava to version 32.1.3-jre from the 
previous 31.0.1-android version. Initially, the 4.x branch maintained 
compatibility with Java 7, necessitating the use of the Android variant of 
Guava. However, with the end-of-life (EOL) status of the 4.x branch, the move 
to the standard JRE version of Guava signifies a shift in compatibility 
standards{quote}

> Upgrade to phoenix-thirdparty 2.1.0
> ---
>
> Key: OMID-254
> URL: https://issues.apache.org/jira/browse/OMID-254
> Project: Phoenix Omid
>  Issue Type: Sub-task
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>
> Phoenix-thirdparty has been releases, see 
> [https://www.mail-archive.com/user@phoenix.apache.org/msg08204.html]
> {quote}The recent release has upgraded Guava to version 32.1.3-jre from the 
> previous 31.0.1-android version. Initially, the 4.x branch maintained 
> compatibility with Java 7, necessitating the use of the Android variant of 
> Guava. However, with the end-of-life (EOL) status of the 4.x branch, the move 
> to the standard JRE version of Guava signifies a shift in compatibility 
> standards{quote}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (OMID-254) Upgrade to phoenix-thirdparty 2.1.0

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/OMID-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799723#comment-17799723
 ] 

ASF GitHub Bot commented on OMID-254:
-

NihalJain opened a new pull request, #151:
URL: https://github.com/apache/phoenix-omid/pull/151

   (no comment)




> Upgrade to phoenix-thirdparty 2.1.0
> ---
>
> Key: OMID-254
> URL: https://issues.apache.org/jira/browse/OMID-254
> Project: Phoenix Omid
>  Issue Type: Sub-task
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>
> Phoenix-thirdparty has been released, see 
> [https://www.mail-archive.com/user@phoenix.apache.org/msg08204.html]
> {quote}The recent release has upgraded Guava to version 32.1.3-jre from the 
> previous 31.0.1-android version. Initially, the 4.x branch maintained 
> compatibility with Java 7, necessitating the use of the Android variant of 
> Guava. However, with the end-of-life (EOL) status of the 4.x branch, the move 
> to the standard JRE version of Guava signifies a shift in compatibility 
> standards
> {quote}
> It's time we bump up.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (OMID-254) Upgrade to phoenix-thirdparty 2.1.0

[Nihal Jain (Jira)]

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

Nihal Jain reassigned OMID-254:
---

Assignee: Nihal Jain

> Upgrade to phoenix-thirdparty 2.1.0
> ---
>
> Key: OMID-254
> URL: https://issues.apache.org/jira/browse/OMID-254
> Project: Phoenix Omid
>  Issue Type: Sub-task
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (OMID-254) Upgrade to phoenix-thirdparty 2.1.0

[Nihal Jain (Jira)]

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

Nihal Jain updated OMID-254:

Summary: Upgrade to phoenix-thirdparty 2.1.0  (was: [Placeholder] Upgrade 
to latest phoenix-thirdparty release)

> Upgrade to phoenix-thirdparty 2.1.0
> ---
>
> Key: OMID-254
> URL: https://issues.apache.org/jira/browse/OMID-254
> Project: Phoenix Omid
>  Issue Type: Sub-task
>Reporter: Nihal Jain
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)