Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

check for change in dfsgroup

Description

dfsgroup changes to thor and roxie need to be caught by dali and handled, throwing an error if administrator action is required.

Conclusion

None

Activity

Show:

Michael Gardner May 5, 2015 at 1:14 PM

Still need some link to documentation dealing with changes in dfsgroups and how we deal with logical files where the host IP changes, for when I resubmit this.

Michael Gardner May 5, 2015 at 1:12 PM

Rejected pull request due to which is a complete init_thor re-write. Run_thor no longer will exist within 5.4+ so I'll submit the changes necessary to fix this issue once that PR gets merged into the upstream branch.

Michael Gardner March 17, 2015 at 6:39 PM
Edited

So the reason that thor doesn't start up is that the slaves file is pointing to an expired IP.

For single node: daliadmin dfsgroup is used to create slaves file -> used to create thorgroup -> used to create thorgroup.slave in start_slaves -> never matches the IP passed so we never start a thorslave, and thormaster hangs waiting for a connection.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Fix versions

Pull Request URL

Created March 13, 2015 at 1:07 PM
Updated June 24, 2015 at 1:24 PM
Resolved June 24, 2015 at 1:24 PM