nodetool requires akka.tcp protocol that SiriusShortNameParser doesn't support
- Dominant language
- Scala
- Stars
- 296
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
When using nodetool, if I pass in an "akka://..." nodeId, I get the following error message:
> akka.remote.RemoteTransportException: No transport is loaded for protocol: [akka], available protocols: [akka.tcp]
However, [SiriusShortNameParser expects nodeIds to start with "akka://"](https://github.com/Comcast/sirius/blob/master/src/main/scala/com/comcast/xfinity/sirius/util/SiriusShortNameParser.scala#L90):
> java.lang.IllegalArgumentException: akka.tcp://.../user/sirius does not appear to be a vaild Akka address or Sirius node short name
Contributor guide
Research direction
Start with src/main/scala/com/comcast/xfinity/sirius/util/SiriusShortNameParser.scala at the referenced validation logic, then reproduce the nodetool failure using an akka:// nodeId. Compare the accepted address formats with the akka.tcp transport shown in the error. Done means nodetool and SiriusShortNameParser handle the same valid Akka address without the protocol or validation error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- cli, distributed-systems
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100