lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-10397) Port 'autoAddReplicas' feature to the policy rules framework and make it work with non-shared filesystems
Date Wed, 12 Jul 2017 12:05:00 GMT

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

Shalin Shekhar Mangar commented on SOLR-10397:
----------------------------------------------

Linking SOLR-11045 as blocker

> Port 'autoAddReplicas' feature to the policy rules framework and make it work with non-shared
filesystems
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-10397
>                 URL: https://issues.apache.org/jira/browse/SOLR-10397
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>            Reporter: Shalin Shekhar Mangar
>            Assignee: Cao Manh Dat
>              Labels: autoscaling
>             Fix For: 7.0
>
>         Attachments: SOLR-10397.1.patch, SOLR-10397.patch
>
>
> Currently 'autoAddReplicas=true' can be specified in the Collection Create API to automatically
add replicas when a replica becomes unavailable. I propose to move this feature to the autoscaling
cluster policy rules design.
> This will include the following:
> * Trigger support for ‘nodeLost’ event type
> * Modification of existing implementation of ‘autoAddReplicas’ to automatically create
the appropriate ‘nodeLost’ trigger.
> * Any such auto-created trigger must be marked internally such that setting ‘autoAddReplicas=false’
via the Modify Collection API should delete or disable corresponding trigger.
> * Support for non-HDFS filesystems while retaining the optimization afforded by HDFS
i.e. the replaced replica can point to the existing data dir of the old replica.
> * Deprecate/remove the feature of enabling/disabling ‘autoAddReplicas’ across the
entire cluster using cluster properties in favor of using the suspend-trigger/resume-trigger
APIs.
> This will retain backward compatibility for the most part and keep a common use-case
easy to enable as well as make it available to more people (i.e. people who don't use HDFS).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message