Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logging enhancements and single-node rename #3641

Merged
merged 6 commits into from
Aug 13, 2015
Merged

Logging enhancements and single-node rename #3641

merged 6 commits into from
Aug 13, 2015

Conversation

jwilder
Copy link
Contributor

@jwilder jwilder commented Aug 12, 2015

This PR makes it more seamless to rename a single-node cluster. Renaming a raft peer in a multiple node cluster still requires operator intervention.

This also cleans up the logging to add more consistency to what and how things are logged. Specifically:

  • Capitalize first letter of message
  • Log all services starting consistently
  • Remove some extraneous log statements in meta.Store
  • Log data dirs for meta, data and hinted handoff
  • Log raft leadership changes

@@ -57,6 +57,9 @@ func NewService(c Config) *Service {

// Open starts the service.
func (s *Service) Open() error {

s.Logger.Printf("Starting collected service")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

collected -> collectd

@otoolep
Copy link
Contributor

otoolep commented Aug 12, 2015

+1, just very minor stuff.

@@ -53,6 +53,8 @@ func NewService(c Config) *Service {

// Open opens the network listener and begins serving requests.
func (s *Service) Open() error {

s.Logger.Println("Staring cluster service")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Staring -> Starting

Renaming a host that is a raft peer member is pretty difficult but
we can special case single-node renames since we know all the member
in the cluster and we can update the peer store directly on all nodes
(just one).

Fixes #3632
Make is much easier to determine when a cluster is in a healthly state
as well as who the current leader is.
* Capitalize first letter of message
* Log all services staring consistently
* Remove some extraneous log statements in meta.Store
* Log data dirs for meta, data and hinted handoff
jwilder added a commit that referenced this pull request Aug 13, 2015
Logging enhancements and single-node rename
@jwilder jwilder merged commit 1181427 into master Aug 13, 2015
@jwilder jwilder deleted the jw-fixes branch August 13, 2015 16:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants