Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-18544

Make cassandra-stress able to read all credentials from a file

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 5.0-alpha1, 5.0
    • Tool/stress
    • None

    Description

      If there is username/password required in order to connect via JMX, there is currently no way how to do this as NodeProbe constructor in cassandra-stress does not accept any credentials.

      The way how we are reading the credentials should be refactored. Currently, if there are credentials on the command line, they will be visible in the logs. Making it visible on the command line for JMX credentials is not ideal either.

      What I would like to see is to read all credentials which are necessary for cassandra-stress from ONE file. CQL and JMX combined.

      Because there is already some logic in place and it would be cool to have this backward compatible, we may still support command line credentials for CQL but we would make it deprecated and we would remove it in 6.0 so cassandra-stress will be reading credentials from the file only.

      I looked into the implementation and I have an idea how to "inject" credentials where necessary so they would be used even we do not use them on the command line but I have not coded up anything yet.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            smiklosovic Stefan Miklosovic Assign to me
            smiklosovic Stefan Miklosovic
            Stefan Miklosovic
            Brandon Williams
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 10m
                10m

                Slack

                  Issue deployment