Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-7310

Ignite should be easily configured to share hardware resources between instances

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      This may be handy when working with containers or in test environments when starting more than 1 node per host.

      Suggestion is to introduce Ignite system property IGNITE_NODES_PER_HOST which is 1 by default and calculate all resource related config parameters using this value, e.g. offheap memory, pool threads, nio workers in TcpCommunicationSpi, etc. dividing total amount of available resource by IGNITE_NODES_PER_HOST.

      Upd: Another suggestion is to have IGNITE_AVAILABLE_CPU property which is more intuitive.

      Attachments

        Activity

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

          People

            Unassigned Unassigned
            yzhdanov Yakov Zhdanov

            Dates

              Created:
              Updated:

              Slack

                Issue deployment