Hello,
I have a field which is indexed and stored in the solr schema( 4.4.solr
cloud).This field is relatively huge and I plan to only index the field
and not to store.Is there a need to re-index the documents once this
change is made?.
Thanks,
Nishanth
You are hitting hbase harder now which is important for benchmarking.If
there is no data loss it means your hbase cluster is good enough to handle
the load.You are simply making more use of the cores from where you launch
ycsb process.Write your own workload depending on the record sizes,format
Please email user-subscr...@hbase.apache.org
-Dima
On Fri, Jan 30, 2015 at 7:35 AM, wangyongqiang0...@163.com <
wangyongqiang0...@163.com> wrote:
>
>
>
>
> wangyongqiang0...@163.com
>
See http://hbase.apache.org/mail-lists.html
Cheers
On Fri, Jan 30, 2015 at 5:35 AM, wangyongqiang0...@163.com <
wangyongqiang0...@163.com> wrote:
>
>
>
>
> wangyongqiang0...@163.com
>
wangyongqiang0...@163.com
Please ignore..
On Fri, Jan 30, 2015 at 10:39 AM, Nishanth S
wrote:
> Hello,
>
> I have a field which is indexed and stored in the solr schema( 4.4.solr
> cloud).This field is relatively huge and I plan to only index the field
> and not to store.Is there a need to re-index the documents onc
Hello,
I'm seeing an issue similar to the one described here:
http://webmail.dev411.com/t/hbase/user/149jddw9gh/hbase-establishes-session-with-zookeeper-and-close-the-session-immediately/.
The only difference is that I don't have a replication set up since HBase is
running in a single-node mode
I have coming back to the benchmark.I executde this command:
yscb run hbase -P workflowA -p columnfamilty=cf -p
operationcount=10 threads=32
And I got an performace of 2000op/seg
What I did later it's to execute ten of those commands in parallel and
I got about 18000op/sec in total. I don't g
