HBASE-15461 update links to blogs posted on the Cloudera website to account for site restructuring.
Signed-off-by: Dima Spivak <dspivak@cloudera.com> Signed-off-by: Matteo Bertozzi <matteo.bertozzi@cloudera.com>
This commit is contained in:
parent
431c8c9ad0
commit
48af3f5f7a
|
@ -340,7 +340,7 @@ Do not move to Apache HBase 0.96.x if you cannot upgrade your Hadoop. See link:h
|
|||
HBase will lose data unless it is running on an HDFS that has a durable `sync` implementation.
|
||||
DO NOT use Hadoop 0.20.2, Hadoop 0.20.203.0, and Hadoop 0.20.204.0 which DO NOT have this attribute.
|
||||
Currently only Hadoop versions 0.20.205.x or any release in excess of this version -- this includes hadoop-1.0.0 -- have a working, durable sync.
|
||||
The Cloudera blog post link:http://www.cloudera.com/blog/2012/01/an-update-on-apache-hadoop-1-0/[An
|
||||
The Cloudera blog post link:https://blog.cloudera.com/blog/2012/01/an-update-on-apache-hadoop-1-0/[An
|
||||
update on Apache Hadoop 1.0] by Charles Zedlweski has a nice exposition on how all the Hadoop versions relate.
|
||||
It's worth checking out if you are having trouble making sense of the Hadoop version morass.
|
||||
|
||||
|
|
|
@ -437,7 +437,7 @@ Caching for the input Scan is configured via `hbase.client.scanner.caching`
|
|||
By default, CopyTable utility only copies the latest version of row cells unless `--versions=n` is explicitly specified in the command.
|
||||
====
|
||||
|
||||
See Jonathan Hsieh's link:http://www.cloudera.com/blog/2012/06/online-hbase-backups-with-copytable-2/[Online
|
||||
See Jonathan Hsieh's link:https://blog.cloudera.com/blog/2012/06/online-hbase-backups-with-copytable-2/[Online
|
||||
HBase Backups with CopyTable] blog post for more on `CopyTable`.
|
||||
|
||||
[[export]]
|
||||
|
|
|
@ -59,9 +59,9 @@ link:http://ianvarley.com/UT/MR/Varley_MastersReport_Full_2009-08-07.pdf[No Rela
|
|||
[[other.info.sites]]
|
||||
=== HBase Sites
|
||||
|
||||
link:http://www.cloudera.com/blog/category/hbase/[Cloudera's HBase Blog] has a lot of links to useful HBase information.
|
||||
link:https://blog.cloudera.com/blog/category/hbase/[Cloudera's HBase Blog] has a lot of links to useful HBase information.
|
||||
|
||||
* link:http://www.cloudera.com/blog/2010/04/cap-confusion-problems-with-partition-tolerance/[CAP Confusion] is a relevant entry for background information on distributed storage systems.
|
||||
* link:https://blog.cloudera.com/blog/2010/04/cap-confusion-problems-with-partition-tolerance/[CAP Confusion] is a relevant entry for background information on distributed storage systems.
|
||||
|
||||
link:http://wiki.apache.org/hadoop/HBase/HBasePresentations[HBase Wiki] has a page with a number of presentations.
|
||||
|
||||
|
|
|
@ -126,7 +126,7 @@ A number of properties exist to configure SPNEGO authentication for the web serv
|
|||
== Secure Client Access to Apache HBase
|
||||
|
||||
Newer releases of Apache HBase (>= 0.92) support optional SASL authentication of clients.
|
||||
See also Matteo Bertozzi's article on link:http://www.cloudera.com/blog/2012/09/understanding-user-authentication-and-authorization-in-apache-hbase/[Understanding User Authentication and Authorization in Apache HBase].
|
||||
See also Matteo Bertozzi's article on link:https://blog.cloudera.com/blog/2012/09/understanding-user-authentication-and-authorization-in-apache-hbase/[Understanding User Authentication and Authorization in Apache HBase].
|
||||
|
||||
This describes how to set up Apache HBase and clients for connection to secure HBase resources.
|
||||
|
||||
|
@ -451,7 +451,7 @@ Substitute the keytab for HTTP for _$KEYTAB_.
|
|||
== Simple User Access to Apache HBase
|
||||
|
||||
Newer releases of Apache HBase (>= 0.92) support optional SASL authentication of clients.
|
||||
See also Matteo Bertozzi's article on link:http://www.cloudera.com/blog/2012/09/understanding-user-authentication-and-authorization-in-apache-hbase/[Understanding User Authentication and Authorization in Apache HBase].
|
||||
See also Matteo Bertozzi's article on link:https://blog.cloudera.com/blog/2012/09/understanding-user-authentication-and-authorization-in-apache-hbase/[Understanding User Authentication and Authorization in Apache HBase].
|
||||
|
||||
This describes how to set up Apache HBase and clients for simple user access to HBase resources.
|
||||
|
||||
|
|
|
@ -41,7 +41,7 @@ RegionServer suicides are 'normal', as this is what they do when something goes
|
|||
For example, if ulimit and max transfer threads (the two most important initial settings, see <<ulimit>> and <<dfs.datanode.max.transfer.threads>>) aren't changed, it will make it impossible at some point for DataNodes to create new threads that from the HBase point of view is seen as if HDFS was gone.
|
||||
Think about what would happen if your MySQL database was suddenly unable to access files on your local file system, well it's the same with HBase and HDFS.
|
||||
Another very common reason to see RegionServers committing seppuku is when they enter prolonged garbage collection pauses that last longer than the default ZooKeeper session timeout.
|
||||
For more information on GC pauses, see the link:http://www.cloudera.com/blog/2011/02/avoiding-full-gcs-in-hbase-with-memstore-local-allocation-buffers-part-1/[3 part blog post] by Todd Lipcon and <<gcpause>> above.
|
||||
For more information on GC pauses, see the link:https://blog.cloudera.com/blog/2011/02/avoiding-full-gcs-in-hbase-with-memstore-local-allocation-buffers-part-1/[3 part blog post] by Todd Lipcon and <<gcpause>> above.
|
||||
|
||||
[[trouble.log]]
|
||||
== Logs
|
||||
|
@ -211,7 +211,7 @@ Similarly, to enable GC logging for client processes, uncomment one of the below
|
|||
# If <FILE-PATH> is not replaced, the log file(.gc) would be generated in the HBASE_LOG_DIR .
|
||||
----
|
||||
|
||||
For more information on GC pauses, see the link:http://www.cloudera.com/blog/2011/02/avoiding-full-gcs-in-hbase-with-memstore-local-allocation-buffers-part-1/[3 part blog post] by Todd Lipcon and <<gcpause>> above.
|
||||
For more information on GC pauses, see the link:https://blog.cloudera.com/blog/2011/02/avoiding-full-gcs-in-hbase-with-memstore-local-allocation-buffers-part-1/[3 part blog post] by Todd Lipcon and <<gcpause>> above.
|
||||
|
||||
[[trouble.resources]]
|
||||
== Resources
|
||||
|
|
Loading…
Reference in New Issue