Descendants
of Unknown King
[ Click on the red arrow wherever it is found
for a shortcut to the list of family trees
s Click on the
blue question mark wherever it is found for assistance navigating among
family trees
n Click on the
two-headed arrow to move between the Outline and Report formats for this
family tree
|
Generation No. 1 1. UNK1 KING He married UNK. Children of UNK KING and UNK are: 2. i. MESHACK2
KING, b. 1780, Maryland; d. Bet. 1833 - 1840, Monroe
Co. OH. ii. SHADRACK KING,
b. Unknown; m. ELIZABETH WELLS. Generation No. 2 2. MESHACK2 KING (UNK1) was born 1780 in
Maryland, and died Bet. 1833 - 1840 in Monroe Co. OH. He married MARY WELLS. She was born Abt. 1780
in Maryland. Children of MESHACK KING and MARY WELLS are: 3. i. MESHACK3
KING, b. 1802, Ohio County, VA; d. June 03, 1864, Licking Co. OH. 4. ii. JOHN
WILLIAM KING, b. September 17, 1800, Woods Co., VA (now WV); d. February 24,
1898, Noble Co., OH. iii. DAUGHTER
KING, b. 1803. 5. iv. THOMAS KING,
b. 1804, Ohio Co., VA; d. 1881, East Union, Noble Co., OH. v. DAVID KING, b.
1806. vi. RACHEL KING,
b. 1808. vii. JACOB KING,
b. 1810. viii. NANCY KING,
b. 1812. 6. ix. WILLIAM
KING, b. March 07, 1813, Monroe Co. OH; d. March 04, 1869, Elk Twp., Noble
Co., OH. x. ELIJAH KING, b.
1815. xi. SILAS KING, b.
1816, Monroe Co. OH; d. 1840. xii. DAUGHTER
KING, b. 1820. 7. xiii. ELIZABETH
KING, b. 1822, Monroe Co. OH; d. 1895. Generation No. 3 3. MESHACK3 KING (MESHACK2, UNK1) was born 1802 in Ohio
County, VA, and died June 03, 1864 in Licking Co. OH. He married (1) ROSANNA GROSSE March 06, 1832. She was
born January 05, 1810 in MD. He married (2) MATILDA SHAMBACH
November 11, 1838. She was born June 15, 1818 in Maryland, and died September
1852. Children of MESHACK KING and ROSANNA GROSSE are: 8. i. WILLIAM
HENRY4 KING, b. June 07, 1835, Maryland; d. 1922. ii. ALMEDA LOUISE
KING, b. January 13, 1832. Children of MESHACK KING and MATILDA SHAMBACH are: iii. MARGARET ANN4
KING, b. November 26, 1837, Maryland, MD; d. November 13, 1896, Ohio County,
VA; m. DAVID SNYDER. iv. LEWIS D. KING,
b. April 27, 1839, MD; d. March 14, 1862, Commerce, MO. v. LETHA KING, b.
October 16, 1840, MD. 9. vi. JOHN KING,
b. September 24, 1842, Oldtown, MD; d. June 19, 1914, Summit Station, OH. vii. SARAH
ELIZABETH KING, b. November 29, 1844, Ohio County, VA. 10. viii. GEORGE
WASHINGTON KING, b. November 05, 1846, Harrison Twp., Licking Co., OH; d.
June 06, 1915, Alexandria, OH. ix. MARY KING, b.
January 08, 1849, Ohio County, VA; d. December 23, 1931. x. LAURA ANNIE
KING, b. December 09, 1850, Ohio; m. JOHN CHRYSLER. 4. JOHN WILLIAM3 KING (MESHACK2, UNK1) was born September 17,
1800 in Woods Co., VA (now WV), and died February 24, 1898 in Noble Co., OH.
He married REBECCA PERKINS Abt. 1824. She was born
November 12, 1804 in Belmont Co., OH, and died October 06, 1879 in 1879 in
East Union, Noble Co., OH. More About REBECCA PERKINS: Burial: Allen's
Chapel Cemeter, Marion Twp., Noble Co., OH Children of JOHN KING and REBECCA PERKINS are: 11. i. SAMUEL4
KING, b. 1825, E. Union, Monroe Co., OH; d. 1905. ii. MARY ANN KING,
b. 1827, E. Union, Monroe Co., OH. iii. NANCY ANN
KING, b. Abt. 1832, E. Union, Monroe Co., OH; m. WILLIAM JOHN. iv. JACOB KING, b.
1836, E. Union, Monroe Co., OH; d. August 12, 1862. v. JOHN W. KING,
b. 1836, E. Union, Monroe Co., OH; m. MARTHA. 12. vi. ELIJAH
KING, b. February 15, 1837, E. Union, Monroe Co., OH; d. February 28, 1897,
East Union, Noble Co., OH. 13. vii. HANNAH
HARRIET KING, b. 1841, E. Union, Monroe Co., OH. 14. viii. WILLIAM
KING, b. June 18, 1843, E. Union, Monroe Co., OH; d. August 07, 1919, Stock
Twp., Noble Co., OH. ix. MARTHA ANN
KING, b. May 04, 1846, E. Union, Monroe Co., OH; d. May 31, 1945. x. JOHN KING, b.
Abt. 1847; d. 1905; m. MARTHA M. KING, May 12, 1866; b. May 21, 1848; d. May
27, 1932, Charleston, WV. xi. NELSON KING,
b. Abt. 1848, E. Union, Monroe Co., OH. 5. THOMAS3 KING (MESHACK2, UNK1) was born 1804 in Ohio
Co., VA, and died 1881 in East Union, Noble Co., OH. He married (1) JANE 1824. She died 1847 in
East Union, Noble Co., OH. He married (2) CHARITY SCOTT
Bet. 1828 - 1835. He married (3) SUSANNAH COON
January 13, 1861. Child of THOMAS KING and JANE is: 15. i. GEORGE4
KING, b. 1828, Union Twp., Monroe Co., OH; d. Bet. 1874 - 1879, Noble Co.,
OH. Children of THOMAS KING and CHARITY SCOTT are: ii. MARY4
KING, b. 1835. iii. MESHACK KING,
b. 1837, Olive Twp., Monroe Co., OH; m. SARAH COON, May 26, 1858, Noble Co.,
OH. iv. NELSON KING,
b. 1839, Olive Twp., Monroe Co., OH. v. WILLIAM KING,
b. 1840, Olive Twp., Monroe Co., OH. vi. SARAH KING, b.
1846, Olive Twp., Monroe Co., OH. vii. WILLIAM SWAZE
KING, b. 1849, Olive Twp., Monroe Co., OH. viii. HARRISON
KING, b. November 01, 1850, Olive Twp., Monroe Co., OH; m. ELIZA E. MILLER,
May 02, 1874, Noble Co., OH. 6. WILLIAM3 KING (MESHACK2, UNK1) was born March 07, 1813
in Monroe Co. OH, and died March 04, 1869 in Elk Twp., Noble Co., OH. He
married ELIZA KNAPP 1835 in Ohio. She was
born April 16, 1816 in Randolph Co., VA, and died February 06, 1895 in Elk
Twp., Noble Co., OH. More About WILLIAM KING: Burial: Mt. Tabor
Cemetery Children of WILLIAM KING and ELIZA KNAPP are: i. TILLAS4
KING. ii. WESLEY KING. iii. DAVID KING. iv. JOHN KING. v. MELISSA KING. vi. JAMES KING. vii. SILAS KING. viii. EDWARD KING. ix. ALBERT KING. x. LYMAN KING. xi. HENRY KING, b.
June 15, 1839, Noble Co., OH; d. July 16, 1909, Washington Co., OH; m. MARY
SILLS. 7. ELIZABETH3 KING (MESHACK2, UNK1) was born 1822 in Monroe
Co. OH, and died 1895. She married JOHN NEEDS in Monroe Co., OH. He was
born in PA. Child of ELIZABETH KING and JOHN NEEDS is: i. MARY ELIZABETH4
NEEDS, m. JAMES MCKITRICK. Generation No. 4 8. WILLIAM HENRY4 KING (MESHACK3, MESHACK2, UNK1) was born June 07, 1835 in
Maryland, and died 1922. He married SARAH A. SLAYBAUGH, daughter of JACOB SLAYBAUGH and ELIZABETH. She was born November
04, 1836 in Ohio, and died September 29, 1910. Children of WILLIAM KING and SARAH SLAYBAUGH are: 16. i. CLARENCE
ELWOOD5 KING, b. May 16, 1874; d. November 16, 1959. ii. CLARA KING, b.
Abt. 1861. iii. CHARLES E
KING, b. Abt. 1865. iv. ROSA B KING,
b. Abt. 1871. v. WILLIAM S KING,
b. Abt. 1867. vi. GUY OTTO KING,
b. Abt. 1873. vii. MARY IDA
KING, b. Abt. 1863. 9. JOHN4 KING (MESHACK3, MESHACK2, UNK1) was born September 24,
1842 in Oldtown, MD, and died June 19, 1914 in Summit Station, OH. He married
KATE V. CUPP October 24, 1886 in
Doddridge, WV. She was born Abt. 1865 in Doddridge WV, and died April 14,
1891 in West Union, WV. Children of JOHN KING and KATE CUPP are: i. ROBERT5
KING, b. October 13, 1887. ii. NINA KING, b.
January 04, 1889; m. UNK BUCKINGHAM; b. Abt. 1885, WV. 10. GEORGE WASHINGTON4 KING (MESHACK3, MESHACK2, UNK1) was born November 05,
1846 in Harrison Twp., Licking Co., OH, and died June 06, 1915 in Alexandria,
OH. He married REBECA ELIZABETH PARKHURST March 23, 1868. She was
born 1853 in Jersey, OH, and died May 08, 1886 in Jersey, OH. Children of GEORGE KING and REBECA PARKHURST are: i. SAMUEL LEWIS5
KING, b. October 15, 1869, Jersey, OH; d. August 14, 1960, Columbus, Franklin
Co., OH. ii. MARY ESTELLA
KING, b. July 16, 1877, Jersey, OH; d. July 02, 1935, Concord, TN; m. JACOB
EARL MENTZER, March 21, 1897. 11. SAMUEL4 KING (JOHN WILLIAM3, MESHACK2, UNK1) was born 1825 in E.
Union, Monroe Co., OH, and died 1905. He married ELIZABETH SNYDER. She was born 1825, and
died 1899. More About SAMUEL KING: Burial: Curtis
Ridge Cemeter Children of SAMUEL KING and ELIZABETH SNYDER are: i. MARTHA5
KING. ii. RACHAEL J.
KING. iii. MELISSA KING. iv. ALBERT KING. v. CHARLES H.
KING. vi. ROBERT S.
KING. vii. ABRAHAM
LINCOLN KING. viii. JOSEPHINE
KING. ix. RUTH A. KING. x. LUCY B. KING. xi. JOHN WESLEY
KING, b. February 28, 1848, Summerfield, Monroe Co., OH. 17. xii. JAMES
SAMUEL KING, b. May 24, 1853, Noble Co., OH. 12. ELIJAH4 KING (JOHN WILLIAM3, MESHACK2, UNK1) was born February 15,
1837 in E. Union, Monroe Co., OH, and died February 28, 1897 in East Union, Noble
Co., OH. He married (1) ALICE ROBINSON. He married (2) MARY F. HARBIN July 19, 1858. More About ELIJAH KING: Burial: Allen's
Chapel Cemetery beside his parents Child of ELIJAH KING and MARY HARBIN is: i. THURZA AGNES5
KING, b. October 17, 1860, East Union, Noble Co., OH; d. February 19, 1912,
East Union, Noble Co., OH; m. JAMES ELMER ROBINSON, Caldwell, Noble Co., OH. More About THURZA AGNES KING: Burial: East Union Cemetery 13. HANNAH HARRIET4 KING (JOHN WILLIAM3, MESHACK2, UNK1) was born 1841 in E.
Union, Monroe Co., OH. She married REUBEN THORNTON
April 26, 1866 in Noble Co., OH. He was born Abt. 1843. Children of HANNAH KING and REUBEN THORNTON are: 18. i. JOHN RAMONE5
THORNTON, b. Abt. 1867, Stock Twp., Noble Co., OH. 19. ii. WILLIAM S
THORNTON, b. Abt. 1869, Stock Twp., Noble Co., OH. iii. ADA THORNTON,
b. Abt. 1873. 20. iv. FRANCIS
MARION THORNTON, b. Abt. 1876, Stock Twp., Noble Co., OH. v. RICHMOND F.
THORNTON, b. Abt. 1878. vi. CHARLES
THORNTON, b. Abt. 1882. 14. WILLIAM4 KING (JOHN WILLIAM3, MESHACK2, UNK1) was born June 18, 1843 in
E. Union, Monroe Co., OH, and died August 07, 1919 in Stock Twp., Noble Co.,
OH. He married (1) MARY M. ORR June 05, 1864 in Noble Co.,
OH. She was born Abt. 1845 in Ohio, and died Bef. 1891. He married (2) NANCY ELLEN CLARK March 08, 1891 in Noble
Co., OH. She was born March 12, 1875, and died October 02, 1923. Children of WILLIAM KING and MARY ORR are: i. WARREN H.5
KING, b. Abt. 1865; m. ROSA H. DAVISON, March 06, 1887, Noble Co., OH; b.
Abt. 1867, Ohio. 21. ii. JACOB
ALLEN KING, b. 1867, Stock Twp., Noble Co., OH; d. 1939. 22. iii. FRANCES
A. KING, b. Abt. 1869, Stock Twp., Noble Co., OH; d. Bef. 1910. iv. MARY C. KING,
b. Abt. 1874. v. BENJAMIN F.
KING, b. 1878. vi. BINGHAM E.
KING, b. 1878; d. 1949. vii. SAMUEL J.
KING, b. March 09, 1883; d. February 1980, Miamisburg, OH. Children of WILLIAM KING and NANCY CLARK are: viii. GOLD C.5
KING, b. Abt. 1897. ix. JOSEPH KING,
b. Abt. 1898. x. CLARA EVELYN
KING, b. March 20, 1905. xi. FAIR OAK KING,
b. Abt. 1913. 15. GEORGE4 KING (THOMAS3, MESHACK2, UNK1) was born 1828 in Union
Twp., Monroe Co., OH, and died Bet. 1874 - 1879 in Noble Co., OH. He married
MARTHA E. PRINGLE in Monroe Co., OH. She
was born 1833 in Ohio. Child of GEORGE KING and MARTHA PRINGLE is: i. GIDEON SHERMAN5
KING, b. 1865, Summerfield, Monroe Co., OH; d. October 15, 1953, Buffalo,
Guernsey Co., OH. Generation No. 5 16. CLARENCE ELWOOD5 KING (WILLIAM HENRY4, MESHACK3, MESHACK2, UNK1) was born May 16, 1874,
and died November 16, 1959. He married BERTHA GIESECK,
daughter of WILLIAM GIESECK and ANNIE KREITZ. She was born August 11,
1881 in Lima Twp, Licking Co, OH, and died August 23, 1969 in Rushville, Licking
Co. OH. Children of CLARENCE KING and BERTHA GIESECK are: 23. i. LAWRENCE6
KING, b. August 14, 1904; d. November 08, 1991, Ohio. ii. INFANT HAROLD
KING. iii. INFANT SON
KING. 24. iv. PEARL A.
KING, b. May 31, 1901; d. April 25, 1992. 25. v. RUSSELL KING,
b. July 01, 1908; d. May 01, 1989. 26. vi. GAYLORD
KING KING, b. January 17, 1911; d. July 14, 1996. 27. vii. ROBERT
KING. 17. JAMES SAMUEL5 KING (SAMUEL4, JOHN WILLIAM3, MESHACK2, UNK1) was born May 24, 1853 in
Noble Co., OH. He married DIANTHA
ADRIANNE CALLAND. She was born in
Washington Co., OH. Children of JAMES KING and DIANTHA CALLAND are: i. WILBERT EDGAR6
KING, b. July 19, 1875. ii. IVA ROSILLA
KING, b. September 16, 1876. iii. FRANCIS
MARION KING, b. October 24, 1877. iv. OLIVER ORESTES
KING, b. July 13, 1879. v. OSCAR O. KING,
b. November 24, 1880. vi. GERTRUDE E.
KING, b. February 28, 1882. vii. CHARLES ROSS
KING, b. April 28, 1883. viii. PEARL M.
KING, b. March 27, 1886. ix. J.S. CLYDE
KING, b. July 24, 1889. x. RAY STANLEY KING,
b. March 13, 1892. xi. ATTA L. KING,
b. November 25, 1895; d. June 13, 1909. 18. JOHN RAMONE5 THORNTON (HANNAH HARRIET4 KING, JOHN WILLIAM3, MESHACK2, UNK1) was born Abt. 1867 in
Stock Twp., Noble Co., OH. He married ARMINTA WHITE June
23, 1889 in Noble Co., OH. She was born Abt. 1870 in Center Twp., Noble Co.,
OH. Children of JOHN THORNTON and ARMINTA WHITE are: i. ELMER T.6
THORNTON, b. Abt. 1890. ii. JOHN E.
THORNTON, b. Abt. 1891. iii. TIMOTHY E.
THORNTON, b. Abt. 1893. iv. IONA W.
THORNTON, b. Abt. 1897. 19. WILLIAM S5 THORNTON (HANNAH HARRIET4 KING, JOHN WILLIAM3, MESHACK2, UNK1) was born Abt. 1869 in
Stock Twp., Noble Co., OH. He married SARAH M. FOGLE June 18, 1897 in Noble
Co., OH. She was born 1872 in Ohio. Child of WILLIAM THORNTON and SARAH FOGLE is: i. ANNA6
THORNTON, b. Abt. 1898. 20. FRANCIS MARION5 THORNTON (HANNAH HARRIET4 KING, JOHN WILLIAM3, MESHACK2, UNK1) was born Abt. 1876 in
Stock Twp., Noble Co., OH. He married RACHEL FLORENCE
SHIPLEY March 21, 1895 in East
Union, Noble Co., OH. She was born Abt. 1879 in Stock Twp., Noble Co., OH. Children of FRANCIS THORNTON and RACHEL SHIPLEY are: i. IDA6
THORNTON, b. Abt. 1895. ii. GLEN THORNTON,
b. Abt. 1898. iii. VICTORIA
THORNTON, b. Abt. 1899. 21. JACOB ALLEN5 KING (WILLIAM4, JOHN WILLIAM3, MESHACK2, UNK1) was born 1867 in Stock
Twp., Noble Co., OH, and died 1939. He married EDITH VIOLA MOORE October 20, 1888 in Noble
Co., OH. She was born 1872, and died 1957. More About JACOB ALLEN KING: Burial: East Union
Cemetery, Noble Co., OH More About EDITH VIOLA MOORE: Burial: East
Union Cemetery Children of JACOB KING and EDITH MOORE are: i. MYRTLE C.6
KING, b. Abt. 1891; m. JESSE JAMES GORDON, January 23, 1912. ii. CLYDE KING, b.
April 24, 1893, Stock Twp., Noble Co., OH; d. April 1983, Caldwell, Noble
Co., OH; m. MYRTLE M. UNKNOWN; b. 1896; d. 1975. More About CLYDE KING: Burial: East Union Cemetery, Noble Co., OH More About MYRTLE M. UNKNOWN: Burial: East Union Cemetery, Noble Co., OH iii. WILBERT DEWEY
KING, b. Abt. 1897, Stock Twp., Noble Co., OH. 22. FRANCES A.5 KING (WILLIAM4, JOHN WILLIAM3, MESHACK2, UNK1) was born Abt. 1869 in
Stock Twp., Noble Co., OH, and died Bef. 1910. She married ASBURY WHITE December 09, 1892 in
Noble Co., OH. He was born Abt. 1872. Children of FRANCES KING and ASBURY WHITE are: i. ODESSA V.6
WHITE, b. Abt. 1894. ii. ANNA M. WHITE,
b. Abt. 1898. iii. WILBERT
RAYNOR WHITE, b. Abt. 1899. Generation No. 6 23. LAWRENCE6 KING (CLARENCE ELWOOD5, WILLIAM HENRY4, MESHACK3, MESHACK2, UNK1) was born August 14, 1904,
and died November 08, 1991 in Ohio. He married DORIS MARLENE THARP, daughter of CHARLEY THARP and BERTHA DOWD. She was born January 04,
1905, and died March 15, 1995 in Ohio. Children of LAWRENCE KING and DORIS THARP are: 28. i. KENNETH
WAYNE7 KING, b. March 19, 1936. 29. ii. LYLE
ELWOOD KING. 30. iii. DONALD
KING. 31. iv. MARY LOU
KING. 24. PEARL A.6 KING (CLARENCE ELWOOD5, WILLIAM HENRY4, MESHACK3, MESHACK2, UNK1) was born May 31, 1901,
and died April 25, 1992. She married ROY R. BEESON. He was born December 06,
1896, and died December 18, 1961. Children of PEARL KING and ROY BEESON are: i. DAVID7
BEESON. ii. DWIGHT BEESON,
b. August 31, 1921. 25. RUSSELL6 KING (CLARENCE ELWOOD5, WILLIAM HENRY4, MESHACK3, MESHACK2, UNK1) was born July 01, 1908,
and died May 01, 1989. He married HELEN JONES.
She was born October 19, 1905, and died July 1984. Child of RUSSELL KING and HELEN JONES is: 32. i. WILLIAM7
KING. 26. GAYLORD KING6 KING (CLARENCE ELWOOD5, WILLIAM HENRY4, MESHACK3, MESHACK2, UNK1) was born January 17,
1911, and died July 14, 1996. He married MARY B. MCINTOSH. Child of GAYLORD KING and MARY MCINTOSH is: 33. i. LYNN7
KING. 27. ROBERT6 KING (CLARENCE ELWOOD5, WILLIAM HENRY4, MESHACK3, MESHACK2, UNK1) He married DOROTHY J. MARY MORRISON. She was born July 01,
1917. Children of ROBERT KING and DOROTHY MORRISON are: i. CAROLYN7
KING. ii. KEVIN KING. Generation No. 7 28. KENNETH WAYNE7 KING (LAWRENCE6, CLARENCE ELWOOD5, WILLIAM HENRY4, MESHACK3, MESHACK2, UNK1) was born March 19, 1936.
He married (1) CHRISTINA LOUISE CLAFFEY, daughter of CASSIUS CLAFFEY and EMMA BAILEY. She was born September
23, 1936. He married (2) MARY MCQUISTION. Notes for MARY MCQUISTION: No children born
to this marriage Children of KENNETH KING and CHRISTINA CLAFFEY are: 34. i. MITCHELL
ARLEN8 KING, b. January 13, 1958, Newark, Ohio. 35. ii. CLAYTON
KING, b. November 22, 1959. iii. MELANIE KING,
b. March 03, 1955; m. DAVID RUSHTON. Notes for MELANIE KING: No children 29. LYLE ELWOOD7 KING (LAWRENCE6, CLARENCE ELWOOD5, WILLIAM HENRY4, MESHACK3, MESHACK2, UNK1) He married ELAIN MCGRUDER. Children of LYLE KING and ELAIN MCGRUDER are: i. CRESTON8
KING. ii. KIMBERLY KING. iii. KAREN KING. 30. DONALD7 KING (LAWRENCE6, CLARENCE ELWOOD5, WILLIAM HENRY4, MESHACK3, MESHACK2, UNK1) He married ARLENE BEENY. Children of DONALD KING and ARLENE BEENY are: i. RODNEY8
KING. ii. DEBORAH KING. 31. MARY LOU7 KING (LAWRENCE6, CLARENCE ELWOOD5, WILLIAM HENRY4, MESHACK3, MESHACK2, UNK1) She married KENNETH HANKINSON. Children of MARY KING and KENNETH HANKINSON are: i. SCOTT8
HANKINSON. ii. LARRY
HANKINSON. 32. WILLIAM7 KING (RUSSELL6, CLARENCE ELWOOD5, WILLIAM HENRY4, MESHACK3, MESHACK2, UNK1) He married PAMELA. Children of WILLIAM KING and PAMELA are: i. PAMELA8
KING. ii. PEGGY KING. iii. DAVID KING. 33. LYNN7 KING (GAYLORD KING6, CLARENCE ELWOOD5, WILLIAM HENRY4, MESHACK3, MESHACK2, UNK1) He married CHARLOTTE BRADFORD. Children of LYNN KING and CHARLOTTE BRADFORD are: i. CLARA8
KING. ii. GAIL RUSSELL
KING. Generation No. 8 34. MITCHELL ARLEN8 KING (KENNETH WAYNE7, LAWRENCE6, CLARENCE ELWOOD5, WILLIAM HENRY4, MESHACK3, MESHACK2, UNK1) was born January 13, 1958
in Newark, Ohio. He married KELLY LOU JENNINGS April 14, 1984 in DIllon,
South Carolina, daughter of WILLIAM
JENNINGS and LOIS THOMPKINS. She was born June 20,
1960 in Coshocton, OH. Children of MITCHELL KING and KELLY JENNINGS are: i. KASEY WILLIAM9
KING, b. April 18, 1992, Coshocton OH. ii. AARON MITCHELL
KING, b. January 27, 1994, Coshocton OH. 35. CLAYTON8 KING (KENNETH WAYNE7, LAWRENCE6, CLARENCE ELWOOD5, WILLIAM HENRY4, MESHACK3, MESHACK2, UNK1) was born November 22,
1959. He married CHRIS ISHIMAL. Child of CLAYTON KING and CHRIS ISHIMAL is: i. ANNA CHRISTINE9
KING. |
Provided by Kelly King
Click here for the Short-Cut Table
of Contents


How do you distribute your time?
Each week has {{totalHoursWeek}} hours and each day has {{totalHoursDay}} hours.
Select the number of hours you spend on each category per day and the number of days a week:
Sleep and rest: is the time used for relax and sleep.
Select the number of hours per day:
per day.
How often do you do these activities?
You invest: {{sleepCategory.hoursByWeek}}hrs. per week and {{sleepCategory.hours}} hours per day.
Education: Activities to learn something new or develop abilities.
Select the number of hours per day:
per day.
How often do you do these activities?
You invest: {{educationCategory.hoursByWeek}}hrs. per week and {{educationCategory.hours}} hours per day.
Health: time to improve or maintain your body in good shape.
Select the number of hours per day:
per day.
How often do you do these activities?
You invest: {{healthCategory.hoursByWeek}}hrs. per week and {{healthCategory.hours}} hours per day.

Select the number of hours per day:
per day.
How often do you do these activities?
You invest: {{breakfastCategory.hoursByWeek}}hrs. per week and {{breakfastCategory.hours}} hours per day.
Work: time that you use to develop professionals activities.
Select the number of hours per day:
per day.
How often do you do these activities?
You invest: {{workCategory.hoursByWeek}}hrs. per week and {{workCategory.hours}} hours per day.
Family: spend with your parents, siblings or any member of your family.
Select the number of hours per day:
per day.
How often do you do these activities?
You invest: {{familyCategory.hoursByWeek}}hrs. per week and {{familyCategory.hours}} hours per day.
Transportation: Drive your car or take a bus from one location to another.
Select the number of hours per day:
per day.
How often do you do these activities?
You invest: {{transportCategory.hoursByWeek}}hrs. per week and {{transportCategory.hours}} hours per day.

Select the number of hours per day:
per day.
How often do you do these activities?
You invest: {{mealtimeCategory.hoursByWeek}}hrs. per week and {{mealtimeCategory.hours}} hours per day.
Entertainment: Activities like go to the cinema or be with your friends.
Select the number of hours per day:
per day.
How often do you do these activities?
You invest: {{entertainmentCategory.hoursByWeek}}hrs. per week and {{entertainmentCategory.hours}} hours per day.
Note: If your doing other activities, you try you include within the categories set.


About Our Resturent
Salmon Cookies offer you various types of vanilla, chocolate and raspberry flavours that is made locally through our store.
If you wont to more information about sales visit the sales page
Location:
- Seatile
- Tokyo
- Dubai
- Paris
- Lima
Hours open
| Location: | Hours open |
|---|---|
| Seatile | from 6Am to 7Pm |
| tokyo | from 6Am to 7Pm |
| dubai | from 6Am to 7Pm |
| paris | from 6Am to 7Pm |
| lima | from 6Am to 7Pm |


--- title: Vista Pre-RC1 (build 5536) date: '2006-08-31T08:59:00.000-04:00' author: John tags: - Vista modified_time: '2010-09-05T14:43:12.786-04:00' blogger_id: tag:blogger.com,1999:blog-2811308028656623966.post-4603788618508177431 blogger_orig_url: http://pragmatic-software.blogspot.com/2006/08/vista-pre-rc1-build-5536.html ---
Since my Beta 2 was acting very flakey I decided to format the partition and try a newer version. It installed cleanly and came up with no problems. One issue I discovered is that avast! antivirus (free for home use) does not work on build 5536. After installing and rebooting, you'll get a message that Windows Vista has disabled a faulty driver. Hunting around on avast!'s forums I found out that someone claims MS made a mistake in "banning" avast!'s driver and it would be corrected for the RC1 release coming soon.


J
Recovery Mode
File
Edit
Utilities
Window
Sun, 09:41 AM
Jonathan Levin
NewOSXBook
The NewOSXBook platform is currently running in Recovery Mode. Only the Newscast is available.
View NewOSX Newscast
NewOSXBook Newscast
Volume I - User Mode -
Available, v1.3b4
-
See detailed ToC
Volume II -
Later this year (wrapping up notes for Darwin 19 betas)
- It takes time to write these books.
Volume III - Security & Insecurity is
available, v1.6


--- layout: docs title: Reference ---
Links to the language specific automatically generated API reference documentation.


Toggle navigation
JUST DENTAL
Dr. Ujjwal K
Manage My Clinic
Edit Clinic Details
Change Login/Password
Edit/Modify Services
5
Import/Export
My Dashboard
Sales
Patients
Products & Services
Inventory (Cart)
Modules
Billing
₹ 16,800
Invoices
Inventory
Reminders
2
JD Connect
News
JD Newsletters
Publications
2
Notifications
42
×
Welcome Dr. Ujjwal K - (Whitefield Clinic), Have a good day.
12
New appointments
89
Patients Attended
1.2K
Registered patients
59K
Total Earnings


The save state feature allows you to save the current look of the grid and restore it upon returning to the grid.
For example, you may have an application where your user can reorder the columns, adjust column widths, apply sorts and filters, and select a specific cell. The user might adjust their grid to look as they wish, and then navigate to another page. When the user returns to the page with the grid, they might expect it to look like it did when they left. The save state feature permits this.
Documentation for the saveState feature is provided in the api documentation, in particular:
There are two core methods:
Note that the saveState functionality deliberately sets out to store the transient state - the information that isn't held in gridOptions nor columnDefs. The calling application is responsible for storing gridOptions and columnDefs (and must have had them in order to render the grid the first time).
The feature also provides some options that control what is saved. All options are true by default:
For better performance with the following example, you can choose to load the ui-grid.core.js and specific feature files instead:
<script src="/release/ui-grid.core.min.js"></script> <script src="/release/ui-grid.cellnav.min.js"></script> <script src="/release/ui-grid.selection.min.js"></script> <script src="/release/ui-grid.resize-columns.min.js"></script> <script src="/release/ui-grid.move-columns.min.js"></script> <script src="/release/ui-grid.pinning.min.js"></script> <script src="/release/ui-grid.tree-base.min.js"></script> <script src="/release/ui-grid.tree-view.min.js"></script> <script src="/release/ui-grid.grouping.min.js"></script> <script src="/release/ui-grid.save-state.min.js"></script>
In this example we provide a button to save the grid state. You can then modify the grid layout to something different, and use the restore button to set the grid back the way it was.


This document describes the CapacityScheduler, a pluggable scheduler for Hadoop which allows for multiple-tenants to securely share a large cluster such that their applications are allocated resources in a timely manner under constraints of allocated capacities.
The CapacityScheduler is designed to run Hadoop applications as a shared, multi-tenant cluster in an operator-friendly manner while maximizing the throughput and the utilization of the cluster.
Traditionally each organization has it own private set of compute resources that have sufficient capacity to meet the organization’s SLA under peak or near-peak conditions. This generally leads to poor average utilization and overhead of managing multiple independent clusters, one per each organization. Sharing clusters between organizations is a cost-effective manner of running large Hadoop installations since this allows them to reap benefits of economies of scale without creating private clusters. However, organizations are concerned about sharing a cluster because they are worried about others using the resources that are critical for their SLAs.
 The central idea is that the available resources in the Hadoop cluster are shared among multiple organizations who collectively fund the cluster based on their computing needs. There is an added benefit that an organization can access any excess capacity not being used by others. This provides elasticity for the organizations in a cost-effective manner.
Sharing clusters across organizations necessitates strong support for multi-tenancy since each organization must be guaranteed capacity and safe-guards to ensure the shared cluster is impervious to single rogue application or user or sets thereof. The CapacityScheduler provides a stringent set of limits to ensure that a single application or user or queue cannot consume disproportionate amount of resources in the cluster. Also, the CapacityScheduler provides limits on initialized and pending applications from a single user and queue to ensure fairness and stability of the cluster.
The primary abstraction provided by the CapacityScheduler is the concept of queues. These queues are typically setup by administrators to reflect the economics of the shared cluster.
To provide further control and predictability on sharing of resources, the CapacityScheduler supports hierarchical queues to ensure resources are shared among the sub-queues of an organization before other queues are allowed to use free resources, thereby providing affinity for sharing free resources among applications of a given organization.
The CapacityScheduler supports the following features:
Hierarchical Queues - Hierarchy of queues is supported to ensure resources are shared among the sub-queues of an organization before other queues are allowed to use free resources, thereby providing more control and predictability.
Capacity Guarantees - Queues are allocated a fraction of the capacity of the grid in the sense that a certain capacity of resources will be at their disposal. All applications submitted to a queue will have access to the capacity allocated to the queue. Administrators can configure soft limits and optional hard limits on the capacity allocated to each queue.
Security - Each queue has strict ACLs which controls which users can submit applications to individual queues. Also, there are safe-guards to ensure that users cannot view and/or modify applications from other users. Also, per-queue and system administrator roles are supported.
Elasticity - Free resources can be allocated to any queue beyond its capacity. When there is demand for these resources from queues running below capacity at a future point in time, as tasks scheduled on these resources complete, they will be assigned to applications on queues running below the capacity (preemption is also supported). This ensures that resources are available in a predictable and elastic manner to queues, thus preventing artificial silos of resources in the cluster which helps utilization.
Multi-tenancy - Comprehensive set of limits are provided to prevent a single application, user and queue from monopolizing resources of the queue or the cluster as a whole to ensure that the cluster isn’t overwhelmed.
Operability
Runtime Configuration - The queue definitions and properties such as capacity, ACLs can be changed, at runtime, by administrators in a secure manner to minimize disruption to users. Also, a console is provided for users and administrators to view current allocation of resources to various queues in the system. Administrators can add additional queues at runtime, but queues cannot be deleted at runtime unless the queue is STOPPED and has no pending/running apps.
Drain applications - Administrators can stop queues at runtime to ensure that while existing applications run to completion, no new applications can be submitted. If a queue is in STOPPED state, new applications cannot be submitted to itself or any of its child queues. Existing applications continue to completion, thus the queue can be drained gracefully. Administrators can also start the stopped queues.
Resource-based Scheduling - Support for resource-intensive applications, where-in a application can optionally specify higher resource-requirements than the default, thereby accommodating applications with differing resource requirements. Currently, memory is the resource requirement supported.
Queue Mapping Interface based on Default or User Defined Placement Rules - This feature allows users to map a job to a specific queue based on some default placement rule. For instance based on user & group, or application name. User can also define their own placement rule.
Priority Scheduling - This feature allows applications to be submitted and scheduled with different priorities. Higher integer value indicates higher priority for an application. Currently Application priority is supported only for FIFO ordering policy.
Absolute Resource Configuration - Administrators could specify absolute resources to a queue instead of providing percentage based values. This provides better control for admins to configure required amount of resources for a given queue.
Dynamic Auto-Creation and Management of Leaf Queues - This feature supports auto-creation of leaf queues in conjunction with queue-mapping which currently supports user-group based queue mappings for application placement to a queue. The scheduler also supports capacity management for these queues based on a policy configured on the parent queue.
To configure the ResourceManager to use the CapacityScheduler, set the following property in the conf/yarn-site.xml:
| Property | Value |
|---|---|
| yarn.resourcemanager.scheduler.class | org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler |
etc/hadoop/capacity-scheduler.xml is the configuration file for the CapacityScheduler.
The CapacityScheduler has a predefined queue called root. All queues in the system are children of the root queue.
Further queues can be setup by configuring yarn.scheduler.capacity.root.queues with a list of comma-separated child queues.
The configuration for CapacityScheduler uses a concept called queue path to configure the hierarchy of queues. The queue path is the full path of the queue’s hierarchy, starting at root, with . (dot) as the delimiter.
A given queue’s children can be defined with the configuration knob: yarn.scheduler.capacity.<queue-path>.queues. Children do not inherit properties directly from the parent unless otherwise noted.
Here is an example with three top-level child-queues a, b and c and some sub-queues for a and b:
<property> <name>yarn.scheduler.capacity.root.queues</name> <value>a,b,c</value> <description>The queues at the this level (root is the root queue). </description> </property> <property> <name>yarn.scheduler.capacity.root.a.queues</name> <value>a1,a2</value> <description>The queues at the this level (root is the root queue). </description> </property> <property> <name>yarn.scheduler.capacity.root.b.queues</name> <value>b1,b2,b3</value> <description>The queues at the this level (root is the root queue). </description> </property>
| Property | Description |
|---|---|
| yarn.scheduler.capacity.<queue-path>.capacity | Queue capacity in percentage (%) as a float (e.g. 12.5) OR as absolute resource queue minimum capacity. The sum of capacities for all queues, at each level, must be equal to 100. However if absolute resource is configured, sum of absolute resources of child queues could be less than it’s parent absolute resource capacity. Applications in the queue may consume more resources than the queue’s capacity if there are free resources, providing elasticity. |
| yarn.scheduler.capacity.<queue-path>.maximum-capacity | Maximum queue capacity in percentage (%) as a float OR as absolute resource queue maximum capacity. This limits the elasticity for applications in the queue. 1) Value is between 0 and 100. 2) Admin needs to make sure absolute maximum capacity >= absolute capacity for each queue. Also, setting this value to -1 sets maximum capacity to 100%. |
| yarn.scheduler.capacity.<queue-path>.minimum-user-limit-percent | Each queue enforces a limit on the percentage of resources allocated to a user at any given time, if there is demand for resources. The user limit can vary between a minimum and maximum value. The former (the minimum value) is set to this property value and the latter (the maximum value) depends on the number of users who have submitted applications. For e.g., suppose the value of this property is 25. If two users have submitted applications to a queue, no single user can use more than 50% of the queue resources. If a third user submits an application, no single user can use more than 33% of the queue resources. With 4 or more users, no user can use more than 25% of the queues resources. A value of 100 implies no user limits are imposed. The default is 100. Value is specified as a integer. |
| yarn.scheduler.capacity.<queue-path>.user-limit-factor | The multiple of the queue capacity which can be configured to allow a single user to acquire more resources. By default this is set to 1 which ensures that a single user can never take more than the queue’s configured capacity irrespective of how idle the cluster is. Value is specified as a float. |
| yarn.scheduler.capacity.<queue-path>.maximum-allocation-mb | The per queue maximum limit of memory to allocate to each container request at the Resource Manager. This setting overrides the cluster configuration yarn.scheduler.maximum-allocation-mb. This value must be smaller than or equal to the cluster maximum. |
| yarn.scheduler.capacity.<queue-path>.maximum-allocation-vcores | The per queue maximum limit of virtual cores to allocate to each container request at the Resource Manager. This setting overrides the cluster configuration yarn.scheduler.maximum-allocation-vcores. This value must be smaller than or equal to the cluster maximum. |
| yarn.scheduler.capacity.<queue-path>.user-settings.<user-name>.weight | This floating point value is used when calculating the user limit resource values for users in a queue. This value will weight each user more or less than the other users in the queue. For example, if user A should receive 50% more resources in a queue than users B and C, this property will be set to 1.5 for user A. Users B and C will default to 1.0. |
CapacityScheduler supports configuration of absolute resources instead of providing Queue capacity in percentage. As mentioned in above configuration section for yarn.scheduler.capacity.<queue-path>.capacity and yarn.scheduler.capacity.<queue-path>.max-capacity, administrator could specify an absolute resource value like [memory=10240,vcores=12]. This is a valid configuration which indicates 10GB Memory and 12 VCores.
The CapacityScheduler supports the following parameters to control the running and pending applications:
| Property | Description |
|---|---|
| yarn.scheduler.capacity.maximum-applications / yarn.scheduler.capacity.<queue-path>.maximum-applications | Maximum number of applications in the system which can be concurrently active both running and pending. Limits on each queue are directly proportional to their queue capacities and user limits. This is a hard limit and any applications submitted when this limit is reached will be rejected. Default is 10000. This can be set for all queues with yarn.scheduler.capacity.maximum-applications and can also be overridden on a per queue basis by setting yarn.scheduler.capacity.<queue-path>.maximum-applications. Integer value expected. |
| yarn.scheduler.capacity.maximum-am-resource-percent / yarn.scheduler.capacity.<queue-path>.maximum-am-resource-percent | Maximum percent of resources in the cluster which can be used to run application masters - controls number of concurrent active applications. Limits on each queue are directly proportional to their queue capacities and user limits. Specified as a float - ie 0.5 = 50%. Default is 10%. This can be set for all queues with yarn.scheduler.capacity.maximum-am-resource-percent and can also be overridden on a per queue basis by setting yarn.scheduler.capacity.<queue-path>.maximum-am-resource-percent |
| yarn.scheduler.capacity.max-parallel-apps / yarn.scheduler.capacity.<queue-path>.max-parallel-apps | Maximum number of applications that can run at the same time. Unlike to maximum-applications, application submissions are not rejected when this limit is reached. Instead they stay in ACCEPTED state until they are eligible to run. This can be set for all queues with yarn.scheduler.capacity.max-parallel-apps and can also be overridden on a per queue basis by setting yarn.scheduler.capacity.<queue-path>.max-parallel-apps. Integer value is expected. By default, there is no limit. |
You can also limit the number of parallel applications on a per user basis.
| Property | Description |
|---|---|
| yarn.scheduler.capacity.user.max-parallel-apps | Maximum number of applications that can run at the same time for all users. Default value is unlimited. |
| yarn.scheduler.capacity.user.<username>.max-parallel-apps | Maximum number of applications that can run at the same for a specific user. This overrides the global setting. |
The evaluation of these limits happens in the following order:
maximum-applications check - if the limit is exceeded, the submission is rejected immediately.
max-parallel-apps check - the submission is accepted, but the application will not transition to RUNNING state. It stays in ACCEPTED until the queue / user limits are satisfied.
maximum-am-resource-percent check - if there are too many Application Masters running, the application stays in ACCEPTED state until there is enough room for it.
The CapacityScheduler supports the following parameters to the administer the queues:
| Property | Description |
|---|---|
| yarn.scheduler.capacity.<queue-path>.state | The state of the queue. Can be one of RUNNING or STOPPED. If a queue is in STOPPED state, new applications cannot be submitted to itself or any of its child queues. Thus, if the root queue is STOPPED no applications can be submitted to the entire cluster. Existing applications continue to completion, thus the queue can be drained gracefully. Value is specified as Enumeration. |
| yarn.scheduler.capacity.root.<queue-path>.acl_submit_applications | The ACL which controls who can submit applications to the given queue. If the given user/group has necessary ACLs on the given queue or one of the parent queues in the hierarchy they can submit applications. ACLs for this property are inherited from the parent queue if not specified. If a tilde (~) is prepended to a user name in this list, the real user’s ACLs will allow the proxied user to submit to the queue. |
| yarn.scheduler.capacity.root.<queue-path>.acl_administer_queue | The ACL which controls who can administer applications on the given queue. If the given user/group has necessary ACLs on the given queue or one of the parent queues in the hierarchy they can administer applications. ACLs for this property are inherited from the parent queue if not specified. If a tilde (~) is prepended to a user name in this list, the real user’s ACLs will allow the proxied user to administer apps the queue. |
Note: An ACL is of the form user1,user2 space group1,group2. The special value of * implies anyone. The special value of space implies no one. The default is * for the root queue if not specified.
The CapacityScheduler supports the following parameters to configure the queue mapping based on user or group, user & group, or application name. User can also define their own placement rule:
| Property | Description |
|---|---|
| yarn.scheduler.capacity.queue-mappings | This configuration specifies the mapping of user or group to a specific queue. You can map a single user or a list of users to queues. Syntax: [u or g]:[name]:[queue_name][,next_mapping]*. Here, u or g indicates whether the mapping is for a user or group. The value is u for user and g for group. name indicates the user name or group name. To specify the user who has submitted the application, %user can be used. queue_name indicates the queue name for which the application has to be mapped. To specify queue name same as user name, %user can be used. To specify queue name same as the name of the primary group for which the user belongs to, %primary_group can be used. Secondary group can be referenced as %secondary_group |
| yarn.scheduler.queue-placement-rules.app-name | This configuration specifies the mapping of application_name to a specific queue. You can map a single application or a list of applications to queues. Syntax: [app_name]:[queue_name][,next_mapping]*. Here, app_name indicates the application name you want to do the mapping. queue_name indicates the queue name for which the application has to be mapped. To specify the current application’s name as the app_name, %application can be used. |
| yarn.scheduler.capacity.queue-mappings-override.enable | This function is used to specify whether the user specified queues can be overridden. This is a Boolean value and the default value is false. |
Example:
Below example covers single mapping separately. In case of multiple mappings with comma separated values, evaluation would be from left to right, and the first valid mapping will be used. Below example order has been documented based on actual order of execution at runtime in case of multiple mappings.
<property> <name>yarn.scheduler.capacity.queue-mappings</name> <value>u:%user:%primary_group.%user</value> <description>Maps users to queue with the same name as user but parent queue name should be same as primary group of the user</description> </property> ... <property> <name>yarn.scheduler.capacity.queue-mappings</name> <value>u:%user:%secondary_group.%user</value> <description>Maps users to queue with the same name as user but parent queue name should be same as any secondary group of the user</description> </property> ... <property> <name>yarn.scheduler.capacity.queue-mappings</name> <value>u:%user:%user</value> <description>Maps users to queues with the same name as user</description> </property> ... <property> <name>yarn.scheduler.capacity.queue-mappings</name> <value>u:user2:%primary_group</value> <description>user2 is mapped to queue name same as primary group</description> </property> ... <property> <name>yarn.scheduler.capacity.queue-mappings</name> <value>u:user3:%secondary_group</value> <description>user3 is mapped to queue name same as secondary group</description> </property> ... <property> <name>yarn.scheduler.capacity.queue-mappings</name> <value>u:user1:queue1</value> <description>user1 is mapped to queue1</description> </property> ... <property> <name>yarn.scheduler.capacity.queue-mappings</name> <value>g:group1:queue2</value> <description>group1 is mapped to queue2</description> </property> ... <property> <name>yarn.scheduler.capacity.queue-mappings</name> <value>u:user1:queue1,u:user2:queue2</value> <description>Here, <user1> is mapped to <queue1>, <user2> is mapped to <queue2> respectively</description> </property> <property> <name>yarn.scheduler.queue-placement-rules.app-name</name> <value>appName1:queue1,%application:%application</value> <description> Here, <appName1> is mapped to <queue1>, maps applications to queues with the same name as application respectively. The mappings will be evaluated from left to right, and the first valid mapping will be used. </description> </property>
The CapacityScheduler supports the following parameters to lifetime of an application:
| Property | Description |
|---|---|
| yarn.scheduler.capacity.<queue-path>.maximum-application-lifetime | Maximum lifetime (in seconds) of an application which is submitted to a queue. Any value less than or equal to zero will be considered as disabled. The default is -1. If positive value is configured then any application submitted to this queue will be killed after it exceeds the configured lifetime. User can also specify lifetime per application in application submission context. However, user lifetime will be overridden if it exceeds queue maximum lifetime. It is point-in-time configuration. Note: This feature can be set at any level in the queue hierarchy. Child queues will inherit their parent’s value unless overridden at the child level. A value of 0 means no max lifetime and will override a parent’s max lifetime. If this property is not set or is set to a negative number, then this queue’s max lifetime value will be inherited from it’s parent. |
| yarn.scheduler.capacity.root.<queue-path>.default-application-lifetime | Default lifetime (in seconds) of an application which is submitted to a queue. Any value less than or equal to zero will be considered as disabled. If the user has not submitted application with lifetime value then this value will be taken. It is point-in-time configuration. This feature can be set at any level in the queue hierarchy. Child queues will inherit their parent’s value unless overridden at the child level. If set to less than or equal to 0, the queue’s max value must also be unlimited. Default lifetime can’t exceed maximum lifetime. |
Application priority works only along with FIFO ordering policy. Default ordering policy is FIFO.
Default priority for an application can be at cluster level and queue level.
| Property | Description |
|---|---|
| yarn.cluster.max-application-priority | Defines maximum application priority in a cluster. |
| Property | Description |
|---|---|
| yarn.scheduler.capacity.root.<leaf-queue-path>.default-application-priority | Defines default application priority in a leaf queue. |
Note: Priority of an application will not be changed when application is moved to different queue.
The CapacityScheduler supports preemption of container from the queues whose resource usage is more than their guaranteed capacity. The following configuration parameters need to be enabled in yarn-site.xml for supporting preemption of application containers.
| Property | Description |
|---|---|
| yarn.resourcemanager.scheduler.monitor.enable | Enable a set of periodic monitors (specified in yarn.resourcemanager.scheduler.monitor.policies) that affect the scheduler. Default value is false. |
| yarn.resourcemanager.scheduler.monitor.policies | The list of SchedulingEditPolicy classes that interact with the scheduler. Configured policies need to be compatible with the scheduler. Default value is org.apache.hadoop.yarn.server.resourcemanager.monitor.capacity.ProportionalCapacityPreemptionPolicy which is compatible with CapacityScheduler |
The following configuration parameters can be configured in yarn-site.xml to control the preemption of containers when ProportionalCapacityPreemptionPolicy class is configured for yarn.resourcemanager.scheduler.monitor.policies
| Property | Description |
|---|---|
| yarn.resourcemanager.monitor.capacity.preemption.observe_only | If true, run the policy but do not affect the cluster with preemption and kill events. Default value is false |
| yarn.resourcemanager.monitor.capacity.preemption.monitoring_interval | Time in milliseconds between invocations of this ProportionalCapacityPreemptionPolicy policy. Default value is 3000 |
| yarn.resourcemanager.monitor.capacity.preemption.max_wait_before_kill | Time in milliseconds between requesting a preemption from an application and killing the container. Default value is 15000 |
| yarn.resourcemanager.monitor.capacity.preemption.total_preemption_per_round | Maximum percentage of resources preempted in a single round. By controlling this value one can throttle the pace at which containers are reclaimed from the cluster. After computing the total desired preemption, the policy scales it back within this limit. Default value is 0.1 |
| yarn.resourcemanager.monitor.capacity.preemption.max_ignored_over_capacity | Maximum amount of resources above the target capacity ignored for preemption. This defines a deadzone around the target capacity that helps prevent thrashing and oscillations around the computed target balance. High values would slow the time to capacity and (absent natural.completions) it might prevent convergence to guaranteed capacity. Default value is 0.1 |
| yarn.resourcemanager.monitor.capacity.preemption.natural_termination_factor | Given a computed preemption target, account for containers naturally expiring and preempt only this percentage of the delta. This determines the rate of geometric convergence into the deadzone (MAX_IGNORED_OVER_CAPACITY). For example, a termination factor of 0.5 will reclaim almost 95% of resources within 5 * #WAIT_TIME_BEFORE_KILL, even absent natural termination. Default value is 0.2 |
The CapacityScheduler supports the following configurations in capacity-scheduler.xml to control the preemption of application containers submitted to a queue.
| Property | Description |
|---|---|
| yarn.scheduler.capacity.<queue-path>.disable_preemption | This configuration can be set to true to selectively disable preemption of application containers submitted to a given queue. This property applies only when system wide preemption is enabled by configuring yarn.resourcemanager.scheduler.monitor.enable to true and yarn.resourcemanager.scheduler.monitor.policies to ProportionalCapacityPreemptionPolicy. If this property is not set for a queue, then the property value is inherited from the queue’s parent. Default value is false. |
| yarn.scheduler.capacity.<queue-path>.intra-queue-preemption.disable_preemption | This configuration can be set to true to selectively disable intra-queue preemption of application containers submitted to a given queue. This property applies only when system wide preemption is enabled by configuring yarn.resourcemanager.scheduler.monitor.enable to true, yarn.resourcemanager.scheduler.monitor.policies to ProportionalCapacityPreemptionPolicy, and yarn.resourcemanager.monitor.capacity.preemption.intra-queue-preemption.enabled to true. If this property is not set for a queue, then the property value is inherited from the queue’s parent. Default value is false. |
The CapacityScheduler supports the following parameters to control the creation, deletion, update, and listing of reservations. Note that any user can update, delete, or list their own reservations. If reservation ACLs are enabled but not defined, everyone will have access. In the examples below, <queue> is the queue name. For example, to set the reservation ACL to administer reservations on the default queue, use the property yarn.scheduler.capacity.root.default.acl_administer_reservations
| Property | Description |
|---|---|
| yarn.scheduler.capacity.root.<queue>.acl_administer_reservations | The ACL which controls who can administer reservations to the given queue. If the given user/group has necessary ACLs on the given queue or they can submit, delete, update and list all reservations. ACLs for this property are not inherited from the parent queue if not specified. |
| yarn.scheduler.capacity.root.<queue>.acl_list_reservations | The ACL which controls who can list reservations to the given queue. If the given user/group has necessary ACLs on the given queue they can list all applications. ACLs for this property are not inherited from the parent queue if not specified. |
| yarn.scheduler.capacity.root.<queue>.acl_submit_reservations | The ACL which controls who can submit reservations to the given queue. If the given user/group has necessary ACLs on the given queue they can submit reservations. ACLs for this property are not inherited from the parent queue if not specified. |
The CapacityScheduler supports the ReservationSystem which allows users to reserve resources ahead of time. The application can request the reserved resources at runtime by specifying the reservationId during submission. The following configuration parameters can be configured in yarn-site.xml for ReservationSystem.
| Property | Description |
|---|---|
| yarn.resourcemanager.reservation-system.enable | Mandatory parameter: to enable the ReservationSystem in the ResourceManager. Boolean value expected. The default value is false, i.e. ReservationSystem is not enabled by default. |
| yarn.resourcemanager.reservation-system.class | Optional parameter: the class name of the ReservationSystem. The default value is picked based on the configured Scheduler, i.e. if CapacityScheduler is configured, then it is CapacityReservationSystem. |
| yarn.resourcemanager.reservation-system.plan.follower | Optional parameter: the class name of the PlanFollower that runs on a timer, and synchronizes the CapacityScheduler with the Plan and viceversa. The default value is picked based on the configured Scheduler, i.e. if CapacityScheduler is configured, then it is CapacitySchedulerPlanFollower. |
| yarn.resourcemanager.reservation-system.planfollower.time-step | Optional parameter: the frequency in milliseconds of the PlanFollower timer. Long value expected. The default value is 1000. |
The ReservationSystem is integrated with the CapacityScheduler queue hierachy and can be configured for any LeafQueue currently. The CapacityScheduler supports the following parameters to tune the ReservationSystem:
| Property | Description |
|---|---|
| yarn.scheduler.capacity.<queue-path>.reservable | Mandatory parameter: indicates to the ReservationSystem that the queue’s resources is available for users to reserve. Boolean value expected. The default value is false, i.e. reservations are not enabled in LeafQueues by default. |
| yarn.scheduler.capacity.<queue-path>.reservation-agent | Optional parameter: the class name that will be used to determine the implementation of the ReservationAgent which will attempt to place the user’s reservation request in the Plan. The default value is org.apache.hadoop.yarn.server.resourcemanager.reservation.planning.AlignedPlannerWithGreedy. |
| yarn.scheduler.capacity.<queue-path>.reservation-move-on-expiry | Optional parameter to specify to the ReservationSystem whether the applications should be moved or killed to the parent reservable queue (configured above) when the associated reservation expires. Boolean value expected. The default value is true indicating that the application will be moved to the reservable queue. |
| yarn.scheduler.capacity.<queue-path>.show-reservations-as-queues | Optional parameter to show or hide the reservation queues in the Scheduler UI. Boolean value expected. The default value is false, i.e. reservation queues will be hidden. |
| yarn.scheduler.capacity.<queue-path>.reservation-policy | Optional parameter: the class name that will be used to determine the implementation of the SharingPolicy which will validate if the new reservation doesn’t violate any invariants.. The default value is org.apache.hadoop.yarn.server.resourcemanager.reservation.CapacityOverTimePolicy. |
| yarn.scheduler.capacity.<queue-path>.reservation-window | Optional parameter representing the time in milliseconds for which the SharingPolicy will validate if the constraints in the Plan are satisfied. Long value expected. The default value is one day. |
| yarn.scheduler.capacity.<queue-path>.instantaneous-max-capacity | Optional parameter: maximum capacity at any time in percentage (%) as a float that the SharingPolicy allows a single user to reserve. The default value is 1, i.e. 100%. |
| yarn.scheduler.capacity.<queue-path>.average-capacity | Optional parameter: the average allowed capacity which will aggregated over the ReservationWindow in percentage (%) as a float that the SharingPolicy allows a single user to reserve. The default value is 1, i.e. 100%. |
| yarn.scheduler.capacity.<queue-path>.reservation-planner | Optional parameter: the class name that will be used to determine the implementation of the Planner which will be invoked if the Plan capacity fall below (due to scheduled maintenance or node failures) the user reserved resources. The default value is org.apache.hadoop.yarn.server.resourcemanager.reservation.planning.SimpleCapacityReplanner which scans the Plan and greedily removes reservations in reversed order of acceptance (LIFO) till the reserved resources are within the Plan capacity |
| yarn.scheduler.capacity.<queue-path>.reservation-enforcement-window | Optional parameter representing the time in milliseconds for which the Planner will validate if the constraints in the Plan are satisfied. Long value expected. The default value is one hour. |
The CapacityScheduler supports auto-creation of leaf queues under parent queues which have been configured to enable this feature.
user-group queue mapping(s) listed in yarn.scheduler.capacity.queue-mappings need to specify an additional parent queue parameter to identify which parent queue the auto-created leaf queues need to be created under. Refer above Queue Mapping based on User or Group section for more details. Please note that such parent queues also need to enable auto-creation of child queues as mentioned in Parent queue configuration for dynamic leaf queue creation and management section below
Example:
<property> <name>yarn.scheduler.capacity.queue-mappings</name> <value>u:user1:queue1,g:group1:queue2,u:user2:%primary_group,u:%user:parent1.%user</value> <description> Here, u:%user:parent1.%user mapping allows any <user> other than user1, user2 to be mapped to its own user specific leaf queue which will be auto-created under <parent1>. </description> </property>
The Dynamic Queue Auto-Creation and Management feature is integrated with the CapacityScheduler queue hierarchy and can be configured for a ParentQueue currently to auto-create leaf queues. Such parent queues do not support other pre-configured queues to co-exist along with auto-created queues. The CapacityScheduler supports the following parameters to enable auto-creation of queues
| Property | Description |
|---|---|
| yarn.scheduler.capacity.<queue-path>.auto-create-child-queue.enabled | Mandatory parameter: Indicates to the CapacityScheduler that auto leaf queue creation needs to be enabled for the specified parent queue. Boolean value expected. The default value is false, i.e. auto leaf queue creation is not enabled in ParentQueue by default. |
| yarn.scheduler.capacity.<queue-path>.auto-create-child-queue.management-policy | Optional parameter: the class name that will be used to determine the implementation of the AutoCreatedQueueManagementPolicy which will manage leaf queues and their capacities dynamically under this parent queue. The default value is org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.queuemanagement.GuaranteedOrZeroCapacityOverTimePolicy. Users or groups might submit applications to the auto-created leaf queues for a limited time and stop using them. Hence there could be more number of leaf queues auto-created under the parent queue than its guaranteed capacity. The current policy implementation allots either configured or zero capacity on a best-effort basis based on availability of capacity on the parent queue and the application submission order across leaf queues. |
The parent queue which has been enabled for auto leaf queue creation,supports the configuration of template parameters for automatic configuration of the auto-created leaf queues. The auto-created queues support all of the leaf queue configuration parameters except for Queue ACL, Absolute Resource configurations. Queue ACLs are currently inherited from the parent queue i.e they are not configurable on the leaf queue template
| Property | Description |
|---|---|
| yarn.scheduler.capacity.<queue-path>.leaf-queue-template.capacity | Mandatory parameter: Specifies the minimum guaranteed capacity for the auto-created leaf queues. Currently Absolute Resource configurations are not supported on auto-created leaf queues |
| yarn.scheduler.capacity.<queue-path>.leaf-queue-template.<leaf-queue-property> | Optional parameter: For other queue parameters that can be configured on auto-created leaf queues like maximum-capacity, user-limit-factor, maximum-am-resource-percent … - Refer Queue Properties section |
Example:
<property> <name>yarn.scheduler.capacity.root.parent1.auto-create-child-queue.enabled</name> <value>true</value> </property> <property> <name>yarn.scheduler.capacity.root.parent1.leaf-queue-template.capacity</name> <value>5</value> </property> <property> <name>yarn.scheduler.capacity.root.parent1.leaf-queue-template.maximum-capacity</name> <value>100</value> </property> <property> <name>yarn.scheduler.capacity.root.parent1.leaf-queue-template.user-limit-factor</name> <value>3.0</value> </property> <property> <name>yarn.scheduler.capacity.root.parent1.leaf-queue-template.ordering-policy</name> <value>fair</value> </property> <property> <name>yarn.scheduler.capacity.root.parent1.GPU.capacity</name> <value>50</value> </property> <property> <name>yarn.scheduler.capacity.root.parent1.accessible-node-labels</name> <value>GPU,SSD</value> </property> <property> <name>yarn.scheduler.capacity.root.parent1.leaf-queue-template.accessible-node-labels</name> <value>GPU</value> </property> <property> <name>yarn.scheduler.capacity.root.parent1.leaf-queue-template.accessible-node-labels.GPU.capacity</name> <value>5</value> </property>
Admins need to specify an additional org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.QueueManagementDynamicEditPolicy scheduling edit policy to the list of current scheduling edit policies as a comma separated string in yarn.resourcemanager.scheduler.monitor.policies configuration. For more details, refer Capacity Scheduler container preemption section above
| Property | Description |
|---|---|
| yarn.resourcemanager.monitor.capacity.queue-management.monitoring-interval | Time in milliseconds between invocations of this QueueManagementDynamicEditPolicy policy. Default value is 1500 |
| Property | Description |
|---|---|
| yarn.scheduler.capacity.resource-calculator | The ResourceCalculator implementation to be used to compare Resources in the scheduler. The default i.e. org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator only uses Memory while DominantResourceCalculator uses Dominant-resource to compare multi-dimensional resources such as Memory, CPU etc. A Java ResourceCalculator class name is expected. |
Capacity Scheduler leverages Delay Scheduling to honor task locality constraints. There are 3 levels of locality constraint: node-local, rack-local and off-switch. The scheduler counts the number of missed opportunities when the locality cannot be satisfied, and waits this count to reach a threshold before relaxing the locality constraint to next level. The threshold can be configured in following properties:
| Property | Description |
|---|---|
| yarn.scheduler.capacity.node-locality-delay | Number of missed scheduling opportunities after which the CapacityScheduler attempts to schedule rack-local containers. Typically, this should be set to number of nodes in the cluster. By default is setting approximately number of nodes in one rack which is 40. Positive integer value is expected. |
| yarn.scheduler.capacity.rack-locality-additional-delay | Number of additional missed scheduling opportunities over the node-locality-delay ones, after which the CapacityScheduler attempts to schedule off-switch containers. By default this value is set to -1, in this case, the number of missed opportunities for assigning off-switch containers is calculated based on the formula L * C / N, where L is number of locations (nodes or racks) specified in the resource request, C is the number of requested containers, and N is the size of the cluster. |
Note, this feature should be disabled if YARN is deployed separately with the file system, as locality is meaningless. This can be done by setting yarn.scheduler.capacity.node-locality-delay to -1, in this case, request’s locality constraint is ignored.
The CapacityScheduler supports the following parameters to control how many containers can be allocated in each NodeManager heartbeat. These parameters are refreshable via yarn rmadmin -refreshQueues.
| Property | Description |
|---|---|
| yarn.scheduler.capacity.per-node-heartbeat.multiple-assignments-enabled | Whether to allow multiple container assignments in one NodeManager heartbeat. Defaults to true. |
| yarn.scheduler.capacity.per-node-heartbeat.maximum-container-assignments | If multiple-assignments-enabled is true, the maximum amount of containers that can be assigned in one NodeManager heartbeat. Default value is 100, which limits the maximum number of container assignments per heartbeat to 100. Set this value to -1 will disable this limit. |
| yarn.scheduler.capacity.per-node-heartbeat.maximum-offswitch-assignments | If multiple-assignments-enabled is true, the maximum amount of off-switch containers that can be assigned in one NodeManager heartbeat. Defaults to 1, which represents only one off-switch allocation allowed in one heartbeat. |
Once the installation and configuration is completed, you can review it after starting the YARN cluster from the web-ui.
Start the YARN cluster in the normal manner.
Open the ResourceManager web UI.
The /scheduler web-page should show the resource usages of individual queues.
Changing queue/scheduler properties and adding/removing queues can be done in two ways, via file or via API. This behavior can be changed via yarn.scheduler.configuration.store.class in yarn-site.xml. Possible values are file, which allows modifying properties via file; memory, which allows modifying properties via API, but does not persist changes across restart; leveldb, which allows modifying properties via API and stores changes in leveldb backing store; and zk, which allows modifying properties via API and stores changes in zookeeper backing store. The default value is file.
To edit by file, you need to edit conf/capacity-scheduler.xml and run yarn rmadmin -refreshQueues.
$ vi $HADOOP_CONF_DIR/capacity-scheduler.xml $ $HADOOP_YARN_HOME/bin/yarn rmadmin -refreshQueues
Step 1: Stop the queue
Before deleting a leaf queue, the leaf queue should not have any running/pending apps and has to BE STOPPED by changing yarn.scheduler.capacity.<queue-path>.state. See the [Queue Administration & Permissions](CapacityScheduler.html#Queue Properties) section. Before deleting a parent queue, all its child queues should not have any running/pending apps and have to BE STOPPED. The parent queue also needs to be STOPPED
Step 2: Delete the queue
Remove the queue configurations from the file and run refresh as described above
Editing by API uses a backing store for the scheduler configuration. To enable this, the following parameters can be configured in yarn-site.xml.
Note: This feature is in alpha phase and is subject to change.
| Property | Description |
|---|---|
| yarn.scheduler.configuration.store.class | The type of backing store to use, as described above. |
| yarn.scheduler.configuration.mutation.acl-policy.class | An ACL policy can be configured to restrict which users can modify which queues. Default value is org.apache.hadoop.yarn.server.resourcemanager.scheduler.DefaultConfigurationMutationACLPolicy, which only allows YARN admins to make any configuration modifications. Another value is org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.conf.QueueAdminConfigurationMutationACLPolicy, which only allows queue modifications if the caller is an admin of the queue. |
| yarn.scheduler.configuration.store.max-logs | Configuration changes are audit logged in the backing store, if using leveldb or zookeeper. This configuration controls the maximum number of audit logs to store, dropping the oldest logs when exceeded. Default is 1000. |
| yarn.scheduler.configuration.leveldb-store.path | The storage path of the configuration store when using leveldb. Default value is ${hadoop.tmp.dir}/yarn/system/confstore. |
| yarn.scheduler.configuration.leveldb-store.compaction-interval-secs | The interval for compacting the configuration store in seconds, when using leveldb. Default value is 86400, or one day. |
| yarn.scheduler.configuration.zk-store.parent-path | The zookeeper root node path for configuration store related information, when using zookeeper. Default value is /confstore. |
Note: When enabling scheduler configuration mutations via yarn.scheduler.configuration.store.class, yarn rmadmin -refreshQueues will be disabled, i.e. it will no longer be possible to update configuration via file.
See the YARN Resource Manager REST API for examples on how to change scheduler configuration via REST, and YARN Commands Reference for examples on how to change scheduler configuration via command line.
Once an Application Master has received a Container from the Resource Manager, it may request the Resource Manager to update certain attributes of the container.
Currently only two types of container updates are supported:
This is facilitated by the AM populating the updated_containers field, which is a list of type UpdateContainerRequestProto, in AllocateRequestProto. The AM can make multiple container update requests in the same allocate call.
The schema of the UpdateContainerRequestProto is as follows:
message UpdateContainerRequestProto { required int32 container_version = 1; required ContainerIdProto container_id = 2; required ContainerUpdateTypeProto update_type = 3; optional ResourceProto capability = 4; optional ExecutionTypeProto execution_type = 5; }
The ContainerUpdateTypeProto is an enum:
enum ContainerUpdateTypeProto { INCREASE_RESOURCE = 0; DECREASE_RESOURCE = 1; PROMOTE_EXECUTION_TYPE = 2; DEMOTE_EXECUTION_TYPE = 3; }
As constrained by the above enum, the scheduler currently supports changing either the resource update OR executionType of a container in one update request.
The AM must also provide the latest ContainerProto it received from the RM. This is the container which the RM will attempt to update.
If the RM is able to update the requested container, the updated container will be returned, in the updated_containers list field of type UpdatedContainerProto in the AllocateResponseProto return value of either the same allocate call or in one of the subsequent calls.
The schema of the UpdatedContainerProto is as follows:
message UpdatedContainerProto { required ContainerUpdateTypeProto update_type = 1; required ContainerProto container = 2; }
It specifies the type of container update that was performed on the Container and the updated Container object which container an updated token.
The container token can then be used by the AM to ask the corresponding NM to either start the container, if the container has not already been started or update the container using the updated token.
The DECREASE_RESOURCE and DEMOTE_EXECUTION_TYPE container updates are automatic - the AM does not explicitly have to ask the NM to decrease the resources of the container. The other update types require the AM to explicitly ask the NM to update the container.
If the yarn.resourcemanager.auto-update.containers configuration parameter is set to true (false by default), The RM will ensure that all container updates are automatic.
Scheduling activities are activity messages used for debugging on some critical scheduling path, they can be recorded and exposed via RESTful API with minor impact on the scheduler performance. Currently, there are two types of activities supported: scheduler activities and application activities.
Scheduler activities include useful scheduling info in a scheduling cycle, which illustrate how the scheduler allocates a container. Scheduler activities REST API (http://rm-http-address:port/ws/v1/cluster/scheduler/activities) provides a way to enable recording scheduler activities and fetch them from cache. To eliminate the performance impact, scheduler automatically disables recording activities at the end of a scheduling cycle, you can query the RESTful API again to get the latest scheduler activities.
See the YARN Resource Manager REST API for query parameters, output structure and examples about scheduler activities.
Application activities include useful scheduling info for a specified application, which illustrate how the requirements are satisfied or just skipped. Application activities REST API (http://rm-http-address:port/ws/v1/cluster/scheduler/app-activities/{appid}) provides a way to enable recording application activities for a specified application within a few seconds or fetch historical application activities from cache, available actions which include “refresh” and “get” can be specified by the “actions” parameter:
See the YARN Resource Manager REST API for query parameters, output structure and examples about application activities.
The CapacityScheduler supports the following parameters to control the cache size and the expiration of scheduler/application activities.
| Property | Description |
|---|---|
| yarn.resourcemanager.activities-manager.cleanup-interval-ms | The cleanup interval for activities in milliseconds. Defaults to 5000. |
| yarn.resourcemanager.activities-manager.scheduler-activities.ttl-ms | Time to live for scheduler activities in milliseconds. Defaults to 600000. |
| yarn.resourcemanager.activities-manager.app-activities.ttl-ms | Time to live for application activities in milliseconds. Defaults to 600000. |
| yarn.resourcemanager.activities-manager.app-activities.max-queue-length | Max queue length for app activities. Defaults to 100. |


|
| void | printHelp () const |
| | Prints out 'help' for the user. More...
|
| |
| void | run () |
| | Runs the shell in a loop. More...
|
| |
| std::vector< std::string > | split (const std::string &str, char separator) |
| | Splits the string given as a parameter by the character given as a second parameter. More...
|
| |
| CMD | getCommand (std::vector< std::string > tokens) |
| | Returns a command enumeration. More...
|
| |
| void | loadFileToExecute (std::string path) |
| | Reads the file on the HDD containing commands and executes them right away. More...
|
| |
| bool | executeCommand (std::string input) |
| | Executes a single command.  More...
|
| |
| bool | validRMDIR (const std::vector< std::string > &tokens) |
| | Tests if the line entered by the user is a valid command RMDIR.  More...
|
| |
| bool | validLOAD (const std::vector< std::string > &tokens) |
| | Tests if the line entered by the user is a valid command LOAD. More...
|
| |
| bool | validFORMAT (const std::vector< std::string > &tokens) |
| | Tests if the line entered by the user is a valid command FORMAT. More...
|
| |
| bool | validEXIT (const std::vector< std::string > &tokens) |
| | Tests if the line entered by the user is a valid command EXIT. More...
|
| |
| bool | validHELP (const std::vector< std::string > &tokens) |
| | Tests if the line entered by the user is a valid command HELP. More...
|
| |
| bool | validSLINK (const std::vector< std::string > &tokens) |
| | Tests if the line entered by the user is a valid command SLINK. More...
|
| |
| bool | containsOnlyDigits (std::string str) |
| | Tests if the string given as a parameter is consist of digits only. More...
|
| |
- Author
- A127B0362P silhavyj
Shell the user uses to interact with the file system (commands etc.).
This class represents a shell for the user to interact with the system. All the functionality was implemented as mentioned in the document available on courseware. The class also checks the syntax of the commands the user types when interacting with the system. If a command does not match any pre-defined pattern, the user will be informed via a message in the terminal.
| Shell::Shell |
( |
int |
argc, |
|
|
char * |
argv[] |
|
) |
| |
Constructor of the class - creates an instance of it.
This constructor takes two parameters passed on from the the header of the main method. As one of the requirements, the user is supposed to run the program with one parameter only, which is the name of the file system (e.g. data.dat). If the user doesn't do so, an alert message will be thrown and the program closed.
- Parameters
-
| argc | number of arguments (argument count) |
| argv | arguments themselves (argument values) |
| Shell::CMD Shell::getCommand |
( |
std::vector< std::string > |
tokens | ) |
|
|
private |
Returns a command enumeration.
This method analyzes the tokens given as a parameter. The first token (position 0) is meant to be the shortcut of the command e.g. 'cp'. the rest of the tokens is the arguments the user typed down along with this command, so as a whole, it may look like ['cp','file.txt','file2.txt']. The method will check if the whole command is syntactically correct. If it all seems to be okay, it will return the enumeration of the appropriate command. Otherwise, depending on the situation, it will return either UNKNOWN or INVALID.
- Parameters
-
| tokens | command the user entered split up into separate tokens |
- Returns
- appropriate command enumeration including both UNKNOWN and INVALID
| bool validCAT |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command CAT.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.
| bool validCD |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command CD.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.
| bool validCP |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command CP.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.
| bool validEXIT |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command EXIT.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.
| bool validFORMAT |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command FORMAT.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.
| bool validHELP |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command HELP.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.
| bool validINCP |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command INCP.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.
| bool validINFO |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command INFO.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.
| bool validLOAD |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command LOAD.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.
| bool validLS |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command LS.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.
| bool validMKDIR |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command MKDIR.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.
| bool validMV |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command MV.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.
| bool validOUTCP |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command OUTCP.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.
| bool validPWD |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command PWD.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.
| bool validRM |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command RM.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.
| bool validRMDIR |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command RMDIR.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.
| bool validSLINK |
( |
const std::vector< std::string > & |
tokens | ) |
|
|
friend |
Tests if the line entered by the user is a valid command SLINK.
That includes testing such as number of parameters, values of the parameters, etc. It does not check if the file, for example, exists though. It will be taken care of later in a different part of the program - this is all about syntax.
- Parameters
-
| tokens | command split up into individual tokens |
- Returns
- true, if the command if valid. False otherwise.


I am a responsive designer & developer who thrives on creating websites that are functional and have beautiful form. When I'm not working on websites, I can be found dancing, hiking, drawing, painting, sewing and beading.
I was born and raised in Philadelphia, PA by second generation immigrants from Norway. I developed most of my sensibilities and interests from this heritage. I have no idea why I identify more closely with my Norwegian culture than that of my Irish and German cultures.
My current passion is dance. I've learned bellydance from a broad range of cultures including Egyptian, North African, Turkish, Greek and Lebanese. It's hard to say, but my fav so far is Turkish Romany with Lebanese Debke as a close second. I sort of like Norwegian folk dance, but it's not as spicy as the other folk dances mentioned to the left.
Fun fact: I used to eat a box of crackers per day because they're salty and delicious. But after becoming more serious about the energy it takes to dance 2 hrs/day, I cut out that daily habit cold turkey.


Tags are representations of strings and other objects associated with an item. Tags can act as keywords for an object to help identify its elements; or, as search filters to help users locate specific items within an application. Icon buttons can be nested in a tag to increase the tag's functionality.
Show an association between the information of a tag and the component it is tied to.
Tags are a prevalent component used throughout applications. They can be found tied to search inputs as filters, within email messages as recipients, at the bottom of a product page as item identifiers and many other places. Nest tags within components that will benefit from having a visual representation of keywords available to the user.
As display width becomes smaller tags will begin to row wrap to fit more comfortably on the screen. If the screen width is smaller than the tag then the tag will decrease its width down to a minimum width. When a screen reduces a tag's width, the text inside is also reduced and ellipses are added to the end of the text.


|
| struct | boost::geometry::strategy::transform::copy_direct< P > |
| | Transformation strategy to copy one point to another using assignment operator. More...
|
| |
| struct | boost::geometry::strategy::transform::copy_per_coordinate< P1, P2 > |
| | Transformation strategy to do copy a point, copying per coordinate. More...
|
| |
| struct | boost::geometry::strategy::transform::degree_radian_vv< P1, P2, F > |
| | Transformation strategy to go from degree to radian and back. More...
|
| |
| struct | boost::geometry::strategy::transform::from_cartesian_3_to_spherical_polar_2< P1, P2 > |
| | Transformation strategy for 3D cartesian (x,y,z) to 2D spherical (phi,theta) More...
|
| |
| struct | boost::geometry::strategy::transform::from_cartesian_3_to_spherical_polar_3< P1, P2 > |
| | Transformation strategy for 3D cartesian (x,y,z) to 3D spherical (phi,theta,r) More...
|
| |
| struct | boost::geometry::strategy::transform::from_spherical_polar_2_to_cartesian_3< P1, P2 > |
| | Transformation strategy for 2D spherical (phi,theta) to 3D cartesian (x,y,z) More...
|
| |
| struct | boost::geometry::strategy::transform::from_spherical_polar_3_to_cartesian_3< P1, P2 > |
| | Transformation strategy for 3D spherical (phi,theta,r) to 3D cartesian (x,y,z) More...
|
| |
| struct | boost::geometry::strategy::transform::services::default_strategy< CoordinateSystemTag1, CoordinateSystemTag2, CoordinateSystem1, CoordinateSystem2, Dimension1, Dimension2, Point1, Point2 > |
| | Traits class binding a transformation strategy to a coordinate system. More...
|
| |


Oops it looks like all slots are not filled. You need 6 players to play a game of Tower Storm. Try adding bots to the game to fill the empty slots.


--- layout: page title: Fábio Schmidt description: "Personal web page, blog and promoter projects!" --- {% assign s = site.social %}
Fábio Schmidt
Hi! I'm a Software Developer and Entrepreneur in Planet Earth.


Nabil Sutjipto
Nabil started his deep dive into tech back in high school where he would do house calls to help setup and teach seniors on computers in a small town in Texas. It was from there that he wanted to know more about how software and decide to pursue CS engineering from the University of Washington in Seattle. Following his passion for travel, he then spent 5 years working as an engineer with a major travel company in Seattle. He currently focuses on web-based technology, focusing on scalability and automation.
As he moves around from country to country, he currently now resides in Indonesia hoping to be able to explore the country via his motorcycle.


Continuous Integration
Continuous Integration (CI) is the process of automating the build and testing of
code every time a team member commits changes to version control.
CD
Current suite
- Github
- Codeship
- DockerHub
- Ansible
Flow
Problems
- Time (testing, building images)
- Manual deployment
Gitlab Runners
CI with gitlab
- Docker in Docker
- View an example of gitlab_ci file
Gitlab Pipelines
How to manage the credentials
Runners ENV variables


| Class and Description |
|---|
| Types.ExecMode
Execution mode for entire script.
|
| Class and Description |
|---|
| Types.FileFormat |
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.ExecMode
Execution mode for entire script.
|
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Builtins
Enum to represent all builtin functions in the default name space.
|
| Types.AggOp |
| Types.BlockType
Serialization block types (empty, dense, sparse, ultra-sparse)
|
| Types.CorrectionLocationType |
| Types.DataType
Data types (tensor, matrix, scalar, frame, object, unknown).
|
| Types.Direction
Type of aggregation direction
|
| Types.ExecMode
Execution mode for entire script.
|
| Types.ExecType
Execution type of individual operations.
|
| Types.FileFormat |
| Types.FunctionBlock
Common type for both function statement blocks and function program blocks
|
| Types.OpOp1 |
| Types.OpOp2 |
| Types.OpOp3 |
| Types.OpOp4 |
| Types.OpOpData |
| Types.OpOpDG |
| Types.OpOpDnn |
| Types.OpOpN |
| Types.ParamBuiltinOp |
| Types.ReOrgOp |
| Types.ReturnType
Type of builtin or user-defined function with regard to its
number of return variables.
|
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.AggOp |
| Types.DataType
Data types (tensor, matrix, scalar, frame, object, unknown).
|
| Types.Direction
Type of aggregation direction
|
| Types.ExecMode
Execution mode for entire script.
|
| Types.FileFormat |
| Types.OpOp1 |
| Types.OpOp2 |
| Types.OpOp3 |
| Types.OpOp4 |
| Types.OpOpData |
| Types.OpOpDG |
| Types.OpOpDnn |
| Types.OpOpN |
| Types.ParamBuiltinOp |
| Types.ReOrgOp |
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.DataType
Data types (tensor, matrix, scalar, frame, object, unknown).
|
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.AggOp |
| Types.DataType
Data types (tensor, matrix, scalar, frame, object, unknown).
|
| Class and Description |
|---|
| Types.AggOp |
| Class and Description |
|---|
| Types.AggOp |
| Types.DataType
Data types (tensor, matrix, scalar, frame, object, unknown).
|
| Types.Direction
Type of aggregation direction
|
| Types.OpOp1 |
| Types.OpOp2 |
| Types.OpOp3 |
| Types.OpOpData |
| Types.OpOpDG |
| Types.OpOpDnn |
| Types.OpOpN |
| Types.ParamBuiltinOp |
| Types.ReOrgOp |
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.AggOp |
| Types.CorrectionLocationType |
| Types.DataType
Data types (tensor, matrix, scalar, frame, object, unknown).
|
| Types.Direction
Type of aggregation direction
|
| Types.FileFormat |
| Types.OpOp1 |
| Types.OpOp2 |
| Types.OpOp3 |
| Types.OpOpData |
| Types.OpOpDG |
| Types.OpOpDnn |
| Types.OpOpN |
| Types.ParamBuiltinOp |
| Types.ReOrgOp |
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.DataType
Data types (tensor, matrix, scalar, frame, object, unknown).
|
| Class and Description |
|---|
| Builtins
Enum to represent all builtin functions in the default name space.
|
| Types.DataType
Data types (tensor, matrix, scalar, frame, object, unknown).
|
| Types.FileFormat |
| Types.FunctionBlock
Common type for both function statement blocks and function program blocks
|
| Types.ParamBuiltinOp |
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.FunctionBlock
Common type for both function statement blocks and function program blocks
|
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.FileFormat |
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.DataType
Data types (tensor, matrix, scalar, frame, object, unknown).
|
| Class and Description |
|---|
| Types.FileFormat |
| Class and Description |
|---|
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.AggOp |
| Types.CorrectionLocationType |
| Types.Direction
Type of aggregation direction
|
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.DataType
Data types (tensor, matrix, scalar, frame, object, unknown).
|
| Types.OpOpDG |
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.DataType
Data types (tensor, matrix, scalar, frame, object, unknown).
|
| Types.FileFormat |
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.DataType
Data types (tensor, matrix, scalar, frame, object, unknown).
|
| Class and Description |
|---|
| Types.CorrectionLocationType |
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.CorrectionLocationType |
| Types.OpOp2 |
| Class and Description |
|---|
| Types.FileFormat |
| Class and Description |
|---|
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
| Class and Description |
|---|
| Types.DataType
Data types (tensor, matrix, scalar, frame, object, unknown).
|
| Types.FileFormat |
| Types.ValueType
Value types (int, double, string, boolean, unknown).
|
Copyright © 2021 The Apache Software Foundation. All rights reserved.