Page title matches

  • #перенаправление [[Hadoop Distributed File System]]
    66 B (4 words) - 23:50, 21 December 2013

Page text matches

  • ** not an option for systems where network failures are possible! * Efficient use of distributed indexes and RAM for data storage
    3 KB (468 words) - 09:58, 15 November 2013
  • For [[Distributed Databases]] maintaining consistency is harder. Consistency models determine * [[Database Systems Architecture (ULB)]]
    4 KB (533 words) - 00:04, 2 January 2014
  • [[Category:Distributed Systems]]
    260 B (25 words) - 16:42, 17 November 2013
  • * data records are distributed by messaging Assumptions that we make about distributes systems
    2 KB (303 words) - 09:39, 2 January 2014
  • == Distributed File Systems == Typically [[MapReduce]] I/O operations are performed on distribute file systems.
    4 KB (654 words) - 14:08, 23 November 2015
  • '''Theorem:''' It is impossible to implement a [[Distributed Databases|distributed system]] which will have all three mentioned properties. Only 2 of the 3 is [[Category:Distributed Systems]]
    2 KB (242 words) - 19:12, 22 June 2014
  • * In highly available systems it is very hard to keep replicas consistent, because they have to contact e ...gh might attempt to merge, for example, text data (like in version control systems)
    3 KB (496 words) - 09:19, 15 November 2013
  • To scale incrementally, [[Distributed Databases]] need a mechanism to dynamically partition over a set of nodes. [[Category:Distributed Systems]]
    3 KB (413 words) - 10:43, 25 December 2013
  • ...is a popular data structure for ensuring ordering of events in distributes systems. It is often used for achieving [[Eventual Consistency]] ...esign-patterns-for-distributed-nonrelational-databases Design Patterns for Distributed Nonrelational Databases]
    4 KB (665 words) - 10:39, 25 December 2013
  • ...ans multiple rows - and stored in chunks of the [[Distributed File Systems|Distributed File System]]
    3 KB (430 words) - 09:49, 15 November 2013
  • A way to ensure consistency in a [[Distributed Databases|distributed system]] [[Category:Distributed Systems]]
    921 B (110 words) - 00:23, 2 January 2014
  • [[Category:Distributed Systems]]
    2 KB (249 words) - 16:24, 17 November 2013
  • * [[Distributed Databases|Distributed]], scalable and fault-tolerant * [[Distributed Databases|Distributed systems]] operate over some network,
    24 KB (3,869 words) - 10:15, 2 January 2014
  • ** many empty buckets when data is not uniformly distributed * [[Database Systems Architecture (ULB)]]
    3 KB (361 words) - 23:42, 18 December 2013
  • ...e relations we typically have some [[Histogram]]s that show how values are distributed * We assume that the values are distributed uniformly within there buckets
    1 KB (190 words) - 20:06, 10 May 2014
  • * it typically runs on a [[Hadoop Distributed File System|Distributed File System]] MapReduce is implemented on the following systems:
    3 KB (503 words) - 18:10, 30 December 2015
  • ...d [[Hadoop]] as the implementation for building large Data Warehouses over distributed network of servers that can handle huge volumes of data. Hadoop has already * [[Hadoop Distributed File System]]
    9 KB (1,311 words) - 23:10, 24 June 2015
  • * [[HDFS]] distributed storage ...cal machine, but jobs are executed by hadoop services (see [[Hadoop Pseudo Distributed Mode]] for configuration example)
    2 KB (340 words) - 14:58, 23 November 2015
  • * it's not restricted to [[Hadoop MapReduce]] and can run any systems, e.g. [[Flink]] ...ore running, it get all needed files (e.g. config, job jars, etc) from the distributed cache
    4 KB (714 words) - 15:08, 23 November 2015
  • ** $E$'s salaries are distributed uniformly within range [10 000, 60 000] * [[Database Systems Architecture (ULB)]]
    8 KB (1,198 words) - 17:26, 26 December 2013

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)