Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
HDFS, mail # dev - profiling hdfs write path


+
Radim Kolar 2012-11-25, 21:41
+
Todd Lipcon 2012-11-26, 01:35
+
Radim Kolar 2012-11-29, 15:17
+
Todd Lipcon 2012-11-29, 18:25
+
Radim Kolar 2012-12-04, 17:07
+
Todd Lipcon 2012-12-04, 17:27
+
Suresh Srinivas 2012-12-04, 17:49
+
Radim Kolar 2012-12-04, 17:39
+
Eli Collins 2012-12-04, 17:44
+
Radim Kolar 2012-12-05, 02:00
+
Andy Isaacson 2012-12-05, 22:21
+
Radim Kolar 2012-12-06, 02:02
+
Andy Isaacson 2012-12-06, 23:06
+
Radim Kolar 2012-12-08, 04:39
Copy link to this message
-
Re: profiling hdfs write path
Steve Loughran 2012-12-08, 12:38
On 8 December 2012 04:39, Radim Kolar <[EMAIL PROTECTED]> wrote:

>
> if you want to keep code in safe state you need:
> 1. good unit test
> 2. high unit test coverage
> 3. clean code
> 4. documented code
> 5. good javadoc
+ good functional tests, which explores the deployment state of the world,
especially different networks. Once you get into HA you also need the
ability to trigger server failures and network partitions as part of a test
run.
+
Steve Loughran 2012-12-05, 08:57
+
Radim Kolar 2012-11-26, 03:07