Bug 1257887 - [glusterD]: Brick process is recreated on node where volume is delete and when stopped glusterd is started on other node.
Summary: [glusterD]: Brick process is recreated on node where volume is delete and...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: Byreddy
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-28 10:24 UTC by Byreddy
Modified: 2015-08-28 11:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-28 11:20:40 UTC
Embargoed:

Attachments (Terms of Use)

Description Byreddy 2015-08-28 10:24:08 UTC 
Description of problem:
Brick process is recreated on node where volume is deleted when stopped glusterd is restarted on other node.

Version-Release number of selected component (if applicable):
glusterfs-3.7.1-13

How reproducible:
always

Steps to Reproduce:
1.Create a Distributed volume using two node cluster (Node-1 and Node-2)
2.Stop glusterd on Node-2 (peer node)
3.Stop and delete the volume on Node-1
4.Start the glusterD on Node-2 and Check the Volume status (gluster v status <vol_name>)
5.Check the volume status on Node-1 also.

Actual results:
Brick process is recreated even after volume delete

Expected results:
Brick process should not recreate after volume delete.

Additional info:
Note You need to log in before you can comment on or make changes to this bug.