[jira] [Commented] (OMID-273) IPv6 not working on Mac
[ https://issues.apache.org/jira/browse/OMID-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808669#comment-17808669 ] Richárd Antal commented on OMID-273: With your change for OMID-249 this tests passes on my Mac. Note that it uses IPv4 ip but that is OK > IPv6 not working on Mac > --- > > Key: OMID-273 > URL: https://issues.apache.org/jira/browse/OMID-273 > Project: Phoenix Omid > Issue Type: Bug >Reporter: Richárd Antal >Assignee: Istvan Toth >Priority: Major > > During the OMID 1.1.1 RC0 release we found that TestTSOClientConnectionToTSO > had failing tests: > testSuccessfulConnectionToTSOThroughZK and > testSuccessOfTSOClientReconnectionsToARestartedTSOWithZKPublishing > It might be because it uses IPv6 > 2024-01-17T15:17:45,858 INFO > [TestNGInvoker-testSuccessfulConnectionToTSOThroughZK()] client.TSOClient: * > Current TSO host:port found in ZK: [fe80:0:0:0:aede:48ff:fe00:1122%en5]:52934 > Epoch 0 > 2024-01-17T15:17:45,859 INFO [tsofsm-0] client.TSOClient: Trying to > connect to TSO [/fe80:0:0:0:aede:48ff:fe00:1122%en5:52934] > 2024-01-17T15:17:45,863 ERROR [tsoclient-worker-0] client.TSOClient: Failed > connection attempt to TSO [/fe80:0:0:0:aede:48ff:fe00:1122%en5:52934] failed. > Channel [id: 0x9d8c0b44] > I've checked this en5 interface and it has only IPv6 and no IPv4 > I ran a git bisect but it wasn't very useful. Before OMID-248 > TestTSOClientConnectionToTSO used IPv4 and after it, it is using IPv6 and > failing on my Mac -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [CANCEL][VOTE] Release of Apache Phoenix Omid 1.1.1 RC0
We have worked on this with Richard. I have made some changes to force the test to use IPv6 on my Linux machine, and it still works fine. It is some funky mac networking issue: https://medium.com/@quelgar/java-sockets-broken-for-ipv6-on-mac-5aae72f06b21 Please review https://issues.apache.org/jira/browse/OMID-249, which fixes the issue (at least on Richard's particular mac) best regards Istvan On Fri, Jan 19, 2024 at 8:07 AM Istvan Toth wrote: > Someone who has access to a Mac please try to track down which change > broke the tests. > > > On Fri, Jan 19, 2024 at 8:05 AM Istvan Toth wrote: > >> PR for JDK17 support is up: >> https://issues.apache.org/jira/browse/OMID-272 >> >> On Thu, Jan 18, 2024 at 6:39 PM rajeshb...@apache.org < >> chrajeshbab...@gmail.com> wrote: >> >>> The vote has been canceled to address issues with JDK and Ipv6 interface >>> in >>> MacOS >>> >>> Thanks, >>> Rajeshbabu. >>> >>> On Thu, Jan 18, 2024 at 11:05 PM rajeshb...@apache.org < >>> chrajeshbab...@gmail.com> wrote: >>> >>> > Sure, let me cancel the RC and create another RC after fixes with the >>> > network interface and JDK 17. >>> > >>> > Thanks, Richard and Istvan for finding issues, and Cong Luo for your >>> > support. >>> > >>> > >>> > >>> > >>> > >>> > On Thu, Jan 18, 2024 at 9:52 PM Istvan Toth >> > >>> > wrote: >>> > >>> >> I have found another problem, Omid doesn't work with JDK 17. >>> >> Not necessarily a blocker, but if we do another RC, it would be nice >>> to >>> >> include it. >>> >> >>> >> I'm also working on adding HBase 3 support, which requires a small API >>> >> change (that also affects Phoenix) >>> >> Again, not a blocker, but we'll have to do another release for 5.2 >>> sooner >>> >> than later for HBase 3 support. >>> >> >>> >> >>> >> On Thu, Jan 18, 2024 at 9:11 AM Cong Luo wrote: >>> >> >>> >> > Hi Istvan, >>> >> > Using ipv6 on linux operating systems is available, so the reason >>> may be >>> >> > limited to users using Mac OS. And then, I using the ping the ipv6 >>> >> address >>> >> > on Mac OS, got the 'Unknown host', obviously macos uses ipv6 as the >>> host >>> >> > name. based on this default behavior of the operating system, I >>> >> recommend >>> >> > using macos with ipv4 and others with ipv4/ipv6. >>> >> > >>> >> > On 2024/01/18 06:54:14 Istvan Toth wrote: >>> >> > > I think we should look into this a bit deeper. >>> >> > > Why does this fail with IPv6 ? >>> >> > > >>> >> > > Are we explicitly binding TSO to the IPv4 address only ? >>> >> > > Do we only do that in the tests, or does that happen in >>> production ? >>> >> > > Is it even possible to use Omid with IPv6 ? >>> >> > > >>> >> > > I suspect that fixing >>> https://issues.apache.org/jira/browse/OMID-249 >>> >> > would >>> >> > > improve on this. >>> >> > > >>> >> > > Generally, I think that having a single IP per TSO can be a >>> problem >>> >> in a >>> >> > > mixed IPv4 / IPv6 network, and with some network configurations. >>> >> > > Maybe we should store the name of the active server instead of >>> >> addresses >>> >> > in >>> >> > > ZK, and kick this problem down to the network/DNS administrator. >>> >> > > >>> >> > > If Omid is known to not work with IPV6 in 1.1.0 , then I'm OK with >>> >> Cong's >>> >> > > proposed solution, but if it breaks pre-existing Ipv6 support, >>> then we >>> >> > > should >>> >> > > fix this properly for 1.1.1. >>> >> > > >>> >> > > We should create a follow-up ticket to make sure the Omid is IPv6 >>> >> clean >>> >> > for >>> >> > > the next release at the very least. >>> >> > > >>> >> > > Istvan >>> >> > > >>> >> > > >>> >> > > On Thu, Jan 18, 2024 at 6:56 AM Cong Luo wrote: >>> >> > > >>> >> > > > Hi Richard, >>> >> > > > Actually, I had the same issue before, but it was resolved >>> >> locally: >>> >> > if >>> >> > > > the NIC was assigned both ipv4 and ipv6 addresses, use ipv4 >>> first. >>> >> If >>> >> > we >>> >> > > > all think this is acceptable, then I will create a PR >>> submission. >>> >> > > > >>> >> > > > On 2024/01/17 14:30:50 Richárd Antal wrote: >>> >> > > > > -1 >>> >> > > > > >>> >> > > > > Signature: OK >>> >> > > > > Checksum: OK >>> >> > > > > mvn clean apache-rat:check: OK >>> >> > > > > >>> >> > > > > Changes and release notes: OK >>> >> > > > > >>> >> > > > > Built from source (1.8.0_241): OK >>> >> > > > > - mvn clean install -DskipTests >>> >> > > > > Ran tests on my MacBook locally: >>> >> > > > > - mvn clean verify : Failed >>> >> > > > > TestTSOClientConnectionToTSO had failing tests: >>> >> > > > > testSuccessfulConnectionToTSOThroughZK and >>> >> > > > > >>> testSuccessOfTSOClientReconnectionsToARestartedTSOWithZKPublishing >>> >> > > > > It might be because it uses IPv6 >>> >> > > > > Some logs >>> >> > > > > >>> >> > > > > 2024-01-17T15:17:45,858 INFO >>> >> > > > > > [TestNGInvoker-testSuccessfulConnectionToTSOThroughZK()] >>> >> > > > client.TSOClient: >>> >> > > > > > * Current TSO host:port found in ZK: >>> >> > > > > > [fe80:0:0:0:aede:48ff:fe00:
[jira] [Commented] (OMID-273) IPv6 not working on Mac
[ https://issues.apache.org/jira/browse/OMID-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808660#comment-17808660 ] Istvan Toth commented on OMID-273: -- en5 is the touchbar's network on MacBooks. Something (firewall ?) prevents connecting to the TSO server on that address, even though we do not specify a bind address. Please test the PR for OMID-249, [~richardantal]. > IPv6 not working on Mac > --- > > Key: OMID-273 > URL: https://issues.apache.org/jira/browse/OMID-273 > Project: Phoenix Omid > Issue Type: Bug >Reporter: Richárd Antal >Assignee: Istvan Toth >Priority: Major > > During the OMID 1.1.1 RC0 release we found that TestTSOClientConnectionToTSO > had failing tests: > testSuccessfulConnectionToTSOThroughZK and > testSuccessOfTSOClientReconnectionsToARestartedTSOWithZKPublishing > It might be because it uses IPv6 > 2024-01-17T15:17:45,858 INFO > [TestNGInvoker-testSuccessfulConnectionToTSOThroughZK()] client.TSOClient: * > Current TSO host:port found in ZK: [fe80:0:0:0:aede:48ff:fe00:1122%en5]:52934 > Epoch 0 > 2024-01-17T15:17:45,859 INFO [tsofsm-0] client.TSOClient: Trying to > connect to TSO [/fe80:0:0:0:aede:48ff:fe00:1122%en5:52934] > 2024-01-17T15:17:45,863 ERROR [tsoclient-worker-0] client.TSOClient: Failed > connection attempt to TSO [/fe80:0:0:0:aede:48ff:fe00:1122%en5:52934] failed. > Channel [id: 0x9d8c0b44] > I've checked this en5 interface and it has only IPv6 and no IPv4 > I ran a git bisect but it wasn't very useful. Before OMID-248 > TestTSOClientConnectionToTSO used IPv4 and after it, it is using IPv6 and > failing on my Mac -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OMID-273) IPv6 not working on Mac
[ https://issues.apache.org/jira/browse/OMID-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned OMID-273: Assignee: Istvan Toth > IPv6 not working on Mac > --- > > Key: OMID-273 > URL: https://issues.apache.org/jira/browse/OMID-273 > Project: Phoenix Omid > Issue Type: Bug >Reporter: Richárd Antal >Assignee: Istvan Toth >Priority: Major > > During the OMID 1.1.1 RC0 release we found that TestTSOClientConnectionToTSO > had failing tests: > testSuccessfulConnectionToTSOThroughZK and > testSuccessOfTSOClientReconnectionsToARestartedTSOWithZKPublishing > It might be because it uses IPv6 > 2024-01-17T15:17:45,858 INFO > [TestNGInvoker-testSuccessfulConnectionToTSOThroughZK()] client.TSOClient: * > Current TSO host:port found in ZK: [fe80:0:0:0:aede:48ff:fe00:1122%en5]:52934 > Epoch 0 > 2024-01-17T15:17:45,859 INFO [tsofsm-0] client.TSOClient: Trying to > connect to TSO [/fe80:0:0:0:aede:48ff:fe00:1122%en5:52934] > 2024-01-17T15:17:45,863 ERROR [tsoclient-worker-0] client.TSOClient: Failed > connection attempt to TSO [/fe80:0:0:0:aede:48ff:fe00:1122%en5:52934] failed. > Channel [id: 0x9d8c0b44] > I've checked this en5 interface and it has only IPv6 and no IPv4 > I ran a git bisect but it wasn't very useful. Before OMID-248 > TestTSOClientConnectionToTSO used IPv4 and after it, it is using IPv6 and > failing on my Mac -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OMID-249) Improve default network address logic
[ https://issues.apache.org/jira/browse/OMID-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned OMID-249: Assignee: Istvan Toth > Improve default network address logic > - > > Key: OMID-249 > URL: https://issues.apache.org/jira/browse/OMID-249 > Project: Phoenix Omid > Issue Type: Improvement >Affects Versions: 1.1.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > > NetworkUtils.getNetworkInterface() seems to be only used for determining the > host and port when registering TSO to ZK for HA. > We should get the TSO public IP from the ZK TCP connection on demand, and not > worry about the default network interface at all. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OMID-249) Improve default network address logic
[ https://issues.apache.org/jira/browse/OMID-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808656#comment-17808656 ] ASF GitHub Bot commented on OMID-249: - stoty opened a new pull request, #154: URL: https://github.com/apache/phoenix-omid/pull/154 (no comment) > Improve default network address logic > - > > Key: OMID-249 > URL: https://issues.apache.org/jira/browse/OMID-249 > Project: Phoenix Omid > Issue Type: Improvement >Affects Versions: 1.1.0 >Reporter: Istvan Toth >Priority: Major > > NetworkUtils.getNetworkInterface() seems to be only used for determining the > host and port when registering TSO to ZK for HA. > We should get the TSO public IP from the ZK TCP connection on demand, and not > worry about the default network interface at all. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OMID-249) Improve default network address logic
[ https://issues.apache.org/jira/browse/OMID-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated OMID-249: - Summary: Improve default network address logic (was: Remove default network interface logic) > Improve default network address logic > - > > Key: OMID-249 > URL: https://issues.apache.org/jira/browse/OMID-249 > Project: Phoenix Omid > Issue Type: Improvement >Affects Versions: 1.1.0 >Reporter: Istvan Toth >Priority: Major > > NetworkUtils.getNetworkInterface() seems to be only used for determining the > host and port when registering TSO to ZK for HA. > We should get the TSO public IP from the ZK TCP connection on demand, and not > worry about the default network interface at all. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OMID-249) Remove default network interface logic
[ https://issues.apache.org/jira/browse/OMID-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808638#comment-17808638 ] Istvan Toth commented on OMID-249: -- There is no supported way to get the socket information from Zookeeper. There are some testing only methods that could be used, but I'd rather avoid that. My next idea is just to parse the quorum String, and take the first thing that looks like a hotsname/address, open a socket, and check the outgoing IpAddr. > Remove default network interface logic > -- > > Key: OMID-249 > URL: https://issues.apache.org/jira/browse/OMID-249 > Project: Phoenix Omid > Issue Type: Improvement >Affects Versions: 1.1.0 >Reporter: Istvan Toth >Priority: Major > > NetworkUtils.getNetworkInterface() seems to be only used for determining the > host and port when registering TSO to ZK for HA. > We should get the TSO public IP from the ZK TCP connection on demand, and not > worry about the default network interface at all. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-7185) Error message in SequenceNotFoundException is misleading
[
https://issues.apache.org/jira/browse/PHOENIX-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anchal Kejriwal updated PHOENIX-7185:
-
Description:
In SequenceNotFoundException message it is giving is tableName instead of
sequenceName. So better to change SqlBuilderInfo to support sequenceName also.
{code:java}
testSameSchemaSameClient(org.apache.phoenix.end2end.AppendOnlySchemaIT)
org.apache.phoenix.schema.SequenceNotFoundException: ERROR 1201 (42Z01):
Sequence undefined. tableName=N02
at
org.apache.phoenix.exception.SQLExceptionCode$14.newException(SQLExceptionCode.java:376)
at
org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:217)
at
org.apache.phoenix.schema.MetaDataClient.handleCreateTableMutationCode(MetaDataClient.java:3298)
at
org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:3096)
at
org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:1117)
at
org.apache.phoenix.compile.CreateTableCompiler$CreateTableMutationPlan.execute(CreateTableCompiler.java:420)
at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:443)
at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:425)
at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
at
org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:424)
at
org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:412)
at org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:2009)
at
org.apache.phoenix.end2end.AppendOnlySchemaIT.testTableWithSameSchema(AppendOnlySchemaIT.java:98)
at
org.apache.phoenix.end2end.AppendOnlySchemaIT.testSameSchemaSameClient(AppendOnlySchemaIT.java:186){code}
was:
In SequenceNotFoundException message it is giving is tableName instead of
sequenceName. So better to change SqlBuilderInfo to support sequenceName also.
{code:java}
testSameSchemaSameClient(org.apache.phoenix.end2end.AppendOnlySchemaIT)
org.apache.phoenix.schema.SequenceNotFoundException: ERROR 1201 (42Z01):
Sequence undefined. tableName=N02
at
org.apache.phoenix.exception.SQLExceptionCode$14.newException(SQLExceptionCode.java:376)
at
org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:217)
at
org.apache.phoenix.schema.MetaDataClient.handleCreateTableMutationCode(MetaDataClient.java:3298)
at
org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:3096)
at
org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:1117)
at
org.apache.phoenix.compile.CreateTableCompiler$CreateTableMutationPlan.execute(CreateTableCompiler.java:420)
at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:443)
at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:425)
at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
at
org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:424)
at
org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:412)
at org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:2009)
at
org.apache.phoenix.end2end.AppendOnlySchemaIT.testTableWithSameSchema(AppendOnlySchemaIT.java:98)
at
org.apache.phoenix.end2end.AppendOnlySchemaIT.testSameSchemaSameClient(AppendOnlySchemaIT.java:186){code}
{code:java}
{code}
> Error message in SequenceNotFoundException is misleading
>
>
> Key: PHOENIX-7185
> URL: https://issues.apache.org/jira/browse/PHOENIX-7185
> Project: Phoenix
> Issue Type: Bug
>Reporter: Anchal Kejriwal
>Assignee: Anchal Kejriwal
>Priority: Major
>
> In SequenceNotFoundException message it is giving is tableName instead of
> sequenceName. So better to change SqlBuilderInfo to support sequenceName also.
> {code:java}
> testSameSchemaSameClient(org.apache.phoenix.end2end.AppendOnlySchemaIT)
> org.apache.phoenix.schema.SequenceNotFoundException: ERROR 1201 (42Z01):
> Sequence undefined. tableName=N02
> at
> org.apache.phoenix.exception.SQLExceptionCode$14.newException(SQLExceptionCode.java:376)
> at
> org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:217)
> at
> org.apache.phoenix.schema.MetaDataClient.handleCreateTableMutationCode(MetaDataClient.java:3298)
> at
> org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:3096)
> at
> org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:1117)
> at
> org.apache.phoenix.compile.CreateTableCompiler$CreateTableMutationPlan.execute(CreateTableCompiler.java:420)
> at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:443)
> at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:425)
> at or
[jira] [Updated] (PHOENIX-7185) Error message in SequenceNotFoundException is misleading
[
https://issues.apache.org/jira/browse/PHOENIX-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anchal Kejriwal updated PHOENIX-7185:
-
Description:
In SequenceNotFoundException message it is giving is tableName instead of
sequenceName. So better to change SqlBuilderInfo to support sequenceName also.
{code:java}
testSameSchemaSameClient(org.apache.phoenix.end2end.AppendOnlySchemaIT)
org.apache.phoenix.schema.SequenceNotFoundException: ERROR 1201 (42Z01):
Sequence undefined. tableName=N02
at
org.apache.phoenix.exception.SQLExceptionCode$14.newException(SQLExceptionCode.java:376)
at
org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:217)
at
org.apache.phoenix.schema.MetaDataClient.handleCreateTableMutationCode(MetaDataClient.java:3298)
at
org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:3096)
at
org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:1117)
at
org.apache.phoenix.compile.CreateTableCompiler$CreateTableMutationPlan.execute(CreateTableCompiler.java:420)
at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:443)
at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:425)
at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
at
org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:424)
at
org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:412)
at org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:2009)
at
org.apache.phoenix.end2end.AppendOnlySchemaIT.testTableWithSameSchema(AppendOnlySchemaIT.java:98)
at
org.apache.phoenix.end2end.AppendOnlySchemaIT.testSameSchemaSameClient(AppendOnlySchemaIT.java:186){code}
{code:java}
{code}
was:
In SequenceNotFoundException message it is giving is tableName instead of
sequenceName. So better to change SqlBuilderInfo to support sequenceName also.
testSameSchemaSameClient(org.apache.phoenix.end2end.AppendOnlySchemaIT)
org.apache.phoenix.schema.SequenceNotFoundException: ERROR 1201 (42Z01):
Sequence undefined. tableName=N02
at
org.apache.phoenix.exception.SQLExceptionCode$14.newException(SQLExceptionCode.java:376)
at
org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:217)
at
org.apache.phoenix.schema.MetaDataClient.handleCreateTableMutationCode(MetaDataClient.java:3298)
at
org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:3096)
at
org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:1117)
at
org.apache.phoenix.compile.CreateTableCompiler$CreateTableMutationPlan.execute(CreateTableCompiler.java:420)
at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:443)
at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:425)
at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
at
org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:424)
at
org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:412)
at org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:2009)
at
org.apache.phoenix.end2end.AppendOnlySchemaIT.testTableWithSameSchema(AppendOnlySchemaIT.java:98)
at
org.apache.phoenix.end2end.AppendOnlySchemaIT.testSameSchemaSameClient(AppendOnlySchemaIT.java:186)
{code}
{code}
> Error message in SequenceNotFoundException is misleading
>
>
> Key: PHOENIX-7185
> URL: https://issues.apache.org/jira/browse/PHOENIX-7185
> Project: Phoenix
> Issue Type: Bug
>Reporter: Anchal Kejriwal
>Assignee: Anchal Kejriwal
>Priority: Major
>
> In SequenceNotFoundException message it is giving is tableName instead of
> sequenceName. So better to change SqlBuilderInfo to support sequenceName also.
> {code:java}
> testSameSchemaSameClient(org.apache.phoenix.end2end.AppendOnlySchemaIT)
> org.apache.phoenix.schema.SequenceNotFoundException: ERROR 1201 (42Z01):
> Sequence undefined. tableName=N02
> at
> org.apache.phoenix.exception.SQLExceptionCode$14.newException(SQLExceptionCode.java:376)
> at
> org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:217)
> at
> org.apache.phoenix.schema.MetaDataClient.handleCreateTableMutationCode(MetaDataClient.java:3298)
> at
> org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:3096)
> at
> org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:1117)
> at
> org.apache.phoenix.compile.CreateTableCompiler$CreateTableMutationPlan.execute(CreateTableCompiler.java:420)
> at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:443)
> at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:425)
> at org.
[jira] [Created] (OMID-273) IPv6 not working on Mac
Richárd Antal created OMID-273: -- Summary: IPv6 not working on Mac Key: OMID-273 URL: https://issues.apache.org/jira/browse/OMID-273 Project: Phoenix Omid Issue Type: Bug Reporter: Richárd Antal During the OMID 1.1.1 RC0 release we found that TestTSOClientConnectionToTSO had failing tests: testSuccessfulConnectionToTSOThroughZK and testSuccessOfTSOClientReconnectionsToARestartedTSOWithZKPublishing It might be because it uses IPv6 2024-01-17T15:17:45,858 INFO [TestNGInvoker-testSuccessfulConnectionToTSOThroughZK()] client.TSOClient: * Current TSO host:port found in ZK: [fe80:0:0:0:aede:48ff:fe00:1122%en5]:52934 Epoch 0 2024-01-17T15:17:45,859 INFO [tsofsm-0] client.TSOClient: Trying to connect to TSO [/fe80:0:0:0:aede:48ff:fe00:1122%en5:52934] 2024-01-17T15:17:45,863 ERROR [tsoclient-worker-0] client.TSOClient: Failed connection attempt to TSO [/fe80:0:0:0:aede:48ff:fe00:1122%en5:52934] failed. Channel [id: 0x9d8c0b44] I've checked this en5 interface and it has only IPv6 and no IPv4 I ran a git bisect but it wasn't very useful. Before OMID-248 TestTSOClientConnectionToTSO used IPv4 and after it it is using IPv6 and failing on my Mac -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OMID-273) IPv6 not working on Mac
[ https://issues.apache.org/jira/browse/OMID-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richárd Antal updated OMID-273: --- Description: During the OMID 1.1.1 RC0 release we found that TestTSOClientConnectionToTSO had failing tests: testSuccessfulConnectionToTSOThroughZK and testSuccessOfTSOClientReconnectionsToARestartedTSOWithZKPublishing It might be because it uses IPv6 2024-01-17T15:17:45,858 INFO [TestNGInvoker-testSuccessfulConnectionToTSOThroughZK()] client.TSOClient: * Current TSO host:port found in ZK: [fe80:0:0:0:aede:48ff:fe00:1122%en5]:52934 Epoch 0 2024-01-17T15:17:45,859 INFO [tsofsm-0] client.TSOClient: Trying to connect to TSO [/fe80:0:0:0:aede:48ff:fe00:1122%en5:52934] 2024-01-17T15:17:45,863 ERROR [tsoclient-worker-0] client.TSOClient: Failed connection attempt to TSO [/fe80:0:0:0:aede:48ff:fe00:1122%en5:52934] failed. Channel [id: 0x9d8c0b44] I've checked this en5 interface and it has only IPv6 and no IPv4 I ran a git bisect but it wasn't very useful. Before OMID-248 TestTSOClientConnectionToTSO used IPv4 and after it, it is using IPv6 and failing on my Mac was: During the OMID 1.1.1 RC0 release we found that TestTSOClientConnectionToTSO had failing tests: testSuccessfulConnectionToTSOThroughZK and testSuccessOfTSOClientReconnectionsToARestartedTSOWithZKPublishing It might be because it uses IPv6 2024-01-17T15:17:45,858 INFO [TestNGInvoker-testSuccessfulConnectionToTSOThroughZK()] client.TSOClient: * Current TSO host:port found in ZK: [fe80:0:0:0:aede:48ff:fe00:1122%en5]:52934 Epoch 0 2024-01-17T15:17:45,859 INFO [tsofsm-0] client.TSOClient: Trying to connect to TSO [/fe80:0:0:0:aede:48ff:fe00:1122%en5:52934] 2024-01-17T15:17:45,863 ERROR [tsoclient-worker-0] client.TSOClient: Failed connection attempt to TSO [/fe80:0:0:0:aede:48ff:fe00:1122%en5:52934] failed. Channel [id: 0x9d8c0b44] I've checked this en5 interface and it has only IPv6 and no IPv4 I ran a git bisect but it wasn't very useful. Before OMID-248 TestTSOClientConnectionToTSO used IPv4 and after it it is using IPv6 and failing on my Mac > IPv6 not working on Mac > --- > > Key: OMID-273 > URL: https://issues.apache.org/jira/browse/OMID-273 > Project: Phoenix Omid > Issue Type: Bug >Reporter: Richárd Antal >Priority: Major > > During the OMID 1.1.1 RC0 release we found that TestTSOClientConnectionToTSO > had failing tests: > testSuccessfulConnectionToTSOThroughZK and > testSuccessOfTSOClientReconnectionsToARestartedTSOWithZKPublishing > It might be because it uses IPv6 > 2024-01-17T15:17:45,858 INFO > [TestNGInvoker-testSuccessfulConnectionToTSOThroughZK()] client.TSOClient: * > Current TSO host:port found in ZK: [fe80:0:0:0:aede:48ff:fe00:1122%en5]:52934 > Epoch 0 > 2024-01-17T15:17:45,859 INFO [tsofsm-0] client.TSOClient: Trying to > connect to TSO [/fe80:0:0:0:aede:48ff:fe00:1122%en5:52934] > 2024-01-17T15:17:45,863 ERROR [tsoclient-worker-0] client.TSOClient: Failed > connection attempt to TSO [/fe80:0:0:0:aede:48ff:fe00:1122%en5:52934] failed. > Channel [id: 0x9d8c0b44] > I've checked this en5 interface and it has only IPv6 and no IPv4 > I ran a git bisect but it wasn't very useful. Before OMID-248 > TestTSOClientConnectionToTSO used IPv4 and after it, it is using IPv6 and > failing on my Mac -- This message was sent by Atlassian Jira (v8.20.10#820010)
