[
https://issues.apache.org/jira/browse/IMPALA-14679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18051400#comment-18051400
]
Michael Smith commented on IMPALA-14679:
----------------------------------------
This only seems to happen in Java, so maybe it's performing multiple writes for
some reason. I can't reproduce it with a C++ unit test.
> Authentication hash reload sometimes fails with "did not contain 32 bytes"
> --------------------------------------------------------------------------
>
> Key: IMPALA-14679
> URL: https://issues.apache.org/jira/browse/IMPALA-14679
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 5.0.0
> Reporter: Michael Smith
> Assignee: Michael Smith
> Priority: Major
>
> In diagnosing IMPALA-14678, I noticed that sometimes reload will fail the 1st
> time with
> {code}
> E20260112 15:49:12.255777 338029 openssl-util.cc:385] GENERAL: Authentication
> hash from /tmp/junit713748083974798515/junit3924236808116170714.tmp did not
> contain 32 bytes
> {code}
> It would get successfully reloaded on retry after a 1s sleep.
> This appears to be a result of using {{IN_MODIFY}}, even though writing out
> the 32 bytes should happen via a single {{write}} system call. We should
> instead rely on {{IN_CLOSE_WRITE}} for these cases, which will occur after
> all {{write}} system calls and should let us read the full file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
