I am in favor of calling the chooser for each tablet file. Does anyone know of any performance implications for having all of a tablets files on a single NN versus multiple NNs? It seems like it should not matter, but I am not completely sure about this.
I think this time limit is not ideal in that it introduces behavior outside of the volume choosers control (like volumes being sticky for tablets). I think the best way to go is to provide the volume chooser with enough information so that it can make these type of decisions itself. For example, one possible way to have a sticky chooser would be to provide choosers with the last choice it made for a resource. Another possible way would be to provide the tablets current set of files to the chooser. I don't think we need to modify the chooser to provide more info at this time, unless we have a valid use case. I am not even sure sticky tablets is a good goal. We could call chooser for each tablet file now. If later we find this is bad, then we could provide more info to the chooser so it can make better decisions. [ Full content available at: https://github.com/apache/accumulo/pull/642 ] This message was relayed via gitbox.apache.org for devnull@infra.apache.org
