Remove an eth_getLogs issue from KNOWN_ISSUES.md (#1295)

Signed-off-by: Tim Beiko <t.beiko23@gmail.com>

CHANGELOG.md

@@ -22,7 +22,6 @@ The intent is that the major Java VM version or Java VM type shipped with the de
 
 #### Previously identified known issues
 
-- [Scope of logs query causing Besu to hang](KNOWN_ISSUES.md#scope-of-logs-query-causing-besu-to-hang)
 - [Logs queries missing results against chain head](KNOWN_ISSUES.md#Logs-queries-missing-results-against-chain-head)
 - [Eth/65 loses peers](KNOWN_ISSUES.md#eth65-loses-peers)
 - [Fast sync when running Besu on cloud providers](KNOWN_ISSUES.md#fast-sync-when-running-besu-on-cloud-providers)

KNOWN_ISSUES.md

@@ -5,12 +5,6 @@ in the current release are provided in the [Changelog](CHANGELOG.md).
 
 Known issues are open issues categorized as [Very High or High impact](https://wiki.hyperledger.org/display/BESU/Defect+Prioritisation+Policy). 
 
-## Scope of logs query causing Besu to hang
-
-[`eth_getLogs` queries that are too large or too broad can cause Besu to never return](https://github.com/hyperledger/besu/issues/944). 
-
-Workaround -> Limit the number of blocks queried by each `eth_getLogs` call.
-
 ## Logs queries missing results against chain head
 
 When using `eth_getLogs` against the head of Goerli to retrieve Eth2 deposit log events, [some results seem to be missing](https://github.com/hyperledger/besu/issues/1153).