[jira] [Commented] (KUDU-3367) Delta file with full of delete op can not be schedule to compact
[ https://issues.apache.org/jira/browse/KUDU-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633680#comment-17633680 ] YifanZhang commented on KUDU-3367: -- [~Koppa] [~laiyingchun] Ah, indeed, this GC operation relies on live row counting. I agree that we do need GC deleted rows on tablets that don't support live row counting. > Delta file with full of delete op can not be schedule to compact > > > Key: KUDU-3367 > URL: https://issues.apache.org/jira/browse/KUDU-3367 > Project: Kudu > Issue Type: New Feature > Components: compaction >Reporter: dengke >Assignee: dengke >Priority: Major > Attachments: image-2022-05-09-14-13-16-525.png, > image-2022-05-09-14-16-31-828.png, image-2022-05-09-14-18-05-647.png, > image-2022-05-09-14-19-56-933.png, image-2022-05-09-14-21-47-374.png, > image-2022-05-09-14-23-43-973.png, image-2022-05-09-14-26-45-313.png, > image-2022-05-09-14-32-51-573.png, image-2022-11-14-11-02-33-685.png > > > If we get a REDO delta with full of delete op, wich means there is no update > op in the file. The current compact algorithm will not schedule the file do > compact. If such files exist, after accumulating for a period of time, it > will greatly affect our scan speed. However, processing such files every time > compact reduces compact's performance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KUDU-3415) Kerberos authentication fails with rdns disabled
[
https://issues.apache.org/jira/browse/KUDU-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633688#comment-17633688
]
Marton Greber commented on KUDU-3415:
-
I tried to repro the issue without any success. Here is my setup:
Kudu cluster: 1 master, 2 tservers. 1 dns server, where I even have a CNAME for
the master.
In the krb5.conf I set rdns = false.
Then I execute the [Kudu java
example|https://github.com/martongreber/kudu/tree/master/examples/java/java-example]
.
But with the above setup, it goes successful. Does my setup resemble the setup
where the error happened?
If not could you please provide details to repro this issue?
> Kerberos authentication fails with rdns disabled
>
>
> Key: KUDU-3415
> URL: https://issues.apache.org/jira/browse/KUDU-3415
> Project: Kudu
> Issue Type: Bug
> Components: client
>Reporter: Abhishek Rawat
>Priority: Major
>
> Kudu Java client doesn't retain the original hostname and replaces them with
> the resolved IPAddress in the kerberos principal. This results in error such
> as following:
> {code:java}
> error Message is Server not found in Kerberos database
> cTime is Sat Jul 28 22:29:26 UTC 2018 1532816966000
> sTime is Thu Oct 27 00:35:03 UTC 2022 1666830903000
> suSec is 129588
> error code is 7
> crealm is CDW-KUDU.XCU2-8Y8X.DEV.CLDR.WORK
> error Message is Server not found in Kerberos database
> crealm is CDW-KUDU.XCU2-8Y8X.DEV.CLDR.WORK
> cname is
> hive/impala-1666798978-f8x7@cdw-kudu.xcu2-8y8x.dev.cldr.work
> sname is kudu/10.80.205@cdw-kudu.xcu2-8y8x.dev.cldr.work
> msgType is 30
> cname is
> hive/impala-1666798978-f8x7@cdw-kudu.xcu2-8y8x.dev.cldr.work
> sname is kudu/10.80.194@cdw-kudu.xcu2-8y8x.dev.cldr.work
> msgType is 30
> KrbException: Server not found in Kerberos database (7) - LOOKING_UP_SERVER
> {code}
> [~aserbin] suggested this might require the fix done on cpp client side in
> KUDU-2032 to be extended to Java client also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
