[
https://issues.apache.org/jira/browse/SOLR-16644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768441#comment-17768441
]
Evan Lavelle commented on SOLR-16644:
-------------------------------------
Hi [~raghavanm], [~ichattopadhyaya] - I hadn't realised that there was a new
report on this issue. I've added some comments at
https://issues.apache.org/jira/browse/SOLR-10352?focusedCommentId=17768433&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17768433
which may be helpful.
> Entropy warning thresholds need to be revisited
> -----------------------------------------------
>
> Key: SOLR-16644
> URL: https://issues.apache.org/jira/browse/SOLR-16644
> Project: Solr
> Issue Type: Bug
> Reporter: Ishan Chattopadhyaya
> Priority: Major
> Labels: newdev
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As per the following, newer kernels (5.15+) have recalibrated the entropy
> levels from 0-4096 to 0-256. Hence, everything is throwing a warning:
> {code}
> Warning: Available entropy is low. As a result, use of the UUIDField, SSL, or
> any other features that require
> RNG might not work properly. To check for the amount of available entropy,
> use 'cat /proc/sys/kernel/random/entropy_avail'.
> {code}
> Here's where I found out about this change:
> https://askubuntu.com/questions/1427470/entropy-is-stuck-at-256-after-upgrading-to-kernel-5-15-0-47
> We might need to intelligently report the low entropy (based on kernel
> version).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
