[ 
https://issues.apache.org/jira/browse/CASSANDRA-15404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16971190#comment-16971190
 ] 

Alex Petrov edited comment on CASSANDRA-15404 at 11/10/19 7:35 PM:
-------------------------------------------------------------------

If your hint directory is not writable, this doesn't sound good anyways. 
Unfortunately, there's no good way to distinguish between all errors that were 
caused by concurrent processes, user error, filesystem corruption, and hardware 
failures. We do apply one policy right now, and I still think that having 
separate policies for every directory might be overconfiguration. 


was (Author: ifesdjeen):
This sounds like a minor inconvenience. Moreover, if your hint directory is not 
writable, this doesn't sound good anyways. Unfortunately, there's no good way 
to distinguish between all errors that were caused by concurrent processes, 
user error, filesystem corruption, and hardware failures. We do apply one 
policy right now, and I still think that having separate policies for every 
directory might be overconfiguration. 

> Hint directory error  affect cassandra process 
> -----------------------------------------------
>
>                 Key: CASSANDRA-15404
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15404
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local/Config, Local/Other
>            Reporter: maxwellguo
>            Assignee: maxwellguo
>            Priority: Normal
>             Fix For: 4.x
>
>         Attachments: image.png, log.png
>
>
> I use the default config to do some test. I delete all hint directory by 
> mistake,but my cassandra process at last stoped .Latter I found that that is 
> because the hint directory use the data disk policy . 
> In our production cluster , hint and cache's dir are set separately and are 
> not the same with data dir . And we know that cassandra can use multi data 
> directory to store data, the hint's data operation should not affect the data 
> and commitlog 's read or write . Also 
> hint/cache 's data loss do not affect the cassandra's  correct read .
> so I think hint's disk_faily_policy should be separately. So we can got three 
> type of 
> disk faily policy for : data disk , commitlog disk  and hint disk 。
>  I don't know if my suggestion is meaningful. If it is, I would like to take 
> over the issue。I'm also happy to receive new suggestions.
> I thinks this is a  bug , but now I can not modify the Type of the issue . 
> The situation is easy to reproduce .The data disk policy use stop . every 
> time you delete the hint directory will cause the daemon's stop.Stop 
> NativeTransport server and gossip .
>  !log.png! 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to